Ferndesk

Fern reads each article and checks its claims against what the product actually does, using the connected codebase and a working copy of the app. A screenshot that shows an old menu, a step that references a removed button, a pricing detail that shifted: each one is flagged with the specific mismatch. You get a list of proposed edits rather than a vague warning that something may be out of date.

The importer brings over articles, images, and URL paths in one pass, then sets up redirects for anything that has to move. That matters for search rankings, because a help center rebuild usually costs months of organic traffic when old links start returning 404s. Imports from Intercom, Zendesk, Crisp, Help Scout, HubSpot, GitBook, and Document360 are supported, and the company says a typical migration finishes in about ten minutes.

When a pull request merges, Fern can write the help article before the release ships. It reads the change, works out which customer-facing behavior moved, and drafts an update or a new page. A founder who used to write docs a month late ends up publishing on the same day as the feature, which is the difference between a help center that helps and one that misleads.

Every week, Fern scans the support inbox, community threads, and recent releases to find articles that are missing, stale, or contradicted by the product. Each finding becomes an issue you can assign back to Fern, and the fix comes back as a draft within minutes. The Pro plan includes 1,000 scheduled audits a month, well past what most small teams use.

Ferndesk exposes API and MCP access, so you can manage docs from the tools you already have open. Ask Claude Code to rewrite a set of articles for a new feature name, or have Cursor check whether a documented endpoint still exists. Fern applies the changes inside Ferndesk as a person would, and you review the result before it publishes. For teams that live in an editor, this removes the context switch to a separate admin panel.

Beyond the agent, Ferndesk ships the parts a support site needs: a public portal, AI answers built from your articles, an in-app widget, API documentation, private and authenticated docs with SSO, OIDC, or magic links, translations, analytics, and white labeling with five branded instances included. Five seats come with the plan, and role-based permissions separate who can draft from who can publish.