Repository navigation
Production and Scaling
BJD1997 edited this page Oct 9, 2026
·
3 revisions
Running YADT beyond a single operator.
- Scaling Horizontally — worker/api scale-out, leader election, PgBouncer, read replicas, and what isn't safe yet.
- Updating & Release Channels — updating each deployment path, and how release tags work.
- Securing Your Install — exposing the API only to your proxy, backups, database passwords, who can sign in.
A single api + single worker on one well-specced VM is the default and
is plenty for one operator or a handful of orgs — everything above is
opt-in, invisible unless configured.
← Back to the README · Live demo · Report an issue · MIT licensed
- Quick Start: Docker Compose
- Deploying with Portainer
- Deploying on Azure
- Configuration Reference
- Onboarding an Organization
- IMAP Mailbox
- Google Workspace Mailbox
- Sign-in Providers
- Multi-Tenancy & RLS
- DMARC Subdomain Inheritance
- Report Attribution
- SPF Conditional Mode
- Detected Domains
- DNS Check Scheduling
- Domain Rating
🏗️ Architecture
🗺️ Roadmap