Each student opens a coding environment right in your lesson, ready in seconds. Nothing to install, and no servers for you to run.
Opens an email to [email protected]
Your lesson and the lab sit in the same page, with your brand on both.
4 min read
Add a health check to your API
A health check is a small route that tells the outside world your API is up. Load balancers and deploy tools call it every few seconds and stop sending traffic when it fails.
Add a GET /health route that answers 200 with a short JSON body. Keep it fast and skip the database, so it still answers when the rest of the app is busy.
app.get("/health", (req, res) => {
res.json({ ok: true });
});Sample course and sample students.
A recent browser is enough, so lesson one starts with the exercise and not with a broken setup.
Each step confirms the result, like a passing test or a pod in Running, so students know they got it right.
If they break something, they start over in a fresh environment. Nobody else's mistakes get in their way.
This is the lab your students get, with the editor, the terminal and goals that turn green. No signup. Fix the broken deployment and watch the checks pass.
A real Kubernetes lab with an editor, a terminal and goals that turn green. It starts in a few seconds and lasts 10 minutes.
You bring the lesson. Labfire gives you the environment, the checks and the embed.
Start from a tested template, like a Node app, a Linux shell, a Kubernetes cluster or a Python workspace.
Say what the student should do and what counts as done. The assistant can draft both, and nothing goes live until you try the lab and approve it.
Copy the embed into your course page. Each student opens a fresh lab of their own.
Let the assistant draft the lab, or write every step yourself. Either way, a real run proves each check before you publish.
Describe the lab in a sentence and the assistant drafts it. You review and approve every step.
Say what students should learn. The assistant drafts the starting state, the steps with checks and hints, and a solution.
Animated recreation of Labfire Studio, part of early access. Every check is proven on a real run before you publish.
Pick a stack and watch a lab for it. Each template comes with the tools already installed.
Logos are trademarks of their owners and only show which technologies a lab can teach.
Every lab reports progress step by step, so you can help a student before they give up.
| Student | Status |
|---|---|
 Ana P. | Finished |
 Luis R. | Finished |
 Kenji M. | Step 2 of 3 |
 Sam K. | Stuck on step 1 |
 Noor A. | Not started |
Sample students and stock photos.
Students pay you on the checkout you already use. Labfire never touches your course payments.
Keep the videos in your base price and put the labs in a tier that costs more.
Publish new labs every month and charge for them as a subscription.
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.
One lab hour is one student environment running for one hour. You pay your plan and any extra hours you allow, up to your cap, and never a cut of your sales.
For instructors selling a course on their own.
$49/ month
Request early accessFor bootcamps that teach live cohorts.
Custom
Talk to usTell us your cohort size and class schedule, and we'll reply with a quote by email.
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.
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 reach it.
Every student gets an environment of their own and shares nothing with the rest of the class. The lab is deleted when the session ends, so nothing in it is kept, and every exercise is designed to be finished within one session.
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.
The lab goes into your lesson as an embed snippet, so it needs a page where you can add custom HTML. Platforms differ on that, so tell us which one you use and we'll check it with you before you start.
Labfire is in early access. Request access with any button on this page or write to [email protected], and we'll reply by email to talk about your course.
