Open source · self-hostable

One gateway for every API key you manage

Stop handing out real API keys. Issue safe proxy tokens, route every request through one gateway, and see exactly how each upstream API is used — requests, tokens, latency, and cost.

Get started free See how it works

request.sh

# your app calls the gateway, not the provider
curl https://gateway.yourapp.com/proxy/v1/chat/completions \
  -H "Authorization: Bearer xpxy_live_a1B2c3…"

# the gateway injects your real key — clients never see it
sk-proj-REAL_SECRET_KEY_never_shared

Secrets encrypted at rest

Native SSE streaming passthrough

Per-API usage analytics

One-time token reveal

How it works

Three steps between you and a fully monitored API gateway.

STEP 01

Add your API

Name it, point it at any base URL, paste the key — OpenAI, Anthropic, or your own backend, no provider to pick. It's encrypted immediately and never shown again.

STEP 02

Get a proxy token

Mint an xpxy_live_… token for each app or teammate that needs access. Revoke any token instantly, any time.

STEP 03

Watch usage roll in

Every request is logged automatically — requests, tokens, latency, cost, and errors, charted per API.

Everything you need to manage API access

Built for teams and solo developers wiring up LLM and third-party APIs.

Key masking

Clients get an xpxy_live_… proxy token instead of your real key. It's encrypted at rest and injected server-side on every request.

Usage analytics

Requests, tokens, latency, cost, and errors — charted over time for every API, down to each individual request.

Any API, no provider lock-in

Registering an API is just a name, a base URL, and a key — nothing coupled to OpenAI, Anthropic, or anyone else. Point it at any backend.

Streaming passthrough

Server-sent event streams pass straight through the gateway, chunk by chunk, with no added buffering latency.

Scoped access

Create a separate proxy token per app, teammate, or environment — and revoke exactly one without touching the rest.

Revoke instantly

Suspend a token or disable an API and it stops working immediately — no cache window, no stale access.

What actually happens on each request

The real key never leaves the gateway.

Your app

Calls the gateway with a proxy token — never the real key.

API Manager

Verifies the token, decrypts your real key in memory, and logs usage.

Upstream API

Receives the request with the real key injected. Streams straight back.

Built with security as the default

The whole point of a gateway is that your real credentials never reach a client. Here's how that holds up in practice.

Upstream secrets are encrypted at rest — never stored or logged in plain text.
Proxy tokens are stored as a one-way hash; the raw token is shown exactly once, at creation.
Revoking a token or disabling an API takes effect immediately — no stale cache window.
Every proxied request is authenticated independently; there is no shared session between clients.
All traffic to and from the gateway is expected to run over TLS.

Frequently asked questions

Start managing your APIs today

Free, open source, and self-hostable. No credit card required.

Create your free account