No. This is for AWS you already run. A move onto AWS is a migration engagement.

Will you promise a savings percentage?

No. We look at the account first. Any cost change is specific to what we find, and we agree it before we make it.

What do you need from us?

Access to the account, what has to stay up, and the constraints you already have on security and cost.

AWS cost and operations

The account is already on AWS. The job is to run it with less waste and less surprise. We look at cost, security, and the way your team operates it.

Review our AWS account

What we look at

The bill, the workloads that create it, and the risks sitting next to them. Security and cost are reviewed together, because a cheap change that opens a hole is not a win.

We also look at how the team operates what is running: who can change it, what happens when it breaks, and which practices were agreed and then skipped.

Cost review tied to the workloads, not a generic percentage
Security practices against how the account is actually used
Operating changes your team can keep doing after we leave

What we will not claim up front

We do not quote a savings number before we have seen the account. The engagement produces the changes we agree to, and a way for you to operate them.

Common questions

Is this a migration?: No. This is for AWS you already run. A move onto AWS is a migration engagement.
Will you promise a savings percentage?: No. We look at the account first. Any cost change is specific to what we find, and we agree it before we make it.
What do you need from us?: Access to the account, what has to stay up, and the constraints you already have on security and cost.

AWS migration
A roadmap when you are unsure, and a hands-on move when you are not.