Documentation hosting in Europe

Push your docs and they build in Paris and go live from the EU. Every docs branch gets a preview to review, you set the headers your docs need, and readers see a change the moment you deploy.

Start free Find your docs tool

Will my docs tool build here?

If it builds to static files with Node or Hugo, yes. Starlight and Hugo have presets; Docusaurus and VitePress take the Custom preset with their own command and folder. Python tools build elsewhere and upload.

All presets and their settings
Docs tools on deploybase
Starlight
Astro preset · npm run build → dist
Docusaurus
Custom · npm run build → build
VitePress
Custom · npm run docs:build → .vitepress/dist
Hugo
Hugo preset · hugo --minify → public
MkDocs, Sphinx
build in your CI, upload site/ or _build/html

Commands are each tool's own defaults. Every value is yours to change.

Can reviewers read a change before it is merged?

Every docs branch builds to its own address, so a reviewer reads the change as a reader will, links and all. Previews are kept out of search engines, and the published docs stay as they are until you merge.

How previews work
docs-site
main
docs.example.com
new-install-guide
new-install-guide-docs-site.previews.deploybase.eu
Sent on every preview
x-robots-tag: noindex, nofollow

Example project and branch. The header is what every preview address really sends.

Can I set the headers my docs need?

Yes. Add a _headers file to your build output: a Content-Security-Policy for every page, CORS on the one file an API client fetches. It is the format Netlify and Cloudflare Pages use, so an existing file moves over unchanged.

_headers
  1. /* Every page.
  2. Content-Security-Policy: default-src 'self'
  3. X-Frame-Options: DENY
  5. /openapi.json One file.
  6. Access-Control-Allow-Origin: *

Do readers see a fix straight away?

Yes. Pages are checked on every visit and cleared from the CDN when you deploy, while hashed assets are kept for a year. These are the headers a real Astro site on deploybase sends, domain left out.

What the CDN sends
  1. GET /about A page.
  2. cache-control: public, max-age=0, s-maxage=2592000
  3. Checked on every visit.
  4. GET /_astro/_slug_.BUS0mBml.css A hashed asset.
  5. cache-control: public, max-age=31536000, immutable
  6. Kept for a year.

What a docs site cannot do here yet.

  • Redirects for moved pages A _redirects file only works for the single-page-app catch-all today. When a docs page moves, keep a page at the old address for now.
  • Python docs tools MkDocs and Sphinx do not build here, because the images have no Python. Upload their output instead.
  • A build cache Nothing carries over between builds, so a large docs site installs and builds from scratch each time.

Questions about hosting docs.

Something else? Write to support@deploybase.eu. A person answers.

Can I host Docusaurus or VitePress?

Yes. Pick Custom and give its build command and output folder: npm run build and build for Docusaurus, npm run docs:build and .vitepress/dist for a default VitePress setup. Starlight uses the Astro preset as it is.

Frameworks
What about MkDocs or Sphinx?

They need Python, which our build images do not have. Build the site in your own CI and upload the folder it writes, site/ or _build/html, and it is served the same way.

Are docs previews indexed by search engines?

No. Every preview address sends x-robots-tag: noindex, nofollow, so a branch never competes with your published docs.

Can I keep several versions of the docs online?

Production serves one deployment at a time. Older versions can live in folders inside the build, the way most docs tools do it, or on branch previews for a while.

Put your docs in the EU.

Create a team on the free plan and connect the docs repository.

Start free Talk to the founder