The Best Documentation Hosting For A Built Docs Site

The best documentation hosting for a built Docusaurus, MkDocs, VitePress or Starlight site: seven hosts ranked on free tier, true price and catch, Nov 2026.
The OxyPages Team · · 9 min read
You have a docs folder, a static site generator that turns it into HTML, and a PDF manual that people keep asking for by email. The generator is chosen. Now the built folder needs a home.
Most advice on the best documentation hosting mixes two different products. Some, like GitBook and Mintlify, are a docs editor and host in one: they render their own pages, so you'd leave your generator behind. Others take the folder Docusaurus, MkDocs, VitePress or Starlight already built and serve it as it is.
This post is about the second kind, plus the two editors for anyone thinking of switching. Plenty of people arrive searching "github pages documentation alternatives", so GitHub Pages is on the list too, ranked fairly.
My angle is a project maintainer or a small team: one docs site, a PDF manual of a few megabytes, and no appetite for running servers. Every price was checked on the vendor's own page and is current as of November 2026, labelled monthly or yearly.
If GitHub Pages itself is what you're weighing, the full GitHub Pages rundown covers its limits in detail.
TL;DR: A built docs site is a folder of static HTML, so any static host can serve it. OxyPages builds it from GitHub or takes a dropped folder, with password protection from $5 a month. GitHub Pages and Cloudflare Pages are free with custom domains and far more traffic headroom. Read the Docs is free for open source with ads, and adds versioned docs. Netlify is free on 300 credits a month. GitBook (Essential $79 a site a month, monthly billing) and Mintlify (free for 5 editors, Pro $540 a month monthly) replace your generator rather than host its output.
Disclosure: we make OxyPages, which is why it's first on this list. Everything after it is ranked on merit, and each entry says plainly who should pick it over us.
What Makes The Best Documentation Hosting?
The best documentation hosting builds your docs on every merge, serves every page over HTTPS at a stable address, and keeps old links working when pages move. Here's what to check:
- It builds from your repository, or accepts the built folder, so nobody uploads files by hand.
- Old URLs survive. A redirects file matters once pages get renamed.
- Large files fit. Your PDF manual must fit under the per-file limit.
- Private docs are possible if anything is internal.
- Traffic headroom. Docs pages get read a lot.
- The true monthly price, not the yearly rate divided by 12.
- Versioned docs, if users run older releases.
The Best Places To Host A Docs Site, Ranked

1. OxyPages: Built Docs From GitHub, With A Password Option
Who it suits: a maintainer or small team who wants Git builds without YAML, or a dropped folder, and possibly private docs.
Connect a GitHub repository and it builds Node-based generators such as Docusaurus, VitePress and Starlight on every push, with 100 build minutes a month on Free. Python tools like MkDocs build in a GitHub Actions workflow first, then deploy with our action. You can also drop the built folder or run npx oxypages. _redirects and _headers files work, and every deploy keeps version history with rollback.
Price: Free is one site with 25 MB of storage, 5,000 page views a month and HTTPS, for personal, non-commercial use. Lite is $5 a month on monthly billing or $48 a year, with 500 MB, 20,000 views, custom domains, password protection and commercial use.
The catch: 25 MB on Free is tight once a PDF manual is in the folder, single files cap at 25 MB, and page-view quotas run out sooner than GitHub's bandwidth. The builder runs Node only, and there's no versioned docs feature beyond what your generator builds.
2. GitHub Pages: Free For Public Project Docs
Who it suits: open source projects whose code already lives on GitHub.
GitHub Pages serves a site up to 1 GB with a soft bandwidth limit of 100 GB a month, free from public repositories. Any generator works through a GitHub Actions workflow, and custom domains are free.
Price: free. Publishing from a private repository needs a paid GitHub plan, such as Team at $4 per user a month.
The catch: a private repository still gives you a public site; private publishing needs GitHub Enterprise Cloud. GitHub's docs don't describe a redirects file, so a renamed page usually needs a redirect page or a generator plugin. Pick it over us for public open source docs with real traffic.
3. Cloudflare Pages: Free With Unmetered Traffic
Who it suits: a team expecting heavy traffic that's comfortable in a developer dashboard.
Requests to static assets are "free and unlimited", and the free plan includes 500 builds a month, 20,000 files per site, 25 MiB per file and custom domains. It supports _redirects and _headers.
Price: free for static docs. Workers Paid starts at $5 a month if you add code.
The catch: Cloudflare's own docs now tell new projects to start on Workers instead of Pages, and the choice confuses people. Pick it over us if traffic is high or the docs are commercial and you want a free plan.
4. Read the Docs: Built For Versioned Docs
Who it suits: open source projects that publish docs for several releases at once.
Read the Docs "provides documentation hosting for any tool that can output HTML", naming Sphinx, MkDocs, Docusaurus, VitePress and Starlight among others. It builds on every push and publishes a version of the docs for each Git branch or tag you choose.
Price: the Community plan is free for open source and ad-supported. Business starts at $50 a month for Basic, then $150 and $250. Yearly billing exists but the page doesn't list yearly prices.
The catch: free is open source only, with ads, and paid starts at $50 a month. Pick it over us whenever versioned docs matter.
5. Netlify: Free, With Deploy Previews
Who it suits: teams who want a preview link on every pull request.
Netlify builds any generator from Git and supports _redirects. Deploy previews and branch deploys aren't metered, so reviewers can check a docs change before it merges. Free allows commercial use and custom domains.
Price: Free is 300 credits a month. Personal is $9 a month and Pro is $20 a month.
The catch: each production deploy costs 15 credits and bandwidth 20 credits per GB, so 300 credits is at most 20 deploys if nothing else is used. At zero credits, every site on the account pauses. Pick it over us for pull request previews at no cost.
6. GitBook: An Editor Instead Of A Generator
Who it suits: teams where writers who never touch Git own the docs.
GitBook is a block-based editor and host in one, with two-way Git Sync to GitHub or GitLab on every plan and unlimited page views. It renders its own site, so your Docusaurus or MkDocs build isn't what visitors see.
Price: Free covers one user, without a custom domain. Essential is $79 per site a month on monthly billing or $65 yearly, plus $15 per user a month ($12 yearly).
The catch: you'd be moving off your generator, and per-site plus per-user pricing climbs fast. Pick it over us if non-technical writers run the docs.
7. Mintlify: Polished API Docs, Free For Small Teams
Who it suits: a product team with an API reference.
Mintlify's free plan covers up to 5 editors with hosting, search, a custom domain, Git sync, a web editor, authentication, an API playground and an MCP server. You write Markdown or MDX in its format, and it offers migration from Docusaurus.
Price: free. Pro is $540 a month on monthly billing or $450 a month yearly.
The catch: like GitBook, it replaces your generator, and the step from free to Pro is steep. Pick it over us for API docs with an interactive playground.
Documentation Hosts Compared
Prices are monthly billing as of November 2026, unless the row says otherwise.
| Host | Hosts your built folder | Free tier | Paid from (monthly) | Custom domain free | Private docs |
|---|---|---|---|---|---|
| OxyPages | Yes | 1 site, 25 MB, 5,000 views, non-commercial | Lite $5 ($48 a year) | No, Lite and up | Password, Lite and up |
| GitHub Pages | Yes | 1 GB site, 100 GB soft bandwidth | Team $4 per user, for private repos | Yes | Enterprise Cloud only |
| Cloudflare Pages | Yes | Unmetered static requests, 500 builds | Workers Paid $5 | Yes | Not checked |
| Read the Docs | Yes | Open source only, with ads | Basic $50 | Not listed for free | Business plans |
| Netlify | Yes | 300 credits a month | Personal $9 | Yes | Not checked |
| GitBook | No, its own editor | 1 user, no custom domain | Essential $79 per site, plus users | No | Paid plans |
| Mintlify | No, its own MDX | 5 editors, custom domain | Pro $540 | Yes | Authentication on free |
Walkthrough: An MkDocs Site And An 8 MB PDF Manual
Here's how I'd set up a maintainer's command-line tool with an MkDocs site and an 8 MB PDF manual.
- Put the manual inside the docs folder, for example
docs/manual/tool-manual.pdf. MkDocs copies non-Markdown files into the builtsite/folder. - Check the size.
mkdocs build, then look atsite/. If the PDF plus the site is over 25 MB, a free plan with a 25 MB cap won't hold it; compress the PDF or pick a host with more room. - Name the PDF once. People bookmark it and link to it from issues.
- Connect the repository to your host, with
mkdocs buildas the build command andsiteas the output folder. A host that runs Python can do this itself; a Node-only builder, ours included, needs the build to run in GitHub Actions first. Docusaurus outputs tobuild, and VitePress and Starlight todist. The GitHub Actions deploy guide has each folder if you'd rather build yourself. - Add redirects for any moved pages with a
_redirectsfile, so old links return a permanent redirect. MDN on the 301 Moved Permanently status - Link the manual from the docs home page and from the README, so people stop emailing for it.
For sharing the manual on its own, say on a QR code at a meetup, hosting a single PDF covers that.
When OxyPages Is The Wrong Pick

We're the wrong pick in plenty of cases. Here's the better host for each one:
- Public open source docs with real traffic. GitHub Pages or Cloudflare Pages, free and with far more headroom than our view quotas.
- Docs for several releases at once. Read the Docs.
- A preview link on every pull request. Netlify.
- Commercial docs on a free plan. Cloudflare Pages or Netlify. Our Free plan is non-commercial.
- Writers who don't use Git. GitBook.
- An interactive API reference. Mintlify.
- Server-side search, logins or anything that runs code. We serve static files only, so use a platform that runs code.
For general static hosts beyond docs, the static hosting comparison ranks the wider field.
What To Do Next
Decide whether you're keeping your generator. If you are, you need a static host, and the choice comes down to traffic, private docs and versions. If you aren't, compare GitBook and Mintlify on monthly billing.
Then build once, check the folder size with the PDF inside, and deploy. Put your built docs folder online free for a personal project, and add a password on Lite.
FAQ
Can I Host Private Documentation Cheaply?
Yes. A password-protected static site is the cheapest route, from $5 a month on our Lite plan. Read the Docs Business starts at $50 a month, and private GitHub Pages sites need GitHub Enterprise Cloud.
Can GitBook Host A Docusaurus Site?
No. GitBook renders its own pages from its editor or from Markdown synced with GitHub or GitLab. To keep your Docusaurus build, use a static host such as GitHub Pages, Cloudflare Pages or Netlify.
Where Should A PDF Manual Live?
Inside the docs site, at a stable address linked from the home page. Check it fits the host's per-file limit, which is 25 MiB on Cloudflare Pages and 25 MB on OxyPages, and keep the filename fixed so bookmarks and links never break.
What Is The Best Documentation Hosting For Open Source?
For most open source projects, GitHub Pages or Read the Docs is the best documentation hosting. GitHub Pages is free from a public repository, and Read the Docs is free for open source with ads and adds versioned docs. Both build Docusaurus, MkDocs, VitePress and Starlight.