I have been flashing DD-WRT to my routers for many years. My current setup is an Archer C9 that connects via cable to an Archer C8, which then wirelessly bridges to an R7000. All of them run DD-WRT. If I had "fun money," I would buy a low-power SFF PC with dual NICs, run OPNsense or OpenWrt, and use the wireless routers strictly as access points. Since I don't have that much to spend, I look for older DD-WRT friendly routers, usually under $30, on Craigslist or Facebook Marketplace, and flash them myself.
I see that Ubiquiti and MikroTik make quality routers with proprietary OSes for around $65 new. Protectli and Netgate offer pfSense routers starting at $259.00. The GL.iNet Flint 2 is $169.00, and the OpenWrt One is $89.
According to ResellBot (because eBay now requires a login to see sold listings with prices), the sold "DD-WRT Routers" generally go for under $160. These include the WRT3200ACM, Netgear AC1750, Linksys EA9300, and Linksys R7350.
When I asked an AI how I would go about judging interest, building, raising funds, and manufacturing, it seems doable but expensive (said $125,000 minimum in total made up of $30,000 for regulatory approval, engineering and protoyping $10,000+) and time-consuming just to get to a "golden prototype" for demos.
So if I were a "hacker" and wanted an open-source router, depending on my funds, I would either:
1. Flash DD-WRT to an existing router (used or new).
2. Buy one with it already installed, like the OpenWrt One or a Protectli device.
3. Get an SFF PC and build my own.
I remember when some comments about DropBox said it was a waste because any hacker could make that. I also know DropBox was marketed to the average person and businesses. I don't really see how a hacker friendly router could take off like that unless hackers are choosing the hardware and setting up the networks for average people. And I assume that most people setting up the networks want different qualities like brand name recognition, ease and speed of purchasing equipment (Walmart or BestBuy), and the ability to point a customer or family member to the number of solid reviews and articles saying it a good router to qualify their choices.
So, do you actually want a router that you can buy with DD-WRT pre-installed?
Similarly though, there's limited appeal to those who aren't already capable of setting it up themselves.
I'm still slowly pursuing this because I believe in it, whether it's profitable or not.
Edited to add: Part of what I'm setting up: https://lists.uninvitedactivity.com/DNS/, a vague explainer here: https://news.ycombinator.com/item?id=49990394
ISPs would have been able to do this kind of thing since forever but, strangely, I don't see it advertised as a potential value-add at all. Had ISP's commonly taken up such a mantle, players like NextDNS probably would be less necessary.
I find ASUS hardware high quality in general. And using an open-source project like ASUS Merlin means the pain-points and limitations that I would face with stock firmware have been resolved to (at least to satisfactory extent) when I need reach for the hacker type configurations.
So I buy GL.iNet routers, which come with OpenWrt pre-installed.
For routers, the only realistic way that can happen is by getting some big vendor to adopt ddwrt or openwrt to offload (some of) the job of writing the firmware. And even then, most people use their ISP provided router. A niche vendor supplying preflashed routers isn't going to make a dent.
1) Privacy/ ad-protection native (as you say)
2) High security and performance (fully tuned DD-WRT). Even solving bufferbloat for end users would be amazing - the world is barely catching up on that.
3) Good software add-ons that aren't proprietary junk. Asset management/upgrade, sign-in/landing pages, monitoring and trafffic shaping that holds up, etc.
Bunlding FOSS to solve these problems well, even on some else's hardware, does seem like work, and work can be charged for.
Back in the day I probably modded over 100 consoles for people, Xbox, Wii, DS, Switch, PS3.... I can't say that even once the person cared about hearing what XBMC was and all the things it could theoretically do. They just cared about being able to play/watch things with the press of the button without having to know any of the tech aspects.
Anyone I knew that could mod consoles just did it themselves.
Would be legit to be able to have an Llm do a source audit before installing …. Not perfect but damn sure better than nothing
https://www.gl-inet.com/en-de/products/gl-be14000
so.. yes? I haven't gotten around to flashing stock openwrt on it - but I probably will at some point - seems to be supported now?
https://forum.gl-inet.com/t/flint-4-openwrt-vanilla/71383/10
I think it would be difficult to compete with existing offerings - even though they are quite few.
No, I'd rather flash it myself and use OpenWrt instead of DD-WRT.
It's currently serving as a wireless bridge client for a network of 10 IP cameras.
pfsense can sell for a relatively high price, I think, because they market themselves more towards businesses and big corporations.
If there wasn't, I was going to use this as a project to explore vibecoding...
* An Opnsense firewall (purchased from Deciso; ie: "official" hardware)
* An OpenWRT One (ie: "official" hardware) to be used as an access point
* A Microtik switch (SW OS, not Router OS)
My plan is to create multiple SSIDs, have each one on a different vlan, and then control services provided to that vlan. For example, I'll dump all IOT crap onto a vlan that doesn't have internet access.
I'm still not 100% sure it will work (the hardware still hasn't arrived). But finally, to answer your question: "Yes!"
Holy crap, give me official hardware. I installed DD-WRT on my linsys router. It's been so long that I don't remember exact details, but the process was INTIMIDATING. I felt like I had to download a blob from a website that wasn't the official website (ie: I seem to recall different people building DD-WRT for different hardware). I also recall some features not being available on some hardware.
Give me the hardware that is sold by the people that work on the project!
I want some reassurance that I have the "most supported hardware", so I don't have to go through huge feature matrices to see if my hardware supports feature X.
I want headroom to install new packages. I don't want to have so little space that I need to remove one package to install another.
And finally, I want the people writing the software to GET PAID, because I want it to still be around... and being actively developed 10 years from now.
PS:
I initially wanted to get a consumer grade switch, but my network operator friends told me that was a terrible idea... and that I should get a use Cisco switch on Ebay. Cisco is probably great and network operators love it... but holy crap... trying to figure out what switch to buy is an enormous pain in the a$$. I pushed my friends, they relented and said: "Mikrotik is also great". I went to their website. 1000 times better than Cisco's; their switches were cheaper. I didn't have to "call for a quote" or scour Ebay. I haven't turned it on yet, but the buying experience was so much better.
Buy https://www.gl-inet.com/en-us/products/gl-mt3600be and move on with your life.
Alternately, what's the problem you're trying to solve? Who are your potential customers? Why do existing options in the market not address their needs?
Those who look at you blankly when you mention open-source router firmware aren’t likely going to become customers.
I'm not sure how approachable tools like Claude Code have made this for people though. If I was just getting started, I would probably just have the tool do it for me.
compared with RouterOS where the Linux bits are almost completely hidden behind the proprietary config engine (and the proprietary cli and webuis that power that config engine). for the most part with routeros, you'd be hard pressed to know that you're even on a unix let alone linux.
At one point, and I don't remember exactly when, I just started using OpenWRT instead. It wasn't always the case, but it presents a very usable GUI straight away these days and it has a ton of flexibility for getting creative later.
At home I run it on a Pi4 that I bought for the purpose. It keeps up with my 500/20Mbps DOCSIS internet very well indeed. I've used it with a USB NIC to get dedicated ports, and also with VLANs and a managed switch instead. I just download and flash the card, plug stuff in, and configure it. No real issues -- for years, now. (Wireless is provided by Mikrotik access points.)
When something faster happens in my neighborhood (which may be very soon; I had a very brief chat with a dude whose fiber splicing trailer was parked across the street just yesterday), I'll probably want to move to something more capable.
That could be in the form of faster Pi, or an old PC running OPNsense -- or even stick with OpenWRT. No big deal.
If I really wanted a tidier package for light-weight travel or something, then I guess I'd pick something appropriate from glinet and put an official OpenWRT image on it.
For heavier-travel, I've got a kit with a Pi4, a managed PoE switch, and a backup Mikrotik box (that can be a switch or a router; it runs OpenWRT as well and the normal config is that it just provides more switch ports), and all this stuff is mounted onto a 1U rack shelf that is in-turn inside of a road case. It's meant to be physically durable and to include enough gear that if any part of it dies then I can replace that functionality Right Now without spending time finding parts in the middle of nowhere.
So, no: I would not buy one that was prefabulated. It wouldn't scratch my itch.
---
For everyone else? Honestly, the regular folks I know who ask me questions about networking aren't into that stuff at all or they wouldn't be asking. They don't care about ultimate speeds, or latency under load, or any of those things. They don't care about running Internet services from their network, or services on their local network, and probably don't even have a printer to abuse if something goes awry. They're also not interested in exploring the bowels of their home to install cabling for PoE access points.
They just want decent-enough wifi coverage that they don't have to think about it, and then: They want to succeed at not thinking about it.
So for those folks, I've come to recommend proprietary multi-node mesh systems. It doesn't really matter to me which one it is, or how terrible some aspect or other is: They all tend to check the right boxes, they update themselves, and then: Nobody thinks about them.