AWS-first systems
Cloud Architecture
Architecture on AWS and adjacent cloud: service boundaries, data stores, networking, identity, and cost. I design for the system you will operate, not a conference diagram.
Discuss this workThe usual failure
Cloud estates grow by accident. Services multiply, data gravity shows up late, and the architecture only makes sense to the person who clicked it together.
How I take it
I start from traffic, data, and failure modes. Then I pick the smallest set of managed services that can carry the load, with identity, networking, and observability as first-class pieces — not extras.
What you leave with
▸A written architecture you can defend
▸Service and data boundaries that match the product
▸Identity, networking, and blast-radius decisions made explicit
▸A cost and operations story, not just a diagram
Typical engagements
▸Greenfield cloud design
▸Existing estate review and simplification
▸Well-architected style assessments
▸Migration and modernization plans
Other lanes
If the work is real, I will take it.
Pactum is a one-person practice. You work with Matthew Swezey — not a bench that gets swapped after the pitch.