Talkyard

Last reviewed Sep 13, 2026 · 781 words

There is exactly one reason to pick Talkyard over Discourse, and it is a good one: Talkyard is a full forum and a Disqus-style embedded comments system at the same time, with one account and one moderation queue covering both. If you run a blog with comments and want a community forum behind it, that dual role saves you running two applications, two logins and two spam filters. If you only want a forum, Discourse is the safer choice with a community many times larger, and you should go there.

Forum, chat, Q&A and comments, from one Postgres database

Talkyard is AGPL-3.0, first released in 2016, with 1,813 GitHub stars at the time of writing. The frontend is TypeScript; the backend runs on the JVM with PostgreSQL for data. Within one site you can create categories that behave as discussion topics, as question-and-answer threads with accepted answers and voting, as open-ended ideas boards, or as chat channels that update in real time. A single site can mix all of them, which is the "inspired by Discourse, StackOverflow and Slack" line in the project's own description.

The embedded comments work through a script tag on your blog pages. Each page that loads it gets a discussion thread inside your Talkyard site, in a category you designate for comments, and commenters can sign in with the same account they use on the forum, or through single sign-on from your main site. Moderators see forum posts and blog comments in one place.

The 2 GB minimum is Elasticsearch, and it is not optional

The supported install is the project's talkyard-prod-one repository: a Docker Compose stack on a single server with Nginx, the app server, PostgreSQL, Redis and Elasticsearch for search. The maintainers say one server, and they mean it; splitting services across hosts is unsupported. Plan on 2 GB of RAM as the floor and 4 GB if the site has more than a few hundred active users, with most of that going to the JVM app and Elasticsearch. That puts it in the same weight class as Discourse and well above lighter PHP or Node forums like Flarum and NodeBB, which run happily in 512 MB.

Setup is Medium difficulty: the install script handles the compose stack and TLS, but you will want a mail relay configured before you invite anyone, because Talkyard, like every forum, is only as good as its notification emails.

Where the smaller community bites

Talkyard is effectively a one-maintainer project with a paid hosted offering funding it. Releases are steady but not frequent, third-party themes and plugins are rare, and searching an error message will find the project's own issue tracker and little else. That is the standing risk of anything in the 1,000 to 3,000 star band, and here it is concentrated on one person. Discourse, by comparison, has a company, a plugin ecosystem and a decade of Stack Overflow-style answers for every failure mode.

The upside is that the codebase is coherent and the maintainer answers questions. If you can tolerate reading source to understand behaviour, you will manage. If you need a forum a volunteer moderator can administer without you, that is the argument for Discourse.

The Disqus replacement question, honestly

If you only want blog comments and have no forum ambitions, Talkyard is heavier than you need. Giscus stores comments in GitHub Discussions with no server at all, and Cusdis is a tiny Node service with no login required. Both are far lighter and less capable. Talkyard earns its 2 GB when you want commenters to become community members: someone asks a question under a blog post, the reply turns into a forum thread, and the same profile follows them. The forums category lists the alternatives if that is not your shape.

What I'd do

If I had a blog with real comment traffic and wanted a forum to grow out of it, I would run Talkyard from the prod-one repository on a 4 GB VPS, wire single sign-on to the blog, and accept the smaller community as the price of not running two systems. Otherwise, Discourse for the forum, and a lightweight comments tool for the blog. Do not adopt Talkyard for the chat or Q&A features alone; Discourse has both now, and its bus factor is not one.