Overview
What Admiral is and where to start
Admiral is a control plane for coordinating infrastructure and application delivery across environments. It gives platform teams one place to define what should exist - infrastructure and workloads alike - and a pull-based execution fleet that makes it real wherever your workloads live.
Status: These docs are in active development. The concept model is settled; setup and reference sections are being expanded.
What Admiral does
- Unifies infrastructure and application delivery. Terraform-managed infrastructure and Kubernetes workloads move through the same model: define, review, deploy.
- Keeps every change reviewable. You never edit live state directly. Changes are staged in changesets, planned, and applied as one reviewable unit, with history captured as immutable revisions.
- Coordinates without reaching in. Agents run next to your workloads and pull their own work. Admiral never needs inbound access to your clouds or clusters.
- Composes systems from components. Components declare dependencies and pass outputs to each other, so a deployment unfolds in the right order with data flowing downstream automatically.
Start here
Concepts Overview
The mental model: resources, ownership, and the deploy flow
Architecture
The deployment topology - control plane and execution fleet
Get Started
Connect a cluster and run your first deploy
CLI Reference
The admiral command-line interface
How the docs are organized
- Concepts - the resource model and how a change becomes a deployment. Read this first.
- Setup - getting started and connecting your first cluster.
- Guides - the agent lifecycle and the authentication model.
- Tools & SDKs - the CLI, Terraform provider, and Go SDK.
- API Reference - the REST API contract.