dropify.dev as a Queue-it alternative

The +118% is the whole argument

Queue-it does not publish a price list you can act on. The UK G-Cloud 14 framework makes them publish one anyway, and it is the most useful document in this category.

Standard 1 is £16,368 a year. That buys 15,000 queued visitors a month, one waiting room, and basic bot management. It does not buy a custom theme, reporting, email notifications or API access.

Standard 2 is £35,724 a year. Same traffic volume. The difference is those features.

That is +118% for the things most buyers assume are part of a waiting room — and it is their own number, on a government framework, not our characterisation of it. Every extra waiting room is roughly £6,720 a year on top.

Our position is not that we are cheaper, although at these tiers we are. It is that gating branding and reporting behind a doubling of the invoice is a pricing structure, not a product decision, and it is the specific thing we are built against. Cryptographic fairness, bot defence, the branding studio and order-level pass enforcement are included at €99.

They publish no admission rate

The specification that decides whether a queue can run a drop — how many people per minute it lets through — does not appear in Queue-it’s public documentation or in the G-Cloud rate card.

We are not going to guess at it. Filling that cell with an inferred number is exactly how our own comparison table went wrong once before. What we can say is that it is not a number you can compare before you buy, and that ours is on the pricing page as a column: you set it, no floor, no cap, same on every plan.

Where Queue-it beats us, plainly

Shopper-facing wait times. Queue-it gives shoppers a real-time estimate of how long they will be waiting, and it is the most-praised thing they do. We show position by default; a merchant can switch on an estimated wait at the current pace — a point figure, hidden while the line is paused — and a countdown to a scheduled presale draw. Theirs is the richer figure. If you have ever watched a support inbox during a drop, you know how much that one number is worth.

A real SLA. Queue-it sells a bespoke Enterprise SLA with monthly fee refunds as a remedy. We have no automated billing, let alone contractual remedies. If procurement needs a signed uptime commitment today, that is a real reason to buy Queue-it and not us.

Scale. They serve organisations far larger than our ICP, across ticketing, retail and public sector, and their published rate card goes up to ten million redirected visitors a month.

Shopify. They have a Shopify product. Ours is in development.

Open source. A thing we got wrong once and will not repeat: Queue-it is not a closed shop. Their GitHub organisation carries thirteen repositories, mostly MIT. An earlier version of our homepage said otherwise, and it was disprovable in ten seconds.

The random draw is not ours alone. Queue-it ships randomisation at event start. What differs is that ours is standard rather than an enterprise event feature, and that we publish the mechanism.

Who should actually buy which

Buy Queue-it if you are an enterprise with a sustained-load problem, a procurement process that needs a signed SLA, a Shopify storefront, or shoppers who need to be told how long they are waiting.

Buy this if you run scarce-inventory drops on WooCommerce, need to control the pace of admission rather than accept a vendor’s, want the queue enforced inside your own stack so their outage cannot be your outage, and are not willing to pay double for a custom theme.