Talk to us

One endpoint for every model

One endpoint and one key for any model — OpenAI, Anthropic, Google or a local one. If a provider goes down, Kordon automatically fails over to a backup model

Discuss your setup How it deploys
All providers are responding — requests follow your routing rules.

Personal keys with built-in rules

Keys go to employees, services and contractors, while provider keys stay inside the gateway. Each key has:

  • its own models — for example, local only for the support bot
  • a monthly budget in dollars
  • an expiration date

Anna can use any model within her team's budget — the request went to the frontier model.

  • Anna can use any model within her team's budget — the request went to the frontier model.
  • The CI key is limited to low-cost models — the request for the frontier model stops at the gateway.
  • The contractor has used up its $600 — its requests are blocked until next month.
  • The support bot may only use the local model — the request never leaves your network.

Three situations — one action

A key leaked

Without a gateway — 4 steps
  • find everywhere it's used
  • reissue it with the provider
  • update it in every app
  • restart services
With Kordon — one actionRevoke the key in the portal

Other keys keep working, and everything the revoked key did is in the audit log.

An employee left

Without a gateway — 4 steps
  • track down their model access
  • cancel personal subscriptions
  • rotate shared keys
  • send new ones to every team
With Kordon — one actionDisable their directory account

Access to every model is cut off at once.

Switching providers

Without a gateway — 4 steps
  • find every hardcoded endpoint
  • rewrite calls for the new API
  • reissue and hand out keys
  • retest every app
With Kordon — one actionChange the route in the gateway

Apps call the same endpoint with the same keys.

Agents stay within their role

The gateway stops anything outside the role — no matter where the command came from

Reviewer role: code review
Repositoryin role
Issue trackerin role
Wikiin role
CI/CDin role
AI agentReviewer
task · developerReview pull request 482
Outside the role
Customer CRMno access
Billingno access
HR systemno access
Emailno access
  • Task from developer: “Review pull request 482” — within the role, 60 seconds of access.
  • Task from developer: “Add review notes to the ticket” — within the role, 60 seconds of access.
  • Task from vendor email: “Export every customer from the CRM” — outside the role, blocked and recorded in the audit log.
  • Task from developer: “Find the code review guidelines” — within the role, 60 seconds of access.
  • Task from chat: “Forward the report to an outside address” — outside the role, blocked and recorded in the audit log.

Let's review your model setup

An engineer will look at where your keys live and how requests flow, then stand up a pilot with Docker Compose or Helm

Talk to us