Book a ConsultationCloud Architecture & DevOps on AWS
Hire an AWS-certified engineer to design or fix your production infrastructure — cost, reliability, and deployment process, handled by someone who's run it at real volume.
Infrastructure work usually shows up in one of two states: nothing exists yet and needs designing, or something exists and is either too expensive, too fragile, or too undocumented for the team to touch confidently. I work in both — greenfield architecture and taking over infrastructure someone else built.
Decisions are made for the traffic and team you actually have, not for hypothetical scale. Serverless where it removes operational burden, containers or instances where it doesn't, and infrastructure as code either way so nothing lives only in a console.
Who this is for
- Teams launching a new product that needs infrastructure designed, not improvised
- Products whose AWS bill or reliability has become a problem
- Founders who inherited infrastructure nobody can explain and need it documented and stabilized
What you get
Infrastructure as code
Terraform or CDK, so environments are reproducible and changes are reviewed, not clicked.
CI/CD pipelines
Build, test, and deploy automated end to end, with rollback that actually works.
Cost review and right-sizing
An honest read on what's driving the bill and what to change, ranked by impact.
Monitoring and alerting
Logs, metrics, and alerts that tell your team about a problem before a customer does.
Disaster recovery
Backup and recovery plans that are documented and actually tested, not assumed to work.
How the engagement runs
- 01
Infrastructure review
What exists today, what it costs, and where the risk is.
- 02
Architecture plan
A written plan for what changes, in what order, and why.
- 03
Implementation
Changes rolled out incrementally against a working environment, not a big-bang cutover.
- 04
Validation
Load and failure-mode testing before anything is called done.
- 05
Handover or retainer
Documentation and runbooks handed to your team, or an ongoing retainer to keep operating it.
Engagement options
Architecture Audit
An honest read on what's already built
1–2 weeks
Teams inheriting a codebase, pre-fundraise diligence, or diagnosing 'why is this so slow'.
- Codebase, infrastructure, and cost review
- Written findings ranked by risk and effort
- A prioritized remediation plan
- A walkthrough call to go through the findings
Monthly Retainer
An embedded senior engineer, minus the hiring cycle
Rolling, one-month minimum
Teams shipping continuously who need senior capacity without a headcount req.
- A fixed block of engineering hours each month
- Feature delivery, code review, and refactors
- Works inside your existing tools — Slack, board, standups
- Cancel or pause with notice
Fractional CTO
Senior technical leadership, part-time
Ongoing
Non-technical founders and seed-stage teams with no senior engineer in the room.
- Architecture and build-vs-buy decisions
- Hiring support — scorecards, technical interviews, contractor vetting
- Vendor and agency due diligence
- Regular roadmap and delivery check-ins
Proof, not promises
Termii
SaaS · Internal Tools · Africa
Built a fully automated internal operations platform for Termii, a fast-growing African SaaS company. The system unifies team management, notification pipelines, and org-wide visibility into a single seamless dashboard. Whether overseeing dozens or thousands of staff, the platform runs on full autopilot — routing alerts, tracking team activity, and surfacing the right information to the right people without any manual intervention.
Read the Termii case studyFrequently asked questions
Can you review infrastructure someone else built?
Yes — that's the architecture audit engagement: a cost and reliability review with a prioritized, written remediation plan.
Do you only work with AWS?
AWS is where most of my production experience is, including running infrastructure for a messaging platform at real volume, so it's what I recommend by default. I'll flag it plainly if a different provider genuinely fits your situation better.
Can you reduce our AWS bill without a full redesign?
Often, yes — right-sizing, reserved capacity, and removing unused resources typically account for a meaningful chunk of overspend before any architectural change is needed.
Do you handle ongoing operations, or just the initial setup?
Both — a one-time architecture engagement, or a retainer if you'd rather have an engineer accountable for infrastructure on an ongoing basis.
Related services
Ready to talk about cloud architecture & devops?
Book a call or send a message — you'll hear back within a day.