install

Additional install commands

macOS

Homebrewverified · 100%

brew install atmos

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#atmos

nixpkgs package indexes · pkgs/by-name/at/atmos/package.nix · source: api.github.com

Windows

Scoopverified · 92%

scoop install main/atmos

Scoop official bucket manifest trees · bucket/atmos.json · source: api.github.com

overview

Package summary

Universal Tool for DevOps and Cloud Automation

Project links

Commands and aliases

atmos

history

Project history and usage

Atmos is Cloud Posse's open-source framework and CLI for orchestrating infrastructure workflows across Terraform, OpenTofu, Helmfile, Ansible, Packer, Devcontainers, and related DevOps tooling. Its main idea is to separate reusable components from YAML stack configuration so large cloud architectures can be driven through consistent CLI commands.

Project history

The official README describes Atmos as a framework for orchestrating and operating infrastructure workflows across multiple cloud and DevOps toolchains. It emphasizes reusable components implemented as Terraform root modules, stack configurations in YAML, DRY configuration, vendoring, custom commands, GitOps capabilities, and policy controls.

The README also identifies Cloud Posse as a heavy internal user for automating cloud infrastructure with Terraform and Kubernetes, while saying the tool can automate any complex workflow. The generated README's copyright span covers 2017-2026, fitting Cloud Posse's long-running open-source infrastructure ecosystem.

Adoption history

Atmos is distributed as a Homebrew formula and appears in Nix and Scoop in the input, which matches its cross-platform CLI positioning. The official website calls it free and open source and promotes installation, examples, CLI reference, and community support through Cloud Posse's SweetOps Slack and office hours.

The project has a fast-moving release line: official Git tags include early 0.x releases and later v1.x releases reaching v1.99.0. That matters to package maintainers because Atmos is both a CLI and an opinionated framework; changes in config discovery, stack behavior, and integrations can affect whole infrastructure repositories.

How it is used

Atmos users define components, stacks, workflows, and custom commands, then run atmos commands locally or in CI/CD to describe, plan, apply, vendor, validate, and orchestrate infrastructure. The README highlights Terraform-native orchestration, backend and varfile generation, stack configuration, component libraries, vendoring, and workflow orchestration.

The CLI configuration docs define atmos.yaml as the main config file. Atmos searches the current directory, Git repository root, parent directories, the home directory, and system directories, and can merge multiple config files plus .atmos.d fragments. On Windows, docs recommend forward slashes in atmos.yaml paths.

Why package nerds care

Atmos is package-nerd catnip because it is a CLI that encodes an entire infrastructure repo layout philosophy. Installing it is not just getting another terraform wrapper; it brings Cloud Posse's conventions for stacks, components, vendoring, custom commands, and GitOps into a portable binary.

Its config discovery order is especially important for packagers and shell users because the same atmos binary behaves differently depending on current directory, repo root, home config, and system config.

Timeline

2017-2026: The generated official README carries Cloud Posse copyright across this span.
0.x: Official Git tags include early 0.0.2 and 0.1.0 releases.
1.x: Official Git tags show an active v1 release line reaching v1.99.0.
Current: Official docs describe Terraform, OpenTofu, Helmfile, Ansible, Packer, and Devcontainers use cases.

Related projects

Terraform and OpenTofu are primary IaC engines Atmos orchestrates.
Helmfile, Ansible, Packer, Devcontainers, and Kubernetes are documented toolchain targets.
Cloud Posse's Terraform modules, SweetOps community, and terraform-provider-utils are closely related ecosystem pieces.

Sources

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for atmos. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Build metadata lists 2 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: ./atmos.yamlrepo-root/atmos.yamlparent directories: atmos.yaml~/.atmos/atmos.yaml/usr/local/etc/atmos/atmos.yaml
Windows: ./atmos.yamlrepo-root/atmos.yamlparent directories: atmos.yaml%LOCALAPPDATA%/atmos/atmos.yaml

executables

Installed executables

Command	Kind	Exposure	Note
`atmos`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-26

manager version1.224.0

manager updated2026-07-23

local dataok

upstreamcurrent

latest detectedv1.224.0

https://github.com/cloudposse/atmos

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:atmos
Version	1.224.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/atmos
Homepage	https://atmos.tools
Repository	https://github.com/cloudposse/atmos
Upstream docs	https://atmos.tools/
License	Apache-2.0
Source archive	https://github.com/cloudposse/atmos/archive/refs/tags/v1.224.0.tar.gz
Last updated	2026-07-23T21:30:15Z
Pulse	updated
Build dependencies	go, pkgconf
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	atmos
Version Scheme	0
Revision	0
Head Version	HEAD
Conflicts With	tenv
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

atmos

nix profile install nixpkgs#atmos

normalized package name match
Matched by: Atmos

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/at/atmos/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Scoop95%

main/atmos

scoop install main/atmos

normalized package name match
Matched by: Atmos

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/atmos.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/atmos.yml

Used sources

Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install atmos with Homebrew, Nix, scoop