Open-source plugins — running inside your store — we never touch your traffic

A fair line for every drop.
Enforced by your own store.

A virtual waiting room your store enforces itself — open-source adapters, zero per-request callouts, no reverse proxy, no DNS changes. When traffic spikes for a drop or flash sale, shoppers wait in one cryptographically fair line, and your store verifies each signed admission pass locally, with no round trip to us on every page.

acme-store.example Admitting
In queue 12,450
Admitted 8,210
Avg wait 42 s
Admit rate 410 /min
Last 60 minutes Console preview
<30 ms
added to a shopper's page load
Shadow
mode first — the plugin enforces nothing until you switch it on
0%
of your traffic routed through us

How a drop runs

Four steps, and none of them reward a faster script.

From the moment the presale opens to the moment a shopper reaches checkout. Step through it, or let it play.

Phase 1 — Presale window

Scripts are stopped at the gate.

Automated clients are identified and turned away before they can take a position. Only genuine shoppers reach the pool, so the draw is over real people.

Bot check
On every entrant
Speed advantage
None — arrival time is ignored
Incoming traffic
Verified pool
Screening

Automated clients stopped at the line

Phase 2 — The draw

Positions are drawn, not raced for.

Everyone in the pool is assigned a position at once. Refreshing at 11:59:59 buys nothing, and a fast connection buys nothing — the slot you get does not depend on how you arrived.

Chance
Equal for every entrant
Camping advantage
Eliminated
Phase 3 — Queue positions

Each position is a signed, single-use pass.

A position is an artefact your store can verify on its own, not a number the browser is trusted to report. It cannot be forged, replayed, or handed to somebody else.

Integrity
Signed, tamper-evident
Reuse
Single-use, bound to one shopper
Phase 4 — Store entry

Shoppers arrive at a rate you set.

Your store admits at the pace it chose, and checks each pass locally — no call back to us on any request. The queue absorbs the spike; the origin never sees one.

Added latency
Under 30 ms
Checkout queries
Zero
Your store
Pass check
Local, < 1 ms
Database queries
0
Origin status
Serving normally

What you get

Everything you need for one fair drop.

Three parts: the line itself, the code that enforces it inside your stack, and the numbers afterwards.

01

Fair, cryptographically verified queue

In order, or drawn at random

One signed queue per drop. Run it first-come-first-served, or open registration ahead of time and draw every position at random the moment the drop starts.

  • Random draw — registering first and registering last are worth the same
  • Signed, single-use passes — can't be forged, replayed, or handed on
  • A built-in bot check keeps scripts and scalpers out of the line
02

Open-source adapters

Verified in your stack, every time

Your store enforces the queue itself. Install one MIT-licensed adapter and it checks each pass on the spot, with no network call.

  • Cloudflare Worker or WooCommerce plugin — both MIT
  • Fails open — if we're ever unreachable, your store keeps selling
  • No reverse proxy, no DNS change, and your origin never moves

Shopify support is in development. Tell us if you need it →

03

Live dashboard & telemetry

See every drop as it happens

Watch the queue while the drop runs, then read the last 24 hours or 7 days back and export them.

  • Live queue depth, admission rate and time-to-clear during a drop
  • Queued, admitted, checkouts and average wait over 24 h or 7 d — exportable as CSV or JSON
  • One dashboard across every store and domain you run

What shoppers see

The waiting room, exactly as it ships.

This is the real waiting-room page — the same markup, styles and copy a shopper gets — pinned to one state and making no network calls. Your logo, store name, colour and headline replace ours from the console.

State
Theme

Sample figures: 128 shoppers ahead of 400, an estimate of about four minutes, a draw scheduled twelve and a half minutes out. The wait estimate and the presale countdown are per-store switches, off by default; the room follows each shopper’s own light or dark preference.

Under the hood

Runs on your stack. Keeps your traffic yours.

Most queue tools force a choice you shouldn't have to make: route all your traffic through them, or skip real admission control. We don't. Queue admission and pass issuance run in our cloud. A small open-source adapter runs in yours and does the enforcing, checking a signed pass on its own.

Your WooCommerce store or your Cloudflare Worker enforces the queue without sending a single shopper through us — and for a stack neither fits, there is a JavaScript integration library you can read and vendor. Nothing slows down for your customers, and their payment details never touch our systems.

Get started

Runs in our cloud

dropify cloud
  • Queue admission
  • Pass issuance & signing
  • Bot challenge scoring
signed admission pass Crossed once, when a pass is issued — never on a page load.

Runs in your stack

pick one
  • Cloudflare Worker
  • WooCommerce plugin

Each checks the signature itself, in your stack, with no network call.

Local pass check
< 1 ms
Checkout queries
0
Traffic via us
0%

Going live

Nothing is enforced until you say so.

The plugin activates in shadow mode. You watch what it would have done, then flip the switch — and if we are ever unreachable, your store keeps selling on the last policy it pulled.

  1. Install in shadow mode

    The WooCommerce plugin activates enforcing nothing: it logs every request it would have queued and every pass it would have refused, and lets everyone straight through. The edge connector has the same switch.

  2. Watch the log

    Read it through a normal trading day, then through a small drop. If it disagrees with your theme, your cache or your checkout, you find out with nobody affected — and the source is MIT, so you can read that too.

  3. Switch enforcement on

    Set the admission rate — no floor, no cap — and open the queue. The rules you watched are the rules that run. Going live is a switch, not a cutover.

Running both

The edge stops your store being hammered. The plugin stops one admission becoming five orders.

The WooCommerce plugin and the Cloudflare edge connector enforce the same signed policy from different places. Together they are the strongest configuration, and each covers what the other structurally cannot.

The edge sheds the crowd

A queued visitor’s redirect is manufactured at Cloudflare, so your origin never sees them. Plugin-only, every queued shopper’s poll costs a full WordPress bootstrap and the store still has to survive the crowd even though the allocation is fair. At the edge, the crowd never arrives.

The origin owns allocation

Spend on confirmed payment, release on failure, the pending-order window and one checkout per admission exist only in the plugin, because only it sees the cart, the checkout and the payment. A pass spent at the origin still verifies at the edge.

Why dropify.dev

Compared on the specs that decide a drop.

Compare at the plan you would buy
Why dropify.dev dropify.dev CrowdHandler Queue-it Cloudflare
Plan compared Launch Starter Essentials Business
Peak concurrent shoppers 1,000 1,000 5,000 metered per event, not concurrency 1 room
You set the admission rate — no floor, no cap Yes No 60/min cap Partial Not published No 200/min floor, cannot go lower
Presale drops can be drawn at random, not first-come Yes No Yes No
Works without DNS change Yes Yes Yes No
Open-source adapters (MIT) Yes Partial Yes No
Order-level pass enforcement in WooCommerce Yes No No No
Branding, reporting and bot defense included Yes Partial Partial bot management still basic No
Annual contract required No No No No
Price per month €99 €176 free tier available €462 $5,999/yr, unlimited events €185 one basic room
Plan compared Pro Standard Standard 1 Business
Peak concurrent shoppers 2,500 5,000 15,000 visitors/month, not concurrency 1 room
You set the admission rate — no floor, no cap Yes No 150/min cap Partial Not published No 200/min floor, cannot go lower
Presale drops can be drawn at random, not first-come Yes No Yes No
Works without DNS change Yes Yes Yes No
Open-source adapters (MIT) Yes Partial Yes No
Order-level pass enforcement in WooCommerce Yes No No No
Branding, reporting and bot defense included Yes Partial No +118% for theme and reporting No
Annual contract required No No Yes No
Price per month €299 €741 €1,624 £16,368/yr, no theme or reporting €185 one basic room
Plan compared Ultimate Plus Standard 2 Enterprise
Peak concurrent shoppers 10,000 20,000 15,000 visitors/month, not concurrency By quote
You set the admission rate — no floor, no cap Yes No 300/min cap Partial Not published No 200/min floor, cannot go lower
Presale drops can be drawn at random, not first-come Yes No Yes No
Works without DNS change Yes Yes Yes No
Open-source adapters (MIT) Yes Partial Yes No
Order-level pass enforcement in WooCommerce Yes No No No
Branding, reporting and bot defense included Yes Partial Partial bot management still basic Partial
Annual contract required No No Yes Yes
Price per month €999 €1,389 €3,544 £35,724/yr, same volume By quote Advanced Waiting Room add-on
Plan compared Enterprise Enterprise Enterprise Enterprise
Peak concurrent shoppers Unlimited 100,000 10 million visitors/month, not concurrency By quote
You set the admission rate — no floor, no cap Yes No 1,000/min cap Partial Not published No 200/min floor, cannot go lower
Presale drops can be drawn at random, not first-come Yes No Yes No
Works without DNS change Yes Yes Yes No
Open-source adapters (MIT) Yes Partial Yes No
Order-level pass enforcement in WooCommerce Yes No No No
Branding, reporting and bot defense included Yes Yes Partial bot management still basic Partial
Annual contract required No No Yes Yes
Price per month Custom €5,185 €10,527 £106,116/yr, 4 rooms By quote Advanced Waiting Room add-on

Competitor figures are vendor-published list prices, the UK G-Cloud 14 framework rate card, or marketplace listings, converted at $1.08/€ and £0.84/€. Annual prices are shown per month.

Pricing

Flat monthly pricing
built for your scale.

Four tiers tailored to your peak concurrency needs: Launch for your first drop, Pro for growing stores, Ultimate for high-volume drops, and Enterprise for custom infrastructure. All plans are flat-rate with soft caps and fail-open security — no metered usage fees or surprise bills.

Full pricing breakdown
Starter

Launch

€99 /mo

Up to 1,000 concurrent capacity

Contact sales

Onboarded manually for now.

Powerhouse

Ultimate

€999 /mo

Up to 10,000 concurrent capacity

Start Ultimate

For brands scaling hard

Custom

Enterprise

Custom

Unlimited concurrent capacity

Contact sales

Contract billing and a 24/7 SLA

Get started

Three steps to your first fair drop.

No DNS to change, no reverse proxy, and none of your traffic rerouted. The adapter is open source — read it before you install it.

  1. Install the adapter Cloudflare Worker or WooCommerce plugin.
  2. Paste your setup code One string from the console. There is no second thing to configure.
  3. Open the queue Registration, the draw and admission all run from the dashboard.