Skip to content

Every AI call your company makes,
metered, filtered, and logged.

A zero-trust reverse proxy for your LLM traffic. Point your SDK at Vgil to enforce policies, mask PII, and record every token.

Vgil in one sentence

Vgilkeepswatch.Everyrequestyoursoftwaresendsamodel,everyanswerthatcomesback,andwhoeversetitinmotion—seenwhenithappens,andrememberedafter.NohiddenAPIwaste,nounvettedpromptleakingpastyourdefenses,andnountracedAIcalls.Completecontrolovereverytoken,fromdayone.

[C]
THREE BLIND SPOTS

What it costs. What it leaks. Who did it.
Three questions nobody can answer yet.

Month end
First time anyone sees total spend

Cost tracking is a scavenger hunt.

Everything your team spends on AI is scattered across engineer laptops, personal API keys, and agents nobody is watching. Finance reconciles invoices for days after the bill arrives — and the bill is the first time anyone sees the number.

PROBLEM SCENARIO01 // 03
In flight
Sensitive data uninspected at egress

Bending over backward to stop prompt leaks.

Customer accounts, internal financial reports, and confidential notes pass straight through third-party model providers. Building custom sanitization scripts for every internal tool is unsustainable.

PROBLEM SCENARIO02 // 03
Last Tuesday
Answerable only by reconstruction

No one can say which system made the call.

One key gets copied into a second service, then a scheduled job, then somebody’s laptop. Agents run unattended for hours. Nothing carries a name, so when someone asks what happened last Tuesday, the answer is a reconstruction.

PROBLEM SCENARIO03 // 03
SWIPE HORIZONTALLY (1 // 03)

All three happen in the same place: the moment your software calls the model. That is the one place to put a control — and it is where Vgil sits.

What Vgil does

Four things it does
from that one position.

SWIPE FOR ALL 4 FEATURES
THE GLASS BOX // LIVE PIPELINE INSPECTOR

Type anything at the page. Watch all six stages think.

Not pass or fail — the whole pipeline on one screen, every stage showing its own verdict and the reason it reached it.

Glass Box0 / 6
Any callerapp · agent · job
↓request
Vgil · six gatestap gate0/6
01Authenticate

Validates workspace key & HMAC signature

↓forward
The modelgpt-4o

Pick a payload or write your own, then send it. Watch which gates it clears.

In-browser simulation — same stages, same order. Nothing you type leaves this page.

Six controls

One line changes in your code.
Everything else is a setting in Vgil.

What each control does, where it lives, and what happens when it fires.

01Reverse proxy & multi-model router

In your code

Point your existing OpenAI or Anthropic SDK at api.vgilai.com. Your provider keys stay in Vgil, encrypted at rest and attached upstream — they never ship inside your application.

The one line
curl https://api.vgilai.com/openai/v1/chat/completions \
  -H "X-Vgil-Key: vgl_live_09x" \
  -H "Content-Type: application/json" \
  -d '{"model": "gpt-4o", "messages": [{"role": "user", "content": "Analyse risk"}]}'
What it reaches
OpenAIAnthropicGeminiCohere

Your request carries a Vgil key only. The provider credential is decrypted and attached server-side, on the way out.

Muninn // after the request

Enforcement is half of it. The other half is what you learn afterwards.

01 · Session tracing

One conversation, not forty requests

An agent run is dozens of calls. Read them one row at a time and the shape of it never appears. Vgil puts them back together as the run they belong to — what it cost, how long it took, how many calls it made, and whether anything was flagged along the way.

SessionsExample datalast 24h
SessionReqsCostDurationIssues
refund-triage-agent14$0.423m 12s—
support-summariser9$0.181m 40s1
onboarding-assistant31$1.077m 55s—
Avg 18 requests · 4m 16s per session
02 · Risk quantification

Risk with a number on it

Most governance tools hand you a red, an amber or a green. Vgil puts a dollar figure on each exposure instead. They rank by money rather than by colour, each carrying its loss type and the steps that would close it.

Risk · exposureExample dataannual
Annual loss expectancy
$134,100
Risk exposure ranking
  • 1Unredacted PII reaching a third-party modelLegal / regulatory$71.4k
  • 2Unmetered agent spendDirect operational$38.9k
  • 3No transparency notice publishedLegal / regulatory$23.8k
Control registry · 14 of 19 satisfied
03 · The advisor

It tells you what to fix first

The advisor looks across everything Vgil has seen and writes back a ranked list of what to do about it — each with an estimated saving and a deadline, each markable as applied once it is done.

AdvisorExample data3 insights
  • HIGHRequires immediate action

    Three API keys have no monthly cap set.

    Estimated saving $2,400 / mo

  • MEDIUMAddress within 2 weeks

    A large share of calls could route to a cheaper model.

    Estimated saving $1,150 / mo

  • LOWPlan for next sprint

    Session tracing is off for two workspaces.

ARCHITECTURE BLUEPRINT

Unmanaged API Calls
vs. Vgil Gateway.

What changes when every call goes through Vgil. One unified zero-trust proxy layer replacing key sprawl, raw data leakage, and blind upstream billing.

Direct Unmanaged Calls

The Leaky Perimeter

Every service reaches model providers on its own, with its own credentials copied across teams, repos, and environments.

UNPROTECTED EGRESS FLOWNO PROXY IN-BETWEEN
App Workers
Keys in .env
↓Raw Egress
Model Provider
OpenAI / Claude
Secret Exposure:High Risk
Audit Trail:Zero
Many exits: Every service calls the provider directly, on its own key.
Keys in application: Credentials copied into env files, repos and laptops.
No decision point: Nothing sits between the request and the provider.
No record: What was sent exists only in the provider’s billing.
Vgil Gateway (api.vgilai.com)

Zero-Trust AI Ingress

Change one base URL and Vgil sits in front of every request. Credentials stay in Vgil, in-flight PII is masked, and an immutable SHA-256 digest is sealed.

MANAGED ZERO-TRUST PROXYIN-FLIGHT DEFENSE
App Workers
Virtual Key
↓
api.vgilai.com
PII + Ledger
↓
Model Provider
Clean Request
Ledger:SHA-256 Sealed
Credentials:KMS Encrypted
Single ingress: Every call from every service arrives at one address.
Keys held server-side: Provider credentials stay in Vgil, encrypted, never in your app.
Decided before dispatch: Checks run on the way out, so a refusal costs nothing upstream.
Append-only record: Each call leaves a SHA-256 digest that cannot be revised.

Regulatory Frameworks & Audit Readiness

How each framework maps to cryptographic evidence recorded by Vgil

LIVE EVIDENCE MAPPING
EU AI Act (2026)Evidence recorded

Transparency obligations and record-keeping for generative AI systems (Articles 50 & 52).

Risk tier assigned per request
Append-only log with per-call token and cost accounting
Transparency notice published and rescanned on a schedule
EARLY ACCESS

Be first
through the gate.

Join the waitlist. When your seat opens, you get early-access pricing, automated key provisioning, and a dedicated onboarding architect. No credit card needed.

VGIL ONBOARDING GATEWAY
STATUS: PRE-LAUNCH

No spam. One email when your seat is ready.