probing

Published limits.

The bench is free, so its capacity is published exactly. Every number below is the number the gate enforces — nothing hidden, nothing arbitrary.

Your meter
windowlimitscope
burst3enhancements / 10 minutes / client
hourly6enhancements / hour / client
daily20enhancements / day / client
concurrent1live job at a time / client
file size15 MBJPEG · PNG · WebP
dimensions64–12000 pxper side, input
global budget750enhancements / day / everyone
retention7 daysimages & results, automatic
records30 daysjob measurements
price0no account, no card

How they are enforced

Anonymous clients are keyed by a salted, rotating hash of their network address — Schott never stores the address itself, and the key rotates daily. Every window is consumed atomically at job creation, so the count you see is the count the server holds.

When a limit is hit, the bench answers 429 with a machine-readable Retry-After — and the panel shows a countdown to the next window. One enhancement runs at a time per client.

Why limits at all

Enhancement consumes GPU time. The published windows keep the service free and fast for everyone, and the daily global budget protects it from automated bulk use. If the budget is exhausted for the day, the bench says so and reopens at the next window.

Retention

Images and results are automatically deleted after 7 days. Job records — measurements only, no image content — are removed after 30 days. See privacy for the full account.