Zhivko Todorov
ALL CASE STUDIES

CASE 169 · RIPTIDE · 2026

SELF-SERVICEINFRASTRUCTURECROSSPLANEBACKSTAGE

An infrastructure portal the application teams actually use.

An AI startup’s platform team had been the bottleneck for every new piece of infrastructure — every S3 bucket, every Aurora instance, every SQS queue. We built a self-service portal on Backstage that engineers used to provision infra against Crossplane-managed AWS resources.

INDUSTRY

AI startup

DOMAIN

PLATFORM

DELIVERED

2026

STACK

BACKSTAGE·CROSSPLANE·EKS·TERRAFORM (BOOTSTRAP)·OPA·GITHUB ACTIONS

RESULTS

What changed, by the numbers.

PLATFORM-TEAM TICKETS

−88%

INFRA REQUESTS

TIME-TO-INFRA

< 20m

WAS 1–5 DAYS

OPA-GUARDRAIL VIOLATIONS

< 2/wk

CAUGHT AT REQUEST

PLATFORM-TEAM HEADCOUNT

STABLE

AT 4× WORKLOAD

HOW IT WENT

The platform team was four engineers managing infrastructure for sixty developers. Every new infra resource was a Jira ticket against the platform team. The queue grew faster than the team could clear it.

Crossplane on EKS managed AWS resources via Kubernetes CRDs. Backstage templates surfaced the supported resource types as forms. OPA policies enforced what each team could request (S3 bucket allowed; Bedrock-trained-model not allowed without ethics review). GitHub Actions wired the request flow.

Platform-team tickets dropped 88%. Time-to-infra fell from 1-5 days to under 20 minutes. OPA-guardrail violations average under two a week and surface at request time, not at audit time. The platform team’s headcount has stayed at four while the developer count grew 4x — a different shape of work, not a bigger queue.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →