The CloudAdvisory
Faculty of Computing and Information Technology
Agreements & Partnerships Unit
A 14-week DevOps internship where students ship real infrastructure — with public, verifiable proof of what each one built.
Prepared at the request of the Agreements & Partnerships Unit for internal review and circulation to stakeholders within the College. DevOps is our core discipline — the area where our curriculum, our grading infrastructure and our track record are strongest — with Cloud, Data and AI taught around it. Below: who we are, what the program covers, the collaboration models we offer, what a first cohort requires from each side, and how an agreement would be structured. Every figure is published live and links straight to the page that proves it.
The CloudAdvisory at a glance
Grading is automated and runs every day, unattended. Our own Review Agent opens each student's assignment repository, checks that week's files against a fixed rubric — between 1 and 11 files per week, 77 across the program — verifies their published blog and LinkedIn work over HTTP, and writes the result to a public student profile. The same rubric runs the same way every time, for every student, so a mark never depends on which mentor happened to read it. Faculty and employers can audit any grade against the student's actual assignment repository rather than take a certificate at face value.
Who we are
The CloudAdvisory Oy is a Finland-registered training and consulting company. Our strongest discipline, and the one this proposal is built around, is DevOps. Our flagship program is DMI — the DevOps Micro Internship with Agentic AI: a 14-week, mentor-led internship in which students build, debug, deploy and operate real infrastructure rather than complete exercises. Cloud platforms, Data and AI are taught inside that DevOps spine, not as separate subjects. Our lead trainer and CTO, Pravin Mishra, has taught over 70,000 learners worldwide.
We built DMI to close one specific gap: graduates who understand cloud concepts in theory but have never had to make them work end-to-end, under review, on a deadline.
What the 14 weeks cover — the DevOps spine
- Linux & Bash
- Git and GitHub
- The DevOps lifecycle
- AWS & Azure
- Terraform & Ansible
- CI/CD — GitHub Actions & Azure DevOps
- Docker & Kubernetes
- Capstone project
Agentic AI runs through every module as a working tool inside real DevOps tasks — not taught as a separate track bolted on at the end.
- 14 weeks · 77 graded assignments · 7 real applications · 24 deployments
- AWS and Azure · 6 capstones plus a final project · 10 AI-assisted assignments
- Every one of those is a reviewable artifact in the student's own assignment repository — a pipeline, an infrastructure-as-code project, a running deployment — not a record of attendance.
Collaboration models we offer
Campus cohort Most common start
A full DMI DevOps cohort for one department or the placement cell, delivered as an elective, a capstone track, or placement-readiness training. Cloud, AI & Data variants available.
Micro-internship
Flexible micro-internship cohorts pairing mentorship with real project work, run alongside existing coursework rather than in place of it.
Certification preparation
Focused, hands-on AWS and Azure certification training, for students or for faculty and technical staff — including the DevOps-track certifications on both clouds.
Custom / enterprise scope
Training scoped to specific outcomes, timelines and delivery constraints — including programs run with the University's industry partners.
Delivery in practice
- Delivered online, in English, so it runs alongside the existing timetable and requires no change to campus facilities or scheduling arrangements.
- Time zones align. Riyadh is UTC+3 and Helsinki is UTC+2/+3, so live sessions and mentor availability fall inside the normal KAU working day — no unsociable hours for students or faculty.
- Scheduled around the KAU academic calendar, including semester dates and examination periods, which we would fix together in the discovery call.
- Faculty co-mentor alongside our team throughout, so the capability transfers to KAU rather than remaining with an external vendor.
- Progress is visible to the College continuously — per-student dashboards and a cohort leaderboard, not a single report at the end.
Why this fits Vision 2030
DevOps is the discipline that turns a digital-transformation strategy into systems that actually run, and it is the skill Saudi employers are hiring for now. Every deliverable a student produces is a real, reviewable artifact — a CI/CD pipeline, an infrastructure-as-code project, a live deployment — not a certificate of attendance. That maps directly onto Vision 2030's workforce-readiness and digital-transformation priorities, and gives the College something a training certificate cannot: public, gradeable evidence of what each graduate can actually build, auditable by any employer at any time.
What a first cohort requires from each side
The CloudAdvisory provides
- Curriculum, assignments and all learning materials
- Mentor-led delivery across the 14 weeks
- Automated daily grading and public student profiles
- Co-mentor training and handover for KAU faculty
- Cohort reporting to the College throughout
KAU provides
- A nominated academic owner within the Faculty
- One limited student group for the pilot cohort
- One or more faculty co-mentors
- Confirmed calendar slot within the semester
- Agreed success metrics for review at the end
How a partnership usually starts
- A short discovery call on curriculum fit, calendar and success metrics.
- One program, one limited pilot cohort, with clear agreed outcomes — not a change to the existing curriculum.
- Faculty co-mentor alongside our team, so the capability transfers to KAU.
- Review against the agreed metrics, and only then a decision on whether and how to scale.
Agreement & commercial approach
- Contracting party: The CloudAdvisory Oy, a company registered in Finland (business ID 3419631-2), Espoo.
- Instrument: we are happy to work to King Abdulaziz University's standard MoU or services-agreement template, or to provide a draft for the Unit to review — whichever is faster for your internal process.
- Scope and term: we would propose scoping the first agreement to a single pilot cohort with a defined term, rather than an open-ended framework, so both sides can review against evidence before committing further.
- Pricing: quoted once outcomes, cohort size and delivery scope are defined — never before. We would rather size it correctly against the pilot than send a number that has to be renegotiated.
- Student data: student results are published to public profiles as part of the program's design. What is published, and any consent process the College requires, is something we would agree explicitly before a cohort starts.
Verify this yourself — every link, in one place
Nothing in this document has to be taken on trust. The figures above are clickable, and every page behind them is listed again here so none of it depends on spotting a link earlier. All of it is public and updated daily.
The online meeting you offered
We would welcome the meeting the Unit proposed, and suggest a 20–30 minute call covering curriculum fit, the academic calendar, and what a first pilot cohort at the Faculty of Computing and Information Technology would look like. We are glad to work to whatever time suits the College.
Arrange the meeting →
Milla Leppänen — Co-founder · milla.leppanen@thecloudadvisory.com
Pravin Mishra — Co-founder & CTO, lead trainer