The platform

One governed system, from the commit to the customer.

Gravity is where your documentation is generated, written, reviewed and read — one connected path that turns a code change into an answer your customer can trust, with a complete record of how it got there.

  • Commit
  • Generated
  • Reviewed
  • Published
  • Answered
An abstract iridescent surface representing your documentation, under sandblasted glass
Move your cursorThe fog clears where you look

Follow one change

From a commit to a customer’s answer

Scroll to watch a single API change travel the whole platform — generated, reviewed, published and answered — without ever leaving the loop.

Commit
Generated
Reviewed
Published
Answered
Stage 1 / 5 · Commit

A change lands in your codebase

An engineer adds rate-limit headers to an endpoint and merges. Nothing about the docs is touched by hand — Gravity is already watching the source it was pointed at.

How generation works
router.go
+w.Header().Set("X-RateLimit-Limit", "100")
+w.Header().Set("X-RateLimit-Remaining", n)
merged to main

Six parts, one platform

Everything documentation needs, governed end to end

Each part stands on its own — and works better because the others are right next to it. Explore any of them in depth.

Generation

Docs that follow your code, not the other way round

API reference and structure derived from your codebase, with drift caught in CI before your customers find it.

  • API reference from your gateway
  • Drift caught in your pipeline
  • You own the words, we keep the facts
Explore generation
source
Gravity
reference

Editor

Write together, with no save button to wait on

Real-time co-editing with presence, comments and a clean version history you can actually read.

  • Live presence and cursors
  • A rich block toolkit
  • Comments where the work is
Explore editor
3 editing now

Review & publish

Every change earns its place in front of a reader

One review-and-approve workflow for every change, with a complete history kept for your compliance team.

  • One queue for every change
  • Approve in plain language
  • Customers notified on publish
Explore review & publish
Review queue
Generated updateApproved
New: webhooks guideIn review
Fix auth paramsPublished

AI & search

Answers your customers can verify, line by line

Cited AI answers from your own docs, gap detection from real questions, and an MCP memory for your agents.

  • Answers grounded in your docs
  • See what’s missing
  • Memory for your coding agents
Explore ai & search
Reader assistant
How do I rotate an API key?
Call POST /v1/keys/rotate. The old key stays valid for 24h.
[1] API keys[2] Security

Import & migrate

Switch off GitBook without losing a page

Import from GitBook and Markdown repos with structure preserved, so switching is a migration, not a rewrite.

  • GitBook, brought over whole
  • Markdown from your repo
  • Nothing lost in translation
Explore import & migrate
Brought over whole
GitBookMarkdownOpenAPIREADMEMDXDocs repo
GitBookMarkdownOpenAPIREADMEMDXDocs repo
GitBookMarkdownOpenAPIREADMEMDXDocs repo
GitBookMarkdownOpenAPIREADMEMDXDocs repo
Links keptStructure keptRedirects keptHistory kept
Links keptStructure keptRedirects keptHistory kept
Links keptStructure keptRedirects keptHistory kept
Links keptStructure keptRedirects keptHistory kept

Publishing & brand

A docs site that looks unmistakably yours

On-brand, custom-domain docs with analytics that show you what readers actually do.

  • Your brand, within guardrails
  • Your own domain
  • Docs for every audience
Explore publishing & brand
docs.acme.com
0 readers

Why teams trust it

Governed by design, not by hope

0 queue
Every change — human, AI or generated — reviewed in one place
0%
Of answers cite the published source they came from
0/7
Your docs available to readers and coding agents over MCP
0 afternoon
To migrate off GitBook with structure and links intact

Four principles

What makes it one system, not a pile of features

One path, not five tools

Generation, editing, review, publishing and search live in one platform, so a change never falls between the cracks of a handoff.

Nothing reaches readers unreviewed

Human edits, AI suggestions and generated updates all pass through the same approval before anyone outside your team sees them.

Every change is on the record

Proposals, comments, approvals and publishes are retained and searchable — the audit trail your security review will ask for.

Answers always cite their source

The assistant answers only from your published, reviewed content and links back to it — never the open web, never a guess.

Give your docs gravity.

Import from GitBook, point us at your repo, and publish your first reviewed version today.