Run high-demand global drops without overselling.
DropLock is a global scarcity engine for million-scale launches — sneaker drops, concert tickets, game-item launches, NFT mints, and creator merch. Any number of buyers can compete worldwide for a limited inventory cap, and Aurora DSQL remains the strongly consistent source of truth that enforces it.
- 0
- Oversold units
- 1
- Global inventory cap
- DSQL
- Source of truth
How it works
Set the global cap
Configure inventory for a worldwide scarcity event. Aurora DSQL enforces one cap across every region.
Open the drop
Millions of buyers hit stateless Vercel API routes. Inventory shards absorb concurrent reservation pressure.
Prove integrity
The audit dashboard proves successful purchases never exceed configured inventory — even after a burst.
Built for million-scale demand
Every guarantee below is enforced in the database — not in app memory — so the global cap holds under worldwide flash-sale load.
Zero overselling
Successful purchases never exceed configured inventory. The invariant is audited and provable after every burst.
Global inventory cap
Any number of buyers compete worldwide for one limited cap. Aurora DSQL stays the strongly consistent source of truth.
Distributed transactions
Reservations commit through Aurora DSQL transactions — no in-memory counters, no regional drift, no double-spend.
Conflict retries resolved
Concurrent writes that collide are retried and reconciled automatically without ever breaking the cap.
Inventory shard architecture
The global cap is split across shard rows so million-scale demand spreads instead of fighting one hot row.
Stateless edge scale
Vercel API routes hold no inventory state and scale horizontally while DSQL enforces the worldwide limit.
Stateless edge, strongly consistent core
Stateless Vercel API routes accept reservation requests at scale. Aurora DSQL shards the global cap and commits orders with distributed transactional integrity — no single hot inventory row.
Inventory shards
Concurrent writes spread across shard rows instead of one hot counter.
Conflict retries resolved
Colliding writes retry and reconcile without breaking the cap.
Provable cap
The audit trail proves sold ≤ configured inventory after every burst.
See it under flash-sale pressure
Run the pre-seeded demo drop or configure your own scarcity event in seconds.