Comparison
atmos vs terraform-provider-oci
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 terraform-provider-oci if terraform-provider-oci is a Terraform provider for Oracle Cloud Infrastructure, allowing seamless integration with OCI resources.
Markdown twin · atmos alternatives · terraform-provider-oci alternatives
GraphCanon updated Aug 11, 2026
15views this month
vs
Trust & integrity
| Signal | atmos | terraform-provider-oci |
|---|---|---|
| Maintenance | Very active (0d since push) As of Aug 11, 2026 · github_public_v1 | Very active (5d since push) As of Aug 11, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Aug 11, 2026 · github_public_v1 | Not a fork · Organization account As of Aug 11, 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
- terraform-provider-oci
- Terraform Oracle Cloud Infrastructure provider
Stars
- atmos
- 1.4k
- terraform-provider-oci
- 867
Forks
- atmos
- 174
- terraform-provider-oci
- 753
Open issues
- atmos
- 304
- terraform-provider-oci
- 514
Language
- atmos
- Go
- terraform-provider-oci
- Go
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.
- terraform-provider-oci
- terraform-provider-oci is a Terraform provider for Oracle Cloud Infrastructure, allowing seamless integration with OCI resources.
Persona
- atmos
- -
- terraform-provider-oci
- -
Runtime
- atmos
- -
- terraform-provider-oci
- -
License
- atmos
- Apache-2.0
- terraform-provider-oci
- MPL-2.0
Last pushed
- atmos
- Aug 11, 2026
- terraform-provider-oci
- Aug 5, 2026
Categories
- atmos
- Developer Tools
- terraform-provider-oci
- Developer Tools
Trust and health
Days since push
- atmos
- 0d
- terraform-provider-oci
- 5d
Open issues (now)
- atmos
- 304
- terraform-provider-oci
- 514
Full report
- atmos
- Trust report
- terraform-provider-oci
- Trust report
Choose atmos if…
- License: atmos is Apache-2.0, terraform-provider-oci is MPL-2.0.
- Tags unique to atmos: automation, cli, cloud, devops.
- atmos ships Docker support for self-hosted deployment.
- 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 terraform-provider-oci if…
- License: terraform-provider-oci is MPL-2.0, atmos is Apache-2.0.
- Tags unique to terraform-provider-oci: bare-metal, iaas, oci, oracle.
- When deploying infrastructure on Oracle Cloud Infrastructure and preferring to use Terraform configuration files
When NOT to use terraform-provider-oci
- If your project primarily focuses on non-Oracle cloud environments where compatibility or efficiency with other providers may be superior
- When detailed management of OCI's Bare Metal instances is not a priority, as the value proposition of terraform-provider-oci diminishes without leveraging these features
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 (oracle/terraform-provider-oci) · observed Aug 11, 2026
- GitHub forks (oracle/terraform-provider-oci) · observed Aug 11, 2026
- Last push (oracle/terraform-provider-oci) · observed Aug 5, 2026
- License file (MPL-2.0) · observed Aug 11, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: atmos 1.4k · terraform-provider-oci 867 (synced Aug 11, 2026).
Common questions
- What is the difference between atmos and terraform-provider-oci?
- atmos: Terraform Orchestration Tool for DevOps using Go. terraform-provider-oci: Terraform Oracle Cloud Infrastructure provider. See the comparison table for live GitHub stats and shared categories.
- When should I choose atmos over terraform-provider-oci?
- Choose atmos over terraform-provider-oci when License: atmos is Apache-2.0, terraform-provider-oci is MPL-2.0; Tags unique to atmos: automation, cli, cloud, devops; atmos ships Docker support for self-hosted deployment; 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 terraform-provider-oci over atmos?
- Choose terraform-provider-oci over atmos when License: terraform-provider-oci is MPL-2.0, atmos is Apache-2.0; Tags unique to terraform-provider-oci: bare-metal, iaas, oci, oracle; When deploying infrastructure on Oracle Cloud Infrastructure and preferring to use Terraform configuration files.
- 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 terraform-provider-oci?
- If your project primarily focuses on non-Oracle cloud environments where compatibility or efficiency with other providers may be superior When detailed management of OCI's Bare Metal instances is not a priority, as the value proposition of terraform-provider-oci diminishes without leveraging these features
- Is atmos or terraform-provider-oci more popular on GitHub?
- atmos has more GitHub stars (1,352 vs 867). Stars measure visibility, not whether either tool fits your constraints.
- Are atmos and terraform-provider-oci open source?
- Yes - both are open-source projects on GitHub (atmos: Apache-2.0, terraform-provider-oci: MPL-2.0).
- Where can I find alternatives to atmos or terraform-provider-oci?
- GraphCanon lists graph-backed alternatives at atmos alternatives and terraform-provider-oci alternatives (atmos markdown twin, terraform-provider-oci 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 terraform-provider-oci?
- atmos: Very active. terraform-provider-oci: Very active. 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 terraform-provider-oci?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: atmos trust report; terraform-provider-oci trust report.