Sign in Subscribe

Case Study

One login for every internal tool: Authentik as the front door to a Kubernetes platform

Twenty-seven platform tools across two clusters, from Grafana to per-pull-request environments and AI sandboxes, behind one identity broker fed by Google Workspace and AWS Identity Center, configured entirely from Git.

An AI prototyping sandbox where product teams ship in minutes

Product staff and their coding agents deploy sandboxed services in under five minutes. Ten days after launch, prototypes were running, a shadow cloud was being emptied, and two AI-built services had graduated into the managed platform under human review.

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.

Building a GitOps platform on EKS for a national media and events company

84 ECS services, two clusters, one Git repo: how a media company went from click-ops to self-service pull request environments.

Crew Finance, part two: one VPC, an isolated cardholder environment, and an 89% NAT bill cut

Five VPCs on the same address range became one shared network with an isolated PCI zone, while NAT costs dropped 89% and load balancer costs halved.

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.