Ferndesk

Ferndesk is a complete help center built around an agent called Fern that checks every article against your product, catches what has changed, and drafts the fixes for you. It is aimed at software teams that publish customer documentation and find it impossible to keep that documentation true while shipping features every week. Instead of treating a help center as a static set of pages that slowly drifts out of date, Ferndesk treats it as something that is continuously verified against the codebase, the live product and the support inbox, so the answers customers read match what the product actually does. The problem it solves is familiar to almost every software company. This month you changed a default, and yet your docs were last updated three months ago. Along the way you renamed a plan, killed a feature, moved the export button, added a plan, changed the pricing page, broke a link, shipped a new flow, renamed a button and changed a setting. None of those changes is dramatic on its own, but together they quietly make a knowledge base wrong. Ferndesk frames this as not the team's fault: keeping docs true while you ship every week is genuinely tough, and most teams fall back on hoping they will remember to update the documentation. The site quotes founders describing exactly this reality, including one who says their previous process for updating documentation was basically hoping they would remember to do it, another who says they ship features every week and updating docs is hell, and another who admits they used to write articles once and let them go stale right from day one. The first core capability is verification. Fern verifies every article in the help center and drafts the fix when something is wrong. Each claim is checked against the code and the product, and anything that is no longer true comes back as a change you approve, together with the reason it was flagged. A typical example shown on the site is a sentence that says a setting lives under Settings, Billing when it has actually moved to Settings, Plans and Billing; Ferndesk surfaces the outdated claim, proposes the corrected wording, and presents it for you to approve and publish. Nothing publishes without you. The second half of this capability is automatic updates for new releases: when a pull request merges, Fern drafts the documentation for that feature before the release goes out, so new functionality is documented as part of shipping rather than months later. The site illustrates this with a merged pull request that adds image editing, after which Fern drafts the docs for editing images in articles and updates the article about automating screenshots in your docs. Beyond verification and drafting, Ferndesk is a full help center product. It provides a public help center that can live on your own domain or at /help, and it is described as fast, searchable, and indexed both by Google and by AI search engines. AI conversations let customers ask questions in plain language and receive answers drawn from your verified docs rather than a guess, which matters because an AI answer is only as trustworthy as the documentation behind it. An in-app widget can be embedded with one script tag and brings search, articles and AI chat inside your product, exactly where people get stuck. Together these surfaces give customers more ways to answer their own questions before they ever open a ticket. Ferndesk also covers the more specialized documentation needs that usually require extra tools. API documentation provides an OpenAPI reference with a try-it playground that sits next to your customer docs. Private docs support magic link, OIDC or JWT access, so the same system can serve customer-facing documentation, partner documentation or an internal knowledge base for your own team. Translations produce a multilingual help center with a glossary and language-prefixed routes. Analytics surface searches, missed searches, failed answers and feedback, so you can see what to write next instead of guessing which articles are missing. Escalation connects the widget to your existing support stack: when the widget cannot answer a question, it hands the conversation off to Intercom, Zendesk or Help Scout. Ferndesk works by connecting to the tools where the truth about your product already lives. You connect your codebase, your live product and your support inbox, and the site lists GitHub, Intercom, Linear, Zendesk, your live app, Slack, Help Scout and Discord among the connectors. Setup is described as taking about ten minutes, after which Fern can see what your customers see. From that point on, verification runs continuously rather than as a one-off audit: every article is checked against what the product actually does, incorrect claims are turned into reviewable changes, and newly shipped features are drafted into articles. The workflow keeps a human in the loop at all times, since you review and approve and Fern publishes. Ferndesk also lets you manage your docs from tools such as Claude Code, Cursor or ChatGPT, meeting documentation work where developers already are. The benefits reported by customers are concrete. Ferndesk states that founders report saving 20 hours a month on docs, with one founder saying that a task which used to take an hour now takes five minutes. Because the docs Fern keeps current are the same docs a support AI trains on, better documentation also produces better AI answers. Customers describe support requests dropping significantly, and one customer reports a measurable drop in churn within three months of launch. Another says they have started to get organic clicks for queries and questions they did not expect to be ranking for. Together these point to a help center that reduces tickets, keeps customers self-serving, and continues to work as a marketing and search asset even after launch. Typical use cases follow directly from that. A team that ships weekly connects its repository so that merged pull requests turn into drafted documentation before each release. A company with a stale help center imports its existing articles and gets a verified, searchable public portal, then adds AI conversations and an in-app widget to bring tickets down. A support-driven company keeps its existing ticketing tool and uses Ferndesk for the knowledge layer, with the widget escalating unanswered questions into Intercom, Zendesk or Help Scout. A team selling internationally adds translations to run a multilingual help center, as Metricool did with seven languages live while using the same docs to train their AI support agents. A company with private or partner-facing material uses magic link, OIDC or JWT protected docs for audiences that should not see the public portal. And a content-led team reviews analytics to find missed searches and failed answers, then writes the articles those queries reveal. Ferndesk is used by more than 100 software teams, including Metricool, Zeffy, Andri, PixelFlow and SEO Gets, and is positioned for founders and support teams at software companies of varying size. Migration is deliberately low friction. Imports are supported from Intercom, Zendesk, Crisp, Help Scout, HubSpot, GitBook, Document360 and other help centers, with every URL preserved and redirects created, usually in under ten minutes, and your existing support tool stays where it is. A custom domain is supported, and customers can keep their knowledge base at a subfolder of their own domain. Getting started is a 7-day free trial with no card required, and nothing publishes without your approval. The takeaway is that Ferndesk turns documentation from something you hope is right into something you know is right. It combines a complete help center, covering the public portal, AI conversations, the in-app widget, API documentation, private docs, translations, analytics and escalation, with an agent that verifies every article against your product, drafts the fixes, documents new releases as they merge, and leaves the final decision to you. For teams whose docs have been stale for months, the promise is a help center that never goes stale, imported in ten minutes and kept current from then on.