Gravity is now available.

See pricing
Gravity
Book a demo

One 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 customers can trust, with a record of how it got there.

See Gravity in actionRequest access
G

Acme API docs Add rate-limit headers

  1. Code changes

    router.go

    + X-RateLimit-Limit

    + X-RateLimit-Reset

    Merged to main

  2. Reference drafted

    Response headers

    X-RateLimit-Limit
    int
    X-RateLimit-Remaining
    int
    X-RateLimit-Reset
    int

  3. Reviewed

    Priya approved

    “Clear. Added an example response.”

    Ready to publish

  4. Published

    docs.acme.com/rate-limits

    Rate limits

    Subscribers notified

  5. Answered

    When does my limit reset?

    Read X-RateLimit-Reset…

    Source: Rate limits

One change, start to finish.

Generation, editing, review, publishing and search live in one place, so a change never falls between two tools. Here is one API change on its way from a commit to a reader’s answer.

  1. A change lands in your code

    An engineer adds rate-limit headers to an endpoint and merges. Nobody touches the docs by hand: Gravity is already watching the source you connected.

    How generation works

  2. Gravity drafts the reference update

    It reads the change and proposes the matching update to the reference: the new headers, their types and an example.

    How generation works

  3. A person approves it

    The update joins the same review queue as hand-written edits. A reviewer reads the difference, asks for a wording change in plain language, and approves.

    How review works

  4. It goes live on your docs site

    The approved change publishes to your own domain, the people who follow that page can be notified, and the version is kept on the record.

    How publishing works

  5. Readers get a cited answer

    Someone asks how rate limiting works. The assistant answers from the page that was just published and links to it. Your coding agents can read the same reference over MCP.

    How AI and search work

One system, not a pile of features.

  • One path, not five toolsGeneration, editing, review, publishing and search share one platform, so nothing gets lost in a handoff.
  • Nothing reaches readers unreviewedHuman edits, AI suggestions and generated updates all go through the same approval before anyone outside your team sees them.
  • Every change is on the recordChange requests, comments, approvals and publishes are kept and searchable: the audit trail a security review asks for.
  • Answers cite their sourceThe assistant answers only from your published, reviewed content and links back to it. It never answers from the open web.
G

History Add rate-limit headers · #418

  1. G

    Gravity opened a change request from router.go

    09:02

  2. Priya asked for an example response

    09:14

  3. Marco approved as required reviewer

    09:40

  4. Priya published version 3.4

    09:41

Seven parts, one platform.

Each part stands on its own and works better because the others sit next to it.

  • Create · Write the docs, and generate them from code
  • Control · Decide what goes out, when, and to whom
  • Answer · Turn the docs into answers for people and agents

Generation in CI

Create

Docs that follow your code

Connect a repository once and every merge runs Gravity in your pipeline: it works out what changed and drafts the matching reference, guides and changelog for review. On pull requests, it fails the check when the docs have drifted.

Learn more about Generation in CI

Editor

Create

Write together, with no save button

Live presence, comments on the exact block, and the blocks docs need: code, tables, tabs, callouts and diagrams.

Learn more about Editor

Review & publish

Control

Nothing goes live unreviewed

Edits, AI drafts and generated updates share one queue. Approve now or schedule the release, and notify the readers who follow the page.

Learn more about Review & publish

Versioning

Control

Every version kept, and provably untouched

Each publish is a new numbered version with a block-by-block diff. A hash chain shows no past version was changed, and readers can open the site as it was on any date.

Audiences

Control

The right docs for each reader

Show or hide spaces for each audience, keep single blocks for developers, and share a private audience by a link you can revoke at any time.

Ask AI

Answer

Answers that show their sources

An assistant on your docs site that answers only from published pages, cites every claim, and never uses what the reader is not allowed to see. The questions it could not answer become your list of docs to write.

Learn more about Ask AI

Nucleus

Answer

A memory your agents can read

Gravity condenses your docs into facts, decisions and procedures, linked to each other and kept current as you publish. Any MCP client can recall them, and what AI writes back can wait for a person to approve.

Give your docs gravity.

Start from your existing docs, upload what you have, or begin with a blank page, and publish your first reviewed version.

Book a walkthroughRequest access