Platform team
Retiring a stale wiki for code-true reference
Generated the API reference straight from the gateway and bound every fact to source — reference drift fell to zero.
Story coming soonDesign partners
Teams 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, code-true documentation. Their stories are landing here as we grow.
Quotes and logos on this page are illustrative, drawn from our design-partner conversations until named stories are published.
In their wordsSEStaff engineerFintech design partner · illustrative
“We stopped arguing about whether the docs were right. They are bound to the code, so the answer is just yes.”
Reviewed & auditedCited answers
The teams who ship fastest keep their docs closest — a few of the kinds of teams shaping Gravity.
NorthwindApertureMeridianLattice LabsHalcyonFoundryBeaconCartographVantageKeystone
NorthwindApertureMeridianLattice LabsHalcyonFoundryBeaconCartographVantageKeystone
NorthwindApertureMeridianLattice LabsHalcyonFoundryBeaconCartographVantageKeystone
NorthwindApertureMeridianLattice LabsHalcyonFoundryBeaconCartographVantageKeystone
Placeholder wordmarks — named design-partner logos appear here as their stories go live.
- Live
- docs that update when your code does
- Cited
- AI answers that link their source
- Reviewed
- every change approved before readers see it
- SSO
- enterprise sign-in, roles, and audit
What partners feel first
The change teams notice in the first week
- 0
- Reference pages edited by hand to keep them current
- 0%
- Of AI answers cite the published source they came from
- 0 queue
- Every change reviewed in one place before readers see it
- 0 afternoon
- To migrate off GitBook with structure and links intact
Illustrative figures from our early design-partner programme.
In their words
What design partners tell us
Persona-based voices from the teams shaping Gravity. Clearly illustrative until named stories are published — honest about where we are.
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.
Stories in progress
Case studies, landing soon
The first named case studies are being written with our design partners. Here is the shape of each — full stories land in this space.
Security & 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 coming soonSupport & success
Answers the support team can actually trust
Grounded, cited answers from published content turned the docs into the first line of support, for people and agents alike.
Story coming soonPut your name on this page.
Join the design partners shaping the enterprise knowledge platform — and ship reviewed, audited, code-true docs from day one.