SECURITY, WITHOUT THE BLACK BOX
Your database.
Your control.
OpenDash reads through a read-only role. You choose the model provider and keep your keys. The core that touches your data is open source.

Read-only by design
A database role that can only SELECT. No write, update, delete or DDL grants.
Hosted in Europe
OpenDash Cloud is hosted in the EU. Self-hosting runs the application and its state in your environment.
Your provider. Your key.
Connect the model provider you choose, under your own account and terms.
Open core you can audit
Query engine, tracing and permissions are Apache 2.0. Read every line on GitHub.
THE ARCHITECTURE
One question.
A visible path to the answer.
Live queries run against your database. Definitions, checks and recorded results make the answer inspectable.
Your database
Live queries through
a read-only role.
Your analyst, with the working attached.
- 01Read the definitionmetrics/mrr · workspace context
- 02Run a read-only querySource permissions stay in force
- 03Verify and attach the traceQuestion, SQL and recorded result
Your model provider
Your account, your key
and your terms.
Your team
Answers in OpenDash,
Slack or email.
Read-only queries leave your source database unchanged. OpenDash saves results needed for answers and traces in its own database. When self-hosted, that state lives in PostgreSQL in your environment.
PERMISSIONS
Read-only means
read-only.
WORKSPACE CONTROLS
The controls your security
team will ask for.
SSO with OIDC or SAML 2.0
Available with an Enterprise license. Enforce it for your domain and turn off passwords.
Roles and permissions
Owners, admins, members and viewers. Owners and admins approve what the analyst learns.
An attributable audit trail
A record of sign-ins, role changes, sources, sharing and approved knowledge, including who and when.
Retention for your requirements
90 days on every instance. Enterprise adds up to seven years, a tamper-evident chain and CSV export.
Audit log
Last 90 days| Time | Person | Action | Object |
|---|---|---|---|
| 09:42 | Maya Chen | Added a source | analytics_pg |
| 09:31 | Dev Patel | Approved knowledge | metrics/mrr · v8 |
| 09:05 | Maya Chen | Shared a dashboard | Launch readiness |
| 08:58 | Sam Ortiz | Changed a role | Ana Ruiz → Viewer |
| 08:40 | Dev Patel | Connected Slack | Northlake |
analytics_pg
metrics/mrr · v8
Launch readiness
Enterprise adds a tamper-evident chain and CSV export.
TRUST & DATA RESIDENCY
Made in Germany.
Hosted in the EU.
OpenDash Cloud is hosted in the EU. Source databases are queried directly, and results needed for answers are saved by OpenDash.
Made in Germany
Built by a team in Germany.
EU infrastructure
Cloud hosted in the EU. Self-host in your own environment.
DPA available on request
EU law applies.
SOC 2 · planned
Not certified today.
Subprocessors
and destinations
Optional models use your account, key and selected region.
App hosting
EUProduct analytics and errors: IDs and counts, never questions, answers or source data
Frankfurt, GermanyOptional model provider
Your accountOptional model provider
Your accountOptional model provider
Your accountDestination for answers
Your workspaceCOMMON QUESTIONS
Know what
goes where.
- Where is my data stored?
- Your source database is queried in place. OpenDash saves conversations, definitions, query results and jobs in its own database. Self-hosting uses PostgreSQL in your environment; OpenDash Cloud is hosted in the EU.
- Does data leave our network?
- Model requests go to the provider you connect, under your account and terms. When you self-host, the application, saved results and other state run in your environment.
- Where do memory and corrections live?
- Definitions and reviewed corrections are saved in OpenDash’s own database. Self-hosting uses PostgreSQL on your infrastructure, alongside conversations, query results and jobs.
Talk to us about
your setup.
We’ll walk your team through the architecture and your setup.
Talk to an engineer