Skip to main content
Each orun node exposes a lightweight HTTP API on port 9100 (configurable via --status-port) that lets you inspect node health and the current state of all deployments and services. The server binds to localhost only — to query it from a remote machine, open an SSH tunnel first.
The status API is read-only and makes no changes to containers or configuration. It reads exclusively from the in-memory state store maintained by the agent.

Accessing the API remotely

Because the API listens on localhost, use an SSH tunnel to reach it from outside the node:
Then query the API locally as if you were on the node.

POST /healthz

Returns a simple liveness response. Use this endpoint to confirm the orun agent process is running and able to accept requests. Request: no body required. Response:
string
required
Always "ok" when the agent is alive. If the agent is not running, the connection will be refused rather than returning an error body.

POST /status

Returns the full NodeReport — a consistent, point-in-time snapshot of the node, all tracked deployments, and all active ingress routes. Request: no body required. Response: a NodeReport object.
object
required
Node-level status information.
object
required
A map of deployment name to deployment status. Each key is the deployment’s metadata name from its manifest.
object
required
A map of service name to service status. Each key is the service’s metadata name from its manifest.

Example request and response

orun is pre-release software. The structure of the NodeReport response may change in future versions without a deprecation period.