The alternatives

Three ways to handle user input.

Do nothing, ask a frontier model yourself on every message, or put the guard in front. The honest version of the comparison.

No guard
Frontier model, DIY
Super Simple Guardus
Coverage

Whatever gets through

As broad as your prompt

8categories on by default
Accuracy

Catches nothing

You build the eval set

Measuredon hard cases and look-alikes
Latency

+0 ms, nothing checked

+1 frontier round trip

<1stypically ~0.2s
Cost

$0 today, the incident later

100% frontier tokens

<1%of traffic on the last stage
Observability

You find out from screenshots

Yours to build and maintain

Built inper project, nothing to maintain

Accuracy is measured on hard cases and benign look-alikes, including a held-out set of new scenes. Typical latency is about 0.2s; the hard path is designed to stay under 1s.

Put a guard in front of it. Keep building.

Nothing is billed today. Sign in, get a key, and you will hear from us before that changes.