SpookyJuice · free & open firmware
SpookyWrt

A free, professional-grade OpenWrt firmware with a GL.iNet-class UI — for any box that runs OpenWrt. From a $15 thrift-store router to an x86 VM: one identity, one workflow.

Device dashboard ↗ Configure ↗ View the repo
4
architectures
6
modes
~30s
to build
$0
forever
the ecosystem

One identity, three engines

The trick that keeps "many tools on many boards" from becoming twenty forks: a shared look and a shared tool suite, with the right base OS chosen per role.

routers

SpookyWrt

OpenWrt image-builder flow. Router / AP / travel / NAS / hacker / honeypot on any OpenWrt target. LuCI underneath, GL.iNet-class UI on top.

diagnostics

SpookyProbe

Plug-in "network doctor in a box" for field techs. Debian + a containerized tool suite. Auto-sweep, pcap to NVMe, hand-off report.

security · authorized

SpookyLab

Home-lab / CTF / authorized-audit toolkit. Monitor-mode Wi-Fi, IDS, isolated lab VLAN, consent-gated. Your gear, your rules.

supported hardware

Any box that runs OpenWrt

Four architectures, one identity — the UI and the workflow are identical whether it's an arm64 SBC, an x86 VM, or a $15 MIPS router. Adding a board is a thin driver + form-factor layer, not a rewrite.

architecture

Three decoupled layers

Write the tools once, choose an OS by role, keep hardware differences to a thin edge.

TOOL SUITE — portable, containerized (write once) probe · wifi · capture · collector (Influx+Grafana) · analyze · the SpookyJuice UI BASE OS — chosen by ROLE, not by board Router → OpenWrt (image builder) · Diagnostics/Security → Debian + containers HARDWARE FLAVOR — thin per-board layer drivers + form factor: NICs · Wi-Fi · NVMe · OLED / HDMI console adding a new board ≈ a day, not a rewrite
dynamic workflow

Build, then configure

Two point-and-click tools: assemble a custom image, then generate its first-boot config. Everything writes itself — copy, paste, done.

Build Factslive