What a waiting room costs, and how fast it lets people in

Most waiting room vendors don’t publish a price. You can read the pricing page of Queue-it, CrowdHandler and Queue-Fair; for Akamai, Imperva, Radware and Fastly you get a contact form. So we collected the ones that exist — public rate cards on the UK government’s G-Cloud framework, the AWS Marketplace, and published pricing pages — and put them on one axis.

Here is what came back, and then the single metric that actually decides whether a queue can run a drop.

The prices, on one axis

Normalised to annual cost. Monthly list prices are multiplied by twelve; where a marketplace contract exists at a different figure it is noted. Converted at $1.08 and £0.84 to the euro.

Vendor and tier	Per year	As published
Queue-it Enterprise	€126,300	£106,116/yr — 10M visitors/mo, 4 rooms
Queue-it Pro 2	€106,600	£89,580/yr — 100k visitors/mo, extended
CrowdHandler Enterprise	€62,200	$5,600/mo — 100k concurrent
Queue-it Pro 1	€58,000	£48,708/yr — 100k visitors/mo
Queue-it Standard 2	€42,500	£35,724/yr — 15k visitors/mo, extended
CrowdHandler Professional	€35,600	$3,200/mo — 50k concurrent
Queue-it Standard 1	€19,500	£16,368/yr — 15k visitors/mo
CrowdHandler Plus	€16,700	$1,500/mo — 20k concurrent
dropify.dev Ultimate	€12,000	€999/mo — 10,000 concurrent
CrowdHandler Standard	€8,900	$800/mo — 5,000 concurrent
Queue-it Essentials	€5,550	$5,999/yr — unlimited events
dropify.dev Pro	€3,600	€299/mo — 2,500 concurrent
Cloudflare Business	€2,220	$200/mo — one basic room
CrowdHandler Starter	€2,110	$190/mo — 1,000 concurrent
dropify.dev Launch	€1,190	€99/mo — 1,000 concurrent
Queue-Fair Free Tier	€0	outflow capped at 10/min

Two market patterns stand out immediately:

There is a market below €9,000 a year, and a quote-gated one above €19,000, with almost nothing in between. If you run a store rather than a stadium, you are shopping in the bottom third of that table whether you meant to or not.

Queue-it’s Standard 1 and Standard 2 lines carry identical traffic allowances. £16,368 against £35,724 — a 118% price increase — buys custom branding, traffic reporting, email notifications and API access. Capacity does not change. That is not an accidental bundle; on their published rate card it is the business model.

The number that decides whether a queue can run a drop

Capacity is the axis everyone meters, so it is the axis everyone compares. For a drop, capacity is secondary.

If you have 500 units and 20,000 people, what matters is how fast people are let through the door. Admit everyone in two minutes and you have recreated the stampede inside your checkout. Admit them slowly and steadily and your payment provider, your stock system and your support inbox all survive the afternoon.

That number is the admission rate (or outflow), and it is published far less often than price:

	Admission rate
CrowdHandler Starter, $190/mo	60 per minute, capped
CrowdHandler Standard, $800/mo	150 per minute, capped
CrowdHandler Enterprise, $5,600/mo	1,000 per minute, capped
Cloudflare, any plan	minimum 200 per minute
Queue-Fair Free Tier	10 per minute
Queue-it	not published
dropify.dev, every plan	you set it — no floor, no cap

Read the Cloudflare row twice. Their configuration reference states that new_users_per_minute cannot be set lower than 200. It is a floor, not a cap. You cannot configure a Cloudflare waiting room to admit fewer than roughly 200 people a minute.

For a 500-unit drop, that means the entire allocation is gone in two and a half minutes, and no setting in the product can slow it down. Cloudflare Waiting Room is built to keep a large site standing under sustained load. It is not built to pace scarce inventory.

CrowdHandler has the opposite issue at lower tiers: sixty admissions a minute is a hard ceiling, so a 2,000-unit drop takes thirty-three minutes to admit — a queue you cannot speed up even if your server is coping fine.

On Dropify, admission speed is controlled by one dial, and it is the same dial on the €99 plan as on Enterprise. Set it to a trickle, set it wide open, or adjust it live while the drop is running based on how your checkout is holding up.

Where CrowdHandler is cheaper, and why we differ

At raw concurrent seat pricing, CrowdHandler’s Standard plan carries 5,000 concurrent for $800/mo where our €299 Pro carries 2,500. If you are buying waiting-room seats by the thousands for sustained traffic, they will often win on raw capacity per dollar, and they have a free tier.

However, two critical differences set our plans apart:

1. Admission rate control: CrowdHandler caps outflow per tier; ours has no floor and no cap on any plan.
2. Features included vs. gated: Queue-it charges +118% for branding and reporting at identical traffic volume. CrowdHandler gates IP threat databases, ML anomaly detection, and automated refunds behind their $5,600/mo Enterprise plan. Queue-it’s own rate card lists bot defense as “basic” on every tier including the £106,116/yr plan.

Our bot defense (human verification, proof-of-work challenges, and datacenter IP escalation), branding studio, and order-level enforcement are standard on every plan starting at €99.

The part of a drop that happens after the queue

A queue decides who gets in. It does not decide what they do once inside — and for scarce inventory, that is where inventory leaks. Someone who clears the queue and buys eight units defeated the queue without bypassing it. So did someone who reuses one admission across five browser tabs.

The published state of post-queue enforcement:

• CrowdHandler offers a cart validator and checkout busting for Shopify. Their WordPress path is a browse-level gate.
• Queue-it provides a post-exit validation API — a building block you must integrate into your own backend.
• Cloudflare holds people in line and lets them through; post-queue enforcement does not exist.

Our WooCommerce plugin binds an admission to an order: one admission means one order. The pass is reserved when an order is created and spent when payment actually confirms — ensuring 3-D Secure and iDEAL payment redirects work seamlessly, while blocking duplicate checkouts on the same pass. As far as we can establish, nobody else ships this as a ready-made WooCommerce feature.

Architectural resilience: Origin load shedding

A waiting room that runs entirely inside your shop costs your server resources for every polling request. At twenty thousand waiting shoppers, your origin can crash even if stock allocation is fair.

Our edge connector runs as a Cloudflare Worker in front of your store. Queued visitors get their responses generated directly at Cloudflare’s edge — your origin never sees their requests. Paired with our WooCommerce plugin, the edge sheds crowd load so your server stays fast, while the plugin handles order-level enforcement at checkout.

Bottom line

If you sell scarce inventory on WooCommerce, controlling admission speed with no artificial floor and enforcing limits all the way to payment confirmation are what decide whether a drop succeeds. Both capabilities are standard on every Dropify plan.