Repolode
Submit
cloudposse

cloudposse/atmos

Open-source runtime for orchestrating Terraform, OpenTofu, Helmfile and containers with shared config, auth and CI workflows.

Open-source alternative to:Terragrunt

View on GitHubWebsite
Stars
1,413
Forks
195
Open issues
299
Last commit
7 hours ago

What is it?

Atmos is an open-source runtime for infrastructure that builds, authenticates and runs Terraform, OpenTofu, Kubernetes, Helm and containers with the same commands on a laptop, in CI, or through AI agents. Environments are modeled as stacks and components, so every region or stage can reuse the same root modules through hierarchical imports and inheritance instead of copy-pasted configuration.

Beyond running IaC tools, Atmos bundles features that otherwise require separate tools: multi-cloud authentication (AWS, Azure, GCP), secrets sourced from backends such as 1Password, SSM, Vault and SOPS, dependency vendoring, a build cache, and automatic installation of pinned Terraform, OpenTofu and Helmfile versions. It also detects which components changed in git so CI only plans or applies affected parts.

Atmos supports custom workflows and commands, lifecycle hooks, OPA and JSON Schema validation, and an MCP server with agent skills for tools such as Claude Code and Cursor. It is written in Go and licensed under Apache-2.0.

Key features

  • 01Hierarchical stack configuration with imports and inheritance for DRY environments.
  • 02Unified authentication across AWS, Azure and GCP, including SSO and OIDC.
  • 03Secrets sourced from 10+ backends and masked in output.
  • 04Automatic installation of pinned Terraform, OpenTofu and Helmfile versions.
  • 05Git-aware detection of changed components for CI plan and apply.
  • 06Custom workflows, commands and lifecycle hooks.

Use cases

  • Managing many cloud accounts and regions with one shared set of root modules.
  • Running the same Terraform and Helmfile deployments locally and in CI pipelines.
  • Enforcing compliance policies with OPA or JSON Schema validation across environments.
  • Letting AI agents operate infrastructure through the MCP server and agent skills.

Things to know

  • Anonymous telemetry is collected by default and must be opted out of in atmos.yaml or via an environment variable.

In collections

CLI & terminal tools

Topics

#terraform#infrastructure-as-code#devops#orchestration#helm#opentofu#gitops#cli#automation#cloud

FAQ

What is atmos?
Open-source runtime for orchestrating Terraform, OpenTofu, Helmfile and containers with shared config, auth and CI workflows. Atmos is an open-source runtime for infrastructure that builds, authenticates and runs Terraform, OpenTofu, Kubernetes, Helm and containers with the same commands on a laptop, in CI, or through AI agents. Environments are modeled as stacks and components, so every region or stage can reuse the same root modules through hierarchical imports and inheritance instead of copy-pasted configuration.
Is atmos free to use? What license does it have?
atmos is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is atmos still maintained?
Actively maintained. The last commit to atmos was on Nov 6, 2026.
What can I use atmos for?
Managing many cloud accounts and regions with one shared set of root modules. Running the same Terraform and Helmfile deployments locally and in CI pipelines. Enforcing compliance policies with OPA or JSON Schema validation across environments. Letting AI agents operate infrastructure through the MCP server and agent skills.
Where can I get atmos?
The source code and installation instructions are on GitHub: https://github.com/cloudposse/atmos

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects