Home/Compare/atmos vs terraform-provider-oci

Comparison

atmos vs terraform-provider-oci

Verdict

Unverified catalog guidance: 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.

Markdown twin · atmos alternatives · terraform-provider-oci alternatives

GraphCanon updated Sep 20, 2026

atmos logo

atmos

cloudposse/atmos

★ 1.4kpushed Sep 19, 2026
vs
terraform-provider-oci logo

terraform-provider-oci

oracle/terraform-provider-oci

★ 871pushed Sep 18, 2026

Trust & integrity

Signalatmosterraform-provider-oci
Maintenance
Very active (0d since push)
As of Sep 19, 2026 · github_public_v1
Very active (1d since push)
As of Sep 20, 2026 · github_public_v1
Provenance
Not a fork · Organization account
As of Sep 19, 2026 · github_public_v1
Not a fork · Organization account
As of Sep 20, 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
871

Forks

atmos
177
terraform-provider-oci
756

Open issues

atmos
286
terraform-provider-oci
508

Language

atmos
Go
terraform-provider-oci
Go

Adopt for

atmos
Unverified catalog guidance: 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
Unverified catalog guidance: 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
Sep 19, 2026
terraform-provider-oci
Sep 18, 2026

Categories

atmos
Developer Tools
terraform-provider-oci
Developer Tools

Trust and health

Days since push

atmos
0d
terraform-provider-oci
1d

Open issues (recorded)

atmos
286
terraform-provider-oci
508

Stars delta

atmos
+27 (30d)
terraform-provider-oci
+4 (30d)

Open issues delta

atmos
-18 (30d)
terraform-provider-oci
-6 (30d)

Full 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 has Docker configuration in its repository.
  • Unverified catalog guidance: 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

  • Unverified catalog guidance: Avoid using Atmos if you are looking for a solution that supports a wider range of infrastructure definition languages beyond Terraform and Helmfile.
  • Unverified catalog guidance: 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.
  • Unverified catalog guidance: When deploying infrastructure on Oracle Cloud Infrastructure and preferring to use Terraform configuration files

When NOT to use terraform-provider-oci

  • Unverified catalog guidance: If your project primarily focuses on non-Oracle cloud environments where compatibility or efficiency with other providers may be superior
  • Unverified catalog guidance: 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 on cards: atmos 1.4k · terraform-provider-oci 871 (synced Sep 20, 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 recorded GitHub metadata and shared categories.
When should I choose atmos over terraform-provider-oci?
For atmos, compare these recorded points with terraform-provider-oci: License: atmos is Apache-2.0, terraform-provider-oci is MPL-2.0; Tags unique to atmos: automation, cli, cloud, devops; atmos has Docker configuration in its repository; Unverified catalog guidance: 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?
For terraform-provider-oci, compare these recorded points with atmos: License: terraform-provider-oci is MPL-2.0, atmos is Apache-2.0; Tags unique to terraform-provider-oci: bare-metal, iaas, oci, oracle; Unverified catalog guidance: When deploying infrastructure on Oracle Cloud Infrastructure and preferring to use Terraform configuration files.
When should I avoid atmos?
Unverified catalog guidance: Avoid using Atmos if you are looking for a solution that supports a wider range of infrastructure definition languages beyond Terraform and Helmfile. Unverified catalog guidance: 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?
Unverified catalog guidance: If your project primarily focuses on non-Oracle cloud environments where compatibility or efficiency with other providers may be superior Unverified catalog guidance: 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 recorded GitHub stars (1,379 vs 871). Stars measure visibility, not whether either tool fits your constraints.
Which licenses are recorded for atmos and terraform-provider-oci?
atmos: Apache-2.0. terraform-provider-oci: MPL-2.0. Check each repository's current license and terms before use. Public GitHub hosting alone does not establish open-source licensing.
Where can I find alternatives to atmos or terraform-provider-oci?
GraphCanon lists candidates at atmos alternatives and terraform-provider-oci alternatives (atmos markdown twin, terraform-provider-oci markdown twin). The discovery order uses stored relationship proposals and shared categories; it is not a verified replacement ranking.
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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.