LibreQoS vs Bequant

Your subscribers use more than TCP. Improve the whole connection.

Video calls, gaming, browsing, and downloads share the same connection. LibreQoS combines published queueing algorithms with an explicit network hierarchy to help keep competing traffic responsive under load. Bequant also documents active queue management, congestion mitigation, and subscriber policies alongside TCP acceleration. Compare the engineering and operating controls below.

LibreQoS in use

A better connection, from shared link to subscriber

Manage competing flows, control the capacity they share, and follow service problems through the Network Tree to the affected circuit.

LibreQoS v2.2 Network Tree: configured and effective limits, live throughput, RTT, QoO, and child node queue metrics
Actual LibreQoS v2.2 Network Tree with identifying details obscured. The selected node and child rows show live evidence; circuit investigation continues in another view. This is workflow proof, not a comparative performance result.
  1. Keep calls and games responsive while downloads run.

    CAKE gives competing flows their own queues, helping protect latency-sensitive traffic when bulk transfers fill the connection. Follow the CAKE illustration below to see the principle in action.

  2. Control congestion where subscribers share capacity.

    Set nested limits for backhaul, site, access point, and subscriber circuits. The Network Tree puts shared capacity and live quality signals in the context of the network you operate.

  3. See what happens to the connection.

    Follow the affected branch into circuit queues, RTT, retransmits, and traffic flows. Use the local console for live investigation and add Insight to revisit past intervals and recurring problems.

Different approaches. Inspect the engineering.

Compare how each platform manages congestion, allocates shared capacity, and explains its behavior. LibreQoS descriptions link to our technical documentation; Bequant descriptions summarize its own published materials.

Sources reviewed September 10, 2026. This is a comparison of documented designs and controls, not a head-to-head performance benchmark. Deployment and licensing details follow the engineering comparison.

Topic
LibreQoS
Bequant - vendor-published
How is congestion controlled?
LibreQoS
Hierarchical rate limits govern shared capacity. CAKE and fq_codel manage competing flows within those limits using published queueing algorithms and readable Linux implementations. LibreQoS: hierarchy and queueing design
Bequant - vendor-published
Bequant documents TCP optimization, automatic congestion management, and shaping. Its release notes also credit improvements to FQ-CoDel shaping from release 4.6.3. BQN release notes: TCPO, ACM, and FQ-CoDel
How is shared capacity represented?
LibreQoS
An explicit parent-child queue hierarchy represents shared bottlenecks, with circuits operating within their ancestor limits. Model the configured path through backhaul, site, and access nodes. LibreQoS: HTB hierarchy and controls
Bequant - vendor-published
Bequant documents shared subscriber-group limits, including access-point groups, and max-min fairness among group members. Subscribers can belong to multiple groups. The cited guide does not describe an equivalent parent-child queue hierarchy. BQN: Subscriber Group Rate Limiting
Can you review automation before it changes limits?
LibreQoS
StormGuard offers dry-run evaluation, configured bounds, decision reasons, and change logs. Its intended scope is variable WAN links or a small number of highly variable access points. LibreQoS: StormGuard configuration and decisions
Bequant - vendor-published
Bequant markets ACM as machine-learning-based. Its guide documents enable/disable controls and congestion, latency, and retransmission charts. It does not describe a dry-run mode or equivalent per-decision explanations. BQN ACM: Metrics and Configuration
How do you investigate a subscriber problem?
LibreQoS
Follow the local Network Tree into circuit queues, RTT, retransmits, and flows. Circuit views put live throughput, queue telemetry, and the upstream queue path beside subscriber measurements. LibreQoS: Network Tree and circuit investigation
Bequant - vendor-published
Bequant documents live subscriber flows, application metrics, historical charts, and comparisons between a subscriber and its groups, including latency and retransmissions. BQN Network Visibility: Subscriber Dashboard
Deployment: how do you run it?
LibreQoS
Deploy on your own server using an inline Linux Bridge, with a preferred shaped path and a bypass path. Linux Bridge guide
Bequant - vendor-published
Documents Layer-2 inline deployment on standard servers, with VMware and KVM options. BQN platform: Deployment
Licensing: what determines your cost?
LibreQoS
The free packaged build admits up to 1,000 valid mapped circuits. Local licenses larger deployments; Insight adds analytics. Paid plans use subscriber-based pricing. LibreQoS pricing
Bequant - vendor-published
Publishes per-server subscriptions based on peak throughput, independent of subscriber count. BQN platform: Licensing and pricing
See how CAKE handles competing traffic ↗

The illustration compares CAKE with a generic FIFO queue. The Off mode does not simulate Bequant.

Bequant entries summarize vendor-published materials, not independently verified performance. A capability not described in a cited guide may still be available. Published algorithms and documented controls do not by themselves establish superior results on a particular network.

Compare LibreQoS vs Preseem
Evaluate

Put both approaches through the same workload.

Compare loaded latency, loss, throughput, and fairness with interactive traffic and bulk transfers sharing a constrained link. Record the hardware, software versions, configuration, and test conditions.