Open-source alternative to Zendesk Guide

Open-source alternative to Zendesk Guide for teams that need their help center on their own servers

If your renewal, data residency rules or lock-in concerns extend to Zendesk Guide, the closest built-in match is Zammad, whose knowledge base supports draft, internal (staff-only) and public answers, publishing in several languages chosen at setup, categories with per-category permissions, and wiki-style links between answers and tickets. Chatwoot offers a Help Center portal for articles, FAQs and guides, while FreeScout only covers this need through its paid Knowledge Base module, so plan for that license cost if you choose it.

The help center is only one module, and its fit depends on the ticketing system it sits beside. Zammad's knowledge base is part of the same application as its ticketing, so answers can be linked directly to tickets and internal answers stay visible to agents only. Chatwoot's Help Center is designed to sit alongside its omnichannel inbox, so you should check whether your ticket workflows, channels and reporting needs match that model. Before choosing, confirm with each vendor whether the features your team uses, such as custom knowledge base domains (documented for self-hosted Zammad), search and category permissions, are available in the edition you plan to run.

Next, export your Zendesk Guide articles and categories, map who owns each one, and decide which answers must remain internal. Ask your implementation partner to test article import, link integrity and language variants on a copy before you commit to a platform.

Which Guide capabilities map to Zammad, Chatwoot and FreeScout

This table compares the main Zendesk Guide capabilities with Zammad's knowledge base, Chatwoot's Help Center and FreeScout's Knowledge Base module. Read the gap rows first, since they decide whether a help center can stay separate from the ticket system or must be built into it. Items marked to confirm need a check in the current release or a test on your own instance before you commit.

Capability	Zammad	Chatwoot	FreeScout
Article drafts and staff-only answers	Draft, staff-only (internal) and public answers are supported in the built-in knowledge base	Help Center portal publishes articles, FAQs and guides; confirm how drafts and internal-only articles are handled	Knowledge Base is a paid module; confirm draft and internal-only states after purchase
Multilingual publishing	Publishes in several languages chosen at setup	Confirm language variants per article in the Help Center	Confirm language handling in the Knowledge Base module
Categories and permissions	Categories with per-category permissions	Confirm category structure and access rules in the Help Center	Confirm category and access controls in the Knowledge Base module
Custom domain for public help center	Available only on self-hosted instances	Confirm custom domain setup on your own deployment	Confirm custom domain setup for the module on your own server
Answers linked to tickets	Wiki-style links between answers and tickets inside one system	Help Center is separate from the conversation inbox; links to conversations need confirmation	Knowledge Base is a module beside the shared inbox; ticket linking needs confirmation
Ticket deflection and analytics	Knowledge base sits alongside ticket reporting; confirm deflection metrics	Reports cover conversations, agents, inboxes, teams and CSAT; article-level deflection needs confirmation	Satisfaction Ratings is a separate paid module; confirm deflection reporting
Migrating Guide articles	Zendesk migrator covers tickets and users; confirm whether help center articles are imported	Confirm import path for existing Guide articles and categories	Confirm import path for Guide articles; the migration service covers help desk data

Which open-source option fits which help center model

Zendesk Guide couples the help center to the ticket system, the chat inbox or the shared mailbox, depending on how a team works. The three open-source options below each keep the knowledge base close to a different core tool, so the right choice follows from where your agents answer questions today.

Zammad's built-in knowledge base

Zammad keeps articles inside the same application that handles tickets, so an agent can link an answer to a ticket and a customer can find the same article on the public help site. Articles can be drafts, staff-only internal answers or public answers, in several languages chosen at setup, and categories carry their own permissions. The trade-off is that the knowledge base is only as separate as your ticket system: if you want a standalone docs site with its own design, confirm how far the custom domain and theming options go on your version before you commit.

Chatwoot's Help Center portal

Chatwoot's Help Center portal publishes articles, FAQs and guides alongside an inbox that already handles website live chat, email, WhatsApp and social channels. It suits teams where most first contact happens in chat and the same agents should see the article a customer was sent. Check which features your edition includes, since the free Community Edition leaves out SAML SSO and SLA policies. Plan for PostgreSQL and Redis as the only supported database and cache, because the portal lives inside that stack.

FreeScout's Knowledge Base module

FreeScout is a shared inbox built on PHP and Laravel, and its Knowledge Base is a paid lifetime module rather than part of the core product. That fits email-first teams that want a light stack and a one-time module purchase for each instance. Budget for the module on each FreeScout instance, and check that its article features match what your customers need before you move the help center over. Because the module is separate from the core, its update path and licensing should be confirmed in writing before rollout.

Migrating articles and categories

Each option needs articles, categories and their publication status exported and re-imported, and the Zendesk Guide content is not carried over by the ticket migrator alone. Confirm with the vendor and in a test instance whether article bodies, images, translations and redirects from old help center URLs survive the move. Map each Zendesk category to a target category and permission set before you start, so public and internal answers are not mixed during cutover.

Ticket deflection and self-service

Deflection depends on whether customers can find articles before they open a ticket and whether agents can link those articles to tickets. Zammad's linking between answers and tickets supports agent reuse, while Chatwoot's chat widget can surface the portal during conversations. Measure deflection on your own data after launch, because no figure is supplied here, and test search quality on your real customer questions before counting on it.

How the help center runs alongside the rest of the suite

If Zendesk Support keeps handling tickets and only the help center moves, articles become a separate site that agents and customers reach from two places. Links from macros, ticket templates and saved replies still point at Guide URLs, so those references need a planned update or redirect list before cutover.

Article links: Every macro, trigger and saved reply that links to a Guide article must be found and rewritten, or the old URLs must redirect. Build a link map from a full content export before you switch.
Search and deflection: Customers search the new portal, but suggestions inside the Zendesk ticket flow only see content Zendesk holds. Confirm whether deflection still happens in the ticket form after the move.
Content export: Zendesk's ticket, user and organization exports are available on Suite Growth and higher and Support Professional and higher, and the account owner must ask Zendesk support to enable them. Confirm whether that export includes Guide articles and attachments on your plan.
Sign-in: Staff access to Zendesk and customer access to the new portal use separate systems. Confirm which identity provider the portal supports so customers do not face two login flows.

Before committing, confirm exactly which Zendesk features, links and deflection paths will stop working once articles live outside Zendesk.

What carries over from Zendesk Guide and what needs rework

Plan the knowledge base move as two separate jobs. Article bodies, categories, languages, draft status and the split between public and internal visibility are content and metadata that you can move by export or re-entry. Everything that depends on the Zendesk address space or on past behavior needs manual rebuilding: article URLs, redirects from old help center paths, search history, links embedded in article bodies that point at Zendesk pages, and any deflection tracking you built from Zendesk reports. Start by inventorying the Guide structure (categories, sections, languages and which articles are drafts or internal) before choosing a target, because that inventory defines the size of the job.

The most important gap is in the export itself. Zendesk's CSV export omits ticket comments and descriptions, and article content is not something you should assume a plain ticket export will give you. Confirm with your own account which export formats and fields you can obtain. Zendesk exports are not enabled by default, the account owner has to ask Zendesk support to turn them on, and availability depends on the plan: JSON, CSV and XML exports are offered on Suite Growth and higher and Support Professional and higher, not on Team plans. Ask the account owner to request the export early, because the approval step can hold up the whole project.

Before you cut over, decide how each old URL will behave. Zammad's knowledge base offers a custom domain only on self-hosted instances, so the new public address is yours to design, but it will not match the Zendesk Guide paths. Plan a redirect map from every published article URL to its new location, and test it with the most visited articles. Also record how deflection is measured today, since ticket deflection figures tied to Zendesk reporting will not carry over automatically. Set a baseline on the new help center from the first day so that a drop in measured deflection is not mistaken for a drop in article quality.

How to move Guide articles and categories into a self-hosted help center

This sequence moves Zendesk Guide content into a self-hosted help center in a controlled way, so articles, categories, languages and links are verified before DNS changes. It runs as a separate content route, because Zammad's built-in migrator works only on a new instance and is all or nothing.

Inventory articles, categories and languages
The Guide owner lists every category, section, article and translation in Zendesk, marks which items are public, internal or outdated, and records which articles receive the most traffic or support links. Confirm with the Zendesk account owner which languages are live and whether any articles are restricted to particular user segments. The inventory is done when every article has a row with its category, language, visibility and owner, and the list is signed off by the support lead.
Export Guide content on a supported plan
Zendesk's account exports (JSON, CSV and XML) are available only on Suite Growth and higher and Support Professional and higher, and they are not enabled by default. The account owner must ask Zendesk support to turn them on, and the export is confirmed when the account owner can open a dated file that contains the article bodies. Because CSV omits comments and descriptions, prefer JSON for content and keep a copy of the raw export as a backup. Confirm with Zendesk whether your plan covers Guide article bodies in the export before relying on it, since the export documentation focuses on tickets, users and organizations.
Build a staging help center
The platform team installs the chosen self-hosted platform in a non-production environment inside the organization's own infrastructure. For Zammad, this means a new instance with its knowledge base enabled, because the built-in migrator cannot be run on an instance that already holds data. The step is complete when the staging instance serves a test public article in each target language and an internal article is hidden from anonymous visitors.
Map categories, languages and permissions
Build a mapping sheet that links each Zendesk category and section to a Zammad or Chatwoot equivalent, and each translation to a language chosen at setup. Decide which categories become public and which become staff-only, since Zammad supports draft, internal and public answers and per-category permissions. Review the mapping with the support and compliance owners. The step is done when the sheet is approved and a test import of a small category set shows the expected visibility.
Import articles and rebuild links and redirects
Load the mapped articles into staging, using the platform's API or a custom import script written for the Zendesk JSON structure, since Zammad's built-in Zendesk migrator does not move Guide content in the way this route requires. Rewrite internal article links to the new URLs, and build a redirect table from every old Zendesk help center address to its new address. The step closes when a sample of cross-linked articles opens correctly and the redirect table covers every public URL in the inventory.
Test search and ticket deflection
Testers run a fixed set of real customer questions against the staging help center and check that the right article appears in search, and that the knowledge base is linked from ticket replies where agents expect it. Search quality depends on the platform's indexing: Zammad recommends Elasticsearch for faster search and attachment content, so confirm whether it is part of the target design. The step is done when the agreed question set returns the expected articles and the deflection baseline is recorded for comparison after launch.
Cut over DNS and retire the Zendesk help center
The team lowers DNS time to live where the provider allows, moves the help center hostname to the production instance, and publishes the redirect table. It keeps the Zendesk Guide site readable for a defined period agreed with the business owner, then closes it once traffic and search logs confirm customers reach the new pages. Confirm your contract terms and the export retention period with Zendesk before cancelling. The step is complete when the redirect logs show successful traffic to the new hostname and the old help center is switched off.

What buyers ask before moving Zendesk Guide off the cloud

What are the main cost drivers when replacing Zendesk Guide with a self-hosted tool?

The main drivers are hosting, staff time, content migration and any support contract. Zammad's self-hosted edition has no license fee, but the server, database, search and cache tiers it needs are your cost, recurring each year. Chatwoot's Community Edition is $0, while its Premium Support plan is listed at $19 per agent per month and Enterprise at $99 per agent per month, so agent count changes the total. FreeScout's Knowledge Base is a paid lifetime module. Ask each vendor which features sit in which tier, and ask DeployOpen for a quote built from your written scope, including the one-time migration work and any recurring retainer.

How long does a Zendesk Guide replacement take, and what drives the timing?

The timeline depends on how much content you move, how many languages and categories it spans, how many permission rules must be recreated, and whether the help center is connected to ticket workflows. Zammad's migrator imports tickets all or nothing into a new instance, so the knowledge base is usually rebuilt by hand or through the API after the ticket import. Give your team a clear inventory of articles before work starts. DeployOpen agrees timelines in writing as part of a fixed-scope engagement, so ask for the schedule that follows from that scope.

What does our team need to provide for the project?

Expect to provide content owners who can approve articles, administrator access to Zendesk and to the target servers, and details of your identity provider. Zammad supports SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab, so confirm which one your staff use before setup. Someone must also decide which articles are public, staff-only or draft, and who may edit each category. Ask DeployOpen to list these inputs in the written scope so the dependencies are visible from the start.

Can our own IT team do the migration without an implementation partner?

Yes, if you have people who can run a Linux server, PostgreSQL, Redis and a reverse proxy, and who can handle an API token with full administrator rights for the source system. Zammad documents package, Docker Compose and Kubernetes installs, and Chatwoot documents a Linux installation script. The harder part is repeatable operations: backups, upgrades, security patches and recovering a failed article import. Weigh that ongoing load against the cost of a retainer, and confirm your team can absorb it.

Will ticket deflection metrics survive the move to a self-hosted knowledge base?

Deflection depends on how you measure it today. Zendesk's own deflection figures do not carry over, so you need a baseline of ticket volume, article views and search use before cutover. Zammad's knowledge base supports wiki-style links between answers and tickets, which helps you track which articles are cited. Chatwoot's Help Center portal and reports cover conversations and CSAT, but confirm which article-level metrics each product exposes. Export your Zendesk data in advance so the baseline is kept.

What should we confirm with each vendor about languages and custom domains?

Confirm the language list before you choose a product. Zammad publishes knowledge base answers in several languages chosen at setup, and it allows a custom knowledge base domain only on self-hosted instances. Chatwoot's Help Center portal and FreeScout's Knowledge Base module each have their own language and domain behavior, which you should verify on a test instance. Ask whether translations can be linked to one parent article, how custom domains get their TLS certificates, and whether the list of supported languages covers your staff and customer locales.

Does moving Zendesk Guide off the cloud change our security or compliance position?

Yes, because you take on hosting, patching, access control and backup of the help center. Zendesk's current controls are documented by Zendesk, but on your own servers those controls become your responsibility. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports or certifications; independent auditors and certification bodies do. Ask your auditor which evidence they will require before the cutover.

What a self-hosted help center costs beyond the license line

The license line is the smallest part of a self-hosted help center budget. Self-hosted Zammad has no license fee, and its knowledge base is included in the same install, so the recurring cost sits in the infrastructure that serves public articles and staff-only answers and in the support contract you choose. Zammad's Business, Enterprise and Corporation support subscriptions are priced per year at 2,999 EUR, 5,999 EUR and 9,999 EUR respectively, according to Zammad's pricing page, and they are optional. Chatwoot's Community Edition is free, but its Help Center portal sits alongside paid tiers priced per agent per month at $19 for Premium Support and $99 for Enterprise Edition, according to Chatwoot's self-hosted plans page. FreeScout's Knowledge Base is a paid module with a lifetime license for a single instance, so the cost is a one-time purchase that does not renew, though you should confirm current module pricing on freescout.net before budgeting.

Recurring costs are mainly hosting and database operations. Zammad needs PostgreSQL 15 or newer and Redis 7 or newer, and it recommends Elasticsearch for search across content and attachments. Chatwoot requires PostgreSQL only and recommends Redis 7.0 or higher, with at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day. Cost rises with the number of published articles, languages, attachment volume and agent count, and with whether you run a single server or a multi-node setup that needs Memcached for Zammad. Backups, patching and monitoring of these tiers are ongoing staff time, so ask any implementation partner to quote them as recurring operations, not as a one-off setup.

The one-time costs are the migration and the content cleanup. Zammad's Zendesk migrator moves content only into a new instance, and it does not migrate user passwords, so plan a review of which articles, categories and permissions should carry over. Many Zendesk Guide sites contain outdated or duplicate articles, and cleaning them up before import usually costs more staff time than the technical import. Confirm with your vendor or partner which Guide content the migrator will and will not transfer, and whether your Zendesk export and API token permissions cover it, before you estimate effort.

How DeployOpen scopes and delivers a help center replacement

DeployOpen plans, implements, customizes, integrates, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Zendesk Guide replacement, we start by mapping which articles, categories, languages and permissions must carry over, then build the help center in your environment.

How we scope

Inventory the Guide articles, categories, languages and public or internal audiences that must move.
Confirm which platform fits the need: Zammad's knowledge base, Chatwoot's Help Center portal or FreeScout with its Knowledge Base module.
Agree deliverables, timelines and responsibilities in writing before work starts, since most engagements are fixed-scope.

How we build

Deploy the chosen platform and its database, cache and search components in your cloud account, data center or air-gapped network.
Configure draft, internal and public answers, language settings, category permissions and any custom knowledge base domain.
Test article import, ticket links and public search with representative content before any cutover.

How we hand over

Document the architecture, configuration decisions, backup procedures and the steps your editors need to publish answers.
Provide a record of the content mapping, so you can confirm which Guide articles were moved, merged or retired.
Walk your support and content teams through the platform so they can maintain articles without outside help.

How we support

Ongoing support, upgrades and continuous testing are available as a retainer after handover.
Keep the help center current with platform releases, patched security fixes and backup verification.
Ask any partner or vendor for the support tier your own environment requires, and we will confirm what our scope covers.

Open-source alternative to Zendesk Guide