The Progressive Delivery with Argo Rollouts week made our metric gates explicit—before that we “trusted the graph” without writing down what failure meant.
Mika Kobayashi · Platform engineer · Regional payments stack
Nonthaburi studio · cohorts in English
DevOps delivery, drafted for working teams
- Mentor-reviewed merges—not anonymous autogrades
- GitOps, CI, and progressive delivery labs with rollback stories
- Evening-friendly schedules for Bangkok and hybrid squads
12
Open catalog tracks
5.1 / 10
Average mentor score on exit surveys
18
Program staff across instruction and design
3
Sandbox regions for labs
Since 2019
First public cohort shipped
The flow across five beats
Each beat ends with an artifact: YAML, note, or retro doc. Nothing is “watch-only” unless you explicitly choose audit mode for a module.
Beat 01
Map risks your pipeline already whispers about.
Beat 02
Instrument gates reviewers can defend in standup.
Beat 03
Rehearse failure injections before prod borrows the pattern.
Beat 04
Ship narrative release notes stakeholders skim on mobile.
Beat 05
Archive evidence for the next rotation of engineers.
Inclusions worth the commute
Cohort tracks bundle live critiques, async briefings, and capstone reviews. Self-paced tracks lighten live hours but keep mentor checkpoints on written work.
Reviewed diffs
Human comments on pipeline changes—not boilerplate rubrics.
Project briefs
Portfolio-shaped labs with acceptance notes you can reuse at work.
Office hours
Queued questions across APAC-friendly windows.
Signals from recent cohorts
Pipeline Foundations for Busy Teams
8,900 THB Wire linting, tests, and artifact promotion into a single Git-backed pipeline you can explain to stakeholders.
Release Engineering Studio
12,400 THB Versioning, changelogs, and deployment windows treated as a craft—not a midnight scramble.
GitOps Intensive: Declarative Ops
15,600 THB Reconcile loops, drift detection, and PR hygiene for clusters that should match Git, not drift.
Kubernetes Ops Field Manual
18,200 THB Node pressure, scheduling quirks, and upgrade rehearsals for teams inheriting clusters they did not design.
From our cohorts
Ansible Hybrid Footprints inventory rules stopped our CSV sprawl. Still wish the Windows appendix was thicker—Linux focus was clear upfront though.
Lin · Chiang Mai
Terraform & IaC Collaboration turned our plan reading club from roast sessions into twenty-minute reviews.
Noor Hadi · 5/5
Client in logistics: Pipeline Foundations gave our release train vocabulary to argue for required checks without sounding obstructionist.
Client in logistics
OIDC lab in CI/CD Actions—finally.
Chris · Platform