Skip to content

Developer Docs Platforms Arena

Developer Docs Platforms arenaBuyer checklist

Every requirement we judge developer docs platforms products against, as a ready-to-send RFP checklist — with each item's priority, why it matters, and how the top-ranked products score on it today.

53 requirements · 14 themes · verdicts for 5 products · updated 2026-09-16 · priorities mirror the story weights our scoring uses (methodology)

Procurement report →
Show the markdown export
# Developer Docs Platforms — buyer checklist (RFP)

Derived from ProductArena's evidence-graded user-story taxonomy for Developer Docs Platforms: 53 judged requirements. Priorities mirror story weights (3 = must-have, 2 = should-have, 1 = nice-to-have).

## Agenticness

- [ ] **[must-have]** Plug MCP servers into this product so it can use their tools
- [ ] **[must-have]** Connect an agent via an official MCP server
- [ ] **[must-have]** Drive the product through a documented public API
- [ ] **[must-have]** Delegate tasks to a built-in AI assistant inside the product
- [ ] **[should-have]** Point an agent at llms.txt or agent-oriented docs
- [ ] **[should-have]** Run the product headlessly / in CI for automation
- [ ] **[should-have]** Use an official CLI
- [ ] **[should-have]** Issue scoped/least-privilege API credentials for an agent
- [ ] **[should-have]** Build against official SDKs
- [ ] **[should-have]** Subscribe to events via webhooks
- [ ] **[should-have]** Get AI-generated insights and suggestions from my data inside the product
- [ ] **[should-have]** Set up automations that run autonomously in the background
- [ ] **[should-have]** Operate the product with natural-language commands
- [ ] **[should-have]** Explore an interactive API reference with runnable examples
- [ ] **[should-have]** Download a machine-readable API spec (OpenAPI or equivalent)
- [ ] **[should-have]** Rely on versioned APIs with a documented deprecation policy
- [ ] **[nice-to-have]** Test against a sandbox environment without touching production data

## Ai docs

- [ ] **[must-have]** My published docs site exposes its own MCP server that my users' agents can query for search and page content
- [ ] **[must-have]** My published docs site automatically serves llms.txt (and a full-content variant) so agents can index it
- [ ] **[must-have]** Every published page serves clean markdown at its URL (e.g. appending .md) so agents skip the HTML
- [ ] **[should-have]** An embedded AI assistant on my docs site answers reader questions with citations into my content
- [ ] **[should-have]** A platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests

## Analytics insights

- [ ] **[should-have]** My docs analytics distinguish AI-agent traffic from human traffic so I can see who — or what — is actually reading
- [ ] **[should-have]** I see page views, search terms, and reader feedback so I know which docs work and which fail

## Api reference

- [ ] **[must-have]** My API reference pages are generated from an OpenAPI spec and stay in sync when the spec changes
- [ ] **[should-have]** Readers can try real API calls from an interactive playground embedded in the reference docs

## Authoring editing

- [ ] **[must-have]** I author pages in Markdown/MDX with rich components — tabs, callouts, code groups, steps — without writing custom HTML
- [ ] **[should-have]** Non-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truth
- [ ] **[should-have]** Automated checks lint my content against a style guide and flag issues before they publish
- [ ] **[nice-to-have]** Reusable snippets and variables keep repeated content in sync across pages

## Automation depth

- [ ] **[must-have]** Define rules that trigger actions automatically on events
- [ ] **[should-have]** Perform bulk operations across many items at once
- [ ] **[should-have]** Schedule recurring jobs or workflows
- [ ] **[nice-to-have]** Version, review, and roll back my automations

## Collaboration review

- [ ] **[should-have]** Teammates propose changes that go through review — comments, approvals, and a merge step — before they publish

## Customization

- [ ] **[should-have]** I customize themes, fonts, and layout — down to custom CSS/JS or my own components — so the docs match my brand

## Docs as code

- [ ] **[must-have]** My docs live in my own git repository — branches, pull requests, and merges drive what gets published
- [ ] **[should-have]** Every docs pull request gets a shareable preview deployment before it merges
- [ ] **[should-have]** CI validation catches broken links and invalid configuration before the site publishes

## Openness

- [ ] **[must-have]** Export all of my data in open formats and leave
- [ ] **[must-have]** Self-host the core product
- [ ] **[should-have]** Do everything through the API that I can do in the UI
- [ ] **[should-have]** Read the product's source under an open license

## Privacy posture

- [ ] **[must-have]** Prevent my data from being used to train AI models
- [ ] **[should-have]** Choose where my data is stored (region/residency)
- [ ] **[should-have]** Control data retention and deletion
- [ ] **[should-have]** Opt out of telemetry and usage tracking

## Publishing hosting

- [ ] **[should-have]** I serve docs on my own custom domain or as a /docs subpath of my main site
- [ ] **[should-have]** Export my entire docs site as a static bundle and host it anywhere, so my content is never locked in
- [ ] **[nice-to-have]** I gate some or all docs behind authentication — password, JWT, or SSO — for customers-only content

## Search discovery

- [ ] **[must-have]** Readers get fast, typo-tolerant, relevance-ranked search over the whole docs site out of the box

## Versioning localization

- [ ] **[must-have]** I publish versioned documentation per product or API version, and readers switch versions from the site
- [ ] **[nice-to-have]** I publish my docs in multiple languages with translated navigation and content

---

Source: https://ultrametric.ai/productarena/arena/docs-platforms (evidence-graded verdicts for 5 products) · methodology: https://ultrametric.ai/productarena/methodology

Chips show the top 5 ranked products' current verdict on each requirement — ✓ full · ~ partial · ! disputed · — none · n/a not applicable.

Agenticness — how well agents can access and operate the productAgenticness· 17 items

How well agents can access and operate the product

Ai docs — stories about ai docs in this arenaAi docs· 5 items

Stories about ai docs in this arena

  • ai-native userMy published docs site exposes its own MCP server that my users' agents can query for search and page content

    Core requirement — weighs 3× in arena scoring · 4 of 5 products fully deliver this today

    must-have
  • ai-native userMy published docs site automatically serves llms.txt (and a full-content variant) so agents can index it

    Core requirement — weighs 3× in arena scoring · 4 of 5 products fully deliver this today

    must-have
  • ai-native userEvery published page serves clean markdown at its URL (e.g. appending .md) so agents skip the HTML

    Core requirement — weighs 3× in arena scoring · 3 of 5 products fully deliver this today

    must-have
  • ai-native userAn embedded AI assistant on my docs site answers reader questions with citations into my content

    Important, not disqualifying — weighs 2× in arena scoring · 3 of 5 products fully deliver this today

    should-have
  • ai-native userA platform AI agent drafts, updates, and reviews my docs — from a prompt, a PR, or a schedule — and ships its work as change requests

    Important, not disqualifying — weighs 2× in arena scoring · 3 of 4 products fully deliver this today

    should-have

Analytics insights — stories about analytics insights in this arenaAnalytics insights· 2 items

Stories about analytics insights in this arena

  • ai-native userMy docs analytics distinguish AI-agent traffic from human traffic so I can see who — or what — is actually reading

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • devrel leadI see page views, search terms, and reader feedback so I know which docs work and which fail

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have

Api reference — stories about api reference in this arenaApi reference· 2 items

Stories about api reference in this arena

  • developerMy API reference pages are generated from an OpenAPI spec and stay in sync when the spec changes

    Core requirement — weighs 3× in arena scoring · 3 of 5 products fully deliver this today

    must-have
  • developerReaders can try real API calls from an interactive playground embedded in the reference docs

    Important, not disqualifying — weighs 2× in arena scoring · 3 of 5 products fully deliver this today

    should-have

Authoring editing — stories about authoring editing in this arenaAuthoring editing· 4 items

Stories about authoring editing in this arena

  • technical writerI author pages in Markdown/MDX with rich components — tabs, callouts, code groups, steps — without writing custom HTML

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-have
  • technical writerNon-technical teammates can edit docs in a visual web editor without touching git, and their changes flow into the same source of truth

    Important, not disqualifying — weighs 2× in arena scoring · 4 of 5 products fully deliver this today

    should-have
  • technical writerAutomated checks lint my content against a style guide and flag issues before they publish

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have
  • technical writerReusable snippets and variables keep repeated content in sync across pages

    Differentiator, not a dealbreaker — weighs 1× in arena scoring · 2 of 5 products fully deliver this today

    nice-to-have

Automation depth — how much of the product can run unattendedAutomation depth· 4 items

How much of the product can run unattended

Collaboration review — stories about collaboration review in this arenaCollaboration review· 1 item

Stories about collaboration review in this arena

  • technical writerTeammates propose changes that go through review — comments, approvals, and a merge step — before they publish

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 4 products fully deliver this today

    should-have

Customization — bending the product to your needs — settings, theming, extension pointsCustomization· 1 item

Bending the product to your needs — settings, theming, extension points

  • devrel leadI customize themes, fonts, and layout — down to custom CSS/JS or my own components — so the docs match my brand

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 5 products fully deliver this today

    should-have

Docs as code — stories about docs as code in this arenaDocs as code· 3 items

Stories about docs as code in this arena

  • developerMy docs live in my own git repository — branches, pull requests, and merges drive what gets published

    Core requirement — weighs 3× in arena scoring · 4 of 5 products fully deliver this today

    must-have
  • developerEvery docs pull request gets a shareable preview deployment before it merges

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 4 products fully deliver this today

    should-have
  • developerCI validation catches broken links and invalid configuration before the site publishes

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Openness — open source, data portability, and self-hosting storiesOpenness· 4 items

Open source, data portability, and self-hosting stories

Privacy posture — data-handling and privacy storiesPrivacy posture· 4 items

Data-handling and privacy stories

Publishing hosting — stories about publishing hosting in this arenaPublishing hosting· 3 items

Stories about publishing hosting in this arena

  • devrel leadI serve docs on my own custom domain or as a /docs subpath of my main site

    Important, not disqualifying — weighs 2× in arena scoring · 4 of 5 products fully deliver this today

    should-have
  • developerExport my entire docs site as a static bundle and host it anywhere, so my content is never locked in

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have
  • devrel leadI gate some or all docs behind authentication — password, JWT, or SSO — for customers-only content

    Differentiator, not a dealbreaker — weighs 1× in arena scoring · 1 of 5 products fully deliver this today

    nice-to-have

Search discovery — stories about search discovery in this arenaSearch discovery· 1 item

Stories about search discovery in this arena

  • developerReaders get fast, typo-tolerant, relevance-ranked search over the whole docs site out of the box

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-have

Versioning localization — stories about versioning localization in this arenaVersioning localization· 2 items

Stories about versioning localization in this arena

  • developerI publish versioned documentation per product or API version, and readers switch versions from the site

    Core requirement — weighs 3× in arena scoring · 2 of 5 products fully deliver this today

    must-have
  • technical writerI publish my docs in multiple languages with translated navigation and content

    Differentiator, not a dealbreaker — weighs 1× in arena scoring · 1 of 5 products fully deliver this today

    nice-to-have

Full evidence behind every verdict lives on the arena page and each product page — chips above deep-link straight to the judged story.