Yes. Octri’s editor takes MDX with built-in components. Standard Markdown comes across as it is; Docusaurus admonitions and tabs become Octri’s Callout and Tabs components, which you swap in as you paste.

Does Octri replace docusaurus-openapi-docs?

Yes, and it goes further: the reference is written for you rather than rendered from the descriptions alone, every error gets a guide, the changelog writes itself, and each endpoint shows the call through your own SDK. Nothing needs regenerating by hand when the spec changes.

What about my redirects?

Copy the ones from @docusaurus/plugin-client-redirects into navigation.redirects in octri.json, in the API Studio’s Files panel. They go live with your first Publish.

Can I host Octri docs myself?

Not today. Octri hosts your docs on your own domain. If self-hosting is a hard requirement, Docusaurus is built for it.

Will someone help with the move?

Yes. Book a call and a founder will go through your Docusaurus site with you and help the first release over by hand.

Octri vs Docusaurus

Docusaurus is a framework for building a docs site. Octri is the docs site, written from your OpenAPI file and hosted for you, with SDKs in ten languages, an MCP server and monitoring on the same plan.

Written by Octri · Checked 16 October 2026

Octri ahead: 18
Level: 6
Docusaurus ahead: 5

API docs, SDK, agent and monitoring features, Octri against Docusaurus. Every row is in the table below.

1 file

is all Octri needs: upload your OpenAPI file and the reference, playground and SDKs are built from it.

4 in 1

Docs, SDKs, an MCP server and monitoring on one subscription, Free included.

Octri writes your API reference from the spec: every field explained, every error documented with its cause and fix, the call through your own SDK on every page, and a changelog that updates itself. Every merged spec change rebuilds it, with nothing to regenerate or deploy.

The site comes hosted, with search, AI chat, analytics, password protection and a custom domain on every plan. The same plan generates SDKs in ten languages, hosts an MCP server whose tools call your API, and keeps watching after release with error reporting, uptime checks and a status page.

API docs and beyond, head to head

Octri against Docusaurus with its OpenAPI plugin, 29 rows from each project’s own pages on 16 October 2026. Octri is ahead on 18, level on 6, and Docusaurus is ahead on 5.

Feature	Octri	Docusaurus
API docs
Endpoint reference	Written for you: every endpoint, every field, errors by status	MDX generated from your spec’s descriptions by a community plugin
Keeping up with the spec	Rebuilt on every merged spec change	Re-run the plugin’s command, then rebuild and redeploy
Interactive playground	Every plan	The plugin’s API explorer
Calls through your own SDK	Every endpoint, in each SDK language you publish	Not available
Error guide per status code	Every endpoint, with cause and fix	Not available
API changelog	Written from every spec change, breaking changes flagged	Written by hand, in the blog or a page
Spec quality checks	14 scored rules, with one-click fixes	Not available
Docs site
Guides in MDX	Every plan	Yes
Editing	A visual editor on the published page	Files in your repository, in your own editor
Hosting	Hosted for you, on your own domain, every plan	You build and deploy the static site
Self-hosting	Not available	Anywhere a static site runs
Search	Full-text search on every plan	Algolia DocSearch or a local search plugin
Versioned docs	Growth	Built in
Translations	One language per site	Built in
Customization	Custom components, CSS and JavaScript on Growth	Any React component, and swizzling
Password-protected docs	Every plan	Up to your host
Docs analytics	Every plan	A Google Analytics plugin
Redirect rules	Every plan: send a retired page to another, and keep old links working on rename	The client-redirects plugin
Open source	Not available	MIT licensed
SDKs
SDK languages	TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart	Not offered
Built and published for you	A pull request per regeneration, then npm, PyPI, Maven Central and the rest	Not offered
Mock server and contract tests	In every SDK repository, built from your spec	Not offered
AI and agents
AI chat for readers	Every plan	Not built in
MCP server	Hosted: 7 docs tools and a callable tool per endpoint	Not built in
llms.txt and markdown pages	Every plan	A community plugin
After release
Error reporting inside the SDK	Built in, tagged to the release	Not offered
Uptime checks for your API	Generated from your spec	Not offered
Status page for your users	On your own domain, with a docs banner	Not offered
Logs and traces for your API	Every plan	Not offered

Only on Octri

8 things Octri does that a Docusaurus site has no setting or plugin for.

A reference that writes itself
Every endpoint described, every field explained and every error documented, from the spec you already have.
A changelog that writes itself
Every spec change becomes a dated entry of endpoints added, removed and changed, with breaking changes flagged.
An error guide for every status code
Each endpoint lists the errors it can return, with what causes each one and how to fix it.
SDKs in ten languages
Generated from the same spec, regenerated on every change, published for you and shown on every endpoint page.
An MCP server that calls your API
Seven tools for reading your docs and one callable tool per endpoint, hosted for every project.
Error reporting inside every SDK
A failure in your users’ apps reaches you with the SDK version, language and method, tagged to the release.
Uptime checks and a status page
Checks generated from your spec, incidents on a status page on your own domain, and a banner across your docs.
Logs and traces for your API
Follow one failing call from a user’s app into your handler, with latency targets per route.

The reference, already written

Docusaurus with its OpenAPI plugin renders the descriptions your spec already holds. Octri writes the reference from the spec, then keeps it current on its own.

Every endpoint gets a page with a description, every request and response field explained, and each error documented by status code with its cause and fix. Each page shows the call through your own SDK in every language you publish, with a playground beside it that sends the real request using the reader’s own credentials.

Connect the repository your spec lives in and every merged change rebuilds the docs as a draft, with a dated changelog entry flagging anything breaking. Publish when it reads right: there is no generate command to run and no site to rebuild or deploy.

A docs site, hosted and ready

A Docusaurus site is assembled: search, analytics and the API reference each come from a service or plugin you pick and configure. Octri’s site arrives with them.

Guides are MDX in a visual editor on the published page. Full-text search, an ask-the-docs chat, docs analytics, password protection, PDF export, llms.txt and a markdown copy of every page for coding agents, redirects and a custom domain are on every plan, Free included, on a site Octri hosts.

The look is yours to set: page layouts, your accent colour, fonts, light and dark code themes, and on Growth your own components, CSS and JavaScript.

SDKs from the same spec

Docusaurus publishes documentation. Octri also publishes the SDKs your readers install, and shows them on every endpoint page.

Octri generates TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart. Every client comes with typed models and typed errors, auth from your security schemes, retries with backoff, pagination, idempotency, server-sent events, multipart uploads and webhook signature checks, and lands in its repository as a pull request on every merged spec change.

Every SDK repository carries a mock server built from your spec and a contract test suite. SDK Studio shapes each client per endpoint, with the generated code redrawn beside every change. The Free plan includes one language, Starter 2, Growth 4 and Business all ten.

Past the docs, on the same plan

An MCP server whose tools call your API, and monitoring that starts inside the SDK, are part of every Octri project.

Octri’s MCP server has seven tools for reading your docs and one callable tool per endpoint, which makes the real request. It runs locally with credentials kept on the developer’s machine, or as a shared server for a team, and the tool list exports in MCP, OpenAI and Anthropic formats.

Every Octri SDK carries an error reporter the developer switches on with one option, so failures in their application reach you tagged to the release. Uptime checks are generated from your spec, incidents publish to a status page on your own domain and a banner across your docs, and backend packages add logs, traces and latency targets per route.

Both start at $0. One arrives finished.

Docusaurus is free and open source, and you run it. Octri’s Free plan is free and hosted, with docs, an SDK, an MCP server and monitoring in it.

Docusaurus

open source, MIT licensed

The framework, to build and host yourself
Search, analytics and API pages from plugins
Versioning and translations built in
No SDKs, MCP server or monitoring

Octri Free

a month, hosted for you

Docs written from your spec, 50 endpoints
An SDK in one language, published for you
Hosted MCP server and AI chat
SDK errors, uptime checks, status page

Octri Starter

$49

a month, or $41.65 billed yearly

SDKs in 2 languages, 100 endpoints
Everything in Free
Monitoring kept 30 days, up from 7
15% off when billed yearly

Piece by piece

What each part of an API docs site is on each. On Octri it is part of the plan; on a Docusaurus site it is a plugin or service you choose and run.

Piece	Octri	Docusaurus
Hosting and deploys	Included	A host you choose, and a build on every change
API reference	Written from your spec, rebuilt on every change	A community plugin, re-run when the spec changes
Search	Included	Algolia DocSearch or a local search plugin
Analytics	Included	Google Analytics, through a plugin
AI chat and MCP server	Included	A service of your choice
SDKs	Included, in up to ten languages	A separate generator
Monitoring and a status page	Included	Separate services

Every Octri plan, row by row →

Moving from Docusaurus

The move starts from what a Docusaurus site already has: the OpenAPI file its plugin reads, its MDX pages, and sidebars.js.

Start on the Free plan Book a call

How the move works

Stage 1
Bring the spec
You
Upload the OpenAPI file your plugin builds from, or connect the repository it lives in.
Octri
Writes a reference page for every endpoint, with the playground, search and chat switched on.
Stage 2
Bring the guides
You
Paste your MDX into the editor, turn :::note admonitions into callouts, and lay out the sidebar from sidebars.js.
Octri
Generates an SDK in each language you pick and shows the call through it on every endpoint page.
Stage 3
Go live
You
Copy your client redirects into octri.json, publish, and point your domain at Octri.
Octri
Rebuilds docs, SDKs and MCP tools on every merged spec change, and starts the uptime checks.

Which should you choose?

Choose Docusaurus

Choose Docusaurus if you want an open-source framework to host and shape yourself in React, or your docs need translating into other languages.

Choose Octri

Choose Octri if you want API docs your readers can rely on from day one, without building the site first. Octri writes the reference from your spec, documents every error with its cause and fix, shows the call through your own SDK on every page, and keeps a changelog that updates itself, hosted on your domain with search, AI chat and analytics included.

Then comes the rest of the plan. SDKs in ten languages built and published for you, a hosted MCP server whose tools call your API, error reporting inside every SDK, uptime checks with a status page and a docs banner, and logs and traces for your API, all at no extra cost.

Questions

Octri’s Free plan is free too, and hosted: docs written from your spec, an SDK in one language, a hosted MCP server, AI chat and monitoring. The paid plans add SDK languages, endpoints and history. Docusaurus is a framework you build a site with; the reference, search, analytics, SDKs and monitoring are pieces you add and run.

Other comparisons

Written by Octri, from each vendor's public pages and our own testing, checked 16 October 2026. Products change often, so confirm anything that matters to you on the vendor's own site. Product names are the trademarks of their owners, used here only to identify their products. Octri is not affiliated with or endorsed by any of them.

Spotted something out of date? Write to founders@octri.dev and we will correct it.

Try it on your own spec

Bring your OpenAPI file on the Free plan and see your reference written and your first SDK built.

Start for free See pricing

Octri vs Docusaurus

API docs and beyond, head to head

Only on Octri

A reference that writes itself

A changelog that writes itself

An error guide for every status code

SDKs in ten languages

An MCP server that calls your API

Error reporting inside every SDK

Uptime checks and a status page

Logs and traces for your API

The reference, already written

A docs site, hosted and ready

SDKs from the same spec

Past the docs, on the same plan