Feature
Multi-server monitoring
Each connected host runs one agent and reports application state, metrics, health, and redacted logs through an authenticated gRPC stream, so one or many servers appear on a single surface.
simulated
one agent per host · stream opening
Opted in per app
Monitoring is disabled by default. phelix watch enables it for one application, and phelix watch --disable turns it off. Local build, run, and deploy commands work with no account and no dashboard connection.
Each host is one server on the dashboard: a single agent id and state file per host, regardless of how many app instances it runs.
simulated
one command enables the stream for one application
What the agent reports
The agent streams metrics, application state, health snapshots, and redacted logs over a long-lived TLS-secured gRPC stream while at least one app is watched. The monitor service is installed as a systemd unit on Linux and restores running apps on boot.
Monitoring is per agent, not coordinated cross-host orchestration: Phelix does not schedule work across your fleet for you.
- Application status, metrics, health, and logs in one view
- Per-host identity, one agent per server
- Dashboard optional; the CLI stays fully local
- Redacted log streaming, never a remote shell
Frequently asked questions
Short answers; the docs go deeper.
Do I need a Phelix account to build and deploy?
No. Building, running, and deploying work fully locally without authentication. Logging in only links a host to the dashboard for remote monitoring.
Can Phelix monitor several servers from one place?
Yes. Each host reports through its own agent over an authenticated gRPC stream, so the dashboard shows every connected host in one view. It is monitoring, not cross-host orchestration.
One binary between git push and production.
Install the CLI, verify the host, and follow the quick start to build your first application.