Observability data that stays
where you put it.
Data residency rules, a sovereignty policy, or a customer contract that says "EU only": Ultraviolet keeps telemetry in the region and account you choose, because it runs there — not with a vendor.
The problem
Telemetry is full of personal data: user IDs in logs, IP addresses in traffic, what people did in your app. Where it's stored matters — to regulators, to your data protection team, and increasingly to the customers whose contracts say where their data may go.
Most observability products answer with a regional site: your data stays in the EU, in the vendor's cloud. That moves the data, not the question — it's still held by a third party, under its agreements, in its infrastructure.
Ultraviolet doesn't hold your data at all. It runs in your own environment, in whichever region you install it, and stores everything there.
Where each kind of data goes
Traces, logs, metrics, profiles
Stored by the core, on disks in the cluster and region you install it in.
Browser sessions
Your users' browsers send real user monitoring data to your own gateway — not to a vendor's endpoint — masked by default.
Remote sites
A site sends its telemetry to the core it is connected to. Put that core in the region the data has to stay in — or run a core per region.
AI investigation
Runs on a model you choose: one you host in the same region, a hosted model in a region you pick — or none at all.
Questions teams ask
- Many vendors have an EU region. What is the difference?
- An EU region keeps your data in the EU — with the vendor. With Ultraviolet, it stays in your own environment: your account, your cluster, your disks. There is no vendor holding a copy, so there is no vendor to assess, contract with, or rely on for where it lives.
- Does anything leave our environment?
- Not your telemetry. The optional connected mode, for automatic license renewal, sends license usage metadata only — license, customer, node counts. Turn it off and nothing is sent at all; licenses then renew as a signed file.
- How long is data kept?
- As long as you set, per type — traces, logs and metrics each have their own retention, and data older than that is removed automatically. That lets the platform follow a retention policy rather than a vendor plan.
- Can we delete one person’s data on request?
- Not with a dedicated tool yet. Retention removes data automatically as it ages, real user monitoring masks text and input by default, and log pipeline rules can keep personal fields from being stored in the first place.
- Does this make us GDPR compliant?
- Compliance is decided by your data protection team, for your organisation. What changes is the scope: observability data stays inside infrastructure you already control and document, rather than becoming another transfer to a processor.
Related
Keeping regulated data out of your telemetry vendor covers what Ultraviolet avoids collecting in the first place — database values, request bodies, form input, prompts. For networks with no internet access at all, see air-gapped Kubernetes monitoring.
Explore the live demo, or talk to us about an evaluation in your own region — no data leaves it during the trial either.
Run it in your own cluster this week.
A 30-minute call, then an evaluation core on your infrastructure. You will see your own services, traces and logs — from your own traffic — before you decide anything.
- No data leaves your environment, including during the trial
- Helm install, works fully air-gapped
- You talk to the engineers who built it