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.

01

Public Site

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

Client Dashboard

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

Launch Plane Install

Install the Worker with signed configuration, KV, telemetry, report storage, and the required room admission authority.
04

Security & Compliance

Review implemented security controls, evidence boundaries, and open gaps relevant to ISO/IEC 27001 and PCI DSS scope planning.

Guide process

Seven checkpoints before, during, and after launch.

Owner: Admin
01

Connect Cloudflare

Zone, Worker, KV, telemetry queue, report storage, room authority, and scoped token prepared for launch-plane install.

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

Create Launch Profile

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

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

Set Admission Policy

Admission rate, queue mode, emergency state, and queue order prepared for rehearsal.

Checklist
Choose scheduled, queue-all, paused, or reject mode.
Set the new-users-per-minute rate. The local Worker build enforces this pace, FIFO after opening, and deterministic seeded order before opening.
Do not treat active-user/session limits or trusted bot-risk weighting as enforced yet.
Confirm stale config protects origin instead of bypassing queue.
Owner: Marketing
04

Design Fan Experience

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

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

Rehearse Launch

Signed config and room policy reach the edge, telemetry reports back, and rollback path is known.

Checklist
Publish to staging or rehearsal route.
Verify Worker health, config freshness, and sampled decisions.
Record staging migration, load, rollback, and operator approval before production publish.
Owner: Launch room
06

Monitor Live Launch

After production approval, operators see readiness, next action, telemetry freshness, and audit trail.

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

Review Event

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

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

Control plane boundary

Fan admission stays at the customer edge.

The Worker verifies signed configuration locally and can use the last valid KV snapshot when the control plane is offline.
Queued visitors register and claim admission through a dedicated room authority; the control plane is not called for each fan request.
Local tests cover new-users-per-minute pacing, FIFO after opening, and deterministic seeded prequeue order. The new authority is not yet proven in the public deployment.
Active-user/session limits and trusted bot-risk weighting are not yet enforced, so production launch remains blocked.
Decision telemetry leaves the admission transaction through asynchronous reporting.