Skip to content

Guides

Go and Rust deployment guides

Zero-downtime deployment, blue-green and rolling releases, health checks, rollback, and when to skip Kubernetes or Docker. Each guide covers one task, end to end.

Deploy without an orchestrator

Guide

Deploy Go without Kubernetes

How to deploy a Go service to your own server without Kubernetes: versioned builds, health-gated cutover, and rollback from one CLI, on infrastructure you control.

Zero-downtime deployment

Guide

Blue-green deployment for Go

How blue-green deployment works for a Go service: run the new version beside the old one, health-check it, switch traffic atomically, then drain the old instance.Guide

Rolling deployment for Go

Rolling deployment for Go services: replace replicas one at a time behind a proxy, health-check each replacement, and drain the old instance before moving on.Guide

Zero-downtime deployment for Rust

Deploy a Rust service with zero downtime: build the release binary on the host, health-gate the cutover, and roll back to a retained version in one command.

Health checks and rollback

Guide

Health checks for a Go service

Health checks for Go apps: an explicit readiness endpoint, tiered fallbacks, check intervals and retries, and how health gates decide when traffic moves.Guide

How to roll back a Go deployment

Roll back a Go deployment safely: versioned binaries, the rollback command and picker, dry-run previews, retention rules, and the paired environment snapshot.

Containers vs binaries

Guide

Docker vs binary deployment

Docker vs deploying a compiled binary: what each adds to a Go or Rust release, the operational cost of a container layer, and when either is the right unit.

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