Discover
See app health, services, endpoints, allocations, secrets status, and operational events in one control plane.
One application definition. A visible path from preflight to service readiness. Self-hosted or Fleet, with explicit recovery when changes go wrong.
Norn connects an infraspec.yaml to application discovery, source and build, health checks, secrets, deployment progress, and recovery. The API, CLI, and dashboard let you inspect what is serving and what a change actually did. Nomad schedules the workloads, Consul tracks discovery and health, and ingress routes requests to application allocations.
Start with why Norn, define an application, or follow the operator workflow.
Choose self-hosted for a lighter single-host experience with local runtime integration. Choose Fleet for multiple nodes, separate management and controller-driven platform operations. They share application/control concepts and have distinct deployment and recovery procedures.
DigitalOcean is the current provider adapter, not the product boundary. The architecture separates provider effects; other adapters are future work. See capability status for the difference between implemented behavior and live-qualified operations.
The first Fleet milestone proved a controller-managed online Norn upgrade while an existing workload continued responding. The architecture explains the design; release evidence records that qualification and its limits. Version tags and signed deployment artifacts have separate identities.
V2 documentation and V1 documentation remain available. Current source lives under v2/; that path and /api/v1 identify code layout and an API contract, not the product version.