FAQ

Answers to common launch protection questions.

Everything you need to know about setting up, running, and scaling QueueRoom waiting room protection.

Setup and Deployment

How long does it take to set up QueueRoom?
Most teams complete setup in under 10 minutes. You need a Cloudflare account with Workers enabled. Deploy the Worker via Wrangler CLI, configure your protected routes, and publish your first waiting room.
Do I need to change my DNS?
No. QueueRoom Worker runs inside your existing Cloudflare zone. If your domain is already behind Cloudflare, no DNS changes are required. The Worker intercepts requests before they reach your origin.
What Cloudflare plan do I need?
QueueRoom works with any Cloudflare plan that supports Workers (Free plan included). For production launches with high traffic, we recommend the Workers Paid plan for increased CPU and request limits.
Can I use QueueRoom without Cloudflare?
QueueRoom enforcement relies on Cloudflare Workers. If you are not on Cloudflare, you can migrate your domain to Cloudflare (free) or contact us about alternative CDN integrations.

Waiting Room Operation

How does admission pacing work?
You set a maximum admission rate (visitors per second). QueueRoom Worker releases visitors to your origin at that rate. Visitors beyond the rate enter the waiting room queue. You can adjust the rate in real-time from the control plane.
What queuing methods are available?
First-come-first-served (FIFO) for standard queues, randomized admission at drop time for fairness, and priority lanes for VIPs, staff, and accessibility requirements.
What happens when a visitor leaves the page?
Queue position is preserved for 5 minutes via a session cookie. If the visitor returns within that window, they resume their position. After expiry, they re-enter at the back of the queue.
Can I customize the waiting room appearance?
Yes. Use the white-label builder to customize colors, logo, fonts, messaging, and countdown UI. Multi-template support lets you create different designs per product line or campaign.

Security and Bots

How does QueueRoom handle bots?
QueueRoom uses layered defense: Cloudflare Turnstile for initial verification, proof-of-work challenges that scale difficulty with queue depth, and behavioral fingerprinting at the edge.
Does QueueRoom see my visitor data?
No. Visitor data (queue positions, admission records, wait times) is stored in Cloudflare KV within your account. QueueRoom control plane never receives or processes your visitor data.
Can the waiting room be bypassed?
Admission tokens are cryptographically signed and verified by the enforcement Worker. Tokens cannot be forged. Session cookies are bound to verified Turnstile challenges.

Pricing and Plans

How does pricing work?
QueueRoom charges by room capacity per month. No per-visitor fees. Starter plan is free forever. Pro plan is $99/month. Enterprise is custom-priced. See the pricing page for full details.
Is there a free trial?
Yes. Pro plan includes a 30-day free trial with full features. Starter plan is always free — one room, up to 1,000 concurrent visitors.
Can I upgrade mid-launch?
Yes. Plan upgrades take effect immediately. Your waiting rooms and queue positions are preserved during the switch.

Enterprise

Do you offer SLAs?
Enterprise plans include a 99.99% uptime SLA for the control plane. Enforcement SLAs depend on your Cloudflare Worker plan (99.99% with Workers Paid).
Is multi-tenancy supported?
Yes. Enterprise plans support multiple Cloudflare accounts and namespaces under a single QueueRoom organization. Full RBAC with owner, admin, and operator roles.
Do you support on-premises deployments?
QueueRoom enforcement runs at the Cloudflare edge. The control plane can be deployed to a dedicated Cloudflare namespace for enterprise customers with strict data residency requirements.

Have a question not covered here?

Contact us for launch planning, architecture reviews, or enterprise inquiries.