Problems / AI security and governance, medium
A strict prompt-injection filter flags 4% of real users as attackers.
Free to open. Runs in your browser, no sign-up.
Success ≥ 99%.
30 requests a second for 30 seconds: 100% request (reads).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Prompt-injection filterPrompt-injection filter | Traffic enters here.Calls Load balancer.Prompt injection hides instructions in input or retrieved content; no filter catches all of them. | 100000 slots |
| Load balancerLoad balancer | Prompt-injection filter 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 service | Load 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 endpoint | AI app calls it.Latency has two parts: time to the first token, then a steady stream of tokens per second. | 400 streams |
Try it first. Open one hint at a time if you get stuck.
Nothing is overloaded; users are being blocked.
Check the filter’s false positives.
Tune the filter to cut false positives.