Repository
Committed application source and a schema-version-1 manifest.
Execution layer / read-only view
The app runner is the narrow bridge between a committed repository and a public FairyStack application. Explore what it sees, what it does, and where its authority stops.
Waiting for first snapshot
Anatomy
Committed application source and a schema-version-1 manifest.
Validates the contract and hands work to the privileged lifecycle boundary.
A managed system service bound to a dedicated local port.
TLS-terminated HTTPS routed to the healthy application.
Live inventory
A sanitized snapshot from the runner’s public read interface. No environment variables, logs, process arguments, or lifecycle credentials are exposed.
Loading live applications…
Surfaces
/api/versionService name, runner version, and supported lifecycle contract.
PUBLIC · READ ONLY/v1/healthA minimal liveness response from the local execution service.
PUBLIC · READ ONLY/v1/inventoryManifest metadata, runtime state, revision, and source size.
PUBLIC · READ ONLY/v1/apps/*Deploy, restart, create, rename, and removal operations.
UNIX SOCKET · AUTHENTICATEDObserved in this release
For an already-running service, activation does not necessarily replace the process. A changed server entrypoint can therefore remain unloaded even after a successful deployment receipt.
This explorer documents the observation; it cannot invoke or alter lifecycle operations.
The trust boundary
Read version, health, and sanitized inventory metadata through loopback HTTP.
Reach the authenticated lifecycle socket, mutate apps, read secrets, or inspect private logs.