Ferndesk
Work Paragon LLC · Ferndesk: Self-Updating Help Center with an AI Agent That Verifies and Fixes Your Docs
Ferndesk is a hosted help center with a built-in agent, Fern, that checks each article against your code, live product, and support tickets, drafts fixes when something has changed, and writes new articles from merged pull requests. It also answers customers through AI search and an in-app widget. It suits SaaS founders and small teams who ship every week and cannot keep their help docs current by hand.
Best for
SaaS founders and small product or support teams that ship weekly, keep code on GitHub, and want their public help center checked against the product and updated from merged PRs without a dedicated technical writer
Not ideal for
Teams that must keep their docs in Zendesk Guide, Intercom, or another help center, teams not on GitHub that need code-level accuracy checks, buyers that need SOC 2 reports today, and teams looking for a help desk or ticketing system
Who it's for
SaaS founders, product teams, and support leads at small software companies who maintain a customer help center without a dedicated technical writer
Capabilities
- Article verification: extracts each claim in a published article and checks it against your code, live app, support replies, and links, then drafts the fix with retaken screenshots; runs monthly and on demand
- Automatic PR screening: reviews every merged GitHub pull request, works out what changed for users, and drafts updates to affected articles or a new article, with a configurable production branch per repository
- Weekly scheduled audits of support conversations, forums, and recent releases to find missing, stale, or unhelpful content, plus on-demand audits with custom date ranges up to 366 days
- Drafting on request from the dashboard, Slack, Linear @mentions, or the Chrome extension, using your codebase, tickets, videos, and changelogs as context, including bulk edits across many articles
- Automated screenshots: navigates your authenticated product, captures and annotates the right element, and updates images when the UI changes, plus a built-in image editor with redaction
- Changelog entries drafted from merged pull requests and code diffs, with reactions and an optional in-app announcement
- Hosted public help center on a custom domain or a /help subfolder, with private help centers via magic link, OpenID Connect, or JWT
- In-app widget and help center AI answers with source references, plus handoff to Crisp, Intercom, Help Scout, Zendesk, or Pylon with a drafted conversation summary
- API references for OpenAPI, Swagger, and GraphQL with a Try it playground, synced from GitHub or a URL
- AI translations with per-language guidance and a glossary, public API and webhooks, and an MCP server so Claude, ChatGPT, Cursor, and Codex can read docs and create draft changes
- One-click migration that preserves URLs and creates redirects, and export of the whole help center as Markdown
Limitations
- Fern only verifies and updates articles hosted in Ferndesk: it cannot maintain docs that stay in Zendesk Guide, Intercom Articles, or another help center, so you have to migrate
- Code-level checks need GitHub; without it, Fern verifies against your live website, tickets, and other connected sources, which Ferndesk says is less precise, and no GitLab or Bitbucket integration is documented
- Claims Fern cannot check against a source, such as pricing policy or third-party behavior, are flagged for you rather than verified
- No free plan: Pro costs $149 a month (or $1,490 a year) after a 7-day trial, and Enterprise starts at $399 a month
- Pro includes 1,000 AI conversations, 5 seats, and 5 languages; extra conversations cost $25 per 500 and extra seats $10 each per month, and every workspace member counts as a billed seat
- Not yet SOC 2 certified: Ferndesk's security page expects Type I in October or November 2026 and Type II in Q4 2026 or Q1 2027, and there is no public trust center
- SAML SSO, SCIM provisioning, custom integrations, and a data processing agreement require Enterprise
- Ferndesk is a help center, not a help desk: ticketing and live chat stay in your existing support tool
- No self-hosted deployment is documented, and AI processing runs through third-party models routed by OpenRouter
Use cases
- Migrating a stale Zendesk or Intercom help center and getting a list of articles that no longer match the product, each with a drafted fix
- Having a help article and changelog entry drafted automatically when a feature pull request merges
- Retaking every screenshot that shows a settings page after a UI redesign
- Finding recurring support questions with no matching article and drafting the missing docs
- Adding an in-app help widget that answers from verified docs and hands off to Intercom or Help Scout with a summary
- Publishing an OpenAPI or GraphQL reference next to customer docs, synced from a GitHub repository
Our take
Ferndesk targets the cause of most weak AI support answers: help articles that stopped matching the product weeks ago. Verification and PR screening turn doc maintenance into a review queue of drafted changes, each with a reason, which suits small SaaS teams that ship weekly and have no technical writer. The catch is that Fern only maintains articles hosted in Ferndesk, so adopting it means moving your help center. Teams on GitHub get the most precise checks. Larger buyers should note that SOC 2 is still in progress.
Who should use it
SaaS founders and small product teams that ship weekly on GitHub, support leads tired of answering questions that stale articles cause, and teams leaving Zendesk Guide or Intercom Articles that want their help center checked against the product continuously.
Who should skip it
Teams that cannot move their docs out of their current help center, companies without GitHub that need code-level accuracy checks, buyers that need a SOC 2 report or SAML SSO without an Enterprise contract, and teams shopping for a ticketing help desk.
Strengths
- Checks articles against code, the live product, and tickets instead of only answering from them
- Drafts doc updates from merged pull requests
- Retakes screenshots when the UI changes
- Nothing publishes without approval, and each change shows its reason
- Migration keeps URLs, and your support tool stays in place
- Help center, widget, API references, translations, and MCP in one plan
Weaknesses
- Only maintains docs hosted in Ferndesk
- Code-level checks require GitHub
- No free plan after the 7-day trial
- Not yet SOC 2 certified
- Monthly caps on AI conversations, seats, and languages
Ferndesk pricing
Pro
$149
Billed monthly
- Or $1,490 a year (two months free)
- Fern verification, unlimited PR screening and AI drafting, scheduled audits, and automated screenshots
- 1,000 AI conversations a month
- 5 seats and 5 languages included
- Custom domain or /help subfolder, private help centers, white label, API and MCP access
Pro (early-stage rate)
$75
Billed monthly
- For companies under $1M ARR with fewer than 10 people
- Full Pro plan for the first 12 months, or $745 paid up front for the year
- Standard $149 a month from month 13
Enterprise
From $399
Billed monthly
- Everything in Pro with higher limits
- 2,500 AI conversations a month
- SAML SSO and SCIM provisioning, custom integrations
- Data processing agreement, security questionnaire support, invoicing and purchase orders
- Priority support and white-glove onboarding
Free tier limits: No free plan. Every plan starts with a 7-day free trial with full access and no credit card.
Note: An AI conversation is one exchange between a user and Fern in your help center, counted once however many questions it includes; extra conversations cost $25 per 500. Extra seats cost $10 each per month, and every workspace member counts as a seat. Switching to annual billing is prorated; switching back to monthly takes effect at the next billing date.
Technical specs
API pricing
Public API and MCP access included in Pro and Enterprise
Where Ferndesk excels
Keeping docs current in a product that ships every week
When a pull request renames a setting or moves a button, PR screening drafts the article changes before release, and monthly verification catches anything that slipped through, so the help center does not drift between releases.
Cleaning up an inherited help center after migration
Importing an old Zendesk or Intercom help center and running verification produces a list of articles whose steps, setting names, or screenshots no longer match the app, each with a drafted fix to approve.
Turning repeated tickets into articles
Audits read resolved conversations from tools such as Intercom, Help Scout, or Crisp, and widget analytics show missed searches and failed answers, which points the team to the articles worth writing next.
How Ferndesk fits alongside other tools
Ferndesk and Fin
Fin answers customers inside Intercom and other help desks, drawing on help center content, so its answers depend on how current those articles are. Ferndesk works on the articles: it can import an Intercom help center, read closed Intercom conversations for documentation gaps, and hand unanswered widget questions to Intercom chat with a drafted summary. A team can keep Intercom and Fin for conversations while Ferndesk hosts and maintains the help center.
Ferndesk and Zendesk AI Agents
Zendesk AI Agents resolve requests across messaging, email, and voice inside Zendesk, using help center knowledge. Ferndesk imports Zendesk Guide content with URLs preserved, reads resolved Zendesk tickets to find missing or stale articles, and can open the Zendesk chat composer with a drafted handoff. Zendesk keeps the ticketing and agent workspace, and Ferndesk keeps the docs in line with the product.
Ferndesk and Help Scout
Help Scout combines a shared inbox, a Docs knowledge base, and AI Answers in its Beacon widget. Ferndesk overlaps with the Docs and widget layer, so a team would run one or the other as its help center. With Ferndesk hosting the docs, the Help Scout inbox stays, Fern reads resolved Help Scout tickets for documentation gaps, and widget handoffs open Help Scout chat with a drafted message.
Frequently asked questions
What is Ferndesk?
Ferndesk is a hosted help center from Work Paragon LLC with a built-in AI agent called Fern. Fern checks each article against your codebase, live product, and support tickets, drafts fixes when something has changed, writes articles from merged pull requests, and retakes screenshots. Customers get a public help center, AI answers, and an in-app widget.
How much does Ferndesk cost?
Pro is $149 a month or $1,490 a year and includes the Fern agent, 1,000 AI conversations a month, 5 seats, and 5 languages. Extra conversations are $25 per 500 and extra seats $10 each per month. Companies under $1M ARR with fewer than 10 people can pay $75 a month for the first year. Enterprise starts at $399 a month. Every plan starts with a 7-day trial without a card.
Can Fern maintain docs that stay in Zendesk or Intercom?
No. Fern only verifies and updates articles hosted in Ferndesk. You import your existing help center, which Ferndesk says usually takes under ten minutes with URLs preserved and redirects created, and your support tool keeps handling tickets. Fern can still read tickets from it.
Does Ferndesk replace Intercom, Zendesk, or Help Scout?
It replaces the help center part, not the help desk. Ferndesk reads conversations from Intercom, Zendesk, Help Scout, and other support tools to find documentation gaps, and its widget can hand unanswered questions to Crisp, Intercom, Help Scout, Zendesk, or Pylon with a drafted summary.
Does Ferndesk store my source code?
Ferndesk says it reads repositories through a read-only GitHub App and never writes to them. While Fern works on a task it uses a temporary private copy that is deleted about 30 minutes after last use, and it keeps only the code snippets shown in that task's history. It does not use your code to train AI models.
Does Ferndesk work with Claude, ChatGPT, or Cursor?
Yes, through MCP. Your team can connect Claude, ChatGPT, Cursor, Codex, Claude Code, and other MCP clients to search and read articles, review analytics, and make changes that arrive as drafts. You can also let your readers connect their AI tools to your published help center.
Is Ferndesk SOC 2 certified?
Not yet. Ferndesk's security overview says SOC 2 Type I is expected in October or November 2026 and Type II in Q4 2026 or Q1 2027. Enterprise plans include a data processing agreement and security questionnaire support.
Integrations & fit
About Ferndesk
Most AI support agents answer customers from whatever the help center already says, so they are only as good as those articles. Ferndesk works on the articles themselves. You import your existing help center from Intercom, Zendesk, Help Scout, Crisp, HubSpot, GitBook, Document360, Slite, Docusaurus, or elsewhere (original URLs are kept, and 301 redirects are created for anything that changes), then connect sources: GitHub repositories with read-only access, an authenticated product dashboard, and support tools such as Intercom, Zendesk, Help Scout, Crisp, Pylon, Plain, Gmail, Discord, or Slack. From there Fern does three jobs. Verification pulls each claim out of a published article (navigation steps, setting names, feature behavior, screenshots, API shapes) and checks it against your code, live app, and support replies. It runs monthly on every plan and whenever you click Verify, and claims Fern has no source for, such as pricing policy, are flagged rather than guessed. PR screening reviews each merged pull request, drafts updates to the articles it affects, and can draft changelog entries. Weekly audits read your support conversations, forums, and recent releases to find missing or stale content. Every change comes back as a highlighted draft that you approve, edit, or dismiss, with screenshots retaken when the UI has moved. On the customer side, Ferndesk hosts a public help center on your domain or a /help subfolder, an in-app widget with AI answers that hands off to Intercom, Zendesk, Help Scout, Crisp, or Pylon with a drafted summary, OpenAPI and GraphQL references, private help centers, translations, analytics, an API, and an MCP server for Claude, ChatGPT, Cursor, and Codex. There is one self-serve plan, Pro, at $149 a month after a 7-day trial, with a half-price first year for companies under $1M ARR, and Enterprise from $399 a month. The tradeoffs: Fern only maintains articles hosted in Ferndesk, so you have to move your help center; code-level checks rely on GitHub; the service is not yet SOC 2 certified; and AI conversations, seats, and languages have monthly allowances.
Updates from Ferndesk
Ferndesk launched on Product Hunt on September 30, 2026 and invited users to submit feature requests for the team to ship the same day.
API references now support GraphQL from an SDL file, an introspection export, or a live endpoint, alongside REST, with new sidebar layouts, a Try it playground, and sources that re-sync from GitHub on push or from a URL every six hours.
Fern now reads every published article, extracts each claim, and checks it against the code, live app, support replies, and links, then drafts fixes, including retaken screenshots, for review. The release also added per-workspace GitHub repository selection and custom audit date ranges.
Claude, ChatGPT, Cursor, Codex, and other MCP clients can search and read a Ferndesk help center and create article changes as drafts. The public API now covers articles, drafts, publishing, translations, analytics, feedback, and conversations, and signed webhooks were added.
Are you the founder? Claim this listing →