// 01
Cloud architecture
AWS-native by default, multi-cloud by competence. We design for the long run — durable, observable, cheap to operate after we are gone.
- IaC: Terraform · Pulumi · CDK
- Cost modelling at design time
- Cross-region by default
AWS-native by default, multi-cloud by competence. We design for the long run — durable, observable, cheap to operate after we are gone.
From source to model to operator surface. Schemas declared, lineage tracked, freshness instrumented. ETL is a verb, not a vendor.
Role-based logic baked into the system, not painted on top. Operators, supervisors, auditors — each see what they need and can do what they own.
Traces, structured logs, decision provenance — the surface that lets you operate the system instead of guessing about it.
What you run, what you wish you ran, what is held together by one person. The audit is itself a deliverable — even if you do not engage us further.
IaC, identity, data flows, observability — declared, reviewed, costed. Nothing goes to production from a whiteboard sketch.
Strangler-fig where the legacy is alive; greenfield where it is not. Every cutover is rehearsed, instrumented, and reversible.
Runbooks, dashboards, on-call schedule, escalation paths. Your team owns the system at the end; we are on call for surprises.
Neither. We engineer systems for a fixed engagement and a quiet retainer; we are not selling rate-card hours.
If you want a body-shop, we will refer you to one we trust. If you want a team that owns the design, builds the system, and stays on call after — that is us.
Both. The interesting work in greenfield is making good decisions early enough that they survive scale. The interesting work in legacy is unwinding the assumptions that made the system fragile.
We have shipped a greenfield platform onto AWS in 9 weeks, and we have spent 6 months unwinding a 12-year-old monolith. The discipline is the same; the rhythm is not.
We have shipped into private VPCs, gov-cleared environments, healthcare data residency, and Norwegian banking. The architectural primitives are the same; the deployment story is more careful and the audit story is more visible. SOC 2 readiness on every engagement.
No. The stack is documented, the IaC is in your repo, your team can read it in three years. We aim to leave less of ourselves behind, not more.
The handoff at the end of every engagement is a deliverable: runbooks, on-call rotation transitions, dashboards that survive without us. The retainer is a choice, not a leash.
Fixed-fee for the design phase, time-and-materials for the build, fixed monthly for the retainer. We send a cost model with the architecture doc so there are no surprises later.
Often the better answer. We have run engagements where we owned the substrate and your team owned the application; we have run engagements where we wrote the first version and your team took it over by W12. We design the handoff at the start.
Send a brief — the operational system you want supported, the constraints you cannot move. We respond in 48 hours with an architecture sketch and a cost model.