Grow on AWSwithout surprises.
Know who has access to what, see where your costs are coming from, and deploy with confidence.
- 10 years
- building on AWS
- 83
- architectures reviewed
- 100+
- AWS accounts secured
Your environment works. It's just getting harder to run.
You had to build it fast, but now you don't have the full picture of what was deployed and how to keep it under control.
- 01
Everyone has access to everything.
It was the fastest way to build. Now anyone can reach production.
- 02
You can't see what's running, or what it costs.
The bill goes up and it takes a day to work out what caused it.
- 03
Deploys have become risky and painful.
No safety net, manual steps and the fear of causing downtime.
The 3 layers of production engineering on AWS.
- 01
Guardrails
Who can do what, in which account, for both humans and applications.
- 02
Visibility
Logs, metrics and traces per service, plus a bill you can understand.
- 03
Change control
Every deploy tested, reviewed and automated. Releasing a new version stops being an event.
How We Work
- Free · 45 minutes01
Discovery
You describe your situation and where it is hurting.
- 1–2 weeks02
Assessment
We look at your AWS account and your code to find the gaps.
- Scoped from the Assessment03
Build
We implement the fixes alongside your team.
- 04
Handover
Your team gets what they need to continue without us.
Tired of feeling uncertain about your AWS environment?
Fernando Gonçalves
Principal AWS Engineer, Founder
Find out where the gaps are in your AWS environment.
We go through your AWS accounts and your code, and give you a report you can act on: what to fix, and in what order.
What we look at
- Who has access to what, across every AWS account
- What is running, what it costs, and who can change it
- How you deploy, and what happens when it breaks
- Where your data is, and who can reach it
- What you would need to answer a customer's security requirements
- Every gap between what you have and what production needs, ranked by risk
- Each finding pointing at the exact policy, file or resource
- What to change and why, specific to your system
- Impact estimate per item, so you can prioritise the work
- A walkthrough call with your engineers
- A report written for engineers by engineers. Detailed enough to act on with or without us
Common Questions
- What happens during Discovery?
- You explain your particular situation and get our opinion on where you are most exposed today. If it is work we can do, we will propose a technical assessment. If not, we will suggest what to do next.
- What do I need to prepare?
- Nothing. No deck, no access, no diagram. If you can describe your situation and where it hurts, that is enough.
- Our setup is a mess. Is that a problem?
- No. That is what building fast looks like when it works. Most of the calls we take are with teams who know roughly where the problems are and have never had the time to go and fix them properly.
- Who should be on the call?
- You, and whoever runs the AWS account if that is someone else. Two people is usually right.
- Do I have to commit to anything?
- No. If what you need is something your team can handle without us, we will tell you that on the call.
- We're not on AWS. Should we still talk?
- Then we're probably not your best option.
Let's Talk.
Technical, not a deck. You describe your situation and where it is hurting. We tell you what it would take to bridge the gaps, and if we can't help, we'll suggest alternatives.
The call is free. If we go ahead, the assessment is 1–2 weeks at $3,500 fixed, credited in full against the build.
Working from Dubai, UAE. Engagements delivered remote-first.