Deploy with
confidence.
Your IaC provisions infrastructure. Your manifests deploy apps. Admiral maintains the dependency graph across both so config flows automatically, environments stay consistent, and every deployment is a snapshot you can roll back.
Your tools don't talk to each other
IaC is good at provisioning infrastructure. Deployment tooling like Helm and Kustomize are good at getting applications running. They're different concerns for good reason, and pushing one to do the other's job rarely ends well. But one produces outputs the other needs as inputs, and so teams end up building the glue themselves.
Use IaC to manage workloads and you hit state conflicts the moment a CI pipeline bumps an image tag. Use deployment tooling for infrastructure and you lose the guarantees IaC provides. Either way, something has to give.
Then there's environments. Dev, staging, and production share most of the same configuration, but tooling generally treats them as entirely separate: separate manifests, separate values files, separate state. Standing up a new environment means duplicating most of it and keeping it all in sync by hand.
How Admiral solves it
Admiral sits between your IaC and your deployment tooling, maintains the dependency graph across both, and gives you an application-centric model that reduces environment duplication.
Infra ↔ Workload Glue
Admiral lets your workloads reference IaC outputs directly. When infrastructure changes, Admiral knows which workloads depend on it and pulls in the updated values.
Application-Centric
Organized around applications and environments. Define your app once, layer environment-specific config on top, and stop duplicating manifests across dev, staging, and production.
OpenAPI Spec
A fully documented OpenAPI spec with the ability to generate clients in any language. Integrate Admiral into your existing toolchain with ease.
Works With Your Toolchain
A CLI for scripting and CI/CD, a GitHub Action for deploy-on-merge workflows, a Terraform provider for managing Admiral as code. Integrate however your team already works.
GitOps Without the Git
Declarative desired state, immutable versioned snapshots, pull-based agents, continuous reconciliation. The same principles as GitOps, stored in a control plane designed for it instead of a Git repo.
No Lock-In
Admiral orchestrates your tools but doesn't replace them. Your Helm charts, Terraform modules, and manifests stay in standard formats that work without Admiral.
How it works
Define
Your application, its environments, and its configuration. Define once, layer environment-specific values on top.
Connect
IaC outputs to the workloads that depend on them. Admiral maintains the dependency graph so nothing gets lost between provisioning and deployment.
Deploy
To any environment. Every deployment produces a versioned, immutable snapshot you can roll back to at any time.
$ admiral app create billing-api
✓ Application created
$ admiral env create production --app billing-api --cluster us-east-1
✓ Environment created and linked to cluster
$ admiral var set IMAGE_TAG=a3f7c21 --app billing-api --env production
✓ Variable set
$ admiral deploy billing-api --env production
✓ Revision r-28f3a deployed to us-east-1Take command of your fleet.
Admiral is open source, transparent, and portable. No lock-in, no sales calls. Start deploying in minutes.