Govern people and agents in a single layer: ACID financial pre-authorization, multi-LLM routing and tamper-proof audit — between your applications and any provider (OpenAI, Anthropic, Google or self-hosted).
Multi-LLM
providers + self-hosted
ACID
reserve → settle on every call
SHA-256
chained, verifiable audit
0
keys exposed to the caller
// running AI without governance is expensive
Every team spins up its own provider key, with no limit and no visibility. The bill only shows up at the end of the month.
Reserve → settle cycle on every call. With no budget left in the area, the call does not happen (HTTP 402).
Every automation — n8n flow, agent, script — gets its own key and spends without limits. Nobody knows which agent did what, or how to cut one off without taking down the rest.
Each agent is a headless identity with an owner, environment, models, IPs and its own token. Budget and rate limit per agent; suspend or rotate in isolation.
With no reliable record of what was spent and why, audit and compliance turn into fragile manual work.
Append-only trail chained by SHA-256, verifiable, with PII redacted before any persistence.
// what the gateway does on every call
Managed providers and self-hosted models behind a single OpenAI-compatible API. Credentials encrypted (AES-256), never revealed to the caller.
Before the AI runs, it reserves the worst-case cost against the area budget; then settles the real cost. With no budget, the call never leaves (HTTP 402).
Each automation (n8n, agent, script) is a headless identity with owner, budget, models and its own gw_ token. Suspend or rotate in isolation.
Per-call ceiling, per-area budget, end-of-month forecast and automatic switch to a cheaper model. Semantic cache removes repeated calls.
Spend traceable by area, account and token. Z-score detection suspends anomalous tokens. PII redacted before persisting.
Prompt library with variables and artifact generation (PPTX, PDF, infographic) straight from the conversation — ready to download.
// financial governance, per call
Not a thin proxy. Before calling the AI, the gateway reserves the worst-case cost against the area budget; then debits the real cost. End-of-month forecast and per-area ceilings prevent billing surprises.
✓ reservation freed · budget returned
end-of-month forecast: $5.9k · within ceiling
// drop-in, OpenAI-compatible
The API is compatible with the OpenAI format. Point your SDK at the gateway, use a gw_… token instead of the provider key, and every call becomes authorized, metered and audited — without touching your code.
one line changes · governance on every call
// security and compliance
Provider keys encrypted with AES-256. Master key in an environment variable, never in the database. Revealable only by the admin, once, under confirmation.
The audit trail is append-only, chained by SHA-256. Deletion is blocked at the database. The chain is verifiable at any time.
Personal data (national IDs, email, phone, card) is redacted before persisting and before sending to the provider — closing off inbound and outbound leaks.
Any doubt about quota, authentication or state results in a refusal. Rate limit, IP allowlist and anomaly suspension protect every token.
Login via Entra ID / Microsoft 365, Okta or Google Workspace, with account provisioning on first access and role-based profiles.
Docker Compose stack as the production artifact: on-premise or in your cloud. Datastores on an isolated network, daily backup with configurable retention.
// frequently asked questions
No. The API is OpenAI-compatible and routes to OpenAI, Anthropic, Google or self-hosted models (vLLM, Ollama). Switching providers is configuration, not a code rewrite.
Overhead is minimal: observability runs in the background (it never blocks the response) and the semantic cache answers instantly on a hit. Reserve and settle are millisecond database operations.
Yes. The production artifact is a Docker Compose stack — on-premise or in your cloud, with datastores on an isolated network, daily backup and assisted zero-downtime migration.
PII (national IDs, email, phone, card) is redacted before persisting and before sending to the provider. With self-hosted models, data never leaves your network. Every operation lands in a verifiable audit trail.
Change your SDK base URL and use a gw_ token instead of the provider key. Works with Python, Node, cURL and automations like n8n — without changing your application.
Yes. Each automation (n8n flow, agent, script) is a headless identity with its own owner, budget, models and token — governed and auditable individually.
Book a demo and watch reservation, settlement and audit happening on a real call — in your environment.