QoE Control for Broadband Networks

Keep your network responsive when it gets busy.

LibreQoS controls congestion at the subscriber, AP, PON, tower, and backhaul — keeping latency low under load while showing operators exactly where customer experience is degrading.

networks worldwide on LibreQoS
950+
networks worldwide on LibreQoS
WISPA Product of the Year
2025
WISPA Product of the Year
supported shaping tiers
100G+
supported shaping tiers
LibreQoS executive heatmap view

Topology-Aware Shaping

Your network doesn't have one bottleneck.

LibreQoS models the network you actually built. Subscribers get per-flow CAKE fairness while shared capacity at APs, PONs, towers, sites, and backhaul stays under explicit hierarchical control. When one branch is constrained, congestion is contained there instead of degrading everyone upstream.

Topology-Aware Control

Follow load through the runtime tree

See load on every parent and child node, so the congested segment stands out before you open a chart.

RootWest TowerMetro SiteHarbor OLTAP ClusterBackhaulSubscriber Splitwidth = relative loadred node = pressure path

Metro Site

88% load

Shared pressure shows up here before subscriber pain spreads outward.

Backhaul

Pressure path

The congested branch stays visible instead of vanishing into a network-wide average.

West / Harbor

Healthy

The congested branch stands apart from stable parents and clients.

LibreQoS geographic flow view

Traffic Geography

See traffic geography in context

Map flows and upstream patterns visually when you need to understand where subscriber traffic is actually going.

Operational Signals

Keep signal history compact and visible

See latency, retransmits, and quality together so changes are obvious before you open a larger chart.

RTT

Latency drift

Retransmits

Error density

QoO

Quality strip

goodwatchbad

Why Operators Switch

Why operators switch to LibreQoS

Customer-focused operators need precise shaping, real choke-point control, and faster evidence when subscribers feel the network.

How It Works

How LibreQoS shapes traffic

LibreQoS uses CAKE to keep busy networks responsive. Instead of letting downloads and streaming bursts crowd out everything else, it helps gaming, voice, and other interactive traffic stay usable under load.

Basic queueing

Without traffic-aware shaping

A basic queue sends packets in the order they arrive. When download bursts fill the line, interactive traffic has to wait, and the network starts to feel sluggish.

Queue dynamics

ThroughputEnqueuedRTT
Game
Video calls
Streaming
Downloads

What subscribers feel

Downloads take over the line during heavy bursts
Calls, gaming, and other interactive traffic feel slower

LibreQoS with CAKE

Traffic stays fairer under load

LibreQoS uses CAKE to keep interactive traffic moving even when the network is busy, so calls, gaming, and web use stay more responsive.

Queue dynamics

ThroughputEnqueuedRTT
Game
Video calls
Streaming
Downloads

What subscribers feel

Interactive traffic keeps moving during the same load
Latency stays steadier while bulk traffic continues

Live Product View

Live end-user visibility, not just summaries

LibreQoS lets operators watch throughput, queue build-up, and RTT change live on an individual circuit, not just in after-the-fact charts.

Circuit queue dynamics in motion

See the shaping outcome on a live circuit instead of inferring it from aggregate KPIs.

Solutions

Built for the networks ISPs actually run

LibreQoS is purpose-built for wireless and fiber operators — shaping at real AP, site, OLT, and backhaul choke points with subscriber-level evidence. The same hierarchy runs dense shared-capacity environments, from event venues to vessels.

Also used in managed WiFi:Event and venue WiFi·Hospitality·Aviation·Maritime

Operator Proof

Operators run LibreQoS in production

From single-tower WISPs to multi-site networks, operators use LibreQoS to hold the line on busy-hour quality and prove the result.

"We can afford to deploy a box at every step of the network to manage congestion at very little cost."

Louis Elliott

CEO, Streamline Internet

"LibreQoS let subscribers share higher plan speeds fairly and made the service feel much faster during prime time."

Daniel Denson

Denson Technologies

Measure It Yourself

Don't take our word for it. Measure the result.

The public Internet Quality Test measures what subscribers feel on a loaded circuit — idle and loaded latency, jitter, packet loss, throughput, and per-application QoO — and grades the connection from A+ to F. Run it on a busy-hour circuit, deploy LibreQoS, then run it again.

Before

Unshaped circuit

DQoO
Idle latency
18 ms
Loaded latency, download
+91 ms
Loaded latency, upload
+142 ms

Poor

After

Same circuit, shaped by LibreQoS

A+QoO
Idle latency
18 ms
Loaded latency, download
+6 ms
Loaded latency, upload
+9 ms

Excellent

Idle latencyLoaded latencyJitterPacket lossThroughputPer-application QoO

Illustrative before/after readings for a bufferbloat-limited circuit. Run the test on your own network for the numbers that matter.

Integrations

Integrations and deployment guidance for real-world rollout

See how LibreQoS fits into your stack and how to roll it out cleanly.

Pricing

Start free. Upgrade when you need more.

The shaping core is open source and self-serve. Paid plans add support, API, and Insight — with volume brackets that drop the rate as you grow.

Shaping Core

$0open source

The full GPL2 shaping engine on your own hardware. 1-line install, WebUI, complete topology-aware shaping.

Support & API

$0.15per subscriber / mo

Production support and API access, priced per subscriber with regional rates available.

Insight

$0.30per subscriber / mo

Multi-shaper analytics, ASN-level analysis, and history from 15 minutes to a year. Volume brackets reduce the rate as you grow.

US list rates shown. Volume brackets reduce the per-subscriber rate as you grow; regional pricing available.

Deploy

Deploy LibreQoS on your own hardware

Run 1 CLI line, open the WebUI, complete setup, and validate against a known-good pilot before production cutover.