hstd
For product docs, handbooks and API references

Docs that deploy as easily as they build.

Your docs generator already produces a folder of HTML. hstd is the place that folder goes, with a preview per version so nobody ships a broken sidebar.

Free for 3 sites on hstd.app. No card needed.

Sound familiar?

  • A hosting setup more complicated than the docs it serves.
  • No preview before a docs update goes live.
  • Team members who can write docs but cannot deploy them.

hstd is the opposite of all three. Files in, live URL out, you keep the publish button.

How it works here

  1. 01

    Build as usual

    Docusaurus, MkDocs, VitePress, Sphinx, mdBook: any tool that outputs HTML.

  2. 02

    Upload the output folder

    Zip it and drop it, or let a script post it to /uploads and import it over MCP.

  3. 03

    Preview, then publish

    Every build is a version with a link. Publish when the team has looked.

What you get

Everything on this page is on the free plan unless it says Pro. Prices and limits are on the pricing page .

Works with
Docusaurus MkDocs VitePress Sphinx mdBook Starlight Astro
Team roles
Writers deploy, admins manage sites and domains, owners handle billing. A team can have several owners.
Preview every version
v14 and v15 both have their own address. Compare before publishing.
docs.yourproduct.com
Custom domains with automatic HTTPS on Pro.
Redirects when pages move
A _config.json in the build maps "/v1/*" to "/v2/:splat" so old links keep working, and names your own 404 page.

Questions people ask

Can I deploy from CI?

Yes. Post the built zip to https://hstd.app/uploads from your pipeline, then call the import-upload MCP tool, or drop it by hand. Full steps are in the docs.

Do you support client-side search?

Yes. Search indexes are just files, so Lunr, Pagefind and the built-in search of most generators work as they do locally.

Can several people deploy?

Yes. Invite them to your team. Members can upload and publish; admins can also create sites and connect domains.

Are old versions kept?

The last five published versions plus the live one, and any draft. Roll back in one click.

What happens to old URLs when I restructure the docs?

Add redirects to _config.json in the build output, with wildcards and :splat for whole sections. Anything still missing lands on the 404 page you name there instead of a bare error.

Ready when you are.

Your first site can be live before the kettle boils.