Self-Host

Production Checklist

Everything to check before a self-hosted Rivet cluster serves production traffic.

Control plane

Three or more instances, each on its own machine, all on the same pinned version.
A bucket configured in object_storage.primary, with versioning turned on. Never the in-memory default or file_system. See Storage.
One persistent block-storage disk per instance, mounted at depot.log_directory, at least 100 GiB, never shared.
api_peer.advertise_address set to each instance’s private IP and port.
Port 6421 reachable only between instances. It is plaintext and unauthenticated. See Ports & TLS.
A load balancer on port 6420 with TLS and a one hour idle timeout.
The Rivet token in a secret, not in a committed file or image.
Prometheus scraping port 6430 on every instance.
A tested restore. See Backup & restore.