Cloud management

Cloud infrastructure in code, reviewed before it changes

We bring your cloud accounts under version control and put policy checks in front of every change, so you know what runs, why it runs and who changed it.

terraform planExample output
$ terraform planPlan: 3 to add, 1 to change, 0 to destroy.Policy check  storage account "logs" is public     FAIL  14 other policies                    PASSApply blocked until the failure is fixed.
First call
Free, no commitment
After the call
A written proposal: scope, steps, price
Price
Agreed in writing before work starts

The problem

Where it usually hurts

The cloud account grew over years. Resources were created in the console, nobody is sure which ones are still needed, and so nothing is ever deleted.

The bill rises, and nobody can explain the increase line by line.

A change in production is made by hand, by whoever has access. There is no review and no record, and when something is publicly reachable that should not be, it is found by accident.

Scope

What you get

  • An inventory of what runs in your accounts, with an owner and a purpose for each resource
  • Infrastructure as code for the resources you keep, in your repository
  • Policy checks that block a change before it is applied, for example public storage or open network rules
  • Access by role, with unused keys and accounts removed
  • Costs attributed to teams or products, so each line on the bill has an owner
  • A change process of plan, review and apply, with a record of who changed what

Process

How an engagement runs

Four steps. You decide after each one whether there is a next one.

  1. 01

    Book a call

    Tell us what hurts: the release process, an audit finding, a slow database, a cloud account nobody fully understands. We ask questions and say plainly whether we can help.

  2. 02

    Get a written proposal

    Scope, steps and price in writing. You decide with the facts on the table.

  3. 03

    Work in your systems

    We work in your repositories, your pipelines and your cloud accounts, alongside your team. Our changes go through review like any other change.

  4. 04

    Keep everything

    Code, configuration and documentation stay in your repositories. Your team runs the result without us.

FAQ

Questions we get before the first call

Which cloud providers do you work with?

AWS, Azure and Google Cloud, with Terraform for the infrastructure code. If you run something else, smaller European providers included, tell us in the first call. We say plainly whether we have the experience for it, and if we do not, you hear that before any work starts.

Will you reduce our cloud bill?

We do not promise a figure, because we have not seen your bill. What we deliver is the inventory and the attribution that show where the money goes. Unused resources and oversized instances become visible, and you decide what to remove.

Do we have to move everything into code at once?

No. We import existing resources step by step, starting with the ones that change most often or carry the most risk. Everything else keeps running as it does today until its turn comes.

Do you help with a move to another cloud or another region?

Yes, for the infrastructure side: network, compute, storage, access and the migration plan. Where data residency matters, we document where each data store lives.

Who has access during the engagement?

We work with named accounts and the least access the task needs. Every change we make goes through the same plan and review as your own, and you can revoke our access at any time.

Talk to us about Cloud management

Describe where you stand today. We tell you plainly whether we can help and what a first step would look like.

The first call is free and without commitment.