OpenWRT & Embedded Web UI Development
Most embedded devices ship with a clunky, dated web interface — or none at all. I design and build clean, responsive web UIs that run directly on routers and embedded Linux hardware, including OpenWRT firmware — fast enough for constrained CPUs, modern enough to put your brand on.
What I build
Custom router dashboards
Modern admin panels that replace or complement LuCI, tailored to your firmware and branding.
Real-time monitoring
Live views of traffic, connected clients, signal, and system health, streamed over WebSockets.
Configuration interfaces
Settings screens wired straight to the device through ubus, REST, or CGI — no fragile shell scraping.
Captive portals & onboarding
First-boot setup wizards and captive portals that get users connected in seconds.
Lightweight by design
Hand-optimised bundles that load instantly and stay responsive on low-power MIPS and ARM SoCs.
Firmware packaging
Your UI built into the image as an OpenWRT package, with the build and deploy pipeline to match.
How we'll work together
Discover
We map your hardware, firmware, endpoints, and the exact screens your users need.
Design
Wireframes and a clean visual direction that fit constrained displays and your brand.
Build
I implement the UI and wire it to the device, with clickable previews at every step.
Ship
Packaged into your firmware, tested on real hardware, and documented for your team.
Built for constrained hardware
Embedded targets mean tight CPU, memory, and storage budgets. I keep bundles small, avoid heavyweight frameworks where they don’t earn their weight, and make interfaces that stay fast on low-power devices — while still looking like software from this decade.
- Bundles measured in kilobytes, not megabytes
- Stays fast on low-power MIPS and ARM hardware
- No heavyweight runtime fighting your flash budget
- Looks like modern software, not a 2009 admin page
Tech stack
Frequently asked questions
Can you work with my existing firmware?
Yes. I integrate with stock OpenWRT or your custom build, talking to the device through ubus, REST, or CGI — whatever your image exposes.
Will it run on low-end hardware?
That's the whole point. I budget for tight CPU, RAM, and flash, and test on the actual target so the UI stays snappy.
Can it replace LuCI completely?
It can replace it, sit alongside it, or cover just the screens your users actually touch — your call.
Do you handle the firmware packaging?
Yes — I can deliver the UI as an OpenWRT package and set up the build so it ships inside your image.
Have an OpenWRT router or embedded product that deserves a real interface?
Let’s talk →