Features

What Phelix does for Go and Rust releases

Each capability on its own page: the problem it solves, how it works, and the exact commands. Start with the one you came for.

Deployment

Zero-downtime deployment

Ship a new version without dropping requests: blue-green, rolling, canary, and progressive deploys behind a reverse proxy, gated on health checks and backed by one-command rollback.

AI agents & MCP

MCP server for deployment

A built-in MCP server that lets Claude Code, Codex, and other coding agents propose deployments as immutable plans, with execution denied until a human approves that exact plan.

Builds

Multi-platform build matrix

Cross-compile Go and Rust across toolchain versions and platforms in one command: a deterministic build matrix with dry runs, resume, per-combination reports, and a release manifest.Feature

Build reports and regression alerts

Every build prints an automatic report: compiler version, duration, cache state, binary size, and regression alerts against comparable builds. Fully offline, no configuration.

Security

Encrypted environment variables

Per-app environment values encrypted at rest with AES-256-GCM and a local key, snapshotted per build, so rollback restores the binary and its configuration together.

Monitoring

Multi-server monitoring

One CLI and per-host agent stream application state, metrics, health snapshots, and redacted logs to a single view, opt-in per app, with an optional dashboard.

One release path, two toolchains.

Go and Rust are compiled on the host and then travel the same route: build, health gate, cutover. Only the toolchain and the target change.

01build

GoRust

binary

Host toolchain compiles a native binary. Docker stays optional.

02health gate

GoRust

healthy

Same readiness tiers for both. No candidate sees traffic early.

03cutover

GoRust

:8080

Proxy switches atomically, whichever binary is behind it.

Native toolchain: Phelix builds with the host's Go or Rust toolchain, hashes the artifact, and keeps the binary. A container stays optional.
Same release contract: Both runtimes read PORT and answer the same health tiers, so blue-green, rolling, canary, and progressive behave identically.
One rollback path: Every build is a version. Rollback restores the binary and its encrypted environment snapshot together, whichever language built it.

One binary between git push and production.

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