Which site best fits your project?
Free for open-source software.
Sign upPlans starting at $50/month.
Sign upWhich site best fits your project?
Free for open-source software.
Sign upPlans starting at $50/month.
Sign upMintlify is a proprietary documentation platform built around a vendor-specific MDX dialect. If you want a fully managed, closed-source product, Mintlify may suit you.
Read the Docs takes a different approach: your tools, your content, your terms. Write in any documentation tool your team already uses, and publish on a platform trusted by engineering teams at AMD and Canonical, and by open source projects like Jupyter and Flask — over 15 years of reliable documentation hosting.
No lock-in. No per-seat pricing. Business and Enterprise plans for commercial teams, with a free Community tier for open source.
|
|
|
|
|---|---|---|
|
Build your site on the cloud
Generate your site's content on the cloud
|
||
|
Deploy previews
Solve style issues before deploying
|
||
|
Search
Always find what you are looking for
|
||
|
Multiple versions
Publish multiple versions of your documentation
|
||
|
Translations
Serve translated versions of your docs
|
||
|
Page analytics
Understand how people browse your documentation
|
||
|
Search analytics
Explore what people search for in your docs
|
||
|
Private documentation
Give access only to trusted people
|
||
|
Documentation tool agnostic
Use the documentation tool your team prefers (Sphinx, MkDocs, Docusaurus, Jupyter Book, etc)
|
||
|
No per-seat pricing
Unlimited users on every plan
|
||
|
Unlimited builds per month
Trigger as many builds as you need
|
||
|
Open Source
Own your content, self-host if you want, contribute back
|
||
|
|
|
.readthedocs.yaml
# Example for a Node-based doc tool (e.g. Docusaurus).
# Replace the install/build commands with whatever your tool uses
# (mkdocs build, sphinx-build, jupyter-book build, etc).
version: 2
build:
os: ubuntu-24.04
tools:
nodejs: "20"
commands:
# Install dependencies and build the site
- cd docs/ && npm install
- cd docs/ && npm run build
# Copy output to Read the Docs
- mkdir -p $READTHEDOCS_OUTPUT/html/
- cp -r docs/build/* $READTHEDOCS_OUTPUT/html/
Write in the documentation tool your team already uses, keep your content portable, and publish on an open platform with no vendor lock-in.