Helpy

Last reviewed Sep 13, 2026 · 882 words

Helpy is the right answer to a question fewer people ask each year: "I want tickets, a public knowledge base and a community forum in one open-source app, and I am prepared to run Ruby on Rails to get it". In 2016 that was a strong offer and Helpy earned its 2,471 stars on it. In 2026 the open-source repository moves slowly, the commercial Helpy Pro gets the new features, and two or three other projects do each individual piece better. It still works, it is still MIT, and there is a narrow set of teams for whom the bundle beats the best-of-breed alternatives. This guide is about deciding whether you are one of them.

What the bundle actually contains

Three things share one login and one theme. The ticketing side takes email into a shared inbox, turns it into tickets with agents, internal notes, canned replies, tags and priorities, and replies from the same address. The knowledge base is a multi-language article library with categories, and an article can be shared publicly or restricted to logged-in users. The forums are community Q&A, where a customer's question is public, other customers can answer, and an agent can convert it into a private ticket. Multi-language support runs through everything, with the UI available in around 20 languages and articles translatable per locale.

The reason to want this in one place is the self-service loop: a support agent answers a ticket, promotes the answer to an article, and the article deflects the next 50 tickets. Zendesk sells exactly this loop, and Helpy was built as an open-source Zendesk alternative around it.

The stack you are signing up to run

Helpy is a Rails application on PostgreSQL, with a background worker for inbound mail and notifications. The repository ships a Docker setup; the catalogue's 1,024 MB minimum is about right for the app, the worker and the database together, and Ruby processes do not shrink. Inbound email is the fiddly part: tickets are created by polling an IMAP mailbox or by a webhook from a transactional mail provider such as Mailgun or SendGrid, and outbound replies go through SMTP. Get those two flows tested before inviting agents, because a helpdesk that silently drops email is worse than no helpdesk.

Backups are the database plus the uploaded attachments directory. Upgrades are a Rails migration; read the changelog before each one, and expect long gaps between releases.

The maintenance reality

The core project's commit history thins out after 2020. Dependencies get bumped, bugs get fixed, but new features land in Helpy Pro, the hosted and paid product from the same developers. That is a legitimate model, and the open-source version is not abandoned, but a self-hoster should go in knowing that the community edition is a maintained snapshot rather than a moving target. The risk is a Rails security release that the project takes months to adopt, and the mitigation is not exposing the admin side to the internet without a proxy and an identity layer in front.

Where the pieces are done better

For tickets alone, FreeScout is a lighter PHP shared inbox with a much more active community and is the safer pick for a small team. Zammad is the heavyweight helpdesk with proper SLAs, integrations and a bigger install base, at 4 GB of RAM. For customer conversations across email, chat and WhatsApp, Chatwoot has become the default. For the knowledge base alone, BookStack or anything in the wikis category gives you a better editor, and for a community forum, Discourse is in a different league. Each of those has more contributors than Helpy has had in the last 3 years combined.

What none of them offer is all three in one login with one theme. If your support workflow really does move between forum thread, article and ticket several times a day, and your team is small enough that one integrated UI beats three good ones, Helpy is still the only open-source product that does that.

Who should still run it

A small software company with a product community, 2 to 5 support agents, a multilingual customer base, and somebody on staff who is comfortable with Rails. That person exists at plenty of companies, and for them Helpy is a weekend install with no licence fee and a coherent product. A team without a Rails-comfortable operator, or one that only needs tickets, should not take on the stack.

What I'd do

Most teams: FreeScout for the inbox and BookStack for the articles, with a link between them. That is 2 containers, both actively developed, and the loss of an integrated forum rarely hurts. If the integrated forum and multilingual knowledge base are the actual requirement, install Helpy from its Docker setup on PostgreSQL, wire inbound mail through a provider webhook rather than IMAP polling, keep the admin behind a VPN, and schedule a quarterly check of the repository for security releases. Go in with clear eyes about the pace of development, and it will serve a small support team well for years; go in expecting a growing product, and you will be disappointed within one.