Case study: government insurer

Self-service on a catalog-driven developer platform

Client context

A state government-owned workers’ compensation insurer. The engineering estate spans a large end-of-life Java and Oracle claims monolith and a modern catalog-driven internal developer platform on AWS EKS, deployed through a distinctive rainbow release model.

The problem

The platform’s core pipeline existed (service catalog YAML rendered by KubeVela CUE templates, synced by Argo CD to EKS, with a Kafka-driven GitOps choreographer auto-bumping image versions), but self-service had gaps: creating a GitHub repository, getting a development database, or seeing what a catalog change would actually do to infrastructure still required platform-team involvement. CI also ran on aging self-hosted runners that needed migration and security hardening.

What was built

Outcomes

← All case studies

Still fielding tickets your platform should absorb?

The Platform Assessment finds the gaps; the IDP Accelerator closes them.

Start a conversation