Security and data residency

    Your data stays in your own environment. Every connection is on a list.

    Datahub runs in a separate, shielded environment per customer: in your own Azure subscription or as single-tenant SaaS in the EU. Coming in goes through one secured door, going out only through connections you approve.

    Your environmentDataKeysAppsUsersSources
    • ISO 27001:2022
    • GDPR compliant
    • Single-tenant
    • EU or your own Azure
    • Sub-processors: Microsoft and Cloudflare
    Where it runs

    Your own environment, not shared with other customers.

    Every customer gets their own environment with its own network, with no link to other customers. The database, key vault, apps and AI index sit together inside it.

    In your own Azure
    Datahub runs in your own Azure subscription, in the region you choose.
    Hosted by Datahub
    Single-tenant SaaS in the EU: the same separation, without managing Azure yourself.
    You

    Your own plot, without bridges to the neighbours.

    In and out

    Everything that comes in or goes out follows a fixed route.

    Traffic is encrypted everywhere, between internal services too. Stored data is encrypted and can be managed with your own key in Azure Key Vault.

    Microsoft 365DatabricksOne door inOne gate out

    One door in, one gate out

    Users come in through Cloudflare, with a web firewall, DDoS protection and access rules. Only traffic to services you configure goes out, through one fixed IP address. Addresses in your own network are refused by default, and storage is connected per connection through Azure Private Link.

    AdminSupportAppsSupport only with a role you grant

    No standing access to your data

    Datahub has no standing access to your data. Support can only reach it with an Azure role you assign and withdraw. The API has no public Azure endpoint, the database is closed to public networks and the key vault refuses by default.

    Connections and AI

    What is not allowed does not happen.

    Systems, webhooks and AI assistants only get access that was set in advance. That keeps the use of Copilot, Claude or ChatGPT on your company data within the lines as well.

    ConnectionStatusMicrosoft 365Databricksdbt CloudOrders webhookUnknown addressallowedallowedallowedallowedrefusedsha-256 · 9f3a…c41eApproved by IT

    Every connection is on the list

    Every connection runs through one gate that refuses by default. Credentials only leave the key vault once the gate allows a request. IT signs off the configuration, and every decision, allowed or refused, is logged with its reason.

    Newly connectedWith a policyin use

    AI assistants within your limits

    Connecting AI assistants is off by default. A newly connected assistant can do nothing until a policy is bound to it, and never more than the user's role allows. Revoking access takes effect at once.

    For your security team

    Insight into everything that happens.

    • Audit

      Everything logged

      Every decision on a tool or connection is in the log: who, which app, which tool, allowed or refused, the reason and the declared purpose.

    • Monitoring

      Into your own security tools

      Agent activity streams to your security team's collector over OpenTelemetry. Metadata only, never data rows, prompts or arguments.

    • Backups

      Automatic, audit log included

      Backups run automatically. Audit log backups can be automated to any storage you use.

    • Availability

      On Azure's standard

      Datahub runs on Azure services with Microsoft's standard availability of 99.9%.

    Frequently asked questions

    What IT and procurement ask.

    Next step

    Bring your security questions.

    In a technical session your requirements are walked through, from network to audit.