Public status

Live status, without exposing the engine room.

This page answers the practical question: are the public paths healthy? It avoids publishing internal topology, operator details, or sensitive runtime evidence.

Request SessionReport an issue

Live public status

Useful status without exposing private details.

This page reports public availability, proof freshness, and release movement. It does not publish hostnames, topology, capacity numbers, operator paths, secrets, or incident internals.

Public site

Checking

Checking the public status feed now.

Proof

Checking

Checking proof freshness now.

Deployments

Checking

Checking public deployment markers now.

Approvals

Checking

Checking public approval summary now.

Public components

Checking component summary...

Disclosure boundary

  • No internal hostnames or service discovery names.
  • No exact host, allocation, CPU, memory, disk, or pool counts.
  • No operator paths, secrets, customer data, or incident internals.
  • Machine liveness remains at /status/droco.

checking live status...

Public by design

Public endpoints show high-level availability, recent release markers, proof freshness, and intake readiness.

Private by default

Internal service names, LAN hostnames, allocation details, capacity totals, paths, secrets, customer data, and incident notes stay behind authenticated operator tools.

Proof led

If a feed cannot be verified, the page shows unavailable instead of inventing uptime or repeating stale claims.