Answer

Last reviewed Aug 26, 2026 · 899 words

Answer runs as one Go binary, boots on SQLite with no other container, walks you through a browser installer, and gives you a Stack Overflow-shaped site with tags, voting, accepted answers, reputation, and badges in under 10 minutes on 512 MB of RAM. That is a materially smaller operational bill than the alternatives in the forums category, and it is why I would pick it for an internal knowledge base or a product support community before I would pick anything heavier. The caveat is that the software is younger than the format it copies, and you will feel that in the plugin catalogue.

What the format buys you over a forum

A thread forum (Discourse, Flarum, NodeBB) optimises for conversation. Q&A optimises for the answer floating to the top and staying there, which is what an internal engineering team, an open-source project's user base, or a customer support site needs. Answer adds two things that Stack Overflow never had in one place: an "articles" post type for longer-form writing, and a documentation-style browse mode, so a single install covers questions, how-tos, and announcements. Reputation gates privileges (voting, editing others' posts, closing) by default, and the thresholds are editable in the admin panel, which matters because a 40-person company will never hit Stack Overflow's numbers. The pull that made people leave Stack Overflow for private instances was ownership of the content and the moderation policy, and Answer delivers both.

Deploy: pick the database in the installer, not later

services:
  answer:
    image: apache/answer:latest
    volumes:
      - ./data:/data
    ports:
      - "9080:80"
    restart: unless-stopped

Visit the port, and the installer asks for a database. SQLite writes a file under /data and is the correct answer for a team site with a few thousand posts; MySQL and PostgreSQL are supported and become worth it when several hundred people are active or you want to run 2 replicas behind a load balancer. Migrating between them later is not a supported one-click operation, so decide in the installer. The /data volume holds the SQLite file, uploads, the generated config.yaml, and any compiled plugins' state. Set the site URL in the admin panel to the public HTTPS address before inviting anyone, because email links and OAuth callbacks are built from it. Outbound mail is required for registration and notifications; a transactional SMTP account is the sensible route, and my notes on self-hosted email explain why I would not run the mail server too.

Plugins are compiled in, which changes how you upgrade

Answer's plugin model is unusual: plugins are Go packages that get built into the binary, so adding GitHub login, S3 storage for uploads, a Meilisearch or Elasticsearch search backend, or a hCaptcha check means running the project's build command with a list of plugin module paths, or using the image tag that ships with the official plugin set. The upside is one process and no runtime plugin loader to break; the downside is that "install a plugin" becomes "rebuild and redeploy", and the catalogue's "smaller plugin library" is accurate. Before committing, list the integrations you need (SSO provider, storage, search) and confirm each exists in the official plugins repository. Login via OAuth is there for the common providers; a generic OIDC connector is what you want for Authentik or Authelia and it exists, but test it in staging.

Seeding is the hard part, not hosting

Every Q&A site launches empty, and an empty Q&A site looks broken in a way an empty forum does not. The projects I have seen succeed with Answer did three things: imported 30 to 50 real questions from their existing chat or ticket history before launch, answered them under real accounts, and set reputation thresholds low enough that a new employee could vote on day one. Answer's admin panel has a review queue for flagged posts and first-time contributions, which is enough moderation tooling for a private instance and thin for a large public one.

Where it is still young

The project shipped in 2022 and moved under the Apache Software Foundation, which is a good sign for governance and a mixed sign for velocity; releases are steady but the ecosystem of themes, importers, and third-party plugins is a fraction of Discourse's. There is no official migration path from a Discourse or Stack Overflow for Teams export beyond the API, so plan to write a small import script if you are moving content. The interface is modern and responsive, and there is no native mobile app because it does not need one.

What I'd do

Internal knowledge base or support site with under 500 active users: Answer on SQLite behind Caddy, SMTP via a transactional provider, OIDC plugin compiled in if you have an identity provider, and 40 seeded questions before the announcement goes out. Public community that expects to grow into the thousands with heavy moderation needs: Discourse, and accept the 2 GB of RAM and Ruby operations that come with it. For the smaller case Answer is the lightest credible Q&A platform you can self-host, and its Apache-2.0 licence and 15,658 stars say it is not going anywhere.