The verdict in three sentences
When 80,000 visitors arrive in 5 minutes, no standard ticketing site survives without a virtual waiting room: it admits buyers at the pace your payments and inventory can absorb. SaaS at USD 0.01-0.05 per visitor suits occasional peaks, while a custom build at USD 30,000-60,000 pays off beyond a few million queued visitors a year. Either way, budget about USD 6,000 for load testing and 2 to 3 months of project time.
Why the site crashes at every on-sale
The bottleneck is almost never the web server. It is the inventory database (locks on seats), the payment provider (requests per second limits) and scalper bots multiplying sessions. An independent ticketing platform in New York, selling venues of 1,000 to 6,000 seats, hits exactly this scenario each time a hot tour is announced.
| Component | Typical capacity of an independent platform | Peak need (80,000 visitors in 5 min) |
|---|---|---|
| Page views per second | 300 to 500 | 3,000 to 5,000 |
| Payment transactions per minute | 150 to 300 | Demand above 2,000 |
| Concurrent seat holds | 200 to 400 | Several thousand |
| Share of traffic from bots | 10 to 20% day to day | 30 to 60% on a hot on-sale |
| Cost of one hour of downtime | Low outside on-sales | USD 25,000 to 90,000 of delayed or lost sales |
SaaS or custom: costed comparison
| Criterion | SaaS waiting room | Custom waiting room |
|---|---|---|
| Upfront cost | USD 0 to 3,500 integration | USD 30,000 to 60,000 |
| Variable cost | USD 0.01 to 0.05 per queued visitor | Cloud infrastructure, about USD 0.001 per visitor |
| 2 million visitors a year | USD 20,000 to 100,000 | USD 2,000 to 4,000 plus USD 6,000 maintenance |
| Queue customisation | Theme and messages | Member priority, presales, codes, content |
| Anti-bot | Included, depending on plan | Anti-bot service integration, USD 350 to 1,700 a month |
| Time to deploy | 2 to 4 weeks | 2 to 3 months |
| Vendor lock-in | High | Code and data in-house |
Rule of thumb: below 500,000 queued visitors a year, SaaS wins. Above 2 million, custom pays back in one to two years, with a queue that also handles your presales, priority members and promoter codes.
Recommended architecture
The queue sits at the edge, on a CDN, before requests even reach your application. Each visitor receives a signed token with their position, and a regulator admits a fixed rate (for example 400 buyers a minute) calibrated on actual payment capacity. Behind it, the sales application uses auto-scaling, seats are held with short locks (10 minutes) and released if payment fails.
Load testing, around USD 6,000, simulates 100,000 visitors to measure maximum error-free throughput. It sets the queue rate: admitting more people than payments can handle just recreates the outage further down the funnel. On anti-bot, combine invisible challenges, per-device and per-card limits, and account consistency checks.
Mini case study
Michael, CTO of an independent ticketing platform in New York, runs 25 major on-sales a year with 80,000 visitors each, so 2 million queued visitors. On SaaS at USD 0.03, the bill reaches USD 60,000 a year. The custom build costs USD 45,000, plus USD 6,000 of load testing, USD 3,000 of infrastructure, USD 7,000 of anti-bot and USD 6,000 of maintenance, so USD 16,000 a year. Annual saving: USD 44,000. The project pays back in just over a year, and the platform above all recovers sales lost during outages, estimated at USD 45,000 on the last tour.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
How much does a virtual waiting room for ticketing cost in 2026?
On SaaS, USD 0.01 to 0.05 per queued visitor. Custom, USD 30,000 to 60,000 plus about USD 6,000 of load testing, as a 2026 estimate.
Is the queue fair?
Yes if it randomises positions for visitors present before the on-sale, then serves arrivals in order. This removes the advantage of refreshing the page 50 times a second.
How do we block scalper bots?
By combining invisible challenges, per-device and per-card limits, and per-account quotas (for example 4 tickets). On a hot on-sale, this filtering often removes 30% of sessions or more.
Do we have to rebuild the whole ticketing platform?
No, the waiting room sits in front of the existing site. You do need to check seat holds and payment resilience, hence load testing.
What timeline should we plan?
2 to 4 weeks for SaaS, 2 to 3 months for custom with load testing. Go live at least a month before your next major on-sale.
Let's scope your project. Share your visitor volumes, current ticketing stack and on-sale calendar for an architecture review, an indicative budget and a 2 to 3 month plan. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
