Skip to content

Digital sovereignty

Monitoring data hosted in France.

Mihari is built in France as a European platform. Your monitoring data — logs, metrics, traces, and uptime history — is hosted and stored on French infrastructure.

Where Mihari hosts your monitoring data
What Where Operated by
Application servers France OVHcloud
Databases France OVHcloud
Backups France OVHcloud
Logs, metrics and traces France OVHcloud
Uptime history France OVHcloud
Our hosting does not run on AWS, Google Cloud or Azure.
Hosted in France, on OVHcloud
100%
US hyperscaler for hosting
0
Compliant by design
GDPR
Available on request
DPA

Why it matters

Digital sovereignty is not optional anymore.

In an era where data flows across borders freely, businesses need to know exactly where their data resides and who can access it. Relying on non-European cloud providers means your data may be subject to foreign laws and surveillance programs.

Choosing a European platform is not just about compliance — it’s about maintaining control over your most valuable asset: your data. Mihari was founded with the conviction that European businesses deserve infrastructure that respects their sovereignty.

  • Data control

    Know exactly where your data is stored and who can access it at all times.

  • Legal certainty

    Your monitoring data is stored under European jurisdiction — French servers, a French company, EU law.

  • Independence

    Hosting on European providers — access to your data never hinges on a US hyperscaler's terms.

  • Trust

    Build trust with your customers by choosing a platform that values privacy.

Our commitment

Four pillars of sovereignty.

Our philosophy is clear: your monitoring data belongs on European infrastructure. Here’s how we put that into practice.

  • 100% French hosting

    All application servers, databases, and backups run in French data centers, operated by OVHcloud. Complete territorial control over where your monitoring data lives.

  • Monitoring data stored in France

    Your telemetry data, logs, metrics, and monitoring results are stored on French infrastructure — primary data and backups alike. The few external providers a feature may rely on are documented in our sub-processor list, available on request.

  • French company, European rules

    Mihari is a French business, built and operated in France. It is accountable to European regulations and to its European customers.

  • No US hyperscaler for hosting

    Our hosting does not run on AWS, Google Cloud, or Azure. This is a deliberate architectural decision: your hosted monitoring data does not depend on a US hyperscaler's terms, pricing, or jurisdiction.

Cloud inventory

Mihari holds no cloud credentials in the default path.

The Infrastructure section maps your AWS accounts and Kubernetes clusters, and it does so without ever being given a key. Discovery runs on your compute, under your identity: a collector you deploy, holding a read-only role or ClusterRole you created in your own account, reading its own account or cluster. It signs each inventory with an Ed25519 key that never leaves your side and pushes the result to Mihari.

Mihari stores what arrives. It never calls a cloud API on your behalf, and there is no outbound connection from our infrastructure into yours. A new agent key is pinned the first time it is seen and the source stays pending until an owner or admin confirms its fingerprint — so an ingest token on its own, even a leaked one, cannot forge topology.

One setting can cross the boundary, and it starts off

Mihari’s AI SRE can read the cloud map during an investigation, and its answers are produced by a model provider behind our AI gateway — which is outside the EU hosting boundary. That is a real transfer, so it is a deliberate, recorded decision rather than a default:

  • Off by default, on every plan and every deployment. It has never been on for anyone who did not turn it on.
  • It is an organisation-wide setting, not a per-user one, and only an owner or an admin can change it.
  • Every flip is recorded on the organisation with who changed it and when, and the page shows that line back to you.
  • It is a Platform feature: on the Free plan the toggle has no effect, because the AI SRE has no cloud tools there.
  • All three conditions must hold — the section enabled, the plan, and the setting — or the tools do not exist for that workspace.

Exactly what leaves, when it is on

Each cloud tool the AI SRE calls produces a short text answer, and that answer is what is sent to the model provider — nothing else from the section is transmitted.

  • Topology, as it stood at the time of the investigation

    Resource names, kinds, providers, regions, accounts and zones; how they contain and reach each other; the monitors and security findings linked to them; and what changed inside the incident window.

  • Identifiers are withheld by default

    Native ids and ARNs, private and public IP addresses, DNS names and the values of your tags are left out of every answer unless the model explicitly asks for them for a specific lookup.

  • Every answer is bounded

    A single tool answer is capped at 6,000 characters, so an investigation cannot quietly stream an estate out one call at a time.

  • An investigation records what it sent

    When the AI SRE investigates an incident on its own, it writes one line to our logs naming which tool sent which resources and how many bytes went to the model — so "what left?" has an answer after the fact, not just a policy before it.

Turn the setting off and the cloud tools are not offered to the model at all: a tool call that arrives anyway is refused rather than answered. The rest of the Infrastructure section — the map, the history, the overlays, the exports — is unaffected and stays on French infrastructure. How the Infrastructure section works

Compliance & trust

Built for European regulations.

  • GDPR compliant by design

    Built with privacy-by-design principles. Data minimization, purpose limitation, and strong access controls are embedded in our architecture.

  • Data residency

    Your monitoring data is stored in France on OVHcloud infrastructure. A Data Processing Agreement (DPA) is available on request.

  • Documented sub-processors

    A short, documented list of sub-processors — available on request, with no hidden vendors. You know exactly who touches what.

  • Transparent data practices

    Clear documentation of what data we collect, how we process it, and how long we retain it. No hidden practices.

Questions about where your data lives.

Where is my monitoring data hosted?
In France, on OVHcloud. All application servers, databases and backups run in French data centers operated by OVHcloud, and your logs, metrics, traces and uptime history are stored there, primary data and backups alike.
Does Mihari run on AWS, Google Cloud or Azure?
No. Our hosting does not run on AWS, Google Cloud, or Azure. This is a deliberate architectural decision: your hosted monitoring data does not depend on a US hyperscaler's terms, pricing, or jurisdiction.
Does any provider outside France process my data?
The few external providers a feature may rely on are documented in our sub-processor list, available on request. One is described on this page: the AI SRE's answers are produced by a model provider outside the EU hosting boundary, which is why sharing your cloud inventory with it is a setting that starts off.
Can I sign a Data Processing Agreement?
Yes. A Data Processing Agreement (DPA) is available on request.
Who operates Mihari?
Mihari is a French business, built and operated in France. It is accountable to European regulations and to its European customers.

Ready to take control of your data?

Choose an observability platform that respects your sovereignty. Hosted in France, built for Europe.