An open-source API Governance Platform

Gravity for APIs.

Ship APIs that won't break your consumers.

Get started

Free · Self-hosted · Apache 2.0 · No signup required

grapity --tour · 60s

The problem

Your API is governed by memory, not by code.

Six symptoms, one root cause. You've likely dealt with all of them.

Specs are scattered

OpenAPI and AsyncAPI files live across repos, owned by different teams, sometimes absent. No single place answers "what APIs do we have?"

Breaking changes ship silently

A developer removes a required field, changes a schema, or renames a channel. No CI gate. No notification. Downstream teams discover it during an incident.

Consuming APIs is manual

Teams write HTTP clients, Kafka consumers, and WebSocket boilerplate by hand. The spec that describes exactly how to connect exists, but nothing generates typed code from it.

The gateway is disconnected

Auth schemes, rate limits, and routing rules are configured separately from the specs that define the API. When the spec changes, nobody tells the gateway.

AI tools work from stale context

Coding assistants hallucinate endpoints, use deprecated fields, and generate code that doesn't match the spec. No compact, LLM-optimised representation exists.

No audit trail

When a breaking change causes an incident, nobody can answer who changed it, when, or whether it was reviewed. Contract evolution is ungoverned.

The solution

Contract-first, from push to production.

One source of truth. Enforced at every step.

Roadmap Coming later

grapity Forge

Typed clients and consumers, forged from specs. Wraps existing generators into a unified pipeline per service across languages and protocols.

grapity Schema

Bridges AsyncAPI specs with schema registries (Confluent, AWS Glue, Apicurio). Producers and consumers share the same version.

grapity Mind

Specs compressed for AI. Auto-generated LLM-optimised representations. Breaking change explanations in plain language.

How it works

Start. Push. Provision. Explore.

Four steps. One running system. The spec drives everything downstream.

01

Start both servers

$ grapity serve

● Registry ready  ·  http://localhost:3750
● Hub ready     ·  http://localhost:3000

# Open http://localhost:3000 to browse your APIs

One command starts both servers. The Registry validates and stores specs. The Hub serves the developer portal. No Docker, no config files.

↓
02

Your spec earns its place

$ grapity registry push ./openapi.yaml --name payments-api

✓ Spec validated
✓ Backward compatibility: 0 breaking, 2 safe changes
✓ Version 1.1.0 registered

Every push is diffed against the previous version. Breaking changes are blocked with a precise explanation. No breaking change slips through.

↓
03

Provision the gateway

$ grapity gateway push payments-gateway.config.yaml

✓ payments-gateway pushed
◆ Version 018f...

$ grapity gateway provision --name payments-gateway --env staging --sync

Running deck gateway sync against http://localhost:8001…
✓ Applied for payments-gateway → staging

Push the gateway config to the registry, then provision it to Kong via decK. The CLI validates routes against the spec, generates decK YAML, and runs deck gateway diff (or sync with --sync). No handoff, no ticket.

↓
04

Browse and explore

http://localhost:3000 grapity Hub ← Back ENDPOINTS ▼ Groups GET /groups POST /groups DELETE /groups/{id} GET /groups/{id} PUT /groups/{id} ▼ Permissions GET /permissions POST /permissions DELETE /permissions/{id} GET /permissions/{id} ▼ Users GET /users POST /users DELETE /users/{id} GET /users/{id} PUT /users/{id} PATCH /users/{id}/status users-api openapi 1.0.0 initial 6/5/2026 Overview Changelog Versions Compare Raw Spec Endpoints GROUPS GET /groups List groups Retrieves all groups defined in the system. Groups are organizational units used to manage user collections. RESPONSES 200 A list of groups [ { "id": "grp_99" , "name": "Engineering" , "description": "Engineering team members" , "memberCount": 12 , "createdAt": "2025-06-01T00:00:00Z" } { "id": "grp_88" , "name": "Product" , "description": "Product management team" , "memberCount": 5 , "createdAt": "2025-09-15T00:00:00Z" } ]

Click into any spec to see its OpenAPI endpoints rendered with schemas, parameters, and example requests. Understand an API without reading YAML.

Pricing

Self-host for free. Scale with us.

The open source product is complete. Cloud hosting scales with your team.

Self-hosted

Run everything on your own infrastructure. No limits.

  • Backward compatibility engine
  • Unlimited APIs
  • Unlimited team members
  • Self-managed PostgreSQL
  • Developer portal (Hub)
  • Version history and comparison
$0 Free forever. Apache 2.0.
Get started

Cloud

Hosted by grapity. Same features, we run the infrastructure.

  • Backward compatibility engine
  • Unlimited APIs*
  • Unlimited team members**
  • Managed PostgreSQL with backups
  • Managed Developer portal (Hub)
  • Version history and comparison
$29.95/mo 5 APIs* and 5 users** included, then: +$1.99 per additional API / mo +$0.99 per additional user / mo
Get in touch

We sell operations, not features. Self-hosted and Cloud run the exact same software. The only difference is who operates it.