Security

We never hold your keys. Or your data.

Datris is fully self-hosted. It never processes, stores, or transmits your data, there is no managed service, and there are no subprocessors. The rest of this page answers a security questionnaire in the order the questionnaire asks.

Request the security packet Read the source

Deployment model

Datris runs inside your perimeter: on-prem, in your cloud account, or on a laptop. Every byte of customer data stays on infrastructure you operate. Datris.ai the company has no access path to a deployment, no support tunnel, and no hosted control plane. Most SOC 2 controls about data handling do not apply because no customer data reaches us.

Credentials

  • HashiCorp Vault brokers every credential. Source and destination secrets are stored in Vault and delivered to the tap at run time. They are never written into agent configs, prompts, or chat history.
  • The agent never holds a key. An agent asks Datris to use a secret by name. It never sees the value.
  • Scoped API keys. Each agent gets its own API key with an explicit capability bundle, and the MCP tool catalog it sees is filtered to match.

Isolation

  • Tap scripts, including agent-generated ones, run in a sidecar container with no platform credentials inside.
  • Private egress from the sidecar is blocked by default.
  • Secrets are masked in logs.
Agent MCP server Agent Policy Vault Tap sidecar Destination

Every request follows this path. Policy is evaluated before Vault is consulted, and the sidecar receives only the credential the run needs.

Governance

  • Agent Policy. Per-action allow, approve, or refuse, enforced by the platform, not by a prompt.
  • Audit log. Every create, change, run, delete, login, and denied request, attributed to a login or API key. CSV export and SIEM mirroring.
  • Provenance. Every landed row is traceable to the pipeline, run, script commit, and source.
  • Lineage. Where data came from and where it went, per pipeline.

Air-gapped operation

Datris runs with no external dependency. Local models via Ollama and bundled bge-m3 embeddings cover the AI features without a cloud provider, and the one optional outbound request the platform can make (the model-catalog refresh described below) fails silently to a built-in list. See the deployment page for the profile.

No telemetry

The platform sends no usage data. There is no usage beacon, no crash reporter, no license check over the network. You can verify it: clone the repo and grep for it. 

git clone https://github.com/datris/datris-platform-oss.git && cd datris-platform-oss
grep -rniE "telemetry|analytics|posthog|sentry|segment\.io" --include=*.scala --include=*.ts --include=*.py --include=*.sh . | grep -v test

One outbound request exists and you should know about it: when a person opens the AI configuration screen, the server fetches the current model catalog from datris.ai so the model pickers show what is recommended today. It is triggered by that screen only, cached, times out in three seconds, and falls back to a list built into the UI when it fails. It carries no identifying payload beyond the request itself, and an air-gapped install never notices it.

Adoption is measured only from things you choose to do: request logs on our own install host (get.datris.ai), public registry download counts, and deployments people register voluntarily to receive advisories.

Vulnerabilities

  • Disclosure. Report privately through GitHub security advisories, or email info@datris.ai. We acknowledge within three business days and communicate a remediation timeline within ten.
  • Supported versions. Security fixes ship in the next release and go to the latest minor version only.
  • Advisories. Published on GitHub Security Advisories and sent to registered deployments and commercial licensees ahead of public disclosure.
  • SBOM and scanning. A CycloneDX SBOM for each container image is published with every release. Trivy scans every pull request and the published images weekly; Dependabot covers the rest. Signed builds are provided under a commercial license.

Compliance

SOC 2: not yet. We are a small company and we would rather tell you than let you find out. Most SOC 2 trust-services criteria concern how a vendor handles customer data in its own systems. In a self-hosted deployment no customer data reaches us, so most of those controls fall on your environment, where your existing SOC 2 already covers them. The controls that do apply to us, secure development and vulnerability handling, are described above and documented in the security packet.

The company

Datris is a division of IData Corporation, New Jersey, serving financial-services clients since 1998. Insurance and business-continuity statements are available under NDA with the security packet.

Request the security packet Commercial licensing