Admiral is a control plane for coordinating infrastructure and application delivery across environments.
Your infrastructure as code provisions the infrastructure and your manifests deploy the applications, and the wiring between the two is usually done by hand. Admiral holds the dependency graph across both. An output flows to the input that needs it, each component's change is planned and reviewed before it applies, and an environment is promoted rather than rebuilt.
Admiral orchestrates Terraform or OpenTofu, Helm and Kubernetes manifests without replacing them. The control plane is hosted. What runs in your accounts and clusters is a self-hosted agent that connects out to Admiral, so there is no inbound networking to set up.
Admiral is in active development. See the documentation for where it stands.
| Repository | What it is |
|---|---|
| admiral-cli | The admiral command-line interface |
| terraform-provider-admiral | Manage Admiral resources with Terraform |
| admiral-helm | Helm charts, including the Kubernetes agent |
| admiral-sdk-go | Go client library for the Admiral API |
| admiral-sdk-ts | TypeScript client library for the Admiral API |
| admiral-openapi | OpenAPI specifications for the Admiral API |
| admiral-bundle | The packaging format behind the component registry |
Install the CLI with brew install admiral-io/tap/admiral or from the
Scoop bucket on Windows.
Every public repository is licensed under Apache-2.0.
- Bugs, feature requests, questions: admiral-community
- Security vulnerabilities: email security@admiral.io, never a public issue
- Contributing: read the contributing guide
Follow along on LinkedIn.