For customer-facing docs
A GitBook you can defend
Beautiful, on-brand public documentation — where every change is reviewed before a customer sees it, every version is immutable, and the whole record stands up in a security review.
Reviewed · versioned · audited · on your own domain
Authentication
Authenticate every request with a bearer token. Tokens are short-lived and refresh automatically.
curl https://api.yourbrand.com/v1 \ -H "Authorization: Bearer …"
Nothing reaches customers unreviewed
Reviewed, then published — never the other way round
Scroll to walk one public-docs change from a fresh proposal to a published, notified version — the same gate every change clears.
Review
Every edit — written by a person or proposed by AI — arrives as a proposal in one queue. There is no path to a reader that skips it.
Approve
Your required reviewers sign off. The gate is enforced, not advisory, and you decide who holds it per project.
Publish
Merge publishes a content-addressed, signed version to your domain — what you approved is exactly what readers see.
Notify
The customers who subscribed to the pages that changed are notified the moment it goes live.
Update the authentication guide
guides / authentication.md · a public, customer-facing page
Custom domain · edge speed
Live on your own domain, fast everywhere
Point a CNAME at Gravity, we issue the certificate, and your reviewed docs are online — on your brand, served from the edge, indexed under your name.
Your domain, your trust
Readers stay on your domain with HTTPS managed for you — never bounced to a third party — and search engines credit your site, not ours.
Fast at the edge
Published versions are served from a global edge network, so customers anywhere load your docs in a blink.
Search that cites its sources
A semantic search and assistant trained on exactly what you published — every answer pointing back to the page it came from.
- 0ms
- median load at the edge
- 0.00%
- uptime, managed for you
Authentication
Authenticate every request with a bearer token. Tokens are short-lived and refresh automatically.
curl https://api.yourbrand.com/v1 \ -H "Authorization: Bearer …"
Resolving your domain…
Built for your security review
A docs site that holds up under scrutiny
Everything a reviewer asks of a public docs site — and the evidence to back each answer up.
Versioned and immutable
Every publish is a content-addressed, signed version. You can point to exactly what a customer saw on any date — and prove it has not been altered since.
Audited end to end
Every proposal, comment, approval and publish is retained and searchable. When a reviewer asks who approved a change and when, the answer is one query away.
Accessible and yours
Semantic, accessible markup on your own domain, served from the edge — fast for readers and credited to your site in search, never to ours.
- 0%
- of published changes pass review
- 0
- unreviewed edits reach customers
- 0%
- of versions retained, immutable
See it in the wild
A real published site, on your brand
The illustrations on this page are mock previews. The real thing is a live, themeable docs site on your own domain.
A live branded docs site on a custom domain
Go deeper
Everything underneath the surface
The publishing and review machinery behind a public docs site you can defend — and an honest look at how it compares.
Publishing & brand
Theme your docs to look unmistakably yours, then ship them on your own domain — with guardrails that make it impossible to look cheap.
See publishingReview & audit
A pull request for your docs: every change reviewed, approved and kept on the record before a single reader sees it.
See review & auditGravity vs GitBook
Migrating from GitBook? See, honestly, where Gravity is stronger — and where it is not — before you move.
Compare the twoA public docs site you can defend.
Bring your content over, theme it to your brand, and publish on your own domain — with every change reviewed, versioned and on the record.