Step 1
Pick an environment
Start from a tested template, like a Node app, a Linux shell, a Kubernetes cluster or a Python workspace for agents.
Real practice labs inside your coding course
Students open a real environment right in your lesson, ready in about a second. You charge on your own checkout, and we take no cut.
Watch the lesson, then practice on the same page
Your video and a real lab sit in the same lesson, with your brand on both.
cloud pathBuild your first APIWatchPractice
Instructor name
2:14 / 6:30
LabAdd a health check to your API
Now practiceThe lab opens under the video, with your brand on it.
Nothing to install
A recent browser is enough, so lesson one starts with the exercise and not with a broken setup.
A check on every step
Each step confirms the result, like a passing test or a pod in Running, so students know they got it right.
A clean lab every time
If they break something, they start over in a fresh environment. Nobody else's mistakes get in their way.
Sample course and stock footage.
Three steps from lesson to lab
You write the lesson and Labfire runs the lab. There are no servers for you to manage.
- Step 2
Write the exercise and its checks
Say what the student should do and what counts as done. The assistant can draft both, and you try the lab as a student would before you approve it.
- Step 3
Paste the lab into your lesson
Copy the embed into your course page. Each student opens a fresh lab of their own.
- Tested environments for Node, Linux, Kubernetes, Terraform and Python.
- Every lab reports progress, so you see who finished and who's stuck.
You set the price, we take no cut
Students pay you on the checkout you already use. Labfire never touches your course payments.
A higher-priced tier
Keep the videos in your base price and put the labs in a tier that costs more.
A monthly lab subscription
Publish new labs every month and charge for them as a subscription.
A paid cohort with weekly labs
Each week the whole group starts on the same lab, and the checks show you who finished.
What you earn depends on your audience and your price, and Labfire can't promise a number.
Early-access pricing
Simple plans with lab hours included
One lab hour is one student environment running for one hour. Your plan is the only cost, and what students pay you stays with you.
Creator
For instructors selling a course on their own.
$49/ month
Request early access- Lab hours included
- Extra hours billed at cost, with a spend cap you set
- Unlimited labs and lessons
- Node, Linux, Kubernetes, Terraform and Python templates
- Step checks and student progress
- Your logo and colors
- Authoring assistant
- Email support
Bootcamp
For bootcamps that teach live cohorts.
Custom
Talk to us- Everything in Creator
- Custom lab hours and more concurrent labs for live classes
- Usage alerts and per-lab limits
- Priority support
Common questions
How do I get paid?
Students pay you on the checkout you already use, and Labfire doesn't handle course payments or take a cut. To give access, you share a link or a list of your students, and Labfire opens labs only for them.
How do lab hours work and what if I go over?
One lab hour is one student environment running for one hour, and your plan includes hours every month. Extra hours are billed at cost up to a spend cap you set, and you get an alert before you go over.
How are students kept apart?
Every student gets an environment of their own and shares nothing with the rest of the class. Nobody else's work or mistakes can reach it.
Does the AI build the labs for me?
No. The assistant drafts steps and checks from a closed catalog of environments we've tested, and nothing goes live until you review and approve it.
What happens to a student's work when the lab ends?
The lab is temporary and is deleted when the session ends, so nothing in it is kept. That's why every exercise is designed to be finished within one session.
