This matters mostly if you have ever been quoted a price for the privilege of keeping your own logs.
Most security data problems in the European mid-market are not detection problems. They are storage problems in a detection costume.
Telemetry gets filtered, sampled, or never onboarded at all, because the platform that would analyze it charges by the gigabyte. The coverage gap that follows is invisible right up until somebody needs the logs, at which point it is the only thing anyone can see.
Vega takes the other route. The data stays in the customer's own object storage and the analytics run against it where it sits.
On top of that sits the part people demo: investigation in plain language that returns re-runnable queries with cited evidence, coverage assessment against MITRE ATT&CK and NIST, chain reasoning, and agentic triage that hands you a structured case instead of an alert to open. Hunts save as reusable skills. A workflow that turns out to be deterministic gets promoted to a rule. It is headless by API and MCP, and it is SaaS only, so we do not offer it on-premises or in your own cloud.
Vega reports triage falling from 25 minutes to under 8, false positives down about 35 percent, and roughly four times the data for similar spend. Those are their figures, not ours. Our first assessment on a live customer is where we get to measure them ourselves, and we will publish what we find either way.
Or see it for yourself first. On Friday 30 October, Vega and Revolgy run the same investigation twice, with a timer on screen: once the usual way, once in Vega.
This is the part that made the partnership worth doing rather than just worth watching.
Insurance questionnaires and regulatory conversations both ask for a service with a named accountable party behind it. Not a tool that was available. A person who is answerable for whether the control was continuously maintained. No platform can be that, which is the gap we are built to stand in.
European cloud-native mid-market. Companies between 150 and 2,000 employees running on Google Cloud, with a security team somewhere between zero and ten people, no round-the-clock cover, and one compliance obligation that has a date attached to it. Financial technology, SaaS and marketplaces, mostly.
If you are larger than that and already running a SIEM you are unhappy with, the displacement conversation is a different one, and we will have it. If you are smaller than that, the honest answer is that one conversation will tell you quickly whether any of this is worth your time.
Either way, the first useful step is the same: 30 minutes with one of our experts. Bring your daily volume, and we will tell you what is currently dark and whether your estate can land in object storage at all. Whatever you decide afterward, you will know a number you did not know before.
Platform performance figures are Vega's own, measured on their platform, and are reproduced here as theirs. Service stages and pricing shapes are Revolgy's.