Build on Gate
Gate is the shared platform layer behind ShellTime, Rawback, and the Evonia products that follow. It issues identities, decides permissions, stores encrypted configuration, records usage, and runs billing — so each product does not have to build any of it again.
These guides cover the integration side: what your application talks to, which credential it should carry, and what Gate expects in return. For the machine-readable contract, use the OpenAPI explorer.
What Gate gives you
An OAuth 2.1 and OpenID Connect provider with authorization code, PKCE, refresh tokens, and client credentials. Any conformant library works.
02Two layers of permissionsControl-plane roles govern who may administer Gate. Project roles govern what your product's own users may do.
03Encrypted configurationVersioned variables and AES-256-GCM secrets, scoped per environment, with reveal auditing.
04Usage and billingIdempotent usage ingestion, Stripe plans and checkout, entitlements, and durable webhook processing.
Start here
If you are new, read in order. Each page assumes the one before it.
-
Quickstart — create an organization and project, mint a key, make a call.
-
Core concepts — the nouns Gate uses and how they nest.
-
Choose an integration mode — the one decision that determines everything else about your integration.
The two things people get wrong
Where things live
| Purpose | Path |
|---|---|
| Platform API | /api/v1 |
| OpenAPI document | /api/v1/openapi.json |
| OpenAPI explorer | /docs/api-reference |
| OIDC discovery | /.well-known/openid-configuration |
| OAuth metadata | /.well-known/oauth-authorization-server |
| JSON Web Keys | /.well-known/jwks.json |
| Auth and OIDC protocol routes | /api/auth/* |
| Portal | /dashboard |
| Health | /api/v1/health |