Self-host Quackback
Run Quackback on your own infrastructure.
JM
Written By James MortonLast updated 11 days ago
Quackback is designed to be self-hosted. Pick the deployment method that fits your setup.
Choose your path
Method | Best for | Time |
|---|---|---|
Fastest start, no server needed | 2 min | |
Most deployments | 10 min | |
Full control, no containers | 30 min |
Tip: If you're not sure, start with Docker. It handles dependencies, migrations, and updates automatically.
Before you start
Check the system requirements. You need PostgreSQL 18+, Redis or Dragonfly, and about 1 GB of RAM.
What's in this section
- Deploy with Docker: Docker Compose setup, configuration, upgrades
- Install without Docker: Bun, systemd, process management
- System Requirements: Hardware, software, cloud providers
- Reverse Proxy: Caddy, Nginx, Traefik configs for HTTPS
- Declarative Configuration: Manage workspace settings as code
- Troubleshooting: Common issues and solutions
Was this helpful?
Your feedback shapes what we write next.
Related articles
System RequirementsHardware and software requirements for self-hosting Quackback.Set up a reverse proxyServe Quackback securely with Nginx, Caddy, or Traefik.Quick StartGet Quackback running in under 5 minutes with Docker.Deploy to RailwayDeploy Quackback to Railway with one click. No server to manage, automatic SSL, and built-in PostgreSQL and Redis.