cloudposse/atmos
Atmos is the open-source runtime for infrastructure — it builds, authenticates, and ships Terraform, OpenTofu, Kubernetes, Helm, and containers the same way on your laptop, in CI, and with AI agents. observed · 2026-08-28
Health v2 · maintenance only
95/100
- Activity 99
- Release rhythm 87
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 2.0
- age_days: 2191
- days_rel: 7
- days_push: 7
- n_releases_24m: 171
Adoption not part of the score
1362 stars · 173 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Atmos is an open-source CLI runtime for infrastructure that orchestrates Terraform, OpenTofu, Kubernetes, Helm, and containers through declarative YAML stack configuration, with built-in auth, secrets, vendoring, toolchain management, and CI support. It also exposes itself to AI agents via an MCP server and portable Agent Skills, letting assistants like Claude Code or Cursor operate infrastructure directly.
Use cases
- manage terraform environments without copy-pasting code
- configure terraform components with yaml stacks
- run the same infrastructure commands locally and in ci
- manage cli tool versions for terraform and kubectl
- let ai agents operate terraform infrastructure via mcp
- dry multi-environment infrastructure configuration
- authenticate once for aws gcp and azure infrastructure workflows
When to choose
- you manage many terraform environments and want DRY, inheritable configuration instead of duplicated root modules
- you want one tool to handle auth, secrets, tool versions, vendoring, and CI for Terraform/Helm/Kubernetes workflows
- your team wants AI agents (Claude Code, Cursor, Copilot) to safely drive infrastructure through MCP and agent skills
- you want consistent infrastructure commands across laptops, CI pipelines, and agent harnesses
When to avoid
- you have a single small Terraform project where plain Terraform and a few scripts suffice
- you are not using Terraform/OpenTofu, Helm, or Kubernetes and don't need infrastructure orchestration
- you prefer bespoke wrapper scripts or tools like Terragrunt and don't want to learn Atmos's stacks/components model
- you need a GUI or fully managed SaaS rather than a CLI-driven workflow
Facets
cli-tool · maturity active
infrastructure-as-code configuration-management deployment cli developer-tools workflow-automation secrets-management ci-cd mcp scheduling infrastructure-as-code cloud-computing developer-tools self-hosted cli windows go cross-platform terraform opentofu helm kubernetes helmfile stacks iac-orchestration ai-agents agent-skills toolchain-management cloudposse devops automation macos linux docker
10 sources
- readme: https://github.com/cloudposse/atmos · fetched 2026-08-28 · 97f9e223ae11
- homepage: https://atmos.tools · fetched 2026-08-29 · 28eddd6278e3
- site_page: https://atmos.tools/install · fetched 2026-08-29 · ebdd24c513e1
- site_page: https://atmos.tools/changelog · fetched 2026-08-29 · 8b800588558a
- site_page: https://atmos.tools/intro · fetched 2026-08-29 · 5d2c6bc49fe4
- site_page: https://atmos.tools/ai/skills · fetched 2026-08-29 · 37140e410999
- site_page: https://atmos.tools/cli/configuration/toolchain · fetched 2026-08-29 · 1c02fe45a93b
- site_page: https://atmos.tools/cli/configuration/version/managed-versions · fetched 2026-08-29 · 81fee1ff31e4
- site_page: https://atmos.tools/ai · fetched 2026-08-29 · 591f6cd9ba7b
- site_page: https://atmos.tools/ai/mcp-server · fetched 2026-08-29 · f30f7516a32c
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| cloudposse/atmos | main | 95 |
For agents
markdown · JSON · MCP: product_card(name="cloudposse/atmos")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem