AWS work for every stage, from a first landing zone to monthly support. Every engagement ends with documentation and code your team owns.
For teams setting up AWS properly for the first time, or moving to it.
A multi-account AWS setup with guardrails, networking and single sign-on in place before the first workload goes live.
Servers, databases and applications moved with a tested plan, a rehearsal and a way back if something goes wrong.
For teams already on AWS who want to know where they are exposed.
Least-privilege access, logging and threat detection configured and tuned, with written findings you can hand to auditors.
For teams who want lower bills and someone keeping an eye on things.
A clear breakdown of where the AWS bill goes, then rightsizing, clean-up and savings plans that cut it.
Infrastructure as code, deployment pipelines and a monthly review of security findings and spend.
Fixed scope, fixed price and a clear end point. A low-risk way to start working together.
A fixed-scope review of one AWS organisation against the security pillar of the Well-Architected Framework.
A governed multi-account AWS setup, built with Control Tower and ready for your first workloads.
A look at your last three months of AWS spend, with a list of savings and what each one is worth per month.
Assessments follow AWS's own framework, so findings use terms your team and AWS Support already know. It covers six areas.
Prices are agreed in writing before any work starts.
A defined piece of work, such as a security review or a migration, at an agreed price.
From [£ price]
Flexible hands-on help for your team, booked by the day.
[£ day rate] per day
A set number of days each month for maintenance, reviews and small changes.
From [£ monthly fee] per month
Can't see your question? Send it to us and we'll answer it directly.
In the AWS Region you choose. For UK businesses that is usually London (eu-west-2). A landing zone can also include a control that blocks the use of other Regions.
A role created for the engagement through IAM Identity Center, with only the permissions the work needs. Reviews use read-only access. Everything the role does is recorded in CloudTrail, and the role is removed when the work ends.
Yes. We're happy to sign your NDA before you share any details about your systems.
Usually [3–5 working days] for one AWS organisation, followed by a walkthrough of the findings with your team.
Yes. Our main focus is AWS, and we also work on Microsoft Azure, particularly DevSecOps: building security checks into how your software is built and deployed.
No. Many clients start with one of the starter packages and decide what to do next once they have seen the findings.
Yes. We can build with your team and explain as we go, so they can run everything once we have finished.
Tell us what you run today and what you want to change. We'll suggest where to start.
