Cloud & AWS
Cloud engineering for systems that have to stay up
Senior AWS architecture, modernisation and production reliability for organisations worldwide. We design systems to be dependable, affordable to run and possible to hand over — and we run our own products on the same principles.
The problems we're usually called for
The system works, but nobody wants to touch it
We assess the architecture, identify what is actually risky, and modernise that — rather than rewriting everything and creating a second system nobody wants to touch.
The cloud bill doesn't match the traffic
We design for cost as a first-class requirement: serverless and managed services where they fit, right-sized where they don't, and monitoring that tells you what a feature costs to run.
Production is one person's memory
Infrastructure defined as code, separate environments, automated deployments with short-lived credentials, and monitoring and alerting — so the system survives the people who built it.
You need an architect, not another developer
Design reviews, technical decisions, cloud strategy and delivery support for your existing team — from someone who has run these systems inside large organisations.
How we build it
- Architecture and risk assessment of existing systems
- Serverless and event-driven design on AWS
- Infrastructure as code with AWS CDK
- CI/CD with GitHub Actions and OIDC — no long-lived keys
- Least-privilege IAM and separated environments
- Monitoring, alerting and cost visibility
- Migration off servers and legacy hosting
- Production hardening before real traffic and real data
This site, the HomeNurse platform and Motebo's own products all run this way. See the HomeNurse case study for the decisions in practice.
Questions we're often asked
Do you only work with AWS?
AWS is where our depth is — certifications, production systems and our own products all run there. The engineering principles (infrastructure as code, least privilege, separated environments, monitoring) are portable, and we always start by assessing what you already have rather than proposing a move for its own sake.
Can you take over a system you didn't build?
Yes — that's a large part of our work. We start with an architecture and risk assessment, stabilise what's fragile, and modernise only what actually needs changing. A rewrite is the last resort, not the default.
What does a serverless system cost to run?
It scales with use: a quiet month costs close to nothing, and you pay for what actually runs. We design with cost as a first-class requirement and hand over dashboards that show what each part of the system costs, so there are no surprises. Project pricing itself is scoped per engagement.
Who owns the AWS account and the code?
You do. We build in your AWS account, define the infrastructure as code, and hand over the repository and documentation. There is no lock-in to us.
What happens after hand-over?
Monitoring and alerting are part of every build, and we offer ongoing support and architecture review on a retainer. We care what the system costs and how it behaves in year three, not just at launch.
Have a system that needs to be more dependable?
Tell us what it does, what worries you about it and what it costs. We'll tell you what we'd change first.
Talk to an engineer