Skip to content

Process supervision

A process manager for Go on your own servers

Keep compiled Go services running with real supervision: lifecycle control, tiered health checks, bounded restarts, and a live view across every host, from one CLI and agent.

Released Phelix hosts: Linux and macOS. Builds Go and Rust with your host toolchain.

Lifecycle you can script

Start, stop, restart, and inspect applications with a consistent set of commands.

Phelix supervises the native binary it builds, so a Go service becomes a managed application rather than a hand-written unit file. Every command is available through an interactive wizard and stays fully scriptable for automation.

The lifecycle verbs and their flags are documented in build and lifecycle.

phelix · lifecycle
phelix status
api v3 :8080 healthy
worker v7 stopped
phelix restart api
api restarted, health ok

Health you can act on

Tiered checks decide what is healthy, and repeated failures trigger bounded recovery.

Phelix supports explicit HTTP readiness with automatic HTTP, TCP, and PID fallbacks, configured in phelix.yaml. Repeated endpoint-health failures can trigger bounded restart attempts with an attempt cap; if restoration fails, Phelix records a degraded state that needs manual intervention rather than looping forever. The tiers and modes are in health checks.

Health checks reduce risk; they do not prove that every behavior of your application is correct.

phelix · watch
phelix watch api
watching api on 2 hosts
host-1 v3 healthy cpu 4% mem 61MB
host-2 v3 healthy cpu 5% mem 63MB

Every server on one surface

Opt an application into monitoring and watch it across hosts.

Each connected host reports metrics, application state, health snapshots, and redacted logs through an authenticated agent stream, so one or many servers report to a single view. See multi-server monitoring for how the monitor daemon and fleet view work.

The dashboard connection is optional and everything works locally without it. Monitoring operates per agent; it is not coordinated cross-host orchestration, and Phelix does not schedule work across your fleet for you.

One binary between git push and production.

Install the CLI, verify the host, and follow the quick start to build your first application.

Read the docs