Too many control surfaces.
Servers, containers, a 3D printer, AI tasks, and desktops all had their own routes. Repeating work through SSH sessions and scattered panels turned into friction.
Evidence file 01 / dashboard
LUCID Dashboard
Control panel for the home network: start machines, run scripts, launch services, and avoid SSHing into six different boxes for one simple action.
What it was actually solving.
LUCID manages the pile of self-hosted services, VMs, smart devices, and one-off daemons around Calvin's home network. The point is to make annoying operations easy from any device.
One useful panel.
A single-page command surface calls small services on the network: wake a PC, start a container, kick off scripts, open tools, and keep routine operations in one place.
The interface is part of the infrastructure.
LUCID made frontend, backend, and sysadmin work one connected problem. It pushed cleaner API boundaries, safer remote controls, and a UI that makes technical actions readable instead of magical.
Illustrative route map / not live telemetry
Browser to bench.
The page turns a scattered home lab into a short path: choose a target, send one intentional action, and get a useful result.
More from the bench.
Different materials, same habit: find the friction and build the missing tool.