Case Studies
Measured outcomes from platform, migration, compliance, and cost work.
Real results from real clients. Numbers are measured, not estimated.
Pull request environments engineers run themselves: a chart, an operator, and a dashboard
Over 1,470 pull request environments deployed since February across 13 repositories, a median six minutes from push to URL, with dev stacks and AI prototyping sandboxes running on the same operator and dashboard and no platform ticket to see, restart, or tear one down.
Why ECS could not pack and what moving to EKS did to compute costs
On ECS the fleet reserved 57 vCPU and used one. On EKS with Karpenter, spot by default, and measured requests, twenty packed nodes deliver over ten times the work per compute dollar, and the observability, registry, CI, and AI tooling rode along on the spare capacity.
Stopping email-blast HEAD storms from taking down a legacy news site
Every marketing email took the site down for minutes as mail-client link scanners flooded the origin. Five rounds of fixes across nginx, the WAF, cache headers, and PHP-FPM timeouts took p99 from 2.7 s to 1.2 s and made the busiest scanner month on record the most reliable.
Replacing OpenSearch with PostgreSQL for a 25-million-record real estate data platform
Search that ran at a 3.1 second p90 on OpenSearch runs at 704 ms on PostgreSQL 18, validated row for row across 25 million records before cutover.
Crew Finance: SOC2 Type 1 Compliance & AWS Cost Optimization
A sub-10 person fintech passed SOC2 Type 1 and cut AWS spend 42% without pulling engineers off product, then kept us on for the network and PCI work that followed.
Cutting a Laravel monorepo's CI from nine minutes to three without touching a test
A nine-minute pull request gate became 2m 44s, queue wait dropped from over a minute to two seconds, and about 70 engineer-hours a month came back, for roughly $150 a month in runners.
These are six of eleven. See all 11 case studies →