Problems / AI security and governance, easy

Spend governor set too low

A spend governor caps model calls at 1,200 a minute to protect the budget, but legitimate traffic is 30 a second.

Free to open. Runs in your browser, no sign-up.

Your goals

Success ≥ 99%, time to first token p99 ≤ 2.5 s.

The traffic

30 requests a second for 30 seconds: 100% request (reads).

The system

What each component does in this design, and what calls it. The simulator mimics each one from these settings.

ComponentIts job hereSettings
Spend governorSpend governorTraffic enters here.Calls Load balancer.A spend governor enforces budgets per user, task or team before calls go out.100000 slots · 1,200 calls/min
Load balancerLoad balancerSpend governor forwards to it.Calls AI app.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header.–
AI appApp serviceLoad balancer forwards to it.Calls Model.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s.3 replicas × 500 slots · timeout 30 s
ModelLLM endpointAI app calls it.Latency has two parts: time to the first token, then a steady stream of tokens per second.400 streams

Hints

Try it first. Open one hint at a time if you get stuck.

Hint 1

Budgets protect against runaway agents, not normal traffic.

Hint 2

30 × 60 = 1,800 a minute.

One way to solve it

Raise the spend governor’s limit above real demand.

More ai security and governance problems