Teach what happens
after the code ships.

Students move from running one application to designing platforms that can deploy, observe and recover under real constraints. Failure becomes part of the curriculum.

PLATFORM CONTROLCL / LIVESERVICE TOPOLOGY / PRODUCTIONOperate through change and failure.EDGE18msAPI99.98%QUEUE12 jobsDATAhealthyWORKER8 / 8OBSERVE4 signalsSLO WINDOW99.95availability / 30dGAME DAY / ACTIVEAPI latencyPASSQueue lossPASSDB failoverWATCHCHANGE 18 / CANARY HEALTHY / ROLLOUT 76%
CL

OUR POINT OF VIEW

Modern software education must include what happens after the code runs locally.

THE FIELD IS MOVING

What students must learn to see differently.

The durable skill is not familiarity with today’s tool. It is the ability to reason about the system, its constraints, and the evidence behind a decision.

THE UNIT OF WORK
FROM

One application

→
TOA service in a living system
THE CORE QUESTION
FROM

Does it run?

→
TOCan it operate under change and failure?
THE ENGINEERING BAR
FROM

Manual deployment

→
TORepeatable platforms, observability, and reliability

INDUSTRY-VETTED COURSE PORTFOLIO

A pathway from foundations to consequential work.

Representative courses can be configured as electives, honors pathways, minors, faculty-development modules, or an integrated specialization.

CL-3014 credits · deployment lab

Cloud Systems from First Principles

Package, deploy and operate service based applications while seeing every layer beneath them.

01
CL-3154 credits · systems practicum

Distributed Systems under Failure

Reason about consistency, replication, coordination and the failures diagrams tend to hide.

02
CL-4024 credits · platform studio

Internal Developer Platforms

Build paved roads and self service workflows that make engineering teams faster and safer.

03
CL-4104 credits · automation studio

Infrastructure as Code at Scale

Create reviewable, testable and repeatable infrastructure with policy built into delivery.

04
CL-4214 credits · operations lab

SRE and Incident Practice

Set reliability targets, respond to incidents and learn from systems under stress.

05
CL-4904 credits · reviewed capstone

Resilient Systems Studio

Deliver a measured platform under load, change and deliberately injected failure.

06

HOW WE TEACH THE DOMAIN

Practice that creates professional judgment.

Each learning experience is structured around how credible work is actually reviewed: assumptions are explicit, evidence is inspectable, and important tradeoffs must be defended.

01

Architecture under constraints

Students make explicit choices about scale, consistency, cost, latency, and failure instead of copying reference diagrams.

02

Everything as code

Infrastructure, policy, delivery pipelines, and environment configuration become versioned, reviewable systems.

03

Observability as a design input

Logs, metrics, traces and service level objectives are built with the system, not attached afterward.

04

Failure as curriculum

Load tests, dependency failures, rollbacks, and incident reviews teach operational judgment.

APPLIED WORK

The kind of problems students can learn to own.

These briefs illustrate the project scope and engineering judgment we bring into programs, labs, and industry-supported capstones.

BRIEF / 01

Internal developer platform

Self-service service deployment with policy, templates, and observability.

PlatformIaCDX
BRIEF / 02

Failure-aware commerce backend

Distributed transaction workflow tested under dependency outages.

DistributedSREChaos
BRIEF / 03

Campus compute control plane

Multi-tenant scheduling, quotas, cost visibility, and workload lifecycle.

CloudControl planeFinOps

CENTER OF EXCELLENCE BLUEPRINT

A Cloud & Platform Engineering Center of Excellence

A campus environment where students operate shared platforms, practice reliability, and learn infrastructure through responsibility for real systems.

01

FOUNDATIONSNetworks, operating systems, distributed computing, software design

02

PLATFORMContainers, clusters, IaC, CI/CD, secrets, observability

03

OPERATESLOs, incident response, capacity, security, cost management

04

PROVEArchitecture reviews, load tests, game days, runbooks, demos

CAPABILITYEVIDENCE

WHAT ACADEMIC LEADERS CAN INSPECT

Proof beyond completion.

Every program is designed to leave behind concrete evidence of what students can do and how well they can reason.

Versioned infrastructure repositoriesService-level objectives and dashboardsLoad and failure-test reportsIncident reviews and operational runbooks

CL / START A CONVERSATION

What could Cloud & Platform look like at your institution?

We’ll help you choose the right academic format, faculty enablement model, infrastructure, and first set of student outcomes.

Discuss a Partnership