Deploy
Deploy LibreQoS on your own hardware
Run 1 CLI line, open the WebUI, complete setup, and validate with a limited pilot before rolling into production. Inline Linux Bridge is the default path, and the installer handles the bridge setup automatically for most operators.
Stages
Choose the deployment stage first
Start with evaluation, validate with a pilot, then move into production.
Platforms
Use the substrate that matches operational reality
Bare metal remains the default for production headroom. VM remains credible where virtualization is already standard or where managed WiFi environments benefit from that model.
Sizing
Start With The Deployment Profile That Matches Your Network
Use subscriber scale and throughput to narrow the field first, then confirm CPU single-thread performance, RAM, and NIC support before production rollout.
Small
Up to about 1,000 subscribers and up to roughly 1 Gbps. Good fit for pilots, smaller production networks, and lighter managed WiFi environments.
Medium
Roughly 1,000 to 5,000 subscribers and around 1 to 10 Gbps. A common fit for established WISPs, smaller fiber operators, and many production VM deployments.
Large
Roughly 5,000 to 20,000 subscribers and around 10 to 50 Gbps. Requires stronger CPU selection, more RAM, and supported higher-speed NICs.
High-Throughput
50 Gbps and above, or deep hierarchy at scale. Prioritize high single-thread score, queue-to-core balance, and validated XDP-capable NIC support.
Recommended Hardware
Reference Builds From The Official LibreQoS Hardware Guidance
These are practical starting points from the current LibreQoS hardware recommendations. Use them to choose a credible pilot or production platform, then validate fit against your topology and throughput goals.
1G to 10G Small Form Factor
Minisforum MS-01 with i9-12900H, 32 GB RAM, and built-in NICs. A strong compact option for pilots, smaller production deployments, and operators who want serious performance without a rack server.
10G Rackmount
Supermicro SYS-511R-M with E-2488, 32 GB RAM, and dual 10G SFP+. A solid production starting point when you want rackmount hardware and clearer 10G expectations.
10G Rackmount
Dell PowerEdge R260 with E-2456, 32 GB RAM, and Intel X710-T2L dual 10G RJ45. A practical fit where 10G copper is preferable or Dell standardization matters operationally.
25G Production
Supermicro AS-1115S-FWTRT with 8534P, 64 GB RAM, and Mellanox dual SFP28. A stronger fit for operators moving beyond 10G and needing more production headroom.
50G Production
Supermicro AS-1015SV-WTNRT with 8534P, 128 GB RAM, and Mellanox 100G connectivity. A higher-throughput option for larger deployments and more demanding hierarchy depth.
100G Production
Supermicro AS-2015CS-TNR with 9745, 256 GB RAM, and MCX653106A-HDAT. Built for very high-throughput environments where queue-to-core balance and NIC validation matter.
Sizing Estimator
Calculate Hardware Fit
Use current hardware guidance to estimate deployment fit for your CPU, NIC, RAM, and topology.
CPU catalog refreshed at deploy time. Current local snapshot: 2026-04-17T02:12:39.101Z.
Optional target inputs
Fit
good
No explicit target entered. This card shows conservative upper bounds from the docs.
Aggregate throughput
up to ~10 Gbps
Per AP / OLT / top-level node
up to ~6 Gbps
Per subscriber plan
up to ~6 Gbps
Max circuits supported
up to ~4,800
Warnings
- Intel modules can be vendor-locked. Verify optics compatibility.
Prerequisites
Validate These Before You Buy Or Roll Out
Production confidence depends on supported hardware, validated NIC fit, and setup prerequisites, not just raw server specs.
Platform fit
- Ubuntu Server 24.04
- High single-thread CPU performance matters more than generic core count alone
- Enough RAM for expected subscriber scale
- 50 GB or more of disk
- Disable hyper-threading / SMT
- Disable SR-IOV where required
Network fit
- Use a separate management interface
- Use a supported shaping NIC family
- Do not use bonded shaping interfaces
- VM deployments need multiqueue aligned to vCPU
- Above 10 Gbps on VM usually requires passthrough
- Single Interface remains an advanced option only
Install Flow
Default path: inline Linux Bridge, then WebUI setup
For most operators, the installer creates the Linux Bridge automatically, so deployment starts from the CLI and continues in the WebUI.
1-Line Install
Copy, paste, install the current stable Debian package.
cd /tmp && sudo apt-get update && sudo apt-get upgrade -y && wget https://download.libreqos.com/libreqos_2.1.202604032221-1_amd64.deb && sudo apt-get install -y ./libreqos_2.1.202604032221-1_amd64.debInstall Ubuntu Server 24.04
Prepare the host, keep management separate, and verify the machine matches the profile and NIC guidance.
Run the 1-line install
Use the packaged install path to deploy LibreQoS without manually building the Linux Bridge.
Open the WebUI on :9123
Open the WebUI and confirm the system is healthy.
Run Complete Setup
Connect LibreQoS to the data source you use for shaping and topology.
Validate with a pilot
Do not treat a loading dashboard as proof. Confirm scheduler health and one known-good subscriber or device.
Validation
Validate Before Production
Production readiness depends on scheduler health, topology health, and a validated pilot, not just package installation.
Health check
- Dashboard loads
- Scheduler is no longer Setup Required
- Expected topology or subscriber/device list appears
- lqosd and lqos_scheduler are healthy
Pilot readiness
- One pilot subscriber or device behaves as expected
- Expected hierarchy depth appears
- No urgent startup errors remain
- Only then expand toward production cutover
Production
Design The Bypass Path Before Production
Production routing should prefer the inline LibreQoS path during normal operation, then converge cleanly to a higher-cost bypass path during maintenance or failure.
Design The Bypass Path Before Production
Production routing should prefer the inline LibreQoS path during normal operation, then converge cleanly to a higher-cost bypass path during maintenance or failure.
Operational checklist
- Use deterministic OSPF or BGP preference between primary and bypass paths
- Validate backup-path capacity for realistic degraded-state demand
- Test failover and failback during maintenance windows, not just in theory
- Do not skip the limited pilot just because installation was fast
Proof
See what LibreQoS looks like once it is installed
Real product views help operators understand what healthy deployment looks like.
Start
Start the 1-Line Install
Once hardware fit and rollout expectations are clear, move directly into installation.