Softwr

Developer Tools · head to head

Cortex vs Docusaurus

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Full reviewWebsite
Docusaurus logo

Docusaurus

Web Development

Static site generator from Meta for documentation sites

From
Free
Free plan
Yes
Full reviewWebsite

The short version

  • Only Docusaurus has a free tier, so it costs nothing to try first.
  • Each has a real cost: Cortex pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.; Docusaurus customisation past the config file assumes React knowledge, which not every docs team has
  • They diverge on capability: Cortex covers Service catalogue, Docusaurus covers MDX authoring.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and Docusaurus actually diverge.

Attributes where Cortex and Docusaurus differ
AttributeCortexDocusaurus
Starting priceOn requestFree
Pricing modelquoteOpen source, no licence fee; hosting billed separately
Free tierNoYes
PlatformsWeb, APIWeb, Self-hosted, Node.js
CategoryDeveloper ToolsWeb Development

Identical on both: user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

Only in Docusaurus

  • MDX authoring
  • Docs versioning
  • Internationalisation
  • Algolia search
  • React theming
  • Plugin architecture

What people use each for

The jobs each tool is most often brought in to do.

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Docusaurus
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Docusaurus
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Docusaurus
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Docusaurus

Docusaurus

  • Open-source project documentation that must track several released versionsnot Cortex
  • Docs sites needing translation workflows rather than a single languagenot Cortex
  • Teams already writing React who want to extend the docs theme directlynot Cortex
  • Replacing a hand-rolled docs site with something that handles search and versioningnot Cortex

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first.
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything.
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue.
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves.
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract.

Docusaurus

  • Customisation past the config file assumes React knowledge, which not every docs team has
  • Build times grow noticeably on very large sites, particularly with many versions and locales
  • Major version upgrades have required real migration work rather than a dependency bump
  • It generates a static site, so anything dynamic — gated content, per-user docs — needs a separate solution

Pricing, plan by plan

Cortex

On request
  • Cortex$undefined/year
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Docusaurus

Free
  • DocusaurusFree
    • Full generator
    • Versioning
    • Internationalisation

Which should you pick?

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.
Cortex review

Choose Docusaurus if

  • You need mdx authoring.
  • You want to start without paying.
  • You work on Web, Self-hosted, Node.js.
  • You also want docs versioning.
Docusaurus review

Questions people ask

Is Cortex or Docusaurus better?
Neither clearly leads. Cortex starts at On request and Docusaurus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Docusaurus?
Docusaurus has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Docusaurus.
Does Cortex or Docusaurus run on more platforms?
Cortex runs on Web, API. Docusaurus runs on Web, Self-hosted, Node.js.
Can I use Docusaurus for free?
Yes. Docusaurus has a free tier, so you can try it without paying. Cortex starts at On request.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Docusaurus is typically brought in for.
What can Cortex do that Docusaurus cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Docusaurus covers MDX authoring, Docs versioning, Internationalisation, Algolia search.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

Docusaurus: Is Docusaurus free?

Yes. Docusaurus is open source from Meta with no licence fee. You pay only for hosting, and static output can be served from free tiers on Netlify, Vercel or GitHub Pages.

Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

Docusaurus: What is Docusaurus built with?

React and MDX. Pages are authored in MDX — Markdown that can embed React components — and the theme layer is React, so layouts are extended with components.

Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

Docusaurus: Does Docusaurus support multiple documentation versions?

Yes. Versioning is built in, so documentation for several released product versions can be maintained side by side, which is a main reason projects choose it.

Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Docusaurus: Does Docusaurus include search?

It integrates with Algolia DocSearch rather than shipping its own search index. Open-source projects can typically use Algolia’s free DocSearch programme.

Share

Related pages

More on Cortex

More on Docusaurus

Keep looking

Other head to heads