Skip to main content

Why Does Atmos Exist?

Atmos fills the gap for Terraform users by offering a proven framework complete with conventions, methodologies, design patterns, and best practices, ensuring teams succeed with Terraform from the start.

Every team progresses through a similar path when adopting Terraform, maturing over time.

Each advancement brings new challenges, adding complexities that are ultimately justified by the benefits. Often, the true value of these evolutions only becomes clear after we encounter and address these intricate challenges first-hand.

Most companies today wouldn't dream of starting a new product without using a mainstream framework like React or NextJS.

Despite Terraform’s HCL language being a decade old, many companies still begin their Terraform journey with a blank slate, oblivious to the existing tooling and frameworks like Atmos. This is reminiscent of the early days of the web, with languages like NodeJS, PHP, and Ruby, before the rise of modern frameworks like Rails and React revolutionized application design. However, it doesn’t have to be this way. It's no wonder some teams endure over 10 stages of evolution before reaching Terraform maturity.

From Cloud Posse's experience working with countless venture-backed startups all the up to Fortune 100 companies, here's the typical journey we see them take when using Terraform without a framework to guide them.

Shortcuts

You can shortcut this entire process by using Atmos from the start. 😎

What stage are you at?

Let's explore the challenges and constraints we faced using Terraform without a framework.