Releasing soon Vigo is in alpha and closing in on its first stable release. Expect breaking changes between releases until then — we're looking for testing partners with meaningful fleets across diverse architectures. Learn more →

How-to guides

Each page walks one operator task end-to-end. Pick the closest match to what you're trying to do.

Where to start

Your reading order depends on how much of the fleet is already standing up:

When What you'll do Pages
Day 1 — first time Stand up the server, enroll a single envoy, write and apply your first configcrate. Install → Enroll an envoy → Write your first configcrate → Publish your config
Day 7 — basic ops Auth, monitoring, remote access. The fleet now has more than one operator and more than a handful of envoys. Set up auth → Set up Scrier → Set up monitoring
Day 30 — production Compliance reporting, backups, host hardening, the swarm content subsystems. The fleet is doing real work for real stakeholders. Compliance reporting → Back up and recover → Harden envoy secret memory → Set up Swarm → Set up Puddle → Set up Lockbox → Set up Gitback
Day 90 — scale and DR Sizing the server host, spanner federation, disaster recovery, artifact distribution, network devices, custom subsystems. Size a vigosrv host → Set up Spanner → Disaster recovery → Set up Curator → Set up Longdrawer → Set up network devices

The migration guides at the bottom are for coming from another config-management system — read them once when you start, not in the daily flow.

Migrating from another CM

Guide
Migrate from Ansible
Migrate from Puppet
Migrate from Chef
Migrate from Salt
Migrate from CFEngine

When something goes wrong

Troubleshoot common issues is symptom-keyed — search the page for the exact error string an envoy or session is producing and jump to its fix.


Verified on Vigo 0.51.6 · 2026-05-13.

Confidential — Alexander4, LLC. Not for redistribution. See ../legal/license.md.