Labs / AI Gateway

Every LLM call,through one governed gate.

AI Gateway is the pass-through layer for all LLM traffic in your organization. Models, routers, MCP servers, guardrails, policies, budgets, access control, audits, and request logs — one control plane, in front of every provider.

Labs experiment · built by Lakeline Data · not a client engagement

  • Model & router management
  • MCP registry
  • Guardrails
  • Policies
  • Budgets
  • Access control
  • Audits & request logs
Architecture

Everything passes through. Nothing goes around.

CALLERS
Product apps
Agents & copilots
Notebooks & jobs
AI GATEWAY
AuthN / RBACkeys · teams · scopes
Policies & guardrailsPII · topics · schemas
Routercost · latency · fallback
Budgets & meteringper team · per app
Audit & request logsevery call, replayable
PROVIDERS & TOOLS
Claude · GPT · Llama
Self-hosted models
MCP servers

SWAP A MODEL, ROTATE A KEY, OR TIGHTEN A POLICY — WITHOUT TOUCHING A SINGLE APP.

REQUEST LOGLIVE
14:02:11 · support-bot · claude-sonnet · 1.2k tok · $0.004 · ALLOW
14:02:09 · finance-agent · gpt-4.1 · 3.8k tok · $0.021 · ALLOW
14:02:08 · intern-notebook · llama-70b · 0.9k tok · $0.001 · REDACTED: PII
14:02:05 · support-bot · claude-haiku · 0.4k tok · $0.001 · ALLOW · FALLBACK
14:02:01 · marketing-tool · gpt-4.1 · — · — · DENY: BUDGET CAP
BUDGETS · THIS MONTH
PRODUCT
46%
DATA TEAM
71%
MARKETING
98%
How it works

Register. Govern. Observe.

  1. 01

    Register. Providers, self-hosted models, and MCP servers go into one registry; keys live in the vault, apps get scoped gateway credentials — never raw provider keys.

  2. 02

    Govern. Policies and guardrails (PII redaction, topic filters, output schemas), RBAC per team and app, budget caps with hard or soft enforcement, and routing rules with fallbacks.

  3. 03

    Observe. Every request logged and replayable — model, tokens, cost, latency, policy verdict — with audit exports and per-team chargeback built in.

Why it exists

Because "everyone has an OpenAI key" is not a platform.

The moment LLMs spread past one team, you inherit shadow keys, unbounded spend, unlogged prompts carrying customer data, and apps hard-wired to a single provider. AI Gateway centralizes the mess: one endpoint, one policy engine, one bill.

It's also how you stay portable — when a better or cheaper model ships, the router change is one line in the gateway, not a release across twelve apps.

Where it’s useful

Three places it earns its keep.

PLATFORM TEAMS

One endpoint for the whole org

New teams onboard with a scoped gateway key in minutes — no provider accounts, no shared secrets, no procurement loop per project.

REGULATED WORKLOADS

Compliance without slowing teams down

PII redaction at the gate, topic filters per policy, and a replayable audit log of every prompt — the review that used to block launches becomes a query.

AGENT FLEETS

Dozens of agents, one control plane

Agents share models and MCP tools through the gateway — routed by cost and latency, metered per agent, and capped before one runaway loop eats the month's budget.

How many LLM keys are loose in your org right now?

We'll stand up AI Gateway in front of your providers and show you the first week's request log.

Request a walkthrough