Case study — Cloud Infrastructure2026

Foundry

Environments on request, not on a ticket

An internal developer platform where a service, its environments and its guardrails are created from one template rather than a ticket queue.

Industry
SaaS, Enterprise
Year
2026
Screens
09
Foundry platform overview with services created, environment usage and baseline compliance

Overview

About the project

Foundry is a concept product for platform teams who have become a queue: every new service needs a repository, a pipeline, a namespace, secrets, alerts and an on-call rotation, and each is a ticket to somebody. It turns that into a golden-path template a team can run themselves, with the guardrails baked in, and it keeps a live catalogue of what exists, who owns it and whether it still meets the standard.

The challenge

Standing up a new service means five tickets to three teams and a fortnight of waiting, so teams either wait or route around the platform entirely. The result is a sprawl of services nobody can inventory, with no consistent way to say who owns one or whether it meets the security baseline.

Our solution

We made the golden path self-service. A template creates the repository, pipeline, namespace, secrets and alerting together, with the guardrails applied rather than documented. The catalogue then keeps every service, its owner, its dependencies and its scorecard against the baseline current, so drift is visible on the day it happens.

What we built

  1. 01Service templatesRepository, pipeline, namespace and alerts created as one unit.
  2. 02Ephemeral environmentsA full environment per pull request, torn down on merge.
  3. 03Service catalogueEvery service, its owner, dependencies and current state.
  4. 04ScorecardsEach service graded against the security and reliability baseline.
  5. 05GuardrailsPolicy applied at provisioning rather than written in a wiki.
  6. 06Cost attributionSpend attributed to the team that owns the service.
  7. 07Mobile catalogueOwnership, on-call and scorecard from a phone.

Desktop

Where the product doesits heaviest work.

The full-width interface, screen by screen.

Foundry service catalogue listing each service with its owner, tier, dependencies and scorecard
Fig. 01 — Service catalogue
Foundry scorecards grading each service against the security and reliability baseline
Fig. 02 — Baseline scorecards
Foundry environment list with per-pull-request environments and their lifetime
Fig. 03 — Environments
Foundry cost attribution assigning platform spend to the team that owns each service
Fig. 04 — Cost attribution

Mobile

Rebuilt for onehand.

The same information hierarchy, rebuilt for a screen you hold in one hand.

Foundry mobile platform overview with services, environments and baseline compliance
01 — Platform overview
Foundry mobile service detail with ownership, on-call and scorecard
02 — Service detail
Foundry mobile environment list with age and teardown state for each environment
03 — Environments
Foundry mobile scorecard list with the checks services are failing
04 — Scorecards

(→)Start a project

Want something like Foundry for your business?

Tell us what you have in mind and we'll come back with a clear scope, a realistic timeline and an honest opinion on the best way to build it.

Project brief

Sent securely from this page. We only use your details to reply — see our Privacy Policy.