status.vulos.org

Nothing here to monitor.

Vulos runs on your own hardware, not on a service we operate. There is no central Vulos status to report — check your box’s own admin view instead.

There is no Vulos service to be down.

We publish the OS — one open-source binary. We don’t host boxes, run a backend for them, or operate any infrastructure your box depends on to work.

Your box reports its own status.

Every install ships with an admin view covering health, storage, connected devices and an activity log. That’s the status page that matters, and it lives on your box.

Reachability is yours to inspect.

If you reach your box through the built-in Vulos relay or direct over your own domain, either path is something you can run and monitor yourself — nothing is opaque or centrally gated.

Run your own box? It exposes GET /healthz locally.vulos.org