The OpenWrt family: every firmware that grew from it

OpenWrt is not just one program. It is a whole family — a tree from which dozens of firmwares have branched out, each with a different purpose. Some simply add an easier interface, others are built for mesh networks, and others for cellular modems or specific hardware. When someone says "I'm flashing OpenWrt," it can mean ten different things.

This article is a map of that family. We'll walk through every significant firmware built on OpenWrt — what it does, who it's for, and its strengths and weaknesses. At the end you'll find a quick comparison table.

The main trunk: OpenWrt and LEDE

To talk about the branches, you first need to know the trunk. OpenWrt is an open-source Linux distribution for routers, born in 2004 from the effort to liberate the Linksys WRT54G firmware. Version 25.12 (2026) supports over 2,200 devices, ships the apk package manager, and includes the LuCI web interface.

In 2016, a group of developers unhappy with the pace of development created a fork called LEDE. For a while the two projects ran in parallel, confusing the community. In 2018 they merged: LEDE's changes became the new mainline of OpenWrt, and the LEDE name disappeared. Today LEDE is just history — but it's worth knowing about, because the internet still holds old articles and guides with that name describing exactly the same project.

Gargoyle — simplicity above all

Gargoyle is a firmware built on OpenWrt with one goal: to make routers understandable for ordinary people. Where OpenWrt focuses on maximum capability, Gargoyle invests in the user interface.

Its strength is bandwidth management. Limiting the speed of a single device, setting data quotas, controlling downloads — all of this happens in a few clicks, without ever touching a configuration file. Traffic is visualized with clear graphs, and setup feels more like a modern home router than a server.

The weaknesses come from the same philosophy. Hardware support is narrower than OpenWrt's, and updates ship less frequently. The project is alive, but it moves at a slower pace because it's run by a small team.

Who should use it: households and small businesses that want speed limits and quotas without learning the command line. If you want OpenWrt's full power, look at the main trunk.

Gluon — the mesh community firmware

Gluon isn't just one firmware — it's a framework for building firmwares. It's designed for a single thing: creating mesh networks where many routers connect to each other and form one large decentralized network with no central point.

Gluon is the heart of many of Germany's community networks (Freifunk). Devices configure themselves almost automatically, receive updates with cryptographic signature verification, and nodes exchange status data. Several mesh protocols are supported — 802.11s over the radio, WireGuard and fastd over the internet link.

This is a highly specialized tool. If you're not building a community mesh network, Gluon isn't for you — it lacks almost all the features of a normal home router, because that's its whole point.

Who should use it: community network initiatives, municipalities, groups building free decentralized networks.

LibreMesh — mesh for Latin America's communities

LibreMesh is a close cousin of Gluon with its own philosophy. It was born in Latin America's community networks, where missing or expensive internet is replaced by local wireless networks built by the residents themselves.

It's built on OpenWrt and offers automatic node configuration based on the batman-adv mesh protocol. A device connects, configures itself, and becomes part of the network. LibreMesh is actively developed and has its own database of ready-made firmware images.

Like Gluon, it's not a general-purpose router. Its entire life is dedicated to community mesh networks where reliability and easy deployment matter more than a wealth of features.

Who should use it: community networks, local initiatives, organizations building local internet where the market doesn't reach.

CeroWrt — the lab that changed everything

CeroWrt is a special case — a research project that has ended, but whose legacy lives on everywhere. It was created by the people behind the movement against bufferbloat (the cascading latency that hits networks under load).

The project studied how routers behave on saturated links and developed algorithms like CoDel and fq_codel for intelligent queue management. Its last release came out in 2014, and the participants themselves recommended moving to mainline OpenWrt. But the results weren't lost: they were baked into the Linux kernel and into modern OpenWrt, where SQM (Smart Queue Management) brings exactly those ideas to every router.

The practical takeaway: don't look for CeroWrt. Use SQM in OpenWrt — that's the living successor of this lab.

Turris OS — security as the core focus

Turris OS is the operating system of the Czech Turris routers, developed by CZ.NIC — the organization behind the Czech internet registry. It's built on OpenWrt but adds several unique things.

First, automatic updates. With OpenWrt you have to check for new versions yourself; Turris OS updates itself through its Updater-ng system. Second, the reForis web interface is significantly simpler than LuCI, making configuration easier for non-experts. Third, the Sentinel system analyzes network traffic, detects attacks, and can block malicious IP addresses within seconds.

Its strength is the complete solution: hardware and software are designed together, updates are continuous, and security comes first. The limitation is that Turris OS is intended primarily for the company's own hardware.

Who should use it: people who want a secure router with automatic updates and don't want to spend time on maintenance. The hardware, however, costs significantly more than ordinary routers.

ImmortalWrt — the fork for China

ImmortalWrt is a popular fork of OpenWrt aimed at users in mainland China. It solves real problems of the local market that mainline OpenWrt doesn't address.

It adds more packages, including tools for accessing foreign services, interface localization, and optimizations for Chinese networks. It supports devices that are popular in China but absent from OpenWrt's official list. Sometimes hardware that won't even start Wi-Fi with mainline OpenWrt works fine with ImmortalWrt.

Of course, there's a cost. Development is more closed, and packages may include tools of unclear origin. For users outside China, the fork offers little while the security risks remain.

Who should use it: users in China, or those with specific Chinese hardware. For everyone else, mainline OpenWrt is the better choice.

FriendlyWrt — specialized for NanoPi

FriendlyWrt is the work of FriendlyElec — the manufacturer of the NanoPi single-board computers. It's a firmware created specifically for their boards, turning a NanoPi into an exceptionally capable router.

The specialization brings concrete benefits: it uses the full potential of the hardware, including GPIO, display output, and video processing. HDMI console, audio, and a variety of peripherals are supported, making the board suitable not just as a router but also for IoT and NAS applications.

The advantage is deep integration with the hardware. The drawback — the firmware is made for FriendlyElec boards and isn't universal.

Who should use it: hobbyists and companies with NanoPi boards who want the hardware's full potential — from router to small server.

ROOter — internet through a USB modem

ROOter (from "Of Modems and Men") is a firmware dedicated to one task: using USB cellular modems in routers that don't support them out of the box. It's built on OpenWrt and covers over a hundred routers — from tiny travel devices to dual-band models.

Its main strength is broad support for 3G, 4G, and 5G modems over USB, PCIe, or M.2. ROOter shows detailed connection information — signal strength, cell, quality — and offers VPN, plus load balancing across several links. There's also a GoldenOrb variant with extra features.

The limitation is that the firmware targets specific router models and a specific scenario: mobile internet. For classic wired connectivity, mainline OpenWrt is more versatile.

Who should use it: travelers, temporary offices, places without fixed internet, and automation over cellular networks.

CoovaAP — hotspots with full control

CoovaAP is an OpenWrt-based firmware built for running public Wi-Fi hotspots. It integrates a captive portal and a user management system right into the device.

Its strength is the ready-made guest access infrastructure: users authenticate through a login page, their traffic is limited and monitored, and the administrator controls everything centrally. This saves a lot of work when deploying hotel, café, or corporate guest networks.

The weak side is that the project develops at a slow pace and hardware support isn't as broad as mainline OpenWrt's. For complex hotspot scenarios with many users, more serious platforms are often used.

Who should use it: small and medium venues that want to easily offer guest Wi-Fi with login and control.

Quick comparison table

Who should choose what

• A regular user wants an easy interface and speed limits → Gargoyle.
• A hobbyist wants full control and features → OpenWrt.
• A community network in your neighborhood or village → Gluon or LibreMesh.
• Someone with no time wants a secure router → Turris OS.
• A traveler with mobile internet → ROOter.
• A café or hotel with guest Wi-Fi → CoovaAP.
• A developer with a NanoPi → FriendlyWrt.
• A user in China or with Chinese hardware → ImmortalWrt.

Conclusion

OpenWrt is more than a firmware — it's an ecosystem. Every branch of this family solves a specific problem: from Gargoyle's simplicity to Gluon's mesh networks and Turris OS's security. What they all share is open source and OpenWrt's solid foundation.

When choosing a firmware, don't ask "which is the best" but "what problem do I need to solve." The same hardware can be perfect as a community mesh node and completely unsuitable as a home router — only because of the software you'll flash. The OpenWrt family lets you choose exactly what you need.