Self-host Quackback

Quackback is open source, and you can run the full product on your own servers. This section is for teams self-hosting the open-source edition. If you use Quackback Cloud, none of this applies: hosting, upgrades, email, and storage are handled for you.

Choose your path

Tip: If you're not sure, start with Docker. It handles dependencies, migrations, and updates for you.

Before you start

Check the system requirements. In short, you need:

• PostgreSQL 14 or newer with the pgvector (0.5.0 or newer) and pg_trgm extensions
• About 1 GB of RAM
• S3-compatible object storage if you want file uploads (the Docker Compose stack includes one)

There is no Redis or other queue service to run. PostgreSQL is the only datastore: it holds your data, the background job queue, caches, rate limits, and realtime events. The pg_cron extension is not required either.

What's in this section

• Self-hosting quick start: Try Quackback on your machine in a few minutes
• Deploy with Docker: Docker Compose setup, configuration, upgrades
• Deploy to Railway: One-click template or manual setup
• Install without Docker: Bun, systemd, process management
• Upgrade from 0.13 to 0.14: Back up, upgrade, and what changes
• System requirements: Hardware, software, cloud providers
• Environment variables: Every setting the server reads
• Configure email delivery: SMTP, Amazon SES, or Resend
• Set up a reverse proxy: Caddy, Nginx, Traefik configs for HTTPS
• Scale with multiple replicas: Split web and worker roles
• Health endpoints: Liveness and readiness checks
• Declarative configuration: Manage workspace settings as code
• Receive email over IMAP: Inbound email without a public webhook
• Telemetry: What the instance reports and how to turn it off
• Troubleshoot common issues: Common issues and solutions
• Self-hosting FAQ: Quick answers to common questions

Related articles

• Self-hosting quick start
• Deploy with Docker
• System requirements
• Self-hosting FAQ