Product builds, migrations, virtual desktop rollouts and platform rebuilds — what the problem was, what we did, and what we built or changed.
Two kinds of work, grouped the way our services are. Product engineering is software we build and then keep running: for Lernern, a skilling and placement provider, a learner management system with a staff portal and one API behind it, and the learner app on top of it. Cloud infrastructure is moving and rebuilding systems already in use: a surf forecasting and camera-streaming platform and HIPAA-regulated microservices that could not be paused while we worked, and contractor laptops replaced with virtual desktops inside a biotechnology company's own compliance boundary.
Most clients are described by sector rather than by name, at their request; Lernern is named. The figures are not anonymised: on the migrations, resource counts, downtime and run-rate changes are what we measured on the engagement; on the Lernern studies, they describe the systems as built.
Product Engineering
Software we designed and built from scratch, and then kept running: a learner management system and the app learners use.
Lernern is a skilling and placement provider in India. We designed, built and run its learner management system: a staff admin portal, a learner app for Android and iOS, and one NestJS API — about 740 endpoints — behind both.
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