Doram Deployment
Your data stays where it is.
Run Doram in our cloud or in yours. It reads, never writes, and follows the access rules you already have.
Where it runs
Our cloud or yours. Same product.
Both run from the same build, so you can move between them without starting over.
Doram CloudWe run it for you.
- Runs in
- Doram’s cloud, in the region you pick
- Stored outside your network
- The context layer, never your rows
- Inbound ports
- None. An agent in your network connects out.
Your cloudIt runs in your own account.
- Runs in
- Your cloud account
- Stored outside your network
- Nothing
- Inbound ports
- None. Only calls to your AI model leave.
Access
No one learns through Doram what they could not see.
Doram reads your warehouse grants at every sync, so a revoke reaches it straight away. When two rules disagree, the stricter one wins.
| Customer | Spend | |
|---|---|---|
| Lena Fischer | ••••@•••• | €4,210 |
| Marco Rossi | ••••@•••• | €3,880 |
| Ana Silva | ••••@•••• | €2,905 |
- FactsEach person finds only the definitions they may read.
- RowsRow rules sit under every total, so a sum never leaks.
- ColumnsPersonal columns are masked or hidden.
The AI model
What the model sees. What it never sees.
You choose the model. Your data never trains it.
Sees
- Table and column names
- Column profiles and masked samples
- The question, and the asker’s own results
Never sees
- Passwords and keys
- Hidden or personal values
- Another person’s results
- Your data, for training
Running it
Reads a replicaDoram reads from a read replica, never your primary database.
Your budgetYou set a monthly compute budget and a window for jobs.
Your regionThe graph, backups and AI calls stay in the region you pick.
Full auditSee who changed a definition, why, and who saw which number.
Connects read-only to
- and more
The playground
Ask it yourself.
The playground is a whole company, already connected.