Aggregate across all servers
Bandwidth Pool
Bandwidth Pool lets multiple BryskBits servers draw from one contracted capacity pool, so idle servers do not trap bandwidth while another node is under demand.
Pool range
50 Gbps - 1 Tbps+
Billing
Single invoice
Servers
Mixed fleet
Review
Written quote
Port limits
Per server
From
€199/mo
Configurator
Select pooled capacity
Up to 20 servers
€699/mo
Pool pricing is estimated from the current public plan table. Final allocation, alerting, and upgrade terms are confirmed in the written quote.
Instead of each server having its own bandwidth limit, you buy a total pool. Every server draws from it.
When one server spikes and another idles, the pool absorbs it. You are not billed per-server overage.
A single monthly line item for your entire fleet, regardless of how many servers or port speeds you run.
Alerting, upgrade path, overage handling, and eligible server rules are confirmed in the written quote. The public page does not assume one universal policy for every fleet.
Use cases
Workload: Several servers serving different channels, regions, or customer groups.
Sizing: Traffic may be uneven: one node spikes while another is quiet.
Fit: A pool prevents unused capacity from being trapped in the wrong place commercially.
Limit: Physical port limits still apply on each server.
Workload: Cache nodes added as audience clusters grow.
Sizing: Traffic shape changes by region, cache-hit rate, and event schedule.
Fit: Pooling gives simpler fleet billing while the architecture changes.
Limit: Network locations and test endpoints should be confirmed before launch planning.
Workload: Live sessions spike across channels and relays during prime time.
Sizing: Bitrate, concurrency, and middleware overhead determine actual capacity.
Fit: Pooling can reduce commercial waste when peaks move between nodes.
Limit: Rights to distribute content remain the customer's responsibility.
Instead of treating every server as an isolated billing unit, the fleet draws from one contracted capacity pool. This helps when one node is busy while another node is quiet.
No. A pool is a commercial and capacity-planning layer across eligible servers. Each server still has its own configured port speed.
The upgrade path, alerting threshold, and any overage handling are confirmed in the written quote. The public site does not assume a universal overage policy.
Related paths
Compare adjacent bandwidth, media, and pooled-capacity routes before choosing a configuration.
