---
title: "Admiral"
canonical: "https://admiral.io/"
description: "One control plane for infrastructure and application delivery. Terraform and Helm run together, applied by a self-hosted agent in your account."
---

# Admiral

One control plane for infrastructure and application delivery. Terraform and Helm run together, applied by a self-hosted agent in your account.

## Deploy infrastructure and apps together

Terraform provisions your infrastructure. Helm ships your apps. Admiral is the control plane for both. A self-hosted agent in your account applies the change.

- [Join the waitlist](https://admiral.io/waitlist.md)
- [Read the docs](https://admiral.io/docs.md)

## Why it exists

Terraform plans and applies. A reconciler watches a branch. The seam between them is yours to own, and it tears in the same three places every time.

- **Two places to review one change.** The Terraform plan lands in one pull request and the chart bump in another. Nothing shows you the combined effect before it reaches an environment.
- **One runner, every team's permissions.** A shared Terraform runner needs the union of what every team provisions. Isolating it means splitting repositories, so most teams live with the union.
- **Commits invented to trigger a deploy.** A reconciler watches a branch, so shipping means editing a file to make it notice. The commit records that a line changed, not that anyone decided to change production.

The reasoning behind each is on [Why Admiral](https://admiral.io/why-admiral.md).

## How it works

Define what should run, stage the change, then approve the plan. Nothing ships before that approval.

1. **Define** your applications, environments, and the components in each. Every environment carries its own values, so dev and prod share a definition without sharing config.
2. **Stage** a changeset holding the Terraform change and the release that depends on it. Nothing has touched the environment yet.
3. **Plan, then approve.** Admiral plans what it can resolve and shows you the effects. You approve once, and the run applies the graph in dependency order, recording a revision per component.

## Who it is for

App teams ship their own changes. They take curated components from a catalog and add them to an environment, without knowing every detail underneath. Platform teams own that catalog and the cloud standards those components follow.

### For app teams

Ship without filing a ticket. Create applications and environments and stage your own changes. Own the whole stack, from the database to the deployment. Revert a deployment by replaying a prior revision.

### For platform teams

Curate what teams ship. Publish a catalog of components application teams add to an environment, starting with Terraform, Helm, Kubernetes manifests, and templated manifests. Those components carry the cloud standards you set. Scope the self-hosted agent and its credentials.