Your traffic surges. Your site stays up. Every user gets a fair shot — cryptographically proven.
The problem
Product drops, ticket sales, reservation openings — when everyone shows up at once, your origin collapses. Users see errors. Revenue evaporates. Bots win.
The solution
Ought intercepts traffic at Cloudflare's 300+ edge locations before it reaches your server. Users wait in a branded queue. Admission is automatic, rate-limited, and provably random.
How it works
When demand exceeds capacity, Ought intercepts requests at the edge — before they reach your server.
Each visitor sees your branded waiting page with their position and estimated wait time.
Lottery, first-come-first-served, or a hybrid. Trickle release or flood gate. You decide.
Why ought
Cryptographic Fisher-Yates shuffle with rejection sampling. Every queue position is equally likely. Not gameable — not even by us.
Custom colors, logo, fonts, and injectable HTML content slots. Your users see your brand throughout the wait.
Runs on Cloudflare's global network. The waiting room loads in under 50ms worldwide. Zero cold starts.
Each customer gets their own worker process and database. One tenant's surge never affects another.
Deploy a lightweight Worker on your existing Cloudflare zone. Your WAF, load balancer, and rules stay intact.
Built-in circuit breaker with 5 degradation levels. If something breaks, users get through — not stuck.
We're onboarding early customers now. Get priority access, direct support, and help shape the product.