Skip to content

MIT licensed · open source

This software is free.

TideGuard costs $0. You do not pay us. The number below is Cloudflare infrastructure for one queue runthrough on Workers and Durable Objects, billed on your Cloudflare account like any other Worker.

Crowd and capacity

How many people join the waiting room, and how many can your origin take per minute today? Wait time is derived from that — not something you guess.

18,000

Unique visitors who join the queue during the surge. A stadium analogy helps size it; a ticket drop can be far larger than the seats. Matches the default waiting-row cap of 1,000,000 per queue (raisable in System → Danger zone if you need more).

150 / min

How many users your origin can handle per minute today — checkout, login, or API capacity once TideGuard lets people through. Raise it and waits shrink; lower it and the line lasts longer.

Average wait ~1 hr — last person ~2 hr if this crowd is already in line

Polling mode

By default, TideGuard tells each waiting browser when to check back, so one queue stays near a fixed budget of about 750 status checks per second. Those scheduled check-ins also prove someone is still waiting. Fixed intervals are available for custom clients but are not recommended — they usually cost more.

Polling mode

Estimate uses scheduled check-ins sized for the crowd — no separate keep-alive pings.

Do longer queues cost more?

Cloudflare infrastructure estimate

Estimated Cloudflare cost

$7.50

per queue runthrough

Workers Paid $5/month floor plus list-rate usage for one clear (not a TideGuard fee). Based on our model — setups differ, and prices can change.

TideGuard license: $0

Infrastructure

How much Cloudflare capacity this surge uses.

Cost

$5/month Workers Paid floor plus list-rate usage for one queue runthrough.

Ballpark for one queue runthrough at list rates (Workers Paid$5/month floor included). Assumes this crowd is already in line — new joins are not modeled. Status stays near ~750/s while the room is open; slower admits cost more. Allotments not subtracted. Cap defaults to 1,000,000 waiting visitors. Excludes origin servers and SQLite overages. Estimates can differ from your invoice.