Complementary stack part 1: Same automation market, different jobs

Ansible, Terraform, Backstage, and CMP aren’t actually competing

As platform engineering has grown, the lines between automation, infrastructure as code, developer portals, and cloud management have started to blur. Ansible has added self-service. Terraform offers no-code provisioning. Backstage provides a developer-facing catalog. And each can look, at first glance, like it’s solving the same problem.

This five-part Complementary Stack Series separates those layers and looks at what each tool is actually built to do. Part 1 establishes the framework, mapping Ansible to configuration and execution, Terraform to infrastructure provisioning, Backstage to the developer experience, and CloudBolt CMP to the governance and orchestration that connects them.

Rather than asking which platform replaces which, the brief shows how these technologies can work together across the full request lifecycle, from initial self-service request through approval, provisioning, configuration, and ongoing operations.

In this brief, you’ll learn:

• Where Ansible, Terraform, Backstage, and CloudBolt CMP fit in the platform engineering stack
• Why adding self-service to a tool doesn’t necessarily turn it into an end-to-end platform
• Where gaps in approvals, governance, cost controls, and cross-tool coordination emerge
• Why CMP can provide a consistent orchestration layer without replacing the tools underneath it

Next in the series: Part 2 takes a closer look at Ansible Automation Platform and where its execution and self-service capabilities end and CMP begins.

Read part 2 | Read part 3 | Read part 4 | Read part 5