Platform team
Retiring a stale wiki for code-true reference
Generated the API reference straight from the gateway and bound every fact to source, so reference drift fell to zero.
Story in progressTeams who take their word seriously run on Gravity.
Gravity is early, and shaped in the open with a small group of design partners: platform, security and support teams who publish reviewed, audited documentation that stays true to the code. Their stories will land here as we grow.
Quotes and logos on this page are illustrative, drawn from our design-partner conversations until named stories are published.
“We stopped arguing about whether the docs were right. They are bound to the code, so the answer is just yes.”
- LiveDocs that update when your code does
- CitedAI answers that link their source
- ReviewedEvery change approved before readers see it
- SSOEnterprise sign-in, roles and audit
The change teams notice in the first week.
Illustrative figures from our early design-partner programme.
- 0
- Reference pages edited by hand to keep them current
- 0%
- Of AI answers cite the published source they came from
- 0queue
- Every change reviewed in one place before readers see it
- 0afternoon
- To import your existing docs with structure and links intact
The teams who ship fastest keep their docs closest. A few of the kinds of teams shaping Gravity:
- Northwind
- Aperture
- Meridian
- Lattice Labs
- Halcyon
- Foundry
- Beacon
- Cartograph
- Vantage
- Keystone
Placeholder wordmarks. Named design-partner logos appear here as their stories go live.
Case studies, landing soon.
The first named case studies are being written with our design partners. Here is the shape of each; the full stories will land in this space.
Security and compliance
A review loop the security team signed off on
Every published version is immutable and audited, so the evidence their compliance review asked for is built in.
Story in progressSupport and success
Answers the support team can actually trust
Grounded, cited answers from published content made the docs the first line of support, for people and agents alike.
Story in progressWhat design partners tell us.
Persona-based voices from the teams shaping Gravity, illustrative until named stories are published.
Our security review used to be the thing that held a docs change for a week. Now every published version is immutable and audited; the evidence is just there. It moved from a blocker to a rubber stamp.
“We pointed Gravity at the gateway and the API reference wrote itself, then stayed correct when we shipped. Reference drift basically stopped being a thing we manage.”
“Support answers now cite the published page they came from, so an agent can trust them and a customer can click through. The docs became our first line of support, not our last.”
“I ask for a change in plain language and watch the draft revise itself, but nothing reaches a reader until it has been approved. It feels fast without ever feeling loose.”
“Migrating our docs took an afternoon, links and structure intact. The part I did not expect: our coding agents now read the docs over MCP and stop guessing.”
Put your name on this page.
Join the design partners shaping Gravity, and ship reviewed, audited docs that stay true to your code from day one.