Dory Deployment Guide
Dory can run as a desktop app, local web app, or Docker-based self-hosted deployment. For shared deployments, plan runtime configuration, authentication, AI provider credentials, database network access, secrets, and user access before inviting users.
Deployment Pages
| Page | Use case | Focus |
|---|---|---|
| Self-Hosting | Run Dory in your own environment | Architecture, secrets, persistence, proxying, and rollout checks. |
| Docker | Start Dory quickly in a container | docker run, .env, ports, volumes, and upgrades. |
| Environment Variables | Configure runtime behavior | Auth, AI, email, OAuth, MCP, and init user variables. |
| Auth / SSO | Plan team identity | Email verification, Google/GitHub login, provisioning, and offboarding. |
Recommended Rollout
- Run Dory locally or on a test server with Docker.
- Prepare secrets, auth URL, and AI configuration in Environment Variables.
- Put Dory behind HTTPS.
- Decide login and verification rules in Auth / SSO.
- Validate SQL Console, Explorer, and AI on test databases.
- Add production databases with readonly accounts first.
Quick Answer
Dory can be self-hosted with Docker. Production deployments need DS_SECRET_KEY, BETTER_AUTH_SECRET, BETTER_AUTH_URL, and AI variables when AI is enabled. Team deployments should use HTTPS, readonly database accounts, trusted origins, and a clear user management process.
Related Docs
Save and Reuse Analysis in Dory
Use Dory Saved Queries to preserve SQL, document assumptions, organize folders, and build reusable team analysis assets.
Self-Host Dory
Self-host Dory on your own server, private network, or cloud environment with Docker, HTTPS, secrets, AI, and database access planning.