Press Kit

For journalists and content creators

Here's what we think might resonate most with your audience. Use what's helpful, ignore what isn't. We're not here to tell you what to write - just making it easier to get started. Thanks for your interest.

A native Android app. Not a wrapped website. Real push notifications when your NAS goes offline. Widgets on your home screen. Your homelab status on Android Auto while you drive. Wearable support coming. The server delivers raw stats in milliseconds - the smartphone does the heavy lifting. Linux philosophy: each component does what it does best.

A complementary control layer. DeQ doesn't compete with Homepage or Homarr. It doesn show the weather, it wakes servers, containers and shuts them down. It has a file manager to transfer files across your network. Manage containers on remote hosts. Schedule backups that run while you sleep. Those dashboards run in Docker - and they should stay sandboxed. Punching holes for system access defeats the purpose. DeQ runs bare-metal by design.

Designed to run in trusted networks behind WireGuard, Tailscale, or Cloudflare Zero Trust.

Built for low-power hardware. A Pi, a ZimaBoard, a mini PC - devices you already own, drawing 2-5W, finally doing real work. DeQ runs 24/7 on hardware that costs $8/year in electricity. From there, it controls the big servers you don't want running around the clock.

The whole thing is an SSH wrapper with a web UI. Python talks to your OS, your browser talks to Python. No libraries. No frameworks. No bloat. Just vanilla code using what Linux already provides.

Modern networks are dynamic. Containers come and go, VMs multiply, things change constantly. I kept forgetting to turn off my Windows VM. Cost me €100/year - just for forgetting.

DeQ started as two buttons: start the VM, connect via RDP. Then scheduled shutdowns. Then Wake-on-LAN. Each feature solved a real problem I'd been working around for decades. Pure user perspective, no theoretical design.

The 500KB size limit is enforced discipline. Features compete for bytes. Every line has to justify itself. It's opinionated pragmatism. Less > more, literally.

There's genuine satisfaction in squeezing real utility from a €50 device that draws 3 watts. It becomes its own hobby: how low can you go?

Last year I saved €400 on electricity by optimizing my homelab and being conscious about consumption in my apartment. DeQ is a tool born from that mindset.

Recommended hardware:

• Pi Zero / Pico: Works well in small networks. Proof that the code is lean.
• Pi 4 / ZimaBoard 432 and up: Recommended. Enough headroom for file transfers and multiple SSH connections with short polling intervals.

Your low-power device can do more than run DeQ. Throw Pi-hole on there. Use it as a Tailscale exit node. Sync your most-used files to it. When the big servers sleep, those files are still accessible - download them through DeQ's file manager, upload new ones, sync back automatically when the server wakes.

Always-on. Under 5 watts. Actually useful.