Skip to content
Back up or restore your progress

Back up my progress

Progress is saved only in this browser. Copy a code before clearing site data or switching devices, then paste it back on the other side.

MISSION: 90 DAYS · DEVOPS

From developer to DevOps engineer in 90 days.

A free, hands-on curriculum that takes you from your first terminal command to job-ready — one focused lesson a day, with a story-driven mission to fix a broken system at the end of every week.

~80 hrs core · free, no signup · progress saved in your browser

All 90 days and 10 missions are live now — free, no signup.

mission: server-down 
student@prod-web-01:~$ ps aux --sort=-%cpu | head -3
USER    PID  %CPU  COMMAND
root   4521  94.0  /opt/scripts/nightly-backup.sh
student@prod-web-01:~$ kill 4521
student@prod-web-01:~$ systemctl restart nginx
student@prod-web-01:~$ curl -so /dev/null -w '%{http_code}\n' localhost
200
# 02:07 — the site is back. You did that.

Before you dive in

Is this for you?

Good fit if you're

  • — a developer who wants to understand the infra your code runs on
  • — self-taught and looking for a structured, project-based path into DevOps/SRE
  • — comfortable typing commands in a terminal, even if you've never called yourself "technical"

Maybe skip it if

  • — you're already running production Kubernetes and CI/CD day to day — you'll outpace the early days fast
  • — you want a certification exam, not a hands-on curriculum
  • — you're not near a computer you can install software on and can't use a free browser-only option (see no-install setup)

Before you start

  • — no prior coding required — missions are played in a browser terminal, no code to write
  • — Phase 3 (Cloud) uses a real AWS account; every step is built to stay near the free tier, with an explicit teardown at the end of each lab, but keep an eye on your bill
  • — progress is saved only in this browser's local storage — no account, no email. Back up a code before clearing site data (below) or switching devices
Already know some of this? Jump ahead

Start at Day 1 if you're new to any of this — each day builds on the last. If you've already got a whole phase down elsewhere, mark it done and the hub will pick up right after it.

  • Foundations

    0/20 done

  • Containers & CI/CD

    0/25 done

  • Cloud

    0/20 done

  • Orchestration & IaC

    0/20 done

  • Job Ready

    0/5 done

How it works

Three layers. Forty-five minutes a day.

Every day has the same shape, so you always know what "done" looks like — and the optional depth is there on the days you want more.

Every day

Core lesson

45–60 min

One focused lesson a day — read it, run the commands, understand the why. This is the spine of the whole program.

Optional

Go Deeper

+30–60 min

Extra rabbit-holes for the days you have the time and the appetite — always optional, never assumed by the next lesson.

Weekly

Mission game

15–20 min

End the week inside a broken system and fix it live in your browser — a story-driven mission, no setup, no code required.

The Journey

Five phases, ninety days.

From your first terminal session to a portfolio and interview answers. Jump straight to any phase in the full plan below.

  1. Foundations

    Linux, the terminal, and the habits everything else builds on.

    Days 1–20 0/20

  2. Containers & CI/CD

    Docker from first principles, then pipelines that ship it for you.

    Days 21–45 0/25

  3. Cloud

    AWS fundamentals — from a safe account to a deployed, monitored app.

    Days 46–65 0/20

  4. Orchestration & IaC

    Kubernetes to run at scale, Terraform to define it all in code.

    Days 66–85 0/20

  5. Job Ready

    Turn 90 days of work into a resume, a portfolio, and interview answers.

    Days 86–90 0/5

Preview Phase 5: the job-ready interview hub →

Missions

Every week ends in a broken system.

The theory sticks when you use it under pressure. Each mission drops you into a failing system with a terminal and a goal — no slides, no multiple choice.

All missions
mission-01 · server-down

Week 1 · Playable now

Server Down!

Playable

The web server died at 2 a.m. and you're the only one awake — find it, fix it, bring it back.

  • No setup
  • Runs in your browser
  • No programming required

Skills: Linux navigation · processes & signals · file permissions

Play Server Down!

Next up

7 more playable missions across the program — Docker Rescue, Broken Pipeline, AWS Bill Shock, Database Recovery, Kubernetes Chaos, Terraform Trouble, The Midnight Outage.

The Plan

All 90 days, in order.

Tick a day as you finish it — saved in this browser only, no account.

Plan your pace

Pick how many days a week you can realistically commit, and see when you'd finish the days you have left.

Days per week

Pick a pace above to see your projected finish date.

0 of 90 days complete

Foundations

Linux, the terminal, and the habits everything else builds on. · Days 1–20

0/20
  1. What DevOps actually is + your first terminal session ~50m
  2. The Linux filesystem: where everything lives ~50m
  3. Navigating & managing files — pwd, ls, cd, cp, mv, rm ~45m
  4. Reading & editing files — cat, less, nano, vim survival ~45m
  5. Users, groups & permissions — chmod, chown, octal ~55m
  6. Processes & signals — ps, top, kill, nice ~50m
  7. Week 1 review + Server Down! ~45m Playable
  8. Text power tools — grep, sed & awk one-liners ~55m
  9. Pipes, redirection & command chaining ~50m
  10. Packages & services — apt, systemd, journalctl ~55m
  11. Networking 101 — IP, DNS, ports, curl ~55m
  12. Networking 102 — ss, dig, ping, a troubleshooting flow ~50m
  13. SSH deep-dive — keys, config, scp, tunnels ~55m
  14. Week 2 review + DNS Detective ~45m Playable
  15. Shell scripting 1 — variables, conditionals, loops ~55m
  16. Shell scripting 2 — functions, exit codes, a real backup script ~55m
  17. Git for DevOps — branching, merge vs rebase ~50m
  18. Git collaboration — PRs, reviews, tags, releases ~45m
  19. Cron & scheduled jobs — crontab, systemd timers ~45m
  20. Phase 1 review — Linux interview drill ~45m

Containers & CI/CD

Docker from first principles, then pipelines that ship it for you. · Days 21–45

0/25
  1. Week 3 review + The Locked File ~45m Playable
  2. Containers vs VMs — what Docker actually does ~50m
  3. Docker fundamentals — images, containers, registries ~55m
  4. Dockerfiles — writing & optimizing your first image ~60m
  5. Docker networking & port mapping ~50m
  6. Volumes & persistent data ~50m
  7. docker compose — multi-container apps ~55m
  8. Week 4 review + Docker Rescue ~45m Playable
  9. Image best practices — multi-stage builds, size, security ~55m
  10. Container debugging — logs, exec, inspect, stats ~50m
  11. CI/CD concepts — pipelines, environments, artifacts (+ Jenkins legacy aside) ~45m
  12. GitHub Actions 1 — workflow anatomy, triggers ~55m
  13. GitHub Actions 2 — jobs, matrices, secrets ~55m
  14. GitHub Actions 3 — build & push an image to a registry ~60m
  15. Week 5 review — harden your pipeline ~45m
  16. Testing in pipelines — lint, unit tests, quality gates ~50m
  17. Versioning & releases — semver, tags, changelogs ~45m
  18. Deploy strategies — rolling, blue-green, canary ~45m
  19. Pipeline security — secrets management, image scanning (Trivy), supply-chain basics ~50m
  20. Phase 2 review + Broken Pipeline ~45m Playable
  21. Project 1, Day 1: scope & scaffold ~60m Project
  22. Project 1, Day 2: write & optimize the Dockerfiles ~60m Project
  23. Project 1, Day 3: compose the full stack locally ~60m Project
  24. Project 1, Day 4: build the CI pipeline ~60m Project
  25. Project 1, Day 5: ship, tag & write the README ~60m Project

Cloud

AWS fundamentals — from a safe account to a deployed, monitored app. · Days 46–65

0/20
  1. Cloud fundamentals — regions, AZs, shared responsibility ~45m
  2. AWS account hygiene — IAM, MFA, budgets, cost tagging ~55m
  3. EC2 — launch, connect, security groups ~55m
  4. Week 7 review + AWS Bill Shock ~45m Playable
  5. VPC 1 — subnets, route tables, gateways ~55m
  6. VPC 2 — NAT, public vs private, bastion patterns ~55m
  7. S3 — buckets, policies, static hosting, lifecycle ~50m
  8. RDS & managed databases ~50m
  9. Load balancers & auto scaling ~55m
  10. Route 53 & TLS with ACM ~50m
  11. Week 8 review + Database Recovery ~45m Playable
  12. CloudWatch — metrics, logs, alarms ~50m
  13. AWS CLI & scripting cloud operations ~50m
  14. ECR + ECS/Fargate — containers on AWS (Go Deeper: where Lambda fits) ~60m
  15. Observability 1 — Prometheus & Grafana fundamentals ~55m
  16. Observability 2 — alerts, SLOs & log aggregation (Loki) ~50m
  17. Project 2, Day 1: plan the AWS architecture ~60m Project
  18. Project 2, Day 2: network & IAM groundwork ~60m Project
  19. Project 2, Day 3: deploy containers behind a load balancer ~60m Project
  20. Project 2, Day 4: DNS, TLS & monitoring ~60m Project

Orchestration & IaC

Kubernetes to run at scale, Terraform to define it all in code. · Days 66–85

0/20
  1. Why Kubernetes — the problems it solves ~45m
  2. K8s architecture + kubectl with kind on WSL2 ~55m
  3. Pods & Deployments ~55m
  4. Services & networking in K8s ~55m
  5. ConfigMaps & Secrets ~50m
  6. Health probes & resource requests/limits ~50m
  7. Debugging workloads — describe, logs, events, crashloops ~55m
  8. Week 11 review + Kubernetes Chaos ~45m Playable
  9. Ingress & exposing apps properly ~55m
  10. Helm — charts, values, releases (Go Deeper: GitOps with Argo CD) ~55m
  11. IaC concepts + Terraform first apply ~50m
  12. Terraform 2 — variables, outputs, state ~55m
  13. Terraform 3 — modules & workspaces ~55m
  14. Terraform + AWS — provision the project infra ~60m
  15. Week 12 review + Terraform Trouble ~45m Playable
  16. Project 3, Day 1: design the capstone architecture ~60m Project
  17. Project 3, Day 2: write the Terraform foundation ~60m Project
  18. Project 3, Day 3: build the Kubernetes manifests ~60m Project
  19. Project 3, Day 4: Helm, ingress & TLS ~60m Project
  20. Project 3, Day 5: end-to-end run & writeup ~60m Project

Job Ready

Turn 90 days of work into a resume, a portfolio, and interview answers. · Days 86–90

0/5
  1. Your DevOps resume — turning 90 days into bullets ~50m
  2. Portfolio & GitHub polish — READMEs, diagrams, demos ~50m
  3. Incident management — severity, runbooks, postmortems, error budgets ~55m
  4. Interview drill — rapid-fire across the stack + scenario walk-throughs ~55m
  5. FINAL BOSS: The Midnight Outage + what's next ~60m Playable

FAQ

Before you start.

Tap a question to expand the answer.

Is it really free?

Yes — completely. All 90 days and every mission, with no account, no email capture, no paywall and no upsell. It runs as static pages in your browser, so there is nothing to bill you for, and your progress is saved locally in your own browser.

How much is available right now?

Everything. All 90 days and every weekly mission are live and free to use today — no account, no email wall, no paywall. Start at Day 1, or jump straight to any phase from the plan above, and go at your own pace; your progress is saved locally in this browser.

I only have 30 minutes some days — will I fall behind?

No. The core lesson is built to fit in 45–60 minutes, and on a tight day you can do just the essentials and skip the optional "Go Deeper" section entirely. Nothing in the next day assumes you did the optional depth, so a short day never leaves a hole. Go at the pace your life allows.

Do I need a Linux machine?

No. On Windows you will use WSL2 (the Windows Subsystem for Linux), which gives you a real Linux environment in a few minutes; macOS uses Multipass and Linux works directly. The Day 0 setup at /mission-90/setup/ covers all three, plus a browser-only option (Codespaces or Cloud Shell, /mission-90/setup/#no-install) if you cannot install anything at all.

What if I miss days?

Nothing breaks. The program is a sequence, not a calendar — Day 12 always comes after Day 11, whenever you get to it. There is no streak to lose and no shame screen for a gap. Pick up exactly where you left off; the plan remembers your place in this browser.

Will this actually get me a DevOps job?

Honestly: it gives you the skills, the projects and the vocabulary, but no curriculum can guarantee a job. What you get here is a genuine foundation across Linux, containers, CI/CD, cloud, Kubernetes and Terraform, plus a portfolio of real projects and interview practice. The rest depends on you, your applications and the market you are in.

Who’s building this

Built in public by Pushkar — one day at a time.

I’m a platform / DevOps engineer, and I’m writing this the way I actually work: every command is run on a real Linux box before it ships, and each mission is a system I’ve broken and fixed for real. The whole thing is published in the open as it’s written — no ghostwriters, no content farm — so when a lesson is wrong it gets fixed fast, in public.

OpsCanopy is also where I keep my other free, client-side DevOps tools — same principle: no signup, nothing leaves your browser. That’s the standard this curriculum is held to.

Follow the build on GitHub Updates on X See the OpsCanopy tools Ask a question

Day 1 is a terminal and a problem to solve.

Ninety days from now, debugging a full-stack outage will feel routine. Day 1 is live and free right now — no signup, and your progress stays in your browser.

Read Day 1 free Prefer the hands-on labs? Set up your lab (Day 0 · ~20 min)

All 90 days are live — follow along for updates and what’s next:

Subscribe via RSS or follow the build on GitHub · X

No email, no account — just the feed and the public build log.

Founding note: I’m building this in the open, one day at a time. If you play Day 1 or the first mission, I’d genuinely like to hear your reaction — email hello@opscanopy.com and tell me what landed and what didn’t. The early feedback shapes the days that aren’t written yet.