Your docs are always three sprints behind. Connect your repo and the agent watches the pull requests you merge, writes the pages into a changeset for you to review, and holds it there, while you were going to get to it “next quarter”.
Docs, API references and knowledge bases. One-click migration →
27,000+ docs written
Not autocomplete. A full agent with your repo and your entire docs tree in context. It drafts, restructures, audits, fixes links, and hands you suggestions to accept or bin.
Explore AI features →“Restructure API Basics for a new reader”, and it does all nine pages, links included.
Stale snippets, dead endpoints, contradictions between guides: surfaced, with a fix attached.
Every change lands as a suggestion in a draft. Apply selectively. Nothing publishes behind your back.
Something changes: a PR merges, readers search for something that isn't there, a page gets thumbs-downed. The agent picks it up, writes the answer into a changeset you review in the editor, runs the checks, and waits for one click. That's the whole job.
Every changeset is reviewable, diffable and revertable, and nothing reaches a reader until somebody approves it. Opening the pull request itself is coming soon: today the agent reads the ones you merge and writes up the docs that owe you a change.
Click anywhere and type. Markdown shortcuts if your hands insist, a toolbar if they don't. 30+ block types (tables, tabs, multi-tab code, callouts, drawings) and what you see is exactly what readers get.
Install the SDK, paste your key, make your first call. Five minutes, tops.
Knowledge bases, help centres, internal wikis, product guides, developer portals: one editor, one workflow, one bill. Publish a project to the world or gate it behind SSO, and run as many projects as you need.
Categories, article feedback, reader ratings and search analytics, with the agent drafting answers from tickets you keep re-answering.
Versioning, single-sourced blocks and drafts in review, so a launch is a merge, not a fortnight of copy-paste.
Auto-generated references with try-it requests, generated snippets and CI updates on every build.
SSO or magic links, per-audience conditions, and a search that only shows people what they can actually open.
Drag-and-drop landing designer, custom domain, your CSS, and no DeveloperHub branding anywhere.
Publish one source and gate the sensitive parts per customer, tier or region. Preview as any audience before it ships.
Out-of-the-box migrations from Mintlify, ReadMe and Zendesk: categories, articles, images, code blocks and structure land intact. Sign up and we ask where your docs live today, then bring them across. Markdown, OpenAPI and Git repos import as-is. Every internal link is rewritten to its new URL, so nothing still points back at the old site.
Git sync both ways. MCP so your assistant can publish. A playground developers actually poke at. All shipped, none bolted on.
Your docs become a tool the rest of your AI stack can read and write. No tab-switching, no copy-paste.
Write in the app or in your editor and push. Bidirectional, no winner-takes-all sync. Every PR runs native checks before merge.
Auth, headers and params pre-filled from your spec. OAuth 2.0 flows built in. Snippets in 10+ languages, generated.
Contextual answers with the source page attached, so readers stop opening tickets that your docs already answer.
Visual, Split and Source views over the same spec, with live linting in all three. Friendly forms or raw YAML, your choice.
A block-based, drag-and-drop designer. Drop in a hero, pull cards straight from your docs, then click any block to edit it inline. On-brand and responsive by default.
Top queries, no-hit rates, click positions, per-page helpfulness and inline reader messages, with six months of history. Fix the gap before it becomes a ticket. Export the raw feedback as CSV whenever you want it.
SSO, magic links, JWT or a shared password. Custom CSS and HEAD tags. Conditional blocks so enterprise readers see enterprise content and nobody else does.
Per-reader access. Magic links need zero developer time.
Wrap any block in a condition; preview as any audience.
Zero DeveloperHub branding. Live draft preview before publish.
Synced blocks, edited once, updated everywhere.
Clone a version; links migrate themselves.
Native, with RSS, drafted by the agent.
Numbered, synced multi-language walkthroughs.
docs.acme.dev or acme.dev/docs.
Drag-and-drop docs home, no code.
Meta, sitemaps, and AI summaries for LLMs.
Any version, formatted, for the procurement folder.
Translate the portal UI into any language.
GA, Intercom, Slack, HubSpot, custom JS.
Search and embed docs inside your product.
Push your spec on every build.
Cybersecurity platforms, fintechs, identity providers and open-source projects: 27,000+ documentation sections written and a 4.8★ average on G2.
“Our customers can find what they are looking for, proven by the decrease in the support ticket volume. … It is no longer just about writing documentation; it is about writing, analysing, gathering feedback and iterating to provide the best experience possible.”
“We have APIs and SDKs which we monetise through and they need to be explained. … For them to easily integrate, we need to provide great documentation and this is where DeveloperHub comes in.”
“Lots of time was saved for our customers and us internally. … They can now find the answers they are looking for on their own. By doing that, we are avoiding having multiple calls to go through things. So we get a happy customer and time savings on our end.”
From $99/month, 14-day trial, no card. Skip the six-figure quote and the team to maintain it.
Point the agent at your repo and see what it drafts. Fourteen days free, no card, no sales call unless you want one.
