LibreQoS vs Preseem

Extend queue control through your network hierarchy.

LibreQoS combines per-circuit queue management with explicit parent capacity limits, helping operators address congestion across shared links. Preseem also uses published AQM; the comparison below explains the documented hierarchy and workflow differences.

LibreQoS in use

From a shared link to the affected subscriber

Use the Network Tree to inspect shared capacity and follow the affected branch, then continue into circuit detail.

LibreQoS Network Tree showing node queue state, quality metrics and expandable child branches
An actual LibreQoS interface, with customer names obscured. Markers 1 and 2 identify the node summary and child rows; step 3 continues into another view. This illustrates the workflow, not a head-to-head performance result.
  1. Inspect shared capacity

    Compare configured and effective limits with throughput, RTT and retransmits for the selected node.

  2. Follow the affected branch

    Expand the child rows and compare their queue limits and quality metrics to narrow the investigation.

  3. Continue into circuit detail

    Open the subscriber circuit to inspect queues and flows. Edit parent relationships and capacity in Topology Manager.

LibreQoS: nested queue classes

Conceptual example of explicitly configured shared capacity.

  1. 01Backhaul

    Shared queue class

  2. 02Site

    Nested parent

  3. 03AP / OLT

    Access parent

  4. 04Circuit

    Subscriber plan

Preseem: documented TwoLevelMQ

Preseem also documents manual site caps. The cited guide does not establish a nested shaping tree for upstream backhaul links.

  1. 01Access point

    AP capacity enforcement

  2. 02Subscriber

    Subscriber-plan enforcement

Compare the decisions that matter

Sources describe each platform; operational results depend on configuration and network conditions.

Comparison sources reviewed September 7, 2026. Vendor entries describe their published materials; availability and commercial terms should be confirmed with each vendor.

Topic
LibreQoS
Preseem - vendor-published
Can I inspect the queue behavior?
LibreQoS
Inspect how packets are queued: CAKE and fq_codel have published algorithms and readable Linux implementations. LibreQoS queueing design
Preseem - vendor-published
Documents FQ-CoDel, a published algorithm that separates bulk and interactive flows. Preseem AQM and DPI brief
Where can I control shared capacity?
LibreQoS
Set shared-link capacity explicitly: circuits nest under AP, site, OLT and backhaul queue classes. LibreQoS queueing design
Preseem - vendor-published
Documents subscriber-plan and AP enforcement, plus manual site bandwidth caps. Preseem AP capacity management
Does shaping require application identification?
LibreQoS
Manage queues across TCP and UDP flows without identifying the application from its payload. LibreQoS queueing design
Preseem - vendor-published
Describes flow-based AQM without DPI application classification. Preseem AQM and DPI brief
What can I investigate?
LibreQoS
Follow subscriber symptoms into circuit RTT, retransmits and QoO; use Insight for history and ASN analysis. Insight documentation
Preseem - vendor-published
Describes traffic-based subscriber QoE measurements tied to network topology and centralized support views. Preseem network operations
How do I 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
Preseem - vendor-published
Documents an inline Layer-2 bridge for enforcement, with a separate management interface. Preseem inline deployment
What determines my 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
Preseem - vendor-published
Publishes subscriber-based pricing; current commercial terms are available from Preseem. Preseem FAQ
See how CAKE handles competing traffic ↗

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

Competitor entries summarize Preseem's publications. Both platforms use published AQM; Preseem documents subscriber/AP enforcement and manual site caps, but the cited guide does not document nested upstream backhaul shaping. Neither published algorithms nor subscriber pricing alone establishes superior results or lower cost.

Compare LibreQoS vs Bequant
Evaluate

Measure LibreQoS on your network

Start with a pilot site and compare busy-hour performance before and after deployment.