Infrastructure as Code: Your cloud, written as code you own
We write your accounts, networks and services as code in your repository, and each change reaches staging, then production, once a person approves it.
From a line of code to production
- Write: A change is written in your repository.
- Plan: The plan shows exactly what will change.
- Approve: A person reads the plan and approves it.
- Staging: The change reaches staging first.
- Production: Then production, from the same code.
- Drift caught: A check finds a change made by hand, and a person decides what stays.
Where your cloud starts today
- What we do
- We write the landing zone and the first environments from the cloud’s own foundation.
- What you hold
- Accounts, network, sign-in and logging, as code.
AWS Control Tower with Landing Zone Accelerator on AWS
Azure landing zones on Azure Verified Modules
Google Cloud enterprise foundations blueprint
What lands in your repository
- modulesBuilding blocks every workload reuses
- environmentsDevelopment, staging and production, from the same modules
- policiesThe rules every plan is checked against
- pipelinePlan, a person’s approval, then apply
- docsHow to change it, and how to rebuild it
policies
- No storage open to the internet
- Encryption on
- An owner tag on every resource
- Only the regions you allow
Terraform and OpenTofu state stays in your own account, locked and encrypted.
Yours from the first commit, and yours if we leave.
The tools, on each cloud
- Written in
- AWS CloudFormation or AWS CDK, Terraform or OpenTofu
- Checked before it applies
- Change sets and CloudFormation Guard
- Changes made by hand
- CloudFormation drift detection and drift-aware change sets
Open Policy Agent checks Terraform plans on any of the three.
Customer work
- Managed Services
Network, clusters, autoscaling and CloudFront managed with Terraform.
31 ms at p95Order serviceShwapnoRetail chain, online store, BangladeshRead the story: Shwapno (opens in a new tab) - Cloud Build & Launch
Resources provisioned with Terraform, and changes shipped through AWS CodePipeline.
More registrations and attendanceEuropean biopharmaceutical companyBiopharmaceuticals, Several European countriesRead the story: European biopharmaceutical company (opens in a new tab)
Where you will meet it
- Cloud Build & Launch (opens in a new tab)Every environment of a new platform starts as code.
- Migration & Modernization (opens in a new tab)Each move lands on a landing zone written as code.
- Managed Services (opens in a new tab)Changes go through reviewed code, so each one can be reversed.
- Audit & Compliance (opens in a new tab)A remediation plan is carried out as approved code changes.
Questions
Which tool do you use?
The one your team knows: CloudFormation or CDK on AWS, Bicep on Azure, Terraform or OpenTofu on any of the three. With none, we choose with you and write down why.
What if someone changes something in the console?
A scheduled check compares what runs with the code and raises it. A person decides whether the change goes into the code or is put back.
Can the code rebuild everything?
It rebuilds the infrastructure. Data comes back from the backups the code sets up, so we test a restore before handover.
Terraform or OpenTofu?
Terraform has been under the Business Source License since version 1.6. OpenTofu is the open-source fork, under the Linux Foundation. We tell you which fits, and your legal team decides whether the licence matters.