Nodes, guests, storage and disk health across every server you run — with start, shut down and restart behind Face ID. No account, no telemetry, no server of ours in the middle.
Three platforms today, and the list is growing. Tell us what to add next.
iPhone · iOS 17 or later · coming to the App Store
A monitoring app is only useful if you believe it. These are the parts that earn that.
A degraded pool, a failing drive, a volume filling up, a node that stopped answering — stated in plain language at the top, worst first. You shouldn't have to interpret a wall of numbers to find out whether anything is wrong.
Most stopped guests are stopped on purpose. The alert fires only when the platform's own auto-start flag is set and the guest isn't running — your declaration, on your server, so it can't drift out of sync with reality.
Start, shut down, restart or force stop any VM or container. Controls sit behind a swipe or a long press, every action names what it's about to affect, and force stop is worded so you know you're pulling the power.
Biometrics unlock a short window rather than prompting on every tap. A prompt you tap through without reading protects nothing; the confirmation sheet naming the guest is what stops you halting the wrong VM.
SMART status, drive temperature, SSD life remaining and serial numbers — so the drive you need to replace is the one you actually pull. On TrueNAS, live ZFS vdev state and error counters, not the result of a self-test somebody ran months ago.
ZFS ARC and Unraid's page cache deliberately fill RAM. A single bar paints a healthy machine permanently red, so memory is drawn as two segments: real pressure, and reclaimable cache. Neither figure alone is honest.
Leave power management off your API token and the whole dashboard still works. Controls then return a clear "missing privilege" message rather than failing strangely.
Long-press a concern and it collapses out of the way. It comes back only if the severity changes or the number gets measurably worse — measured from where you acknowledged it, not from a fixed tier you'd trip over immediately.
Every screen below is running against sample data — the same mode you can try before you own a token.
You're handing this app an API token to your infrastructure. Here's exactly what happens to it.
Stored with kSecAttrAccessibleWhenUnlockedThisDeviceOnly,
so they're readable only while the device is unlocked and they don't
sync to iCloud.
Self-signed certs are fine — you compare the fingerprint on first connect. A changed certificate afterwards is a hard failure that asks you again. It's never silently accepted.
There's no server of ours to sign in to and no third-party code in the app at all. The only network requests it makes are to the addresses you typed in.
Each of these needs an API token from the system itself. The app's setup guide walks through it, and so does the support page.
| Platform | Supported from | Tested through | Credential |
|---|---|---|---|
| Proxmox VE | 7.0 | 9.0 | API token (user@realm!tokenid) |
| TrueNAS SCALE | 23.10 | 25.10 | API key |
| Unraid | 7.0 | 7.2 | API key from unraid-api |
Older releases use different API shapes; support goes back to the last clean architectural break on each platform rather than to 1.0.
The app is built so that a platform is an adapter behind one shared interface — the dashboard, the alerting and the controls are already platform-agnostic, so adding one is a contained job rather than a rewrite. What gets built next is decided by what people actually ask for.
