Architecture for teamsbuilding with AI.
Independent AWS architect. I design and implement AI systems built to scale and stay cost-efficient.
Fixed price, scope agreed before we start. You see the plan before you commit to building. No retainers.
- Bedrock
- High Availability
- Security
Architecture, reliability, cost, and the AI on top.
Design and implementation, at a fixed price. Every project starts by getting clear on the goal and the path to it — never a retainer.
- 01
AI Agent & Inference Architecture
Design and implementation of AI systems on AWS — Bedrock Agents, RAG pipelines and inference architecture, built to scale and stay within budget.
- AI Agents
- Bedrock
- Multi-Agent Systems
- 02
Cloud Architecture & Modernization
Moving from rigid systems to architectures that can change without ceremony. Phased, never big-bang.
- Cloud Migration
- Modernization
- Serverless
- 03
High-Availability Design
Resilience designed for the business cost of downtime. Multi-region, fault-tolerant, documented.
- High Availability
- Multi-Region
- Fault Tolerant
- 04
FinOps & Cost Optimization
Full spend analysis and resource inventory. Unused, idle and over-provisioned resources. Reserved Instance and Savings Plan modeling, tagging and cost allocation. Token economics where there is inference in the stack.
- FinOps
- Cost Optimization
- Savings Plans
- 05
Security & Compliance
IAM review, network exposure, encryption at rest and in transit, Well-Architected alignment.
- IAM
- Well-Architected
- Compliance
Where systems built to ship fast get stuck.
It doesn't hold up in production
It worked in staging. Under real traffic it times out, degrades under load, or falls over — the architecture was never designed for what it now carries.
Nobody can change it safely
What you built to get here was built to ship, not to change. Every new feature costs more than the last, and nobody wants to touch what already works.
Nobody can say what it's spending
Cloud spend climbs every month with nothing to attribute it to, inference and vector stores included. You can't decide what to cut when you can't see what's running.
Understand the objective. Design the path. Build it.
Every project works the same way. First we get clear on where you want to get to and what you have today. Then you get the plan in writing — what to do, in what order, what it costs. Whether I build it is your call, later.
The Objective
Where you want to get to, and what you have today. If something's already running: what you spend and on what, who can reach what, and what breaks if one piece fails. If you're starting fresh: what it has to do, and what it can cost.
The Path
The design and the steps to get there, written down: what changes, in what order, what it costs. Anything already broken gets listed by how urgent it is.
The Build
I build it, or your team does with the plan in hand. Fixed price either way. Never a retainer.
Four deliverables.
What the first two steps produce, before anything gets built. Yours to keep, whether or not we build together.
- 01
Executive Summary
A short document you can act on: what you want, where you stand, and what to do first. Written to be read by someone who isn't an engineer.
- 02
Severity-Rated Findings Register
Every problem documented with evidence, how urgent it is (Critical / High / Medium / Low), what it affects, and how to fix it. The document your engineers work from.
- 03
Prioritized Roadmap
What to do and in what order, with the effort and the payoff for each step. Run it yourself, or bring me in to build it. No obligation either way.
- 04
Findings Readout
A live walk-through of the findings with your team. Discussion, questions, push-back welcome. Included.
Illustrative layout. A real register is specific to your setup — every row carries evidence and how to fix it.
For agencies & software factories
I work behind your brand — your client never sees a third party. Take on the work you'd otherwise pass on. AWS, or Hetzner and Proxmox when the numbers point there. Same fixed price, no retainers.
Get in Touch- TravelXperience
- FerlaViajes
Cloud architecture & infrastructure
Ready when you are.
Tell me about your AWS environment.