Support The Project
Keep the labs free, clean, and useful for students who are learning DevOps at home.
This project should not become an ad wall. The public lab guides, learning paths, safety runbooks, and project catalog stay open. Support is for people and organizations who want the portal maintained, reviewed, and expanded without interrupting the learning experience.
Clean funding model
What Support Funds
Support helps pay for documentation review, modern lab updates, screenshots, diagrams, testing time, dependency updates, and new student-friendly DevOps projects.
Ways To Support
Section titled “Ways To Support”Contribute because the free labs helped you learn, build a portfolio, or prepare for interviews.
Best fit: learners, mentors, and community members.Support a practical DevOps learning resource without placing ads inside the lab flow.
Best fit: cloud, DevOps, security, observability, and training companies.Purchase templates, checklists, or guided support while the core labs remain public.
Best fit: students who want a faster route from lab work to portfolio proof.Sponsor Principles
Section titled “Sponsor Principles”- No display ads.
- No popups.
- No tracking-heavy funnels.
- No paywall on the core lab guides.
- No sponsored ranking of projects.
- No credential sharing or managed access to student cloud accounts.
- Sponsor mentions should be quiet, relevant, and clearly labeled.
Current Funding Links
Section titled “Current Funding Links”Funding links can be added here after the accounts are ready:
| Channel | Use For | Status |
|---|---|---|
| GitHub Sponsors | Individual monthly or one-time support | Ready to connect |
| Open Collective | Transparent project funding and company sponsorship | Ready to connect |
| Premium Kit | Paid templates, workbook, and portfolio assets | Page ready |
| Accelerator | Guided cohort, review, and support | Page ready |
| School/Team Use | Curriculum licensing or classroom support | Page ready |
Sponsor Brief
Section titled “Sponsor Brief”Sponsors should support the mission, not control the curriculum.
Good sponsorship looks like:
- Helping keep the project free for learners.
- Funding updates for cloud, Kubernetes, CI/CD, DevSecOps, and observability labs.
- Supporting documentation quality, accessibility, and cleanup guidance.
- Being listed on a sponsor page or brief mention, not inserted into every lab.
Bad sponsorship looks like:
- Ads inside the learning flow.
- Tool lock-in disguised as curriculum.
- Requiring students to create accounts before they understand the lab.
- Asking for access to student credentials or cloud accounts.
Next Step
Section titled “Next Step”Use the Premium Kit for paid self-serve resources, the Accelerator for guided support, or For Schools for classroom and team use.