Guide
Deploy Go without Kubernetes
Running one or a few Go services on servers you already control rarely needs an orchestrator. What it needs is a repeatable release: build a version, start it safely, verify it, and keep a way back.
When you do not need an orchestrator
Kubernetes pays for itself when you need scheduling across many machines, self-healing replicas, and a shared control plane. A single VPS or a handful of servers running a few Go binaries does not have those problems, and adopting an orchestrator adds a second system to operate.
What those services do need is the part Kubernetes is often adopted for: numbered releases, a health gate before traffic moves, and a rollback that does not depend on remembering which binary was live.
What a single-host release actually needs
Four things cover most single-server deployments: a build artifact tied to a version, a strategy that moves traffic only after the new process is healthy, supervision of the running process, and a retained previous version.
Phelix provides those as CLI commands. It builds Go natively with the host toolchain, supervises the process, and routes traffic through a host-local proxy so a blue-green or rolling cutover never drops the listener.
- Versioned build with a build report and encrypted environment snapshot
- Health-gated blue-green, rolling, canary, or progressive deploy
- One-command rollback to a retained version
- Optional dashboard; local commands work without an account
What you give up, and when that matters
Phelix is not an orchestrator. It does not schedule work across a fleet, run a cluster control plane, or manage databases and Compose stacks. Monitoring is per agent, not coordinated cross-host orchestration.
If you need multi-node scheduling, autoscaling, or a service mesh, use Kubernetes or a platform built for it. If you need safe releases for Go services on machines you own, the orchestrator is usually more than the problem requires.
Frequently asked questions
Short answers; the docs go deeper.
Can I deploy Go to a VPS without Kubernetes?
Yes. A native Go binary, a process supervisor, a reverse proxy, and a versioned rollback path cover most single-server deployments. Phelix provides all four from one CLI.
Is a Kubernetes alternative for Go always simpler?
It is simpler when you run a few services on servers you control. If you need multi-node scheduling, autoscaling, or a service mesh, an orchestrator is the right tool and Phelix is not a replacement.
One binary between git push and production.
Install the CLI, verify the host, and follow the quick start to build your first application.