Keep every app responsive at busy hour.
LibreQoS manages congestion from the backhaul down to each household, so games, video calls, and streams stay smooth while downloads keep moving. Then it shows you why, down to the subscriber and the network they're reaching.
- 950+
- networks in production
- WISPA 2026
- Triumph Award
- WISPA 2025
- Product of the Year
- Free
- up to 1,000 circuits


Every app stays responsive
CAKE on every subscriber circuit, for TCP and UDP alike.
Jump to section ↓02Control the whole network
Nested limits at every AP, site, OLT, and backhaul.
Jump to section ↓03See why, down to the destination
Per-ASN latency and retransmits, network-wide and per subscriber.
Jump to section ↓Back-to-back WISPA awards
WISPA members named LibreQoS the 2025 Product of the Year, and LibreQoS received the 2026 Triumph Award.


Games, calls, and streams stay smooth, even when the house is downloading.
What subscribers notice at busy hour is rarely speed. It is lag. LibreQoS runs CAKE on every subscriber circuit: each flow and each device gets a fair share, latency-sensitive traffic is prioritized, and queues stay short. It works the same for TCP, UDP, and QUIC, so the game, the Teams call, and the 4K stream are all covered.
- Per-flow and per-device fairness inside each household
- Priority classes that keep voice and video ahead of bulk transfers
- No TCP proxy: subscriber connections stay end to end
A TCP proxy can act only on TCP connections. CAKE manages queueing for every flow in the circuit.
Get more out of every backhaul before you buy the next one.
Congestion does not only happen at the subscriber's plan. LibreQoS mirrors your real topology, with limits nested at every AP, site, OLT, PON, and backhaul. A busy link is shared fairly instead of building queues that every subscriber behind it feels, so upgrades happen when the data says so, not when the complaints do.
Every level is a real shaping limit, not just a monitoring view.

“We can afford to deploy a box at every step of the network to manage congestion at very little cost.”
Is it the network, the home, or the game server? Know in one view.
LibreQoS measures RTT and TCP retransmits from real subscriber traffic and breaks them down by destination network (ASN), network-wide and for every subscriber circuit. Support can see that one customer's lag comes from one gaming provider, not your AP. Network teams can see which transit and peering paths are underperforming.
- Network
- Site
- Access point
- Subscriber
- Destination ASN


Open, owned, and affordable.
Evaluate it on your own network before you talk to anyone. Keep control of it after you deploy.
Open and inspectable
The control plane, WebUI, and Node API are GPLv2 open source, and queueing uses CAKE with COBALT, a published, peer-reviewed algorithm. Every limit and queue is visible in the WebUI. Nothing is a black box.
Why LibreQoSRuns on your hardware
Install on your own x86 server, or a VM with virtio NICs, from the LibreQoS package repository. Subscriber and traffic data stay on your network.
Deployment guideFree to start, priced to scale
Free up to 1,000 circuits. Published per-subscriber rates beyond that, and bandwidth is not metered.
See pricingA real API and integrations
A full Node API with Swagger documentation, plus built-in integrations with the billing and OSS systems ISPs already run.
IntegrationsBuilt 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.
Wireless ISP
Reduce peak-hour complaints and keep shaping aligned to real AP, site, and backhaul bottlenecks.
Backhaul-aware shapingFiber ISP
Give support teams stronger evidence about congestion, upstream trouble, and subscriber-side issues.
Subscriber evidence fasterManaged WiFi
Keep shared guest uplinks fair at peak concurrency across events, hotels, vessels, and aircraft.
Shared guest capacity“LibreQoS let subscribers share higher plan speeds fairly and made the service feel much faster during prime time.”
Deploy LibreQoS on your own hardware.
Follow the install guide to add the LibreQoS package repository, run the setup wizard, and validate on a pilot before cutover. Routine questions go to the operator community.