Accounts as code
Cloud resources described in files you own and review.
We have no published Terraform build. We have shipped three builds on AWS and three on Azure, and we say plainly that the case studies do not name the provisioning tool.
Cloud resources described in files you own and review.
Environments recreated from code, as we rebuilt environments on Hydrajaws.
Infrastructure changes that run through the same CI/CD as the app.
A plain answer on Terraform and OpenTofu for your use.
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Source: HashiCorp blog, 10 August 2023, and opentofu.org, checked 2 November 2026.

A resilient, auto-scaling AWS platform with daily CI/CD deployments, the kind of build Terraform would describe.

Development and production environments rebuilt on Azure after the previous owner left no documentation.
AWS
Azure
Google Cloud
Kubernetes
DockerTerraform moved to the Business Source License on 10 August 2023 for future releases. OpenTofu is a community-driven fork under the Linux Foundation that describes itself as a drop-in replacement. The licence restricts providing a competitive offering to HashiCorp.
No. We say so on the first call and show the nearest work, which is three builds on AWS and three on Azure, whose case studies do not name the provisioning tool.
Our published builds are on AWS and Azure. We list Google Cloud on our technologies page with no published build.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes on your accounts, your state files and your pipelines. No sales pitch.