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.
$ admiral app create billing-api
✓ Application created
$ admiral env create production --app billing-api
✓ Environment created
$ admiral changeset create --app billing-api --env production --title "Deploy a3f7c21"
✓ Change set cs-1 created
$ admiral changeset var set --changeset cs-1 IMAGE_TAG a3f7c21
✓ Variable staged
$ admiral changeset plan cs-1
✓ Run r-28f3a planned
$ admiral changeset apply cs-1
✓ Run r-28f3a applied to productionInfrastructure and applications were never built to talk
IaC stands up infrastructure. Helm and Kustomize ship apps. The handoff between them is glue you build and maintain by hand.
Glue you maintain by hand
IaC produces the outputs your deploys need as inputs, so every team rebuilds the same brittle plumbing.
State conflicts on every release
Stretch one tool into the other's job and a CI image-tag bump starts fighting your state.
Environments drift apart
Dev, staging, and prod share most config, but separate manifests and state mean syncing them 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.
Autonomy for app teams. Control for platform teams.
One workflow that gives developers self-service without taking the guardrails away from platform.
Ship without filing a ticket
- Create apps and environments and deploy changes yourself.
- Own your whole stack, from database to deployment, within safe boundaries.
- Roll back to any prior revision in a single command.
Keep the guardrails on
- Every change is a reviewable changeset, never a direct edit to live state.
- One dependency graph across every app, environment, and cluster.
- Agents pull their own work, and Admiral never holds standing access to your clusters.
Take command of your fleet.
Admiral is transparent and portable: no lock-in, no sales calls. Join the waitlist and be first to deploy.