Documents and notes decision

ReadMe Pro

A capable developer can replicate a useful subset (hosted MDX docs, OpenAPI-generated reference, search, Git sync) in about a week, but the full hosted product (enterprise compliance, AI agents, audit logs, support) and brand-level trust are nontrivial to reproduce, so keep paying for those features if you need them.

Visit website
Subscription$250/month ✓ verified
Initial build6 hours
Monthly upkeep4 hours + $0
Evidence1/2 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Host searchable, versioned developer documentation generated from Markdown/MDX and OpenAPI, with a simple web editor and deploy pipeline.

What it still won’t have

  • Built-in AI features (AI Linter, Ask AI, Agent/MCP servers)
  • Enterprise features (SSO, audit logs, granular roles, implementation services)
  • Hosted analytics/Developer Dashboard with API call logs
  • Branded enterprise support and migration services
  • Private AI context and Docs Audit

What remains hard

  • Brand trustTrusted by teams who know good docs drive adoption
  • Compliance and regulationSOC2 & GDPR Audited, certified, and ready for
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal hosted docs product using Next.js + MDX for rendering, a Node service to parse OpenAPI files into reference pages, Meilisearch for search, Git-sync that imports Markdown/MDX from a Git repo and provides branch previews, and CI deploys to Vercel. In scope: MDX editor (browser), OpenAPI import, searchable site with autocomplete, Git-backed previews, custom domain support, automated deploy pipeline, and basic request/usage metrics. Out of scope: enterprise SSO/SAML, audit logs, hosted LLM agents, and managed implementation services. Include error handling, retries for external API calls, input validation for uploaded specs, and unit/integration tests covering import, rendering, search indexing, and deploy hooks.
How we checked3 sources · 1/2 runs agreed · evidence score 95

How the score was reached

  • Self-host verdict base92
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Hard moats found in the evidence-3
  • Evidence score95

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 1 of 2 runs agreed; the verdict is the middle of them✓ Citations limited to fetched pages! 2 moats quoted from the page