Stop teaching deployment. Let them ship it.
ZeroTo Labs gives every student a real production workflow — GitHub to container, custom domain with HTTPS, and CI/CD on every push — so they walk into interviews having done it, not watched it.
placement-portal
main · auto-deploy on
Clone
Build
Push
Deploy
▲ push to main · 3f9c2e1 “add payments page”
Three levels, one real workflow
From first push to production-grade shipping
Each level unlocks a skill recruiters actually ask about. No simulators, no screenshots of someone else's terminal.
Deploy from GitHub
Paste a repo. It's cloned, built into a Docker image, pushed to a registry and scheduled onto a real node — with live build logs every step of the way.
- Dockerfile-based builds
- Live build + runtime logs
- CPU & memory limits
Custom domain + HTTPS
Students point a domain they own at the platform. A TLS certificate is issued and renewed automatically, and traffic is routed by SNI.
- DNS setup walkthrough
- Auto-issued certificates
- Automatic renewal
CI/CD on every push
Connect a signed GitHub webhook and every push to the branch triggers a fresh build and redeploy — exactly how teams ship at work.
- HMAC-verified webhooks
- Build history per commit
- Rollback by redeploy
By the end, every student can honestly write: “Deployed a containerized app to a custom domain with HTTPS and CI/CD.”
Everything in the box
A real platform, built for a classroom
The rigor of a production PaaS, with the guard-rails a cohort of first-time deployers needs.
Live build & runtime logs
Students watch their image build line by line and read their app's own stdout — the debugging loop that actually teaches.
#7 [4/5] RUN npm run build
#7 12.4 ✓ Compiled successfully
==> Build succeeded — starting your app
Isolated by default
Every student gets their own namespace. No shared servers, no stepping on each other's work.
Fair resource limits
CPU, memory and build minutes are capped per plan, so one runaway build never slows the cohort down.
Feature-based plans
Seats plus per-student limits, with Levels 2 and 3 switched on per plan. Start small, unlock more as the cohort grows.
Bulk onboarding
Invite a whole batch from a CSV. Resend, revoke or remove in one click — seats free up instantly.
Self-healing apps
Crashed containers restart automatically, and nodes that drop out get their workloads rescheduled.
Multiple admins
Add your TPO, faculty coordinators and mentors as admins. They don't use student seats.
FAQ
Questions placement cells ask us
Do students need to know Docker already?
No. They need a repository with a Dockerfile — the new-deployment screen shows a working example, and build logs make it obvious what went wrong when something does.
Is this a simulator?
No. Every deployment is a real image built from the student's repo, running as a real container, reachable over a real domain with a real TLS certificate.
Who can sign up?
Nobody — access is invite-only. We onboard your university and its admins; your admins invite students individually or in bulk from a CSV.
What happens when a student leaves the program?
An admin removes them in one click. Their apps are stopped, their domains released, and the seat becomes available for someone else.
Can we change our plan mid-semester?
Yes. Seats, limits and features can be adjusted at any time and take effect immediately.
Do students need a domain?
Only for Level 2. Any domain or subdomain they control works; the platform walks them through the DNS record and issues the certificate automatically.
Give your next batch something real to talk about in interviews.
Set up your campus in a day. Students ship their first app in an afternoon.