OB. The Architect Layer
Interactive
Dive In
Every system,
every layer.
Seven systems — shipped platforms and the blueprints I structure everything with — each opened in three layers: the system view, the component map, and the live wire. Every box carries its why.
12+
Projects shipped
4+
Enterprise builds
5+
Years across the stack
01
Care Platform
Serverless GraphQL · AWS
02
Marketplace Platform
FastAPI · React Native · Stripe
03
Home Automation + Security
React Native · Swift · Kotlin · Socket.io
04
Agentic AI Systems
Multi-agent · Bedrock
05
Scalability Blueprint
Reference architecture · the why of every hop
06
Containerised Delivery
Docker · CI/CD · orchestration
07
Knowledge Platform
Docs-as-code · search · shared context
Marketplace Platform
A two-sided booking marketplace — mobile apps for clients and providers, a React admin, and an escrow-based payment spine with automated commission and payouts.
Layer 00
Interface wireframes
Client — Browse & Book
Provider — Earnings
This Month
$2,140
Request Payout
Layer 01
System view
Inspector
Select a component
Click any block in the system view. The highlighted path follows the live wire below.
Layer 02
Component map
Mobile
Booking Engine
Payment Spine
Network Edge
Integrations
Admin
Inspector
Select a module
Click any module in the component map to see what it does and why it exists.
Layer 03
The live wire
- Client → Public SubnetA request reaches the load balancer — the only public IP in the stack.
- ALB → Private SubnetThe balancer forwards into the FastAPI containers, which hold no public IP of their own.
- Auth checkThe API validates the caller before any booking logic runs.
- App → Data SubnetBooking logic writes to Postgres — a subnet with no internet route at all.
- NAT → StripeOutbound calls to Stripe leave through the NAT gateway — the only way out.
- NAT → IntegrationsProvider payouts and notifications route the same controlled, outbound-only way.
Shipped work and working theory — this is how I structure everything I touch.
View résumé →