For Schools And Teams
Use DevOps Projects as a practical lab catalog for classrooms, bootcamps, workforce programs, study groups, and junior engineering teams.
The public portal remains open. Schools and teams can pay for curriculum support, instructor materials, custom sequencing, private review sessions, and implementation help.
Classroom and team use
What You Can License
License the structure around the free labs: recommended routes, instructor notes, assessment rubrics, cleanup policies, portfolio proof requirements, and support sessions for students or junior engineers.
Use Cases
Section titled “Use Cases”Use selected labs as a DevOps, CI/CD, Kubernetes, Terraform, or DevSecOps module.
Best fit: 2-6 week units with defined outcomes.Give students structured home labs, safety guidance, and portfolio-ready proof expectations.
Best fit: cloud computing, platform engineering, security, or software delivery courses.Help junior engineers practice delivery workflows without touching production systems.
Best fit: onboarding, mentorship, and platform team enablement.Classroom Package
Section titled “Classroom Package”| Component | What It Gives Instructors |
|---|---|
| Route map | Which labs to assign by student level and course goal |
| Instructor notes | Prerequisites, expected blockers, and review prompts |
| Assessment rubric | What counts as working proof, partial proof, and cleanup proof |
| Safety checklist | Credential, cost, cloud, and secrets review before students provision resources |
| Student templates | README, architecture note, screenshot log, troubleshooting note |
| Review sessions | Optional live walkthroughs, Q&A, or portfolio review |
Suggested Licensing
Section titled “Suggested Licensing”| Package | Price Range | Best For |
|---|---|---|
| Classroom Starter | $499-$999 | One cohort, route map, templates, instructor notes |
| Cohort Support | $1,500-$3,500 | Starter plus live sessions and student Q&A |
| Team Enablement | $2,500-$7,500 | Custom sequence, internal workshop, review session |
These are starting points, not hard rules. Pricing should reflect cohort size, support depth, live delivery, and whether custom materials are needed.
Recommended Routes
Section titled “Recommended Routes”| Audience | Route |
|---|---|
| Absolute beginners | Linux basics, local validation, GitHub Actions, one local Kubernetes lab |
| Cloud learners | Safety guide, AWS basics, Terraform/OpenTofu, one cleanup-heavy cloud lab |
| Kubernetes learners | Docker packaging, manifests, GitOps, progressive delivery |
| Security learners | Secrets hygiene, Trivy, SBOMs, signing, supply-chain security |
| Portfolio builders | One local lab, one CI/CD lab, one IaC lab, one capstone |
Instructor Safety Notes
Section titled “Instructor Safety Notes”- Students must use their own credentials.
- Never collect student cloud keys.
- Prefer local-first labs before paid cloud work.
- Require budget alerts before cloud projects.
- Require cleanup evidence after cloud projects.
- Treat screenshots as proof only after secrets are removed.
What To Ask Before A Cohort
Section titled “What To Ask Before A Cohort”- How many students are in the cohort?
- What operating systems do they use?
- Will the course allow cloud accounts, or should labs stay local-first?
- Which tools are required: AWS, Azure, Docker, Kubernetes, Terraform, GitHub Actions, Jenkins, Argo CD, Trivy?
- Is the goal learning, portfolio proof, certification support, or internal team enablement?
Next Step
Section titled “Next Step”Start with the Start Here routes and the Credentials and Cost Safety guide. Then choose whether the group needs self-serve templates from the Premium Kit or live support through the Accelerator.