The environment is waiting when the student scrolls to it, so the lesson starts with the exercise.
Students get the tools the lesson needs, whether that's Node and a database, a Kubernetes cluster, a Terraform workspace or Python for building agents.
A step can confirm the result, like a passing test or a pod in Running, and you can see who's stuck.
Your logo and colors sit on the lab, so students stay inside your course from the video to the terminal.
Start from a tested template for the stack you teach, such as a Node app, a Linux shell, a Kubernetes cluster or a Python workspace for agents.
Write the instructions and the checks. The authoring assistant can draft both from Labfire's tested catalog, and nothing goes live until you approve it.
Paste the snippet into your course page. Each student gets a fresh environment of their own, and it's deleted when they finish.
student@lab:~/api$ npm test
✓ GET /health returns 200
student@lab:~/api$ curl -s localhost:3000/health
{"status":"ok"}
student@lab:~/api$ You sell a frontend, backend, DevOps or AI course on your own site or a course platform, and you'd rather not run a server for every student.
You have several courses and a growing student list. You want labs that look like your brand and a cost per student you can plan around.
You teach live cohorts in web development, DevOps or AI, and the whole class needs the same environment ready when the session starts.
One VM-hour is one student environment running for one hour.
Early-access prices. Extra VM-hours from $[x.xx] per hour, and you set the limits.
[N] VM-hours each month
Unlimited labs and lessons
Frontend, backend, infra and AI agent templates
Step checks and student progress
Your logo and colors
Authoring assistant
Email support
[N] VM-hours each month
Everything in Creator
Multi-node Kubernetes clusters
More concurrent sessions for live classes
Cohort and group management
Usage alerts and per-lab limits
Priority support