Learn cloud on real infrastructure

A free programme for engineering students and the colleges that teach them: hands-on labs in Linux, Python, Docker, Kubernetes and infrastructure as code, then real work on a real product. Every term is on this page, including the ones that are less exciting.

Three steps, all in the open

Each step is free, and anyone can start the first one. You can stop after any step and keep what you built.

  1. 01

    Learn

    Who
    Anyone. No selection.
    How long
    Self-paced, about 8 weeks alongside college

    Hands-on labs on real Linux machines and containers, from your first shell command to deploying on Kubernetes with Terraform. Monthly online lab nights where you can ask questions.

    You leave with: A public GitHub portfolio of everything you built

  2. 02

    Prove

    Who
    Anyone who finishes a track.
    How long
    Two to three weeks

    One capstone: take a small app from a laptop to a monitored deployment, written as code. Or build it at one of our hackathons. Then a 30-minute conversation about how you did it.

    You leave with: Written feedback on your capstone, whether or not you go on

  3. 03

    Build

    Who
    Four to six people per batch.
    How long
    8 to 12 weeks, listed on the AICTE internship portal

    Real tickets on the CoverOps product: cloud connectors, Kubernetes tooling, infrastructure as code, tests. A named mentor, a weekly review, and code that ships to customers.

    You leave with: A certificate for completed work and a letter describing what you built

What you will learn

Ten tracks, in the order the job uses them. Each lab ends with a check you can run yourself, so you know it works before anyone reviews it. The first track opens with the first batch.

01 Linux and the shell
Files, processes, permissions, networking, and the commands you will type every day.
02 Bash scripting
Automating the boring parts, safely: quoting, exit codes, traps, cron.
03 Git and GitHub
Branches, pull requests, reviews and the history that saves you at 2 a.m.
04 Python for operations
Scripts that talk to APIs, parse logs and survive bad input.
05 YAML and JSON
The configuration languages every tool below is written in, and their traps.
06 Docker
Images, layers, networks and volumes. Building small, secure containers.
07 Kubernetes
Pods to deployments, services, config, scaling, and reading a failing cluster.
08 Infrastructure as code
Terraform: plan, apply, state, modules, and reviewing a change before it lands.
09 CI/CD
Pipelines that test, build and deploy on every push, with a way back.
10 Cloud and its cost
AWS basics, IAM done properly, and why a forgotten instance is a real bill.

The terms, stated plainly

Read these before you apply. They are the same terms your college signs.

No fee, ever
Not for training, not for a certificate, not for an internship. If anyone asks you to pay for a CoverOps programme, it is not us. Write to office@coverops.dev.
Unpaid, for now
CoverOps is a young company with no revenue yet. We would rather tell you that than promise a stipend we cannot pay. This changes when revenue does, and the page will say so.
Small on purpose
Two founders mentor every intern. Four to six people per batch is what we can do properly.
Certificates mean something
Issued for completed work only, with a letter saying what you actually built. No attendance certificates.
What is yours, what is ours
Your labs, capstone and portfolio are yours. Code you write inside the product belongs to CoverOps and stays confidential, under a short agreement you sign before Build.
No job is promised
When we hire, people who finished Build are the first we talk to. That is the whole promise.

For colleges

We are starting close to home, in Karimnagar district, with the college our founder graduated from. Any engineering college can ask for the same arrangement.

What CoverOps provides

  • Guest lectures and hands-on workshops on cloud, DevOps and cloud cost, on campus
  • Faculty development sessions on the same stack, so the labs can live in your electives
  • Final-year projects built on real problems from a working product, with a mentor from industry
  • Hackathons run on our own platform, with problem statements, judging and certificates
  • Internships listed on the AICTE portal, with attendance and evaluation shared with you
  • Activities your Institution's Innovation Council can report on its calendar

What we ask of the college

  • A faculty coordinator we can plan with
  • A lab or seminar hall with internet on workshop days
  • Help reaching students: notices, nominations, the AICTE listing
  • One signed MoU. No money changes hands in either direction.

Hackathons and events

The first ones are being planned now. Dates appear here once a college has confirmed them, not before.

One-day workshop
On campus. Linux to a running container in a day, on your own laptop.
24-hour hackathon
Real problem statements from cloud operations: cost, reliability, automation.
Monthly lab night
Online. Work through a lab together and ask anything.
Demo day
Each Build batch shows what it shipped to faculty, students and the next batch.

Apply, or bring it to your college

It reaches office@coverops.dev. We reply from there within a few working days.

I am

By sending this you have read the terms. Nothing here costs you anything.