Skip to content

Config0

What is Config0

What (we are like):

  • Config0 is an alternative to Terraform Cloud, Spacelift, and Env0.
  • Think of combining Airtable with workflows and Docker for layering, applying it to Infrastructure As Code (IaC) management.

Where (mission statement):

  • Just like Docker made container technology with application layering accessible, our aim is to make IaC management accessible through workflow layering.

How (we differ) - layering

  • Config0 converts OpenTofu/Terraform code into immutable workflow layers.
  • These workflow layers are distributed through an open-source marketplace.
  • These workflows are layered to build larger workflows and overall more complete solutions.

Why Config0

Ready to Use Automation (For CTOs/Developers)

  • Rapidly adopt IaC without high upfront costs or deep DevOps knowledge.
  • Select off-the-shelf DevOps solutions that work out of the box.

Integrate Existing Investments (DevOps Engineers/SREs)

  • There is no need to abandon existing investments in OpenTofu/Terraform.
  • Easily glue existing investments - OpenTofu/Terraform and Ansible - to create complex solutions that preserve authoring simplicity.
  • Quickly provide security audits for IaC components used in the workflows: who, where, and what.2

Rapidly iterate and provide end-to-end solutions (Platform Engineering)

  • Quickly populate self-service platforms.
  • Provide both stable and bleeding edge infrastructure technologies for users.
  • Control changes by locking downstream workflows and components

  1. Unlike other pipelines (e.g. Gitlab, CircleCI, Jenkins), Config0 stacks (pipelines) allow for many layers (nested) of automation. For example, Gitlab permits one parent, one child, and at most one grandchild. It is not uncommon for a single Config0 stack (pipeline) to contain 5 to 10 layers. ↩

  2. We record who authored the component, where the component came from, and when the component was committed. ↩