QueueRoom docs

Website docs for public pages and client launch operations.

Use these pages to understand what QueueRoom shows publicly, what clients see after sign-in, and how a launch moves from Cloudflare connection to post-event review.

Public Site

Homepage and marketing pages explain QueueRoom, Cloudflare-native enforcement, and high-demand launch use cases without exposing internal traffic rules.

Client Dashboard

Client pages guide each tenant through setup, rehearsal, go-live, live monitoring, and post-event review.

Launch Plane Install

Customer Cloudflare Worker runs from local signed config snapshots and reports back asynchronously.

Guide process

Seven checkpoints before, during, and after launch.

01

Connect Cloudflare

Owner: Admin

Zone, Worker, KV, queue, and scoped token ready for launch-plane install.

Confirm customer zone and hostname ownership.
Install or verify the client Worker with required bindings.
Prove health endpoint works before public traffic is routed.
02

Create Launch Profile

Owner: Launch manager

Protected host, path, sale window, timezone, demand estimate, and fallback mode captured.

Set launch name, organizer, and public sale window.
Map protected paths before checkout or registration origin.
Keep draft state until config is reviewed.
03

Set Admission Policy

Owner: Ops

Capacity, admit rate, queue mode, emergency state, and fairness rules ready.

Choose scheduled, queue-all, paused, or reject mode.
Set origin capacity envelope and admit rate.
Confirm stale config protects origin instead of bypassing queue.
04

Design Fan Experience

Owner: Marketing

Waiting page copy, brand treatment, countdown, and fallback states approved.

Preview desktop and mobile waiting-room states.
Keep public copy clear without exposing anti-bot internals.
Add support-safe FAQ and event messaging.
05

Rehearse Launch

Owner: Ops + engineering

Signed config reaches edge, telemetry reports back, and rollback path is known.

Publish to staging or rehearsal route.
Verify Worker health, config freshness, and sampled decisions.
Record operator approval before production publish.
06

Monitor Live Launch

Owner: Launch room

Operators see readiness, next action, telemetry freshness, and audit trail.

Watch live launches and setup issues from client dashboard.
Tune admission only from approved event context.
Use emergency modes when origin risk changes.
07

Review Event

Owner: Business + ops

Post-event report explains traffic, decisions, incidents, and next tuning changes.

Review admitted, queued, rejected, and late telemetry counts.
Export operator actions and decision timeline.
Capture follow-up changes before next launch.

Control plane boundary

Connected, no hard dependency.

QueueRoom publishes signed config snapshots to the customer Worker.
Worker enforces from local KV when QueueRoom control plane is unavailable.
Decision telemetry reports back through async queues and outbox retry.