Stay safe during traffic surges
with AI-powered control
NetFUNNEL absorbs sudden bursts of access before they reach your origin.
Servers accept only what they can handle, while everyone else waits in a fair order.
NetFUNNEL is a virtual waiting room solution that sequentially controls user entry per second to match processing capacity, holding excess users in a virtual waiting room to prevent server overload and service outages.
The moment access surges,
so do your losses
Traffic surges arrive without warning. An unprepared server collapses at the first peak, and that cost lands squarely on the customer experience.
A single moment of downtime
If a flood of access stalls your server a minute after opening, the event you prepared and the revenue vanish on the spot.
Over-provisioning cost
Keep servers permanently scaled up for a handful of peaks, and you pay every month for resources you rarely use.
An unfair race
A structure where whoever hits refresh fastest wins — not whoever arrived first — erodes trust.
The visible part
Scaling cost, temporary downtime and more —
losses billed immediately
The far larger loss
Lost customers, lost trust,
a weakened brand
Build customer trust
with a fair service experience
Admit only as many users as your service resources can handle to guarantee stability,
and let every user access the service on the same terms.
AI-based automatic traffic control model
It automatically adjusts the number of admissions based on server response time, without anyone manually adjusting thresholds.
It anticipates peaks to stop safely just short of the limit, and lets more users in the moment there is headroom.
Second-level control:
faster,
and steadier
Real-time traffic analysis and control respond stably even to abrupt traffic shifts,
delivering optimal performance and availability.
Scalability to handle
more than 5 million
TPS at peak
It delivers stable processing performance even under large-scale traffic,
flexibly absorbing traffic growth as your service scales.
Stable traffic control
targeting
0% service impact
It controls traffic at the very front of the service, yet runs non-intrusively to minimize service impact.
On failure, automatic bypass delivers traffic straight to the origin service.
Automate
repetitive operations
It applies scheduling policies to match each event's start time. With no need for manual monitoring or hands-on handling, presets alone keep operations stable.
- Scheduling
- Presets
Manage traffic flexibly with
pre-, post-, and block waiting rooms
Use different waiting-room types as the situation calls for: ease traffic concentration before an event starts, and when an event ends early or something unexpected happens, use a post-event waiting room to give customers the guidance and communication they need.
- Pre- and post-event waiting rooms
- Block waiting room
A custom waiting room
ready in five minutes
Configure logos, colors, guidance copy, and waiting-room design directly in the no-code builder.
Launch a branded waiting page that matches your service in as little as five minutes — without development or deployment.
Multi-environment support
, wherever you need it
Deploy NetFUNNEL across CDN, web, iOS, Android, or server environments without replacing your existing infrastructure. Simply integrate it at the most appropriate point in the traffic path.
Apply the waiting room only
where and when you need it
Combine URL, path, and domain conditions to apply the waiting room precisely to the pages that need protection. With no code changes, protect checkout, event, and ticket pages with a single rule.
- Path and domain conditions
- AND/OR combinations
- No-code rules
Keep users safe from
abuse and macros
It automatically blocks abnormal, repeated access that exceeds the per-second request limit you set. First in, first admitted — a fair order for everyone.
- Per-second request limit
- Macro blocking
A real-time monitoring dashboard at a glance
Check and manage waiting information — current waiting count, entry speed, average wait time, and real-time estimated drop-offs.
A fair waiting experience
through entry-key invalidation
It offers timer-based entry-key invalidation that prevents abuse such as waiting in advance, keeping the queue fair.
- Invalidation split by prior-entry users and all users
- Timer-based entry-key invalidation
Polling intervals and
timeouts tuned to
your server environment
Set re-request (polling) intervals and entry timeouts to match your server capacity and traffic profile. Use shorter intervals when capacity allows and longer intervals when resources are constrained, balancing server load and entry speed for your environment.
- Re-request interval settings
- Server-environment tuning
Re-entry without waiting
With queue-position retention, once a user enters they skip the waiting room for a set period. Whether they leave mid-payment and come back or lose and restore their connection, they go straight into the service.
- Re-entry within the valid period
- No wait after leaving and returning
Get notified
when it's your turn
No need to keep the window open and refresh.
As your estimated entry time approaches, we send an alert via popup, sound, and email. Notifications go out about 5 minutes before your estimated entry, improving the customer experience.
(The actual timing may vary slightly depending on queue conditions.)
A queue position
that stays with you
Once assigned, your position does not disappear even if you refresh or briefly lose connection.
Open API integration support
for key features
From creating queues and checking positions to issuing entry tokens,
control every action through the OpenAPI.
const q = await pulse.queues.create({
name: "ticket-open",
rate: "3400/min"
});
// 2. 순번 조회
const s = await pulse.queues.status(q.id, token);
// → { position: 1284, eta: 131 }
After the event,
data for what comes next
Beyond real time, gather metric trends by day, week, and month — completion rate, bypass and blocking, and waiting. Decide the next event's admission limits and policies with data.
- Aggregation by period
- Reports by server, project, and segment
- CSV export
The change teams that adopt it
feel first
NetFUNNEL is not merely a tool for controlling traffic — it transforms both marketing performance and an excessive infrastructure cost structure at once.
By controlling entry speed within safe limits, it stops service interruptions from traffic surges at the source.
Because there is no need to over-provision servers for traffic spikes, you can cut everyday operating resources to under half on average.
By preventing downtime while controlling throughput per second as needed, a Japanese F&B company achieved 200% YoY revenue within the same period. (Real case, Company B, Japan F&B)
For a K-pop idol tournament, 3.5 million concurrent waiting users were flow-controlled with no downtime, ending the event with virtually no customer support issues.
* Figures are based on the average improvement seen by commerce, ticketing, and education customers that adopted STCLab NetFUNNEL.
Frequently Asked Questions
Common questions before getting started. Reach out anytime to learn more.
A virtual waiting room is a traffic-control approach that, when concurrent users exceed a system's processing capacity, holds the excess users in an online queue and admits them to the service sequentially—only as many as the system can handle. NetFUNNEL decides whether to admit a user immediately or make them wait based on current traffic and the configured admission rate. Users within capacity access the service without waiting; only those beyond capacity wait their turn in the virtual waiting room. During the wait, information such as queue position and estimated entry time can be shown, and policies such as FIFO or a random pre-queue before an event start can be configured to fit your operations.
써 보는게 가장 빠릅니다.
서비스 환경 변화 없이 원하는 방식에 따라 빠르게 테스트 및 적용 가능합니다
(Server Side 에이전트의 경우 별도 적용 요청 필요)