Softwr

Documentation · head to head

Fumadocs vs HelpDocs

Fumadocs logo

Fumadocs

Documentation

Documentation framework for Next.js that treats the docs site as an application rather than a static export

From
Free
Rated
-
Full reviewWebsite
HelpDocs logo

HelpDocs

Documentation

Self-service help centre software priced by number of editors, not by readers

From
On request
Rated
-
Full reviewWebsite

The short version

  • Only Fumadocs has a free tier, so it costs nothing to try first.
  • Each has a real cost: Fumadocs it is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.; HelpDocs it is a knowledge base only, so a company still needs a separate ticketing or chat tool for any support that is not fully self-service
  • They diverge on capability: Fumadocs covers Next.js App Router native, HelpDocs covers Editor-only seat pricing.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Fumadocs and HelpDocs actually diverge.

Attributes where Fumadocs and HelpDocs differ
AttributeFumadocsHelpDocs
Starting priceFreeOn request
Pricing modelOpen source, no licence feePer editor seat per month
Free tierYesNo
PlatformsWeb, macOS, Windows, LinuxWeb

Identical on both: user rating (Not yet rated), category (Documentation).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Fumadocs

  • Next.js App Router native
  • Multiple content sources
  • OpenAPI page generation
  • Built in search
  • Headless and styled layers
  • Type safe frontmatter
  • Code and content colocation

Only in HelpDocs

  • Editor-only seat pricing
  • AI drafting and credits
  • Search analytics
  • Custom branding and domain
  • Multi-language content

What people use each for

The jobs each tool is most often brought in to do.

Fumadocs

  • Documentation that must sit behind login and show different content to different customer plansnot HelpDocs
  • A Next.js product team that wants docs to deploy in the same pipeline as the applicationnot HelpDocs
  • API reference pages generated from an OpenAPI document alongside hand written guides in one navigation treenot HelpDocs
  • A design system site where the component documentation must render the live components from the same codebasenot HelpDocs

HelpDocs

  • A SaaS support team that wants a public, brandable help centre separate from its ticketing toolnot Fumadocs
  • A product team publishing release notes and how-to articles that needs unlimited free readers with only a handful of paid writer seatsnot Fumadocs
  • A company scaling its support content team that wants cost tied to writer headcount rather than customer or ticket volumenot Fumadocs
  • A team wanting AI-assisted drafting of support articles without adopting a full AI-enabled helpdesk suitenot Fumadocs

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Fumadocs

  • It is a library rather than a finished theme, so the initial setup is meaningfully longer than a generator that ships a working site from one command.
  • Maintenance is concentrated in a very small group, so an unresponsive week is a blocked upgrade and there is no support contract to escalate to.
  • It only targets Next.js, so adopting it commits the documentation to that framework and a later migration means rewriting the site rather than swapping a theme.
  • Breaking changes have arrived across minor versions during rapid development, so pinning versions and reading migration notes is a recurring cost rather than a one off.
  • Running docs inside the application means docs traffic hits your application infrastructure and shares its failure modes, where a separate static site would have stayed up.

HelpDocs

  • It is a knowledge base only, so a company still needs a separate ticketing or chat tool for any support that is not fully self-service
  • Extra editor seats above a plan's included count cost $25 each per month, which adds up quickly for a growing content team on the Harvest tier
  • AI credits are capped per plan and reset monthly, so a heavy AI-drafting workflow can exhaust the allowance before the billing period ends
  • Moving from Sprout to Bloom to add editors is a large jump in absolute price, not a smooth per-seat increment, since each tier is a fixed bundle rather than pay-per-seat
  • There is no free tier, only a 14-day trial, so a small team wanting to test long-term usage patterns has a short evaluation window
  • Being editor-priced means it does not scale cost with help centre traffic or ticket deflection value delivered, so a high-traffic help site pays the same as a low-traffic one with the same editor count

Pricing, plan by plan

Fumadocs

Free
  • Open sourceFree
    • MIT licence
    • All packages included
    • Self hosted or deployed with your Next.js application

HelpDocs

On request
  • Sprout$99/month
    • 5 editors
    • 1,000 AI credits/month
  • Bloom$239/month
    • 15 editors
    • 5,000 AI credits/month
  • Harvest$399/month
    • 25 editors
    • 10,000 AI credits/month
    • Extra editors at $25/month each

Which should you pick?

Choose Fumadocs if

  • You need next.js app router native.
  • You want to start without paying.
  • You work on Web, macOS, Windows, Linux.
  • You also want multiple content sources.
Fumadocs review

Choose HelpDocs if

  • You need editor-only seat pricing.
  • You also want ai drafting and credits.
HelpDocs review

Questions people ask

Is Fumadocs or HelpDocs better?
Neither clearly leads. Fumadocs starts at Free and HelpDocs at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Fumadocs or HelpDocs?
Fumadocs has a free tier; the other does not. Paid plans start at Free for Fumadocs and On request for HelpDocs.
Does Fumadocs or HelpDocs run on more platforms?
Fumadocs runs on Web, macOS, Windows, Linux. HelpDocs runs on Web.
Can I use Fumadocs for free?
Yes. Fumadocs has a free tier, so you can try it without paying. HelpDocs starts at On request.
What is Fumadocs best used for?
Fumadocs is most often used for documentation that must sit behind login and show different content to different customer plans, a next.js product team that wants docs to deploy in the same pipeline as the application, api reference pages generated from an openapi document alongside hand written guides in one navigation tree, a design system site where the component documentation must render the live components from the same codebase. Of those, documentation that must sit behind login and show different content to different customer plans and a next.js product team that wants docs to deploy in the same pipeline as the application are not what HelpDocs is typically brought in for.
What can Fumadocs do that HelpDocs cannot?
Fumadocs covers Next.js App Router native, Multiple content sources, OpenAPI page generation, Built in search. HelpDocs covers Editor-only seat pricing, AI drafting and credits, Search analytics, Custom branding and domain.

Answered from the vendors’ own pages

Fumadocs: Can I put documentation behind authentication?

Yes. Pages are Next.js server components, so the same session and authorisation checks the rest of the application uses apply.

HelpDocs: Are readers of the help centre charged for?

No, HelpDocs charges only for editors who log in to write and manage content; anonymous readers are unlimited and free.

Fumadocs: Does it work outside Next.js?

No. The UI layer depends on the Next.js App Router.

HelpDocs: Is there a free plan?

No, HelpDocs offers a 14-day free trial rather than a permanent free tier.

Fumadocs: Can it generate pages from an OpenAPI spec?

Yes, including operation pages, schema rendering and an interactive request playground.

HelpDocs: Does HelpDocs include ticketing or live chat?

No, it is a knowledge base and help centre product only; it integrates with tools like Zendesk and Intercom for ticketing.

Fumadocs: Who maintains it and is that a risk?

A very small maintainer group. For a long lived commercial documentation set, treat the low bus factor as a real risk and budget for owning a fork.

Fumadocs: Do I still need a separate docs deployment?

No, and avoiding one is the main reason to choose it. The cost is that docs share your application uptime.

Share

Related pages

More on Fumadocs

More on HelpDocs

Keep looking

Other head to heads