For SaaS products

Docs your whole team can keep up to date.

Product guides and a help centre on docs.yourapp.com. Support writes and fixes pages in the browser, or engineering keeps Markdown in GitHub and the site updates on every push.

Acme Help

Invite your team

Owners and admins can invite people from Settings → Members. Invitations expire after seven days.

Tip

Members can see every project in the workspace.

§ 01 · Why it fits

Built for product teams.

Product guides and a help centre on your own domain, kept current by support and engineering.

01

Support fixes pages in minutes

When a ticket shows a gap, whoever answered it adds the answer. No pull request, no waiting for a release.

02

Or keep Markdown in your repo

Connect a GitHub repository and the site rebuilds itself from your Markdown on every push.

03

On your own domain

Point docs.yourapp.com at us with a CNAME. We verify it and issue the certificate.

04

Answers for AI assistants

Turn on the MCP endpoint and AI tools search and quote your current docs instead of guessing.

§ 02 · Included

What you get out of the box.

Search and ⌘K

Customers find answers before they open a ticket.

Announcement banner

Flag a new release or a known issue across every page.

Drafts, then publish

Write ahead of a launch. Nothing goes live until you publish.

Version history

See what changed, compare versions and restore an old one.

Your brand

Your logo, colour and header links, so docs feel like part of the product.

Your analytics

Connect your own Fathom account to see which pages get read.

§ 03 · Where to start

Start on Starter.

Starter adds custom domains and up to 3 sites. Need more sites or priority support? Pro has 10.

§ 04 · Questions

Before you start.

Can we put the docs on our own domain?

Yes, on the Starter and Pro plans. Add a CNAME record for an address such as docs.yourapp.com; we verify it and issue the certificate. Until then the site runs on a free subdomain.

Can engineers keep the docs in Git?

Yes. Connect a GitHub repository and every push updates the site from its Markdown files. Each site uses either the browser editor or GitHub sync, so you can run a help centre in the editor and developer docs from a repository side by side.

Can AI assistants answer from our docs?

Each site can turn on an MCP endpoint. AI tools that support the Model Context Protocol can then search and read your published pages.

Can we prepare pages before a launch?

Yes. Edits save as drafts and stay private until someone publishes them.

Your first page can be live in five minutes.

Write it in the browser, publish it in a click. Your tenth will take less.