Comparison
atmos vs docker-airflow
Verdict
Pick atmos if atmos is a Terraform orchestration tool for DevOps written in Go. It supports hierarchical imports and inheritance to keep environment configuration DRY; pick docker-airflow if docker-airflow leverages Docker to provide streamlined management of Apache Airflow environments, making it easy for developers to maintain and deploy workflows.
Markdown twin · atmos alternatives · docker-airflow alternatives
GraphCanon updated Sep 16, 2026
10views this month
vs
Trust & integrity
| Signal | atmos | docker-airflow |
|---|---|---|
| Maintenance | Very active (0d since push) As of Aug 11, 2026 · github_public_v1 | Dormant (1294d since push) As of Sep 16, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Aug 11, 2026 · github_public_v1 | Not a fork · Personal account As of Sep 16, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- atmos
- Terraform Orchestration Tool for DevOps using Go
- docker-airflow
- Docker Apache Airflow
Stars
- atmos
- 1.4k
- docker-airflow
- 3.8k
Forks
- atmos
- 174
- docker-airflow
- 591
Open issues
- atmos
- 304
- docker-airflow
- 261
Language
- atmos
- Go
- docker-airflow
- Shell
Adopt for
- atmos
- Atmos is a Terraform orchestration tool for DevOps written in Go. It supports hierarchical imports and inheritance to keep environment configuration DRY.
- docker-airflow
- docker-airflow leverages Docker to provide streamlined management of Apache Airflow environments, making it easy for developers to maintain and deploy workflows.
Persona
- atmos
- -
- docker-airflow
- -
Runtime
- atmos
- -
- docker-airflow
- -
License
- atmos
- Apache-2.0
- docker-airflow
- Apache-2.0
Last pushed
- atmos
- Aug 11, 2026
- docker-airflow
- Mar 1, 2023
Categories
- atmos
- Developer Tools
- docker-airflow
- Developer Tools
Trust and health
Maintenance
- atmos
- Very active (96%)
- docker-airflow
- Dormant (18%)
Days since push
- atmos
- 0d
- docker-airflow
- 1294d
Open issues (now)
- atmos
- 304
- docker-airflow
- 261
Stars delta
- atmos
- Unknown
- docker-airflow
- -1 (30d)
Open issues delta
- atmos
- Unknown
- docker-airflow
- 0 (30d)
Owner type
- atmos
- Organization
- docker-airflow
- User
Full report
- atmos
- Trust report
- docker-airflow
- Trust report
Choose atmos if…
- atmos is primarily Go; docker-airflow is Shell.
- Tags unique to atmos: automation, cli, cloud, devops.
- When you need a tool that supports both Terraform and Helmfile natively, allowing for streamlined management of infrastructure as code with rich inheritance capabilities.
When NOT to use atmos
- Avoid using Atmos if you are looking for a solution that supports a wider range of infrastructure definition languages beyond Terraform and Helmfile.
- Not suitable for those who require extensive UI features, as it primarily focuses on CLI operations and automated DRY configurations.
Choose docker-airflow if…
- docker-airflow is primarily Shell; atmos is Go.
- Pricing: Open source under the Apache-2.0 license, it is free of cost, but support and enterprise features might come at a premium..
- Requirements: Requires Docker.
- Tags unique to docker-airflow: airflow, docker.
- Opt for docker-airflow if you are already using Docker in your workflow setup, because it seamlessly integrates with existing infrastructure without needing additional configuration steps.
When NOT to use docker-airflow
- Avoid docker-airflow if you require a completely customized setup for your workflow management system and have limited experience or resources to understand and manage Docker configurations.
- Should be avoided in environments where there is no need for containerization benefits as using docker-airflow may introduce unneeded complexity.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (cloudposse/atmos) · observed Aug 11, 2026
- GitHub forks (cloudposse/atmos) · observed Aug 11, 2026
- Last push (cloudposse/atmos) · observed Aug 11, 2026
- License file (Apache-2.0) · observed Aug 11, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- GitHub stars (puckel/docker-airflow) · observed Sep 16, 2026
- GitHub forks (puckel/docker-airflow) · observed Sep 16, 2026
- Last push (puckel/docker-airflow) · observed Mar 1, 2023
- License file (Apache-2.0) · observed Sep 16, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: atmos 1.4k · docker-airflow 3.8k (synced Aug 11, 2026).
Common questions
- What is the difference between atmos and docker-airflow?
- atmos: Terraform Orchestration Tool for DevOps using Go. docker-airflow: Docker Apache Airflow. See the comparison table for live GitHub stats and shared categories.
- When should I choose atmos over docker-airflow?
- Choose atmos over docker-airflow when atmos is primarily Go; docker-airflow is Shell; Tags unique to atmos: automation, cli, cloud, devops; When you need a tool that supports both Terraform and Helmfile natively, allowing for streamlined management of infrastructure as code with rich inheritance capabilities.
- When should I choose docker-airflow over atmos?
- Choose docker-airflow over atmos when docker-airflow is primarily Shell; atmos is Go; Pricing: Open source under the Apache-2.0 license, it is free of cost, but support and enterprise features might come at a premium.; Requirements: Requires Docker; Tags unique to docker-airflow: airflow, docker; Opt for docker-airflow if you are already using Docker in your workflow setup, because it seamlessly integrates with existing infrastructure without needing additional configuration steps.
- When should I avoid atmos?
- Avoid using Atmos if you are looking for a solution that supports a wider range of infrastructure definition languages beyond Terraform and Helmfile. Not suitable for those who require extensive UI features, as it primarily focuses on CLI operations and automated DRY configurations.
- When should I avoid docker-airflow?
- Avoid docker-airflow if you require a completely customized setup for your workflow management system and have limited experience or resources to understand and manage Docker configurations. Should be avoided in environments where there is no need for containerization benefits as using docker-airflow may introduce unneeded complexity.
- Is atmos or docker-airflow more popular on GitHub?
- docker-airflow has more GitHub stars (3,810 vs 1,352). Stars measure visibility, not whether either tool fits your constraints.
- Are atmos and docker-airflow open source?
- Yes - both are open-source projects on GitHub (atmos: Apache-2.0, docker-airflow: Apache-2.0).
- Where can I find alternatives to atmos or docker-airflow?
- GraphCanon lists graph-backed alternatives at atmos alternatives and docker-airflow alternatives (atmos markdown twin, docker-airflow markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, atmos or docker-airflow?
- atmos: Very active. docker-airflow: Dormant. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for atmos and docker-airflow?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: atmos trust report; docker-airflow trust report.