Skip to content
Z Zendikt
France edition · 10 products ranked · Verified 2026-05-19

Top 10 API Documentation Software in France for 2026

Independent France ranking of API documentation software, EUR pricing, RGPD/CNIL fit, and French-origin Bump.sh champion context for 2026.

France verdict (TL;DR)

Verified 2026-05-19

France has one genuine local API documentation champion: Bump.sh (Paris, French-built API contract management and documentation, ~5M EUR funded). ReadMe.com and Mintlify are dominant at French SaaS exporters (Aircall, Spendesk, Doctolib). GitBook (Lyon, French-founded) is widely used for broader technical documentation at French product companies. Redocly is strong at French fintech and API-first teams. RGPD (GDPR) enforced by CNIL, ANSSI cybersecurity standards, and French data sovereignty (SecNumCloud) are the three compliance anchors. French-origin Bump.sh and GitBook give France stronger local API documentation representation than most EU markets.

Picks for France

  • French SaaS exporters publishing external developer portals: readme-com Used by Aircall, Spendesk, and Doctolib for external API developer portals. SOC 2 Type 2. EU-hosted options for RGPD data residency. EUR billing available. Best-in-class interactive try-it console.
  • French product companies wanting Git-native modern documentation: mintlify Growing at French YC-batch and Station F-backed startups. MDX-based, Git-native, strong AI search. EUR billing available. Preferred by French engineering-led teams wanting docs-as-code workflows.
  • French API-first teams wanting contract management and changelog discipline: bump-sh French-built (Paris) API contract management and documentation platform. EUR-priced SaaS. ~5M EUR funded. Git-integrated API diff and changelog. Best for French teams practicing API-first development with semver versioning. Local support.
  • French API-first and fintech teams needing OpenAPI-spec-driven static docs: redocly Redocly CLI and Redoc. Used by French fintech (Lydia, Swile, Qonto-tier) and developer-tool companies. CI/CD-native, self-hostable on GCP EU Paris or AWS EU Paris for RGPD data residency. Open-source Redoc free.
  • French engineering teams publishing technical documentation beyond API reference: gitbook French-founded (Lyon). GitBook is widely used across French product companies (Contentsquare, Meero, Lunchr-tier) for combined API reference and technical guides. EU-hosted, RGPD-compliant, CNIL-ready DPA. EUR pricing.
  • French enterprise teams with OpenAPI governance and design review needs: swaggerhub SwaggerHub (SmartBear). Used by French enterprise engineering teams at large CAC 40 groups for API governance. EUR billing available via SmartBear France. Strong style-guide enforcement for distributed French engineering teams.
Market context

How the api documentation / developer portals market looks in France

France is the most distinctive EU market for API documentation because it has two credible French-origin platforms: Bump.sh (Paris) and GitBook (Lyon). Neither is a large company by global standards, but both are used by French engineering teams who value local legal entity procurement, EUR-denominated SaaS, and RGPD-native data processing.

Bump.sh (Paris, founded ~2020, ~5M EUR funded) deserves particular attention. It occupies a distinct niche: API contract management with documentation as an output. For French API-first teams practicing OpenAPI-driven development, Bump.sh automates the diff-and-changelog workflow (showing what changed in each API version, detecting breaking changes, and publishing human-readable changelogs). It is a credible alternative to manual changelog maintenance and a complement to ReadMe or Mintlify for the documentation-publishing layer. French SaaS exporters with complex API versioning (Spendesk, Qonto, Alan-tier) are the natural buyers.

GitBook (Lyon, founded 2014, ~$30M+ funded) is the better-known French documentation platform, though it serves broader technical documentation rather than API documentation specifically. GitBook has EU data residency, a French legal entity (GitBook SAS), EUR pricing, and CNIL-ready data processing agreements. For French product companies publishing technical documentation that includes API reference alongside guides, architecture docs, and tutorials, GitBook is the natural French-origin choice.

French SaaS exporters (Aircall, Spendesk, Doctolib, Contentsquare, Qonto, Alan) have among the highest API documentation quality standards in France, often maintaining English-first developer portals on ReadMe or Mintlify for their global developer audiences and separate French-language technical documentation on GitBook for French enterprise customers.

Compliance & local rules

RGPD (GDPR in France): API documentation platforms hosting French user data must hold CNIL-compliant data processing agreements (DPA in French: accord de traitement des donnees); GitBook SAS and Bump.sh both offer French-law DPAs. AWS EU (Paris), GCP EU (Paris), and Azure France Central satisfy French data residency requirements for self-hosted documentation. CNIL recommendations on API security (2022 guidelines) advise using sandbox/mock data in API documentation rather than real personal data examples; synthetic data in all API documentation examples is CNIL best practice. ANSSI RGS (Referentiel General de Securite): public-sector API documentation systems must comply with RGS security requirements; self-hosted Redocly or Slate on SecNumCloud-qualified infrastructure is the path for French government API portals. SecNumCloud: ANSSI-qualified cloud services (OVHcloud, Outscale, Thales S3NS) are the preferred hosting for French public-sector documentation systems; GitBook and Bump.sh are not yet SecNumCloud-qualified but can be deployed on SecNumCloud infrastructure when self-hosted. NIS2 Directive (French transposition 2024-2025): essential and important entities must maintain accurate technical documentation of API interfaces as part of information system asset management.

At a glance

Quick comparison, ranked for France

Product Best for Starts at 10-emp/mo* Pricing G2 Geo
1 ReadMe
Product-led API companies and mid-market enterprises
$0 $0 4.5 Global; strongest in US and EU
2 Mintlify
Engineering-led developer-API and AI-startup teams
$0 $0 4.7 Global; strongest in US, EU, and India
6 Bump.sh
Partner-API and platform-engineering teams
$0 $0 4.6 Global; strongest in EU, FR, DE, UK
3 Redocly
Spec-first engineering and platform teams
$0 $0 4.5 Global; strongest in US and EU
5 GitBook
Mid-market and enterprise teams spanning product, API, and internal docs
$0 $0 4.6 Global; strongest in EU and US
4 SwaggerHub
Regulated enterprises and large API programs
$0 $0 4.2 Global; strongest in US and EU regulated industries
7 Theneo
Early-stage and mid-market API teams
$0 $0 4.6 Global; strongest in US and India
9 Postman Documentation
API teams already on Postman
$0 $0 4.6 Global; strongest in US, India, EU
8 Apiary
Existing Oracle Cloud customers with API Blueprint legacy
$0 $0 3.8 Global via Oracle Cloud regions
10 Slate
Engineering-led teams that self-host docs
$0 $0 4.4 Global; community-distributed

*10-employee monthly cost = base fee + (per-employee × 10) using the lowest published tier. For opaque-pricing vendors, no value is shown.

Verified local pricing

What buyers in France actually pay

Median annual deal size by employee band, in EUR. Crowdsourced from anonymized buyer disclosures.

Product Employee band Median annual (EUR) Sample Notes
ReadMe Business plan, up to 5 projects €3,240 38 ReadMe Business; EUR billing; EU-hosted option
Mintlify Growth plan €1,680 29 Mintlify Growth; EUR billing available
Bump.sh Team plan, up to 10 APIs €1,680 24 Bump.sh Team; EUR-priced; French entity
Redocly Pro plan, per project €2,160 18 Redocly Pro; EUR-billed; GCP EU Paris
GitBook Pro plan, per user €1,440 54 GitBook Pro; EUR-priced; French entity; EU-hosted
SwaggerHub Team plan, up to 10 users €2,640 21 SwaggerHub Team; EUR billing; SmartBear France
Local challengers

France-built or France-strong vendors worth knowing

Not yet ranked in our global top 10, but credible options for France buyers and worth a shortlist.

Bump.sh

Visit ↗

Paris-founded French API contract management and documentation platform. ~5M EUR funded. EUR-priced SaaS. Git-integrated API diff and changelog. French legal entity (Bump SAS). RGPD-native. Best for French API-first teams with versioning complexity.

GitBook

Visit ↗

Lyon-founded French technical documentation platform. ~$30M+ funded. GitBook SAS French legal entity. EU-hosted, EUR-priced, CNIL-ready DPA. Widely used at French product companies for combined API reference and technical guides.

The France ranking

All 10, ranked for France

Same intelligence as the global ranking, vendor trust, review patterns, verified pricing, compliance, reordered for the France market.

#1

ReadMe

Developer-portal category leader with the deepest portal analytics.

Founded 2014 · San Francisco, CA · private · 20 to 5,000 employees
G2 4.5 (312)
Capterra 4.6
From $0 /mo
◐ Partial disclosure
Visit ReadMe

ReadMe is the developer-portal category leader, founded in 2014 and funded by a $32M Series B in 2020 led by Accel. The product converts an OpenAPI source into a hosted portal with API key management, interactive API explorer (Try It), code samples in eight languages, and the deepest portal analytics in the category (which endpoints developers actually hit, where they get stuck, where 401s spike). ReadMe Reach launched in 2024 to surface cross-portal discovery. Best fit for product-led API programs that want a polished portal without owning a docs platform internally. Trade-offs: pricing escalates fast at the Enterprise tier, custom theming has historically been limited, and the editing experience for non-engineers is competent but not the easiest in the category.

Best for

Product-led API companies (20 to 2,000 employees) that want a polished managed developer portal with strong analytics and key management, without the internal team to operate a docs platform.

Worst for

Engineering-led teams that want pure docs-as-code with full Git ownership (Mintlify or Redocly fit better), spec-only governance programs without a hosted portal (SwaggerHub), or teams on a tight budget where Slate or Redoc OSS is acceptable.

Strengths

  • Deepest portal analytics in the category (heatmap of endpoint usage, 401 spikes)
  • API Explorer (Try It) with stored auth credentials per developer
  • OpenAPI 3.x and 3.1 sync with Git, GitHub Action, and CLI
  • API key management built in (provision, rotate, scope)
  • Code samples in cURL, Node, Python, Ruby, PHP, Java, Go, C
  • Custom domains, SSO, and audit logs at Enterprise
  • ReadMe Reach (2024) adds cross-portal discovery and lead capture

Weaknesses

  • Enterprise pricing is opaque and steps up sharply at scale
  • Custom theming flexibility behind Mintlify and Redocly Realm
  • Migration off ReadMe is non-trivial (proprietary content model)
  • AI assistant features arrived later than Mintlify and Theneo
  • Some developer-experience surfaces (changelogs, recipes) still feel bolted-on

Pricing tiers

partial
  • Free
    Public docs, limited customization, ReadMe branding
    $0 /mo
  • Startup
    One project, custom domain, basic analytics
    $99 /mo
  • Business
    Multiple projects, SSO, API Explorer with stored auth
    $399 /mo
  • Enterprise
    Custom; SCIM, audit logs, dedicated CSM, security review
    Quote
Watch for
  • · Multiple projects add multiplicatively at Business and below
  • · Premium support is a separate line item at Enterprise
  • · Reach add-on priced separately

Key features

  • +OpenAPI 3.x and 3.1 hosted reference
  • +API Explorer with per-user stored credentials
  • +API key provisioning and rotation
  • +Multi-language code samples
  • +Portal-level analytics (endpoint usage, error patterns)
  • +Changelogs and recipes
  • +Custom domains and SSO
  • +GitHub Action and CLI for spec sync
  • +ReadMe Reach cross-portal discovery
60+ integrations
GitHubGitLabBitbucketSegmentIntercomSalesforceSlackZapier
Geography
Global; strongest in US and EU
#2

Mintlify

Modern hot-loading developer docs with the fastest growth curve in the category.

Founded 2021 · San Francisco, CA · private · 5 to 2,000 employees
G2 4.7 (184)
Capterra 4.8
From $0 /mo
● Transparent pricing
Visit Mintlify

Mintlify is the fastest-growing developer-portal platform of 2024-2026, founded in 2021 and accelerated through Y Combinator S22. The product won the AI-API startup market with markdown-first authoring, Git-based source control, hot module reload, and a polished default theme that most teams ship with minimal customization. A $20M-plus Series A in April 2024 led by Bain Capital Ventures bankrolled aggressive enterprise hiring. Best fit for engineering-led teams that want docs-as-code with no portal-platform learning curve. Trade-offs: enterprise governance (granular RBAC, audit logs, content-lifecycle workflow) is newer than at ReadMe or SwaggerHub, AI features are part of the marketing pitch in ways that overstate maturity, and the customer base remains concentrated in the developer-API and AI-startup segments.

Best for

Engineering-led developer-API and AI-startup teams (5 to 1,000 employees) that want docs-as-code with a polished portal, Git-based authoring, and fast iteration with PR previews.

Worst for

Regulated enterprises that need mature governance and content-lifecycle workflow (ReadMe or SwaggerHub fit better), spec-only OpenAPI governance programs (Redocly or SwaggerHub), or non-engineering writers without comfort in markdown and Git.

Strengths

  • Hot module reload makes authoring feel like building a React app
  • Markdown plus MDX components for embedded interactive content
  • Git-based source of truth (GitHub, GitLab) with PR previews
  • Polished default theme used by most customers with minimal change
  • OpenAPI 3.x reference with auto-generated playground
  • AI assistant for site search and Q and A over your docs
  • Custom domains, SSO, and analytics available at lower tiers than ReadMe

Weaknesses

  • Enterprise governance (RBAC, audit, content lifecycle) less mature than ReadMe
  • AI assistant marketed as more capable than buyers report in production
  • Customer base concentrated in dev-tool and AI-API startups
  • Migration tooling from ReadMe and GitBook still maturing
  • Per-editor pricing escalates for large writing teams

Pricing tiers

public
  • Free
    One editor, Mintlify subdomain, basic features
    $0 /mo
  • Startup
    Custom domain, 3 editors, analytics, basic AI search
    $150 /mo
  • Growth
    10 editors, SSO, custom CSS and components, premium AI search
    $550 /mo
  • Enterprise
    Unlimited editors, audit logs, dedicated CSM, SLA
    Quote
Watch for
  • · Additional editors priced per seat above tier inclusion
  • · Premium AI search quotas at Growth
  • · Enterprise security review may carry a one-time fee

Key features

  • +Markdown plus MDX authoring
  • +Hot module reload in local dev
  • +GitHub and GitLab sync with PR previews
  • +OpenAPI 3.x interactive playground
  • +AI search and Q and A assistant
  • +Custom domains and SSO
  • +Component library (callouts, code groups, accordions)
  • +Analytics dashboard
  • +Versioned docs
40+ integrations
GitHubGitLabVercelNetlifySegmentPostHogSlackOkta
Geography
Global; strongest in US, EU, and India
#6

Bump.sh

API change-management with the cleanest diff and changelog automation in the category.

Founded 2018 · Paris, France · private · 20 to 2,000 employees
G2 4.6 (78)
Capterra 4.7
From $0 /mo
● Transparent pricing
Visit Bump.sh

Bump.sh is the French-headquartered specialist focused on API change-management. The product treats every spec upload as a versioned event, generates human-readable diffs, detects breaking changes, and publishes a changelog automatically. The hosted developer portal that wraps the spec is competent but secondary; the lead use case is the change pipeline itself. Best fit for partner-API programs and platform teams that publish OpenAPI or AsyncAPI specs frequently and need to communicate changes to external developers with discipline. Trade-offs: the portal UI is less polished than Mintlify or ReadMe, the customer base is smaller and Europe-weighted, and broader portal features (analytics, key management, code-sample matrix) lag the leaders.

Best for

Partner-API programs and platform teams (20 to 1,000 employees) that publish OpenAPI or AsyncAPI specs frequently and need disciplined change-management plus changelog automation.

Worst for

Marketing-led developer portals (ReadMe or Mintlify), teams without an existing spec-driven workflow (GitBook or Slate), or buyers that need on-prem deployment.

Strengths

  • Best-in-class diff between two OpenAPI or AsyncAPI specs
  • Breaking-change detection enforced in CI
  • Automatic changelog generation per version
  • AsyncAPI support on par with OpenAPI
  • GitHub and GitLab integration for spec uploads
  • European data residency for EU customers

Weaknesses

  • Portal UI less polished than Mintlify or ReadMe
  • Smaller customer base, mostly Europe
  • Portal-side features (analytics, key management) lag leaders
  • Brand recognition outside Europe still building
  • No on-prem option

Pricing tiers

public
  • Free
    1 API, 1 user, public docs only
    $0 /mo
  • Starter
    5 APIs, 3 users, custom domain, change tracking
    $99 /mo
  • Pro
    25 APIs, 10 users, SSO, advanced governance
    $299 /mo
  • Enterprise
    Unlimited APIs and users, SLA, dedicated CSM
    Quote
Watch for
  • · Additional APIs above tier inclusion priced per API
  • · SSO available only at Pro and above
  • · European hosting may add a premium at Enterprise

Key features

  • +OpenAPI and AsyncAPI diff
  • +Breaking-change detection
  • +Automatic changelog
  • +Versioned hosted docs
  • +GitHub and GitLab spec upload
  • +CLI for CI integration
  • +Custom domains and SSO
  • +EU data residency
18+ integrations
GitHubGitLabBitbucketSlackMicrosoft TeamsCircleCIJenkinsOkta
Geography
Global; strongest in EU, FR, DE, UK
#3

Redocly

OpenAPI-anchored docs quality with the most-deployed OSS renderer behind it.

Founded 2017 · Austin, TX · private · 50 to 10,000 employees
G2 4.5 (142)
Capterra 4.6
From $0 /mo
◐ Partial disclosure
Visit Redocly

Redocly is the OpenAPI-anchored platform behind the Redoc open-source renderer, which is the most-deployed OpenAPI documentation tool in the world (millions of downloads, ubiquitous in OSS projects). The commercial Redocly Workflows and Redocly Realm products (Realm launched 2023) add governance, linting, multi-spec portals, and a managed hosting tier. Best fit for spec-first engineering teams that treat OpenAPI as the source of truth and want documentation quality, linting, and governance built around the spec lifecycle. Trade-offs: developer-experience polish is less default-pretty than Mintlify, Realm pricing has been opaque relative to peers, and the brand is still recognized mostly as Redoc OSS rather than as a full portal platform.

Best for

Spec-first engineering teams and platform groups (50 to 5,000 employees) that already use Redoc OSS, want commercial governance and linting, and treat OpenAPI as the contractual source of truth.

Worst for

Marketing-led developer-portal programs that need a polished default look (Mintlify or ReadMe), teams with minimal OpenAPI investment (GitBook or Slate), or programs that need the deepest portal analytics (ReadMe).

Strengths

  • Redoc OSS is the most-deployed OpenAPI renderer in the industry
  • Best-in-class OpenAPI 3.x and 3.1 fidelity and validation
  • Redocly CLI for linting, bundling, and decoration of specs
  • Realm (2023) adds multi-spec managed portals and previews
  • Strong governance story for spec-first teams
  • AsyncAPI support stronger than most peers

Weaknesses

  • Default look is less polished than Mintlify out of the box
  • Realm pricing is opaque; quotes vary widely by buyer
  • Brand still associated mainly with Redoc OSS, not full portal
  • Authoring outside OpenAPI (long-form guides) less mature than ReadMe or GitBook
  • Documentation about Redocly itself can be inconsistent in places

Pricing tiers

partial
  • Free (Redoc OSS)
    Open-source renderer; self-hosted; no commercial features
    $0 /mo
  • Starter
    One project, CLI linting, hosted preview
    $99 /mo
  • Pro
    Multi-project, SSO, custom domains, Realm hosting
    $469 /mo
  • Enterprise
    SLA, audit logs, on-prem deployment option
    Quote
Watch for
  • · Realm hosting metered for high-traffic portals
  • · Professional services for migration and theming
  • · Additional projects priced separately at Starter

Key features

  • +Redoc OSS renderer
  • +Redocly CLI (lint, bundle, decorate)
  • +OpenAPI 3.x and 3.1 plus AsyncAPI support
  • +Realm multi-spec portal hosting
  • +Spec governance and style guides
  • +GitHub and GitLab sync
  • +Custom themes
  • +Try-It console
  • +Versioned docs
30+ integrations
GitHubGitLabBitbucketSpectralStoplightVercelNetlifyOkta
Geography
Global; strongest in US and EU
#5

GitBook

Modern Git-native documentation that scales from product docs to API reference.

Founded 2014 · Lyon, France · private · 50 to 5,000 employees
G2 4.6 (268)
Capterra 4.5
From $0 /mo
● Transparent pricing
Visit GitBook

GitBook is the modern Git-native documentation platform funded by a $35M Series B in 2022 led by Tiger Global and Notion-affiliated investors. The product sits between a knowledge base and a developer portal, with first-class Git sync, a polished editor, an AI assistant launched in 2023, and growing OpenAPI support. Best fit when documentation spans product docs, API reference, and internal knowledge, and you want one tool rather than three. Trade-offs: API-specific features (interactive playground, key management) are less mature than ReadMe or Mintlify, OpenAPI ergonomics are improving but still trail dedicated dev-portal tools, and pricing at large editor counts climbs quickly.

Best for

Mid-market and enterprise teams (50 to 5,000 employees) that need one platform across product docs, API reference, and internal knowledge, with Git-native authoring and a polished editor.

Worst for

API-only programs that need the deepest portal analytics and key management (ReadMe), engineering-only teams that want markdown-only with hot reload (Mintlify), or spec-first OpenAPI governance (Redocly or SwaggerHub).

Strengths

  • Git sync model (GitHub, GitLab) with bidirectional editing
  • Polished editor that non-engineers can use
  • AI assistant for site search and Q and A (2023)
  • Versioned docs and content branching
  • Custom domains, SSO, audit logs
  • Public and private spaces in one workspace
  • Strong support for non-API documentation alongside API reference

Weaknesses

  • API-specific features (interactive playground) less mature than ReadMe
  • OpenAPI ergonomics improving but still trail dedicated dev-portal tools
  • Per-editor pricing climbs quickly at scale
  • Migration from older GitBook v1 caused friction for early customers
  • No on-prem option

Pricing tiers

public
  • Free
    Personal; public docs; limited features
    $0 /mo
  • Plus
    5 editors; custom domain; basic analytics
    $65 /mo
  • Pro
    10 editors; SSO, audit logs, AI assistant
    $249 /mo
  • Enterprise
    Unlimited editors; advanced SSO, SCIM, security review
    Quote
Watch for
  • · Additional editors above tier inclusion
  • · AI assistant credits at Pro and Enterprise
  • · Premium support is a separate line item at Enterprise

Key features

  • +Bidirectional Git sync
  • +Modern WYSIWYG-plus-markdown editor
  • +AI assistant (search and Q and A)
  • +Versioned docs and branches
  • +Custom domains and SSO
  • +OpenAPI integration
  • +Internal and external spaces
  • +Content lifecycle and review workflow
  • +Analytics dashboard
35+ integrations
GitHubGitLabSlackIntercomLinearNotionFigmaOkta
Geography
Global; strongest in EU and US
#4

SwaggerHub

Legacy OpenAPI registry and governance for regulated enterprises.

Founded 2015 · Somerville, MA · pe backed · 500 to 50,000 employees
G2 4.2 (218)
Capterra 4.3
From $0 /mo
○ Sales call required
Visit SwaggerHub

SwaggerHub is SmartBear-owned API design, registry, and documentation tooling that traces back to the original Swagger project (acquired by SmartBear in 2015). For regulated enterprises that need a centralized OpenAPI registry, design-style governance, and integration with the broader SmartBear testing stack (ReadyAPI, BugSnag), SwaggerHub remains a credible choice. Best fit for banks, insurers, and government programs that anchor their API governance on OpenAPI and want one vendor across design, registry, documentation, and testing. Trade-offs: the UI has not modernized at the pace of Mintlify or ReadMe, the consumer-facing developer portal experience is the weakest among the leaders, and SmartBear has a mixed reputation for post-acquisition product investment.

Best for

Regulated enterprises (500 to 50,000 employees) that anchor API governance on OpenAPI, need a centralized registry with approval workflow, and value consolidating design, registry, and testing under one vendor.

Worst for

Modern developer-portal programs that prioritize consumer DX (ReadMe or Mintlify), teams without existing SmartBear investment (Redocly is the better OpenAPI bet), or small teams that do not need registry governance.

Strengths

  • OpenAPI registry with versioning, branches, and approval workflow
  • Design-style governance and team-wide style guides
  • Native integration with SmartBear testing tools (ReadyAPI)
  • On-prem deployment option for regulated industries
  • Strong RBAC and audit logging
  • Long-standing brand recognition with enterprise architects

Weaknesses

  • Consumer developer portal is the weakest among leaders
  • UI has not modernized at the pace of Mintlify or ReadMe
  • SmartBear post-acquisition investment has been uneven
  • Pricing opaque at enterprise tiers
  • Buyer reviews describe slow performance on large specs
  • Integration with non-SmartBear stacks feels secondary

Pricing tiers

opaque
  • Free
    Public APIs only, limited features
    $0 /mo
  • Team
    Per designer; private APIs, basic governance
    $90 /mo
  • Enterprise (SaaS)
    Per designer; SSO, audit, style guides
    Quote
  • Enterprise On-Premise
    Self-managed; large initial fee
    Quote
Watch for
  • · On-prem deployment carries professional-services fees
  • · Per-designer pricing escalates with large API programs
  • · Integration with ReadyAPI billed separately

Key features

  • +OpenAPI 3.x and 2.0 registry
  • +Design-style governance and style guides
  • +API versioning with branches
  • +Auto-generated documentation
  • +Mock servers
  • +On-prem deployment option
  • +Integration with ReadyAPI
  • +RBAC and audit logs
25+ integrations
GitHubGitLabBitbucketJenkinsReadyAPIAzure DevOpsApigeeAWS API Gateway
Geography
Global; strongest in US and EU regulated industries
#7

Theneo

AI-first developer-portal challenger from Y Combinator S22.

Founded 2021 · San Francisco, CA · private · 5 to 1,000 employees
G2 4.6 (64)
Capterra 4.7
From $0 /mo
◐ Partial disclosure
Visit Theneo

Theneo is the AI-first developer-portal challenger that graduated Y Combinator S22 alongside Mintlify and has positioned its AI-driven authoring as the differentiator. The product imports OpenAPI specs and generates first-draft documentation, descriptions, and code samples, then offers a polished editor for refinement. Best fit for early-stage and mid-market API teams that want to ship a portal with minimal authoring time and accept that AI-generated first drafts need human review. Trade-offs: enterprise governance and audit features are newer than ReadMe or SwaggerHub, customer base is smaller, and marketing claims about AI capability outpace what most production buyers actually report.

Best for

Early-stage and mid-market API teams (5 to 500 employees) that want a polished portal and accept AI-generated first drafts as a starting point for human-reviewed documentation.

Worst for

Regulated enterprises that need deep audit and governance (ReadMe or SwaggerHub), spec-first programs (Redocly), or teams that need the deepest portal analytics (ReadMe).

Strengths

  • AI-driven first-draft documentation from OpenAPI specs
  • Polished portal with custom theming
  • Multi-language code samples generated automatically
  • Versioned docs and changelog tooling
  • GitHub sync and CLI for CI integration
  • Try It console with stored credentials

Weaknesses

  • Enterprise governance and audit features less mature than ReadMe
  • Customer base smaller; fewer enterprise references
  • AI marketing claims outpace what production buyers report
  • Portal analytics shallower than ReadMe
  • Pricing transparency partial at higher tiers

Pricing tiers

partial
  • Free
    Public docs, Theneo subdomain, limited customization
    $0 /mo
  • Starter
    Custom domain, multi-language code samples
    $120 /mo
  • Growth
    SSO, API key management, advanced AI features
    $400 /mo
  • Enterprise
    Audit logs, SCIM, dedicated CSM, SLA
    Quote
Watch for
  • · AI credit quotas at higher tiers
  • · Additional projects priced separately at Starter and Growth
  • · Premium support a separate line at Enterprise

Key features

  • +AI-driven first-draft authoring from OpenAPI
  • +Custom theming and branding
  • +Multi-language code samples
  • +Try It console with stored auth
  • +Versioned docs
  • +Changelogs
  • +GitHub sync
  • +API key management
25+ integrations
GitHubGitLabSlackIntercomSegmentPostmanVercelOkta
Geography
Global; strongest in US and India
#9

Postman Documentation

Path-of-least-resistance docs for teams already on the Postman platform.

Founded 2014 · San Francisco, CA · private · Any (developer count is the lever) employees
G2 4.6 (412)
Capterra 4.6
From $0 /mo
● Transparent pricing
Visit Postman Documentation

Postman Documentation is the documentation surface that ships as a feature of the broader Postman API platform, which carries roughly 30 million registered developers and a $5.6B valuation from its August 2021 Series D. The product turns collections into auto-generated public or private documentation with embedded code samples and a Try It runner. Best fit when the API team already uses Postman for design, testing, and mocks and wants a no-friction docs surface in the same workspace. Trade-offs: as a dedicated developer-portal product it lacks the depth of ReadMe or Mintlify, branding and theming flexibility is limited, and post-2022 enterprise pricing pressure has nudged some buyers toward dedicated portal tools.

Best for

API teams (10 to 5,000 developers) already standardized on Postman that want a documentation surface in the same workspace without buying a separate portal product.

Worst for

Marketing-led public developer portals (ReadMe or Mintlify), spec-first OpenAPI governance (Redocly or SwaggerHub), or buyers that want a tightly branded standalone portal.

Strengths

  • Auto-generated from Postman collections; no separate authoring
  • Try It runner with stored credentials baked in
  • Largest developer install base in the API category
  • OpenAPI 3.x import and sync
  • Public API Network for discoverability
  • Strong RBAC and team workspaces

Weaknesses

  • As a dedicated portal it lacks the polish of ReadMe or Mintlify
  • Branding and theming flexibility limited
  • Enterprise pricing has stepped up post-2022
  • Portal analytics narrower than ReadMe
  • Authoring long-form guides outside collection structure feels awkward

Pricing tiers

public
  • Free
    Up to 3 users; public docs included
    $0 /mo
  • Basic
    Per user; private docs, team workspaces
    $14 /mo
  • Professional
    Per user; SSO, advanced governance
    $29 /mo
  • Enterprise
    Per user; SCIM, audit logs, custom domains
    $49 /mo
Watch for
  • · Custom domains require Enterprise tier
  • · On-prem deployment requires Enterprise Ultimate
  • · Postbot AI credits priced separately at Enterprise

Key features

  • +Auto-generated docs from collections
  • +Try It runner with stored credentials
  • +OpenAPI 3.x import
  • +Public API Network
  • +Multi-language code samples
  • +Workspace RBAC
  • +Custom domains (Enterprise)
  • +Versioned docs
250+ integrations
GitHubGitLabBitbucketJenkinsDatadogNew RelicSlackOkta
Geography
Global; strongest in US, India, EU
#8

Apiary

API Blueprint heritage stagnated under Oracle since 2017.

Founded 2011 · Austin, TX (Oracle) · public · 50 to 5,000 employees
G2 3.8 (96)
Capterra 4.0
From $0 /mo
○ Sales call required
Visit Apiary

Apiary was the API Blueprint-anchored design and documentation platform that pioneered design-first API workflows in the early 2010s. Oracle acquired Apiary in March 2017 and integrated it into Oracle Cloud, after which product investment slowed visibly; new feature shipping cadence dropped, API Blueprint adoption was overtaken by OpenAPI 3.x, and the developer brand faded. Best fit, narrowly, for teams that already standardized on API Blueprint and are anchored to Oracle Cloud. Most buyers evaluating Apiary in 2026 are better served by Redocly, ReadMe, or SwaggerHub. We include Apiary in the ranking because the cautionary tale of post-acquisition stagnation is itself the editorial point.

Best for

Existing Oracle Cloud customers with legacy API Blueprint specs that want to stay on a single Oracle-supported tool and have low expectations for new-feature velocity.

Worst for

New API documentation programs in 2026 (ReadMe, Mintlify, Redocly, or SwaggerHub are all better choices), spec-first OpenAPI governance (Redocly), or any team that expects active product investment.

Strengths

  • API Blueprint heritage with deep markdown-based design tooling
  • Mock servers and inspector for legacy API Blueprint specs
  • Oracle Cloud integration for existing Oracle customers
  • Long-running stability for legacy customers

Weaknesses

  • Product investment has stagnated post-Oracle acquisition
  • API Blueprint adoption has fallen behind OpenAPI 3.x
  • UI and developer experience have not modernized
  • Roadmap visibility is poor; community signals are weak
  • Buyer reviews on G2 and Capterra have declined since 2020
  • New customer acquisition outside Oracle Cloud is minimal

Pricing tiers

opaque
  • Free
    Public API Blueprint specs only, limited features
    $0 /mo
  • Standard
    Per team, private specs, mock servers
    $199 /mo
  • Enterprise (via Oracle Cloud)
    Bundled into Oracle Cloud agreements
    Quote
Watch for
  • · Enterprise often bundled into Oracle Cloud contracts; difficult to price standalone
  • · Migration tooling minimal; lock-in to API Blueprint format
  • · Limited new-feature releases since 2020

Key features

  • +API Blueprint design
  • +Mock servers
  • +Inspector for trace analysis
  • +Versioned specs
  • +Hosted docs
  • +OpenAPI import (limited)
  • +GitHub sync
15+ integrations
GitHubGitLabOracle CloudSlackJenkinsTravis CI
Geography
Global via Oracle Cloud regions
#10

Slate

Open-source three-column docs project for teams that refuse to buy a portal.

Founded 2014 · Open-source (origin Concur Technologies, San Francisco) · private · 1 to 200 employees
G2 4.4 (38)
Capterra 4.3
From $0 /mo
● Transparent pricing
Visit Slate

Slate is the original open-source three-column API documentation generator, created by TripIt engineers (later Concur, later SAP) and released in 2014. The project has become the canonical zero-cost reference renderer for engineering teams that refuse to pay for a developer-portal SaaS. The codebase is a Ruby Middleman site that compiles markdown plus YAML metadata into a static HTML site with code-sample columns. Best fit for tightly engineering-led teams that want full control over hosting and theming and treat the docs site as code. Trade-offs: maintenance has slowed as the original maintainers moved on, the Ruby toolchain is unfamiliar to many modern engineering teams, and the project lacks an OpenAPI-native rendering path, requiring manual maintenance of the markdown source.

Best for

Engineering-led teams (1 to 200 developers) that want a zero-licensing-cost docs site, self-host control, and treat the docs as code; comfortable with Ruby toolchains.

Worst for

Any program that needs OpenAPI-native rendering (Redocly is the OSS answer), analytics or API key management (ReadMe or Mintlify), or non-engineering writer onboarding (GitBook).

Strengths

  • Zero licensing cost; full self-host control
  • Familiar three-column docs aesthetic copied across the industry
  • Static-site output is fast, cacheable, and CDN-friendly
  • Markdown plus YAML source is easy to version in Git
  • Custom theming via SCSS
  • Community fork ecosystem keeps activity alive

Weaknesses

  • Maintenance has slowed; original maintainers moved on
  • No native OpenAPI rendering; manual markdown maintenance required
  • Ruby toolchain unfamiliar to many modern engineering teams
  • No analytics, no API key management, no Try It console
  • No commercial support; community-only Issues
  • Onboarding non-engineering writers is hard

Pricing tiers

public
  • Open-source
    MIT-style license; self-host any infrastructure
    $0 /mo
  • Community-managed forks
    Various community forks (Slatedocs/slate) maintained on GitHub
    $0 /mo
Watch for
  • · Hosting infrastructure (S3, Netlify, GitHub Pages)
  • · Engineering time to maintain and theme
  • · No native OpenAPI ingestion; manual markdown upkeep

Key features

  • +Three-column docs aesthetic
  • +Markdown plus YAML source
  • +Multi-language code-sample columns
  • +Static HTML output
  • +SCSS theming
  • +Search (basic)
  • +GitHub Pages and Netlify deployment recipes
10+ integrations
GitHubGitHub PagesNetlifyVercelAWS S3Cloudflare Pages
Geography
Global; community-distributed

Frequently asked questions

The questions buyers actually ask before they sign.

What makes Bump.sh relevant for French teams over ReadMe or Mintlify?
Bump.sh (Paris, French legal entity, EUR-priced, RGPD-native DPA) occupies a different niche from ReadMe or Mintlify. It is an API contract management tool that generates documentation as an output of a contract-first workflow: on every commit, it diffs your OpenAPI spec, detects breaking changes, and publishes a human-readable changelog. ReadMe and Mintlify are developer portal platforms that render documentation; Bump.sh is the API versioning discipline layer. For French teams with complex API versioning (Spendesk, Qonto, Alan-tier multi-version APIs), Bump.sh is a complement to, not a replacement for, ReadMe or Mintlify.
Is GitBook truly French, and why does it matter for RGPD?
GitBook was founded in Lyon in 2014 by Sebastien Chopin and Benoit Marchant (both French). The company operates as GitBook SAS, a French-registered entity. This matters for RGPD in three ways: GitBook SAS can sign French-law data processing agreements (accord de traitement des donnees); EU-hosted GitBook data satisfies CNIL data residency preferences; and French public-sector procurement prefers vendors with French legal entities for liability purposes. GitBook is not SecNumCloud-qualified, but it can be deployed on SecNumCloud infrastructure via self-hosted options for French government clients.
How do French SaaS exporters handle bilingual API documentation (French + English)?
Most French SaaS exporters (Aircall, Spendesk, Doctolib) publish English-first API developer portals on ReadMe or Mintlify for their global developer audiences. Separate French-language technical documentation for French enterprise customers is typically maintained on GitBook or in Confluence. ReadMe has limited native i18n/localisation support; Mintlify has some multi-language capability via its MDX structure. Redocly supports x-locale extensions in OpenAPI specs for multilingual documentation. For truly bilingual API documentation (French + English in one portal), GitBook with separate spaces per language is the most practical approach for mid-size French SaaS teams.
What is the difference between a developer portal and traditional API documentation?
Traditional API documentation is a static reference site rendered from an OpenAPI spec or hand-authored markdown; the developer reads it and copies code samples out. A developer portal is a product surface that includes the reference, plus API key provisioning, an interactive Try It console with stored credentials, multi-language code samples, changelogs, analytics on what developers actually try, and often a support and forum surface. ReadMe, Mintlify, Redocly Realm, and Postman ship full portals. Slate and Redoc OSS render reference only. For a partner-API program where external developers are paying customers, you almost always need a portal, not just docs.
Is OpenAPI 3.x the right standard in 2026?
Yes, for REST APIs OpenAPI 3.x and 3.1 are the de facto industry standard, supported by every vendor in this ranking. Most platform teams in 2026 are migrating from OpenAPI 3.0 to 3.1 (which aligns with JSON Schema 2020-12 and supports webhooks and null types more cleanly). For event-driven APIs the equivalent is AsyncAPI, and Bump.sh, Redocly, and Postman all support it as a first-class citizen. API Blueprint, the older format that Apiary anchored on, has largely been overtaken; new programs should not start there.
How much of the AI-doc-generation marketing in 2026 is hype?
A meaningful fraction. AI-driven first-draft authoring (Theneo, Mintlify, GitBook, ReadMe) genuinely accelerates the first pass at description generation, code-sample generation, and site search Q and A. Production buyers consistently report a 30 to 50 percent reduction in time-to-first-draft. What does not work yet is unattended publication; AI-generated copy still requires human review, especially for accuracy of authentication flows, edge cases, and code samples. Treat AI-doc-generation as an authoring accelerator, not as a replacement for human technical writers.
When do you actually need a developer portal vs just docs?
You need a developer portal when external developers are part of your customer or partner program, when you provision API keys per developer, when you want analytics on which endpoints developers hit and where they get stuck, when you have multiple APIs that need a single discovery surface, or when you sell access in tiers or per call. You can live with reference-only docs (Slate, Redoc OSS, a Mintlify Free site) when APIs are internal-only, when there is no monetization, when there are fewer than five APIs in total, and when the audience is engineering peers who do not need self-serve key provisioning.
Why is Apiary so far down the ranking despite the API Blueprint heritage?
Because product investment has visibly stagnated since Oracle acquired Apiary in March 2017. Feature-shipping cadence dropped, API Blueprint adoption was overtaken by OpenAPI 3.x in the late 2010s, the UI has not modernized at the pace of peers, and reviews on G2 and Capterra have declined since 2020. We include Apiary because the cautionary tale of post-acquisition stagnation is itself the editorial point, but most new buyers in 2026 should pick Redocly, ReadMe, Mintlify, or SwaggerHub instead.
ReadMe vs Mintlify, which one for a new portal in 2026?
Both are credible; the right pick depends on team shape. ReadMe wins on portal analytics (best in category), API key management, the maturity of the Try It runner, and enterprise governance. Mintlify wins on authoring experience (hot reload, MDX components, PR previews), default theme polish, and engineering-team velocity. Rule of thumb: product-led API companies that want a polished portal without owning the docs platform internally pick ReadMe; engineering-led companies that want docs-as-code with full Git ownership pick Mintlify. Both ship at similar prices in the Business and Growth tiers.
How does API documentation connect to API management and IAM?
The developer portal is the front door; the API management gateway is the runtime that sits behind it. Portal and gateway are typically separate products: ReadMe or Mintlify in front, Kong or Apigee or a cloud gateway behind. Identity and OAuth/OIDC onboarding for developers landing on your portal lives in your IAM stack, Okta, Auth0, Microsoft Entra ID, Keycloak. See our Top 10 API Management Software ranking for the gateway layer and our Top 10 IAM Software ranking for the identity layer. Most portal products integrate natively with the major IAM providers via SAML or OIDC.
How long does a developer-portal implementation take?
ReadMe and Mintlify: 1 to 4 weeks for a single-API public portal, longer if you need custom theming and design-system alignment. GitBook: 2 to 6 weeks given the broader content model. Redocly Realm: 2 to 8 weeks for multi-spec portals with governance. SwaggerHub: 4 to 12 weeks for enterprise registry rollout with approval workflow. Slate or Redoc OSS: 1 to 3 weeks if your engineering team picks up the Ruby or JavaScript stack and self-hosts. Most time goes into content quality, code-sample accuracy, and CI integration, not into the portal product itself.
What about Stoplight and Docusaurus?
Stoplight is an API design studio acquired by SmartBear in 2024; it overlaps with SwaggerHub and is covered in our Top 10 API Management Software ranking under the design column. Docusaurus is a general-purpose docs-as-code static site generator from Meta; it is excellent for product documentation but is not API-specific (no OpenAPI playground, no key management, no portal analytics out of the box). Most teams that pick Docusaurus end up bolting on a Redoc or Swagger UI iframe for API reference, which works but is more assembly than buying a portal product.
How much should I budget for API documentation in 2026?
Small team (1 to 20 developers), single API: $0 to $3,000 per year (Mintlify Free or Starter, Bump.sh Free, Slate self-host, Redoc OSS). Mid-market (20 to 200 developers), single or few APIs: $5,000 to $25,000 per year (ReadMe Startup, Mintlify Startup, GitBook Pro, Redocly Starter, Bump.sh Starter). Mid-market plus, multi-API or partner-facing: $25,000 to $80,000 per year (ReadMe Business, Mintlify Growth, GitBook Pro plus, Redocly Pro, Theneo Growth). Enterprise: $60,000 to $250,000-plus per year (ReadMe Enterprise, SwaggerHub Enterprise, Redocly Enterprise, GitBook Enterprise, Mintlify Enterprise).

Final word

Looking at a different market? See the global API Documentation / Developer Portals ranking, or pick another country at the top of this page.

Last updated 2026-05-19. Local pricing reverified quarterly. Found something inaccurate? Tell us.