AI Gateway

Enterprise AI Gateway: Governed Model Access & Spend Control

Cloptima gives platform and engineering teams one high-performance, OpenAI-compatible control plane for model routing, spend limits, real-time guardrails, and token attribution across all AI providers.

Start free trialTalk to the founders
python
from openai import OpenAI

client = OpenAI(
    base_url="https://api.cloptima.ai/v1/ai",
    api_key="clop_vk_dPXO67p…",  # Cloptima virtual key, not a provider key
)

resp = client.chat.completions.create(
    model="gpt-5.5",
    messages=[{"role": "user", "content": "Summarize this ticket"}],
    extra_headers={"x-cloptima-team": "team-support", "x-cloptima-app": "support-copilot"},
)
What happens on every call
Your app
Calls one OpenAI-compatible endpoint with a Cloptima virtual key
Cloptima gateway
Approves provider + model, reserves budget, tags team/app, no-retention
Provider
OpenAI · Anthropic · Vertex AI · Bedrock
Usage record
Tokens, cost, latency, owner — attributed
The problem

Where AI spend actually starts

AI adoption usually starts with scattered provider keys, direct SDK calls, and inconsistent tagging. By the time finance sees the bill, teams cannot explain which app, agent, customer, or workflow created the spend.

  • Unapproved models and endpoints
  • Provider keys spread across apps and laptops
  • No consistent team, app, or environment attribution
  • Budget enforcement that happens after the provider bill
How it works

One governed endpoint, every provider

Applications call one governed endpoint while Cloptima applies policy, captures usage context, and normalizes spend signals across OpenAI, Anthropic, Gemini, Vertex AI, Bedrock, and compatible model APIs.

  • Route requests through approved providers and models
  • Issue app-scoped virtual keys instead of spreading provider keys
  • Attach team, app, environment, user, session, and run context
  • Apply spend, token, request, and model policies before calls leave the control plane
  • Keep gateway usage connected to cloud and Kubernetes ownership data
Day one

Start small, prove it, then expand

Start with a small set of production apps, create governed virtual keys, set default limits, and use dashboards to see spend by model, provider, team, and app before rolling controls out more broadly.

Architecture

Built for production traffic

The gateway supports low-latency budget checks, durable pre-flight reservations, resilient usage finalization, no-retention prompt policies, and policy snapshots for local or VPC deployment options. We publish exactly what a fully governed request costs end to end — see our benchmark (p95 up to 13ms for a fully governed request).

Developer quickstart

Keep your SDK, change the base URL

The gateway speaks the OpenAI and Anthropic protocols. Point your existing client at it and add attribution headers.

bash
curl https://api.cloptima.ai/v1/ai/chat/completions \
  -H "Authorization: Bearer $CLOPTIMA_PAT" \
  -H "X-Cloptima-Team: core-platform" \
  -H "X-Cloptima-App: billing-assistant" \
  -H "X-Cloptima-Environment: production" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.6",
    "messages": [{"role": "user", "content": "Analyze cloud infrastructure cost anomalies"}]
  }'
Get started

Launch path

Create a Cloptima virtual key, connect provider credentials or approved provider routes, update your SDK base URL, and add attribution headers or SDK metadata for richer chargeback.

Comparisons

How the Cloptima gateway compares

Cloptima vs LiteLLM

OpenAI-compatible gateway routing vs. full FinOps control plane, attribution, and hot-path team budget limits.

Cloptima vs Portkey

Routing and guardrails vs. pre-flight budget enforcement, finance ledger, and p95 up to 13ms end-to-end latency.

Cloptima vs Cloudflare AI Gateway

Edge proxying vs. enterprise attribution, team quota enforcement, and cost reporting.

Cloptima vs Helicone

LLM observability logs vs. active request-path budget controls, response caching, and unit economics.

FAQ

Questions teams ask

Put your first governed call through in five minutes

Point your SDK at the gateway, bind a policy, and watch the first call land on the ledger.

Start free trialTalk to the founders
No credit card required
5-minute setup
Free trial