Migrations, platform rebuilds and virtual desktop rollouts — what the problem was, what we did, and what it changed.
Two of these were migrations of systems already carrying live traffic: a surf forecasting and camera-streaming platform, and HIPAA-regulated microservices holding patient data. Neither could be paused while we worked, so the interesting part of each is the cutover rather than the destination. The third replaced contractor laptops with virtual desktops inside a biotechnology company's own compliance boundary.
Clients are described by sector rather than by name, at their request. The figures are not anonymised: resource counts, downtime and run-rate changes are what we measured on the engagement itself.
Region-to-region AWS migration for a live surf forecasting and camera-streaming platform: 718 resources across 20 services and three accounts, cut over with minimal downtime.
Virtual desktops for a biotechnology company's contractors and BYOD staff: ten role-based AWS Workspaces images joined to the client's own Active Directory, built to their HIPAA and HITRUST obligations.
Moving HIPAA-regulated Python microservices off a managed PaaS onto AWS: three environments rebuilt as code on ECS Fargate, PHI isolated in its own account, and roughly 60% off the monthly run-rate.
Read the case study→
Contact us
A free consultation — with an engineer, not a salesperson
Tell us what you are trying to build, fix or migrate. We will look at your architecture, your costs and your risks, and come back with a recommendation in writing — whether or not it turns into an engagement.
Someone who has read up on your stack before the call
A working session on your actual problem — not a product pitch
An honest view of what you need, and what you do not
A written proposal with fixed scope and cost
The same engineers delivering it, and supporting it afterwards