Platform · Security
Precisely what stays, and precisely what leaves.
Self-hosted software makes claims about data residency easy to overstate. This page states the outbound paths exactly, including the one that is mandatory.
Data residency
Where your data sits
Your database telemetry, query data and operational metrics stay within your environment.
The only mandatory external application egress currently identified is licence verification. Additional outbound traffic occurs only for integrations and notification channels the customer chooses to enable.
Outbound traffic
Every path that crosses the boundary
Published in full because this is the table enterprise reviewers ask for. Volunteering it shortens security review; discovering it during a packet capture does the opposite.
| Traffic | Destination | Carries | Required |
|---|---|---|---|
| Licence activation & verification | controller.dbchefs.io — TLS, pinned CA | Licence token, node count, product version, and an installation fingerprint containing hostname, operating system, PHP version, application URL and a database identifier. | Mandatory |
| Integrations | Customer's own Jira / PagerDuty | Incident data the customer configures | Only if enabled |
| Notifications | Customer's configured mail transport | Alert and incident content | Only if enabled |
| Database telemetry & query data | Stays in the environment | Agent to control plane to local InfluxDB / PostgreSQL | — |
| Product telemetry / usage reporting | None found | No phone-home or auto-update path located | — |
Controls
What you can govern
- Access control
- Roles of Admin, Editor, Viewer and Read-only, scoped by organisation and project.
- Audit log
- Actions recorded with actor and time, exportable.
- API log
- API activity recorded and exportable alongside the audit trail.
- Agent identity
- Agents carry signed identities verified by the control plane.
- Backup encryption
- Encryption profiles applied per policy, with credentials stored separately from artefacts.
- Authentication
- Forced password reset, email verification, and CSRF protection on the console.