Vastora

Current route lifecycle: startup-only readiness. This supersedes the historical periodic-health lease behavior described below.

Vastora is a self-hosted desired-state control plane for applications across multiple Sites and Nodes. The Center stores intent and orchestration state; one Agent binary is the only node-side executor for Docker workloads, verified native probes, and an optional local Caddy Gateway. Existing applications and applied routes continue when the Center is unavailable.

Pre-alpha. The repository is intentionally published only with working, tested building blocks. Do not use it to manage production workloads yet.

What is implemented now

• A Go vastora CLI with a Center HTTP API, one-time Agent enrollment, authenticated Agent heartbeats and Agent-local encrypted credentials.
• Schema 4 catalog consumption from the pinned independent petauron/catalog module, with generic Docker/systemd execution contracts. Catalog signing/publishing tools belong to that repository, not the Vastora CLI. Production cutover remains…