Skip to content
Your infrastructure. Your data.

Self-hosted feedback tool

Deploy Quackback on your own servers. Full data ownership, no vendor lock-in, and no per-user limits. Run it behind your firewall or on any cloud provider.

Why self-host your feedback tool

SaaS feedback tools store your customer data on someone else's servers. Self-hosting puts you in control. See our self-hosted feedback tools comparison for a deeper look.

Data sovereignty

Customer feedback stays on your infrastructure. No third-party data processing. Meet compliance requirements without extra agreements.

Predictable costs

Pay only for your servers. No per-seat fees that scale with your team. A $10/month VPS handles most startups.

Full customization

Modify the source code, add custom integrations, change the UI. The AGPL-3.0 license gives you full access.

Deploy anywhere

AWS, GCP, Azure, DigitalOcean, Hetzner, on-premises, or air-gapped. If it runs Docker, it runs Quackback.

System requirements

Quackback runs on minimal infrastructure. Most teams start with a single small server.

CPU
1 vCPU (2+ recommended for larger teams)
RAM
1 GB minimum, 2 GB recommended
Storage
10 GB (scales with feedback volume)
Software
Docker 20+ or Node.js 18+ with PostgreSQL 14+
OS
Any Linux distribution, macOS, or Windows with Docker
Network
Port 3000 (configurable). No outbound internet required after setup.

Three ways to deploy

Choose the deployment method that fits your team. All options give you the same full-featured platform.

Docker Compose

Recommended

Clone the repo and run docker compose up. The fastest path from zero to running. Includes PostgreSQL.

One-click platforms

Easiest

Deploy to Railway, Render, or Fly.io with a single click. Managed PostgreSQL included.

Manual deployment

Advanced

Install Node.js and PostgreSQL directly. Full control over the process for custom environments.

terminal

# Quick start with Docker

$ git clone https://github.com/quackbackio/quackback

$ cd quackback

$ cp .env.example .env

$ docker compose up -d

✓ PostgreSQL ready

✓ Quackback running at http://localhost:3000

✓ Admin panel at /admin

Migrate from your current tool

Switching from a SaaS feedback tool does not mean starting over. Quackback imports your existing data.

Canny

Import posts, votes, comments, statuses, and user data. Board structure and vote counts are preserved.

UserVoice

Import suggestions, votes, comments, and categories. Status mappings are configurable during import.

CSV / Custom

Import from any tool via CSV. Map your columns to Quackback fields. Bulk import with a single command.

Self-hosted vs SaaS feedback tools

Self-hosting is not for every team. Here is how the trade-offs break down.

Self-hosted

  • Full data ownership and sovereignty
  • No per-seat or per-response fees
  • Deploy behind firewalls or VPNs
  • Customize source code and integrations
  • Air-gapped deployment support

SaaS (managed)

  • Zero infrastructure to manage
  • Automatic updates and backups
  • Faster initial setup
  • Managed SSL and uptime monitoring
  • Same open source codebase

Frequently asked questions

What does self-hosted mean for a feedback tool?

Self-hosted means you run the software on your own servers or cloud infrastructure. Your feedback data stays on machines you control. You handle updates, backups, and scaling — but you get full ownership and zero vendor dependency.

How much does it cost to self-host Quackback?

Quackback itself is free. Your only cost is the infrastructure to run it. A small VPS ($5-20/month) handles most teams. Larger deployments may need more resources, but there are no license fees, per-seat charges, or usage limits from Quackback.

Can I migrate from a SaaS feedback tool to self-hosted?

Yes. Quackback includes importers for Canny, UserVoice, and generic CSV files. Posts, votes, comments, statuses, and user data are preserved during migration. You can be up and running on your own infrastructure in an afternoon.

Is self-hosting secure?

Self-hosting gives you full control over your security posture. Quackback supports HTTPS, SSO/SAML authentication, role-based access control, and can run behind your existing firewall or VPN. Your data never passes through third-party servers.

What if I do not want to manage infrastructure?

Quackback also offers a managed cloud option if you prefer not to self-host. You get the same open source product without managing servers. Both options use the same codebase — you can switch between them at any time.

Can I deploy Quackback in an air-gapped environment?

Yes. Quackback runs as a self-contained Docker container with PostgreSQL. It does not require outbound internet access after deployment, making it suitable for air-gapped networks, government environments, and restricted infrastructure.

Deploy Quackback on your infrastructure

Free, open source, and yours to run.