Self-hosting (open source)
Run the open-source edition on your own servers: install, configure, upgrade, and troubleshoot.
JM
Configure email deliverySet up outbound email on a self-hosted Quackback instance with exactly one provider (SMTP, Amazon SES, or Resend), plus sender identity, deliverability, and troubleshooting.
5 min readSelf-host QuackbackRun the open-source edition of Quackback on your own servers: choose Railway, Docker, or a manual install, and find every self-hosting guide.
3 min readSelf-hosting quick startGet a self-hosted Quackback instance running with Docker Compose in a few minutes, complete first-time setup, and prepare it for production.
4 min readSystem requirementsHardware, PostgreSQL 14+ with pgvector and pg_trgm, object storage, ports, and security requirements for self-hosting Quackback. No Redis or pg_cron needed.
6 min readDeploy with DockerRun self-hosted Quackback in production with Docker Compose (app, PostgreSQL, and Silo storage) or docker run: configuration, email, storage, upgrades, and rollback.
9 min readDeploy to RailwayDeploy self-hosted Quackback to Railway with the one-click template (app, PostgreSQL with pgvector, and a storage bucket) or set it up manually. No Redis needed.
6 min readInstall without DockerInstall self-hosted Quackback without Docker using Bun 1.4+ and PostgreSQL 14+ with pgvector and pg_trgm, run it under systemd or PM2, and keep it updated.
8 min readDeclarative configurationManage a self-hosted workspace's name, slug, and use case from a YAML config file in version control, with those fields locked from dashboard edits.
3 min readSet up a reverse proxyServe self-hosted Quackback over HTTPS with Caddy, Nginx, or Traefik, and set TRUSTED_PROXY_HOPS or TRUSTED_CLIENT_IP_HEADER so rate limits see each visitor's real IP.
7 min readTroubleshoot common issuesFix common self-hosted Quackback problems: startup and migration errors, email provider conflicts, sign-in and OAuth callbacks, background jobs, IMAP, rate limits, and Docker issues.
9 min readEnvironment variablesEvery environment variable a self-hosted Quackback server reads: required settings, trusted proxy and client-IP header, email, inbound email, AI, storage, telemetry, logging, and Docker.
26 min readUpgrade from 0.13 to 0.14Upgrade a self-hosted Quackback 0.13 install to 0.14: back up, remove Redis, move to Silo storage, set trusted proxy hops, keep one email provider, and see what changes.
15 min readTelemetrySee exactly what the anonymous daily usage snapshot from a self-hosted Quackback instance contains, what it never contains, and how to turn it off with DISABLE_TELEMETRY.
6 min readReceive email over IMAPTurn inbound email into support conversations on a self-hosted Quackback instance by polling a mailbox over IMAP, with no public webhook endpoint needed.
4 min readScale with multiple replicasSplit a self-hosted Quackback instance into web and worker replicas with QUACKBACK_ROLE, run migrations once, and wire health checks per role. No Redis or sticky sessions needed.
4 min readHealth endpointsUse /api/health/live and /api/health/ready to wire liveness and readiness probes for a self-hosted Quackback instance, and read the readiness response.
2 min readSelf-hosting FAQQuick answers for self-hosters: no Redis or pg_cron needed, OAuth callback URLs, which domain to use, turning on modules, AI with local models, image tags, upgrades, and where to report bugs.
5 min read