Within 14 days
Cancel an enrolment more than 14 calendar days before kickoff and receive a full refund — no reason needed.
Cancel an enrolment more than 14 calendar days before kickoff and receive a full refund — no reason needed.
Cancel between 14 and 5 days before kickoff and receive a 50 percent refund. The Refund page lists the small print.
We consider medical issues, bereavement, or sudden loss of employment. Honest requests are rarely refused — please ask.
When we reschedule a cohort you choose between a full refund or a free deferral, regardless of how close to kickoff.
Read the full Refund & Cancellation page for the exact mechanics.
Nimbus Forge is a small, working studio for engineers and career switchers who want to design cloud systems with intention. Our cohorts are deliberately small — 12 to 22 seats — so every architecture write-up gets read by a working architect, not a teaching assistant. We run live evening sessions twice a week, a Saturday studio block, and a single mentor 1:1 in every long programme. The labs are scenario-based and built from real failure modes, not screen-recordings of a console click-through. If your last training felt theatrical, this one is meant to feel like a quiet workshop. We will tell you plainly when a cohort is wrong for you.
Nine programmes across foundations, AWS, Azure, Kubernetes, multi-cloud, and a private clinic. Filter by skill level, platform, and certification track.
View nine programmesA live walkthrough is the most reliable way to read whether a cohort fits how you learn. The format mirrors a midweek session of the programme you choose: a working architect opens the actual workbook, runs through one lab artefact, and answers questions for the remaining fifteen minutes. Our calendar shows real availability for the next two working weeks. We do not run open-ended demos; the slot is pre-scoped so you leave with a single decision in mind.
Heejin’s engineering team had been migrating workloads to Azure for nine months and the landing zone had quietly drifted into something nobody could defend in writing. Two of the three subscriptions had naming inconsistencies, identity sprawl was undocumented, and the sponsor was asking for a clean answer before the next budget cycle.
We spoke for forty-five minutes before sending a quote. The team booked a two-day Architecture Review Clinic, and afterwards Heejin enrolled in the Azure Solutions Architect Expert Track to formalise the vocabulary the critique had surfaced.
Nineteen weeks later the team published a one-page landing-zone decision record her sponsor signed, presented a hybrid identity strategy that matched the company’s actual headcount curve, and rebuilt the group naming convention the sprint after the cohort closed.
Generic “upskill” language hides what each programme is actually for. Below are four people we expect to meet most weeks, and the cohort we would steer them towards on the first call.
A 12-week path with two evening sessions and a Saturday studio block. Mentor feedback on a written design exercise every week.
See the AWS path →A short, opinionated course built around Argo CD and a real reference repository you keep at the end.
See the GitOps course →A gentle eight-week course paced for analysts and operations specialists, with Sunday office hours and an optional CV review.
See the Azure path →A two-day private engagement scoped with the Academy Director. You leave with a written critique and a prioritised list.
See the Clinic engagement →We dislike long forms in front of strangers. Below is the structure of the conversation — step one above the fold, step two only after the first reply. Hyojin replies personally within one working day.
Yejin runs the studio and personally interviews every applicant for the long-form cohorts. The call below is short, scoped, and written up by email within one working day. It is not a sales meeting; it is a conversation that ends in a clear yes, no, or “take this other path first”.