Courses every student can run
BrowserPod is a microVM that runs in the browser. Give every student a real terminal and real runtimes in the lesson, with nothing to install and nothing for you to host.
Why it works for teaching
Setting up a toolchain is where many lessons lose students before they write a line of code. BrowserPod puts the real runtime in the lesson, with the exercise's files already in place.
Each student's pod runs on their own device, so a whole class running the same exercise costs you nothing and never queues. Pods start without downloading a full image, and a storageKey keeps a student's progress between visits.
The library is free for any use. When exercises need npm, GitHub or an API, add BrowserPod Edge.
What you need to know
Serve the pages that run pods with Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp.
What people build
Courses and workshops
A whole class runs the same exercise at once, each on their own device.
Coding exercises
Each exercise seeds its files, so students start exactly where the lesson is.
Educational apps
Learning tools with a real terminal and real runtimes inside them.
Classroom labs
Lab sessions that run in the browser, with nothing to install on school machines.
What your students get
The real tools, in the lesson, with nothing to install and nothing for you to host.
-
Embeddable
A pod goes inside the lesson, next to the exercise it belongs to.
-
Node.js, Rust, git, bash, npm
Students work with the real Node.js, Rust, git and bash, not an imitation.
-
No concurrency limits
A whole class can run the same exercise at the same time.
-
Runs on the user's device
Every student's work runs on their own device, so a busy term costs you nothing.
-
Loads on demand
Lessons start without downloading a whole image, and progress can persist between visits.
From exercise to lesson
-
Add the package
npm i @leaningtech/browserpod in your course site.
-
Set two headers
Serve the page cross-origin isolated with COOP and COEP.
-
Seed the exercise
Write the exercise's files into the pod when the lesson loads.
-
Let students run it
Attach a terminal and let them run, edit and break things safely.
A runnable exercise
Seed the exercise into the pod and open a shell in it, right in the lesson.
import { BrowserPod } from "@leaningtech/browserpod";
const pod = await BrowserPod.boot({ storageKey: "lesson-1" });
const terminal = await pod.createDefaultTerminal(document.querySelector("#lesson"));
const file = await pod.createFile("/home/user/exercise.js", "utf-8");
await file.write(`// Make this print "Hello, class"`);
await file.close();
await pod.run("bash", [], { terminal, cwd: "/home/user" }); Questions
Do students need an account?
No. Pods run in their browser with no sign-up.
Can a whole class run at once?
Yes. Each student's pod runs on their own device, so a whole class running the same exercise never queues.
Can students break something?
Only their own pod. Each student's work runs in their own browser, apart from your site and from every other student.
Can progress be saved?
Yes. Boot with a storageKey and the student's files persist in the browser between visits.
Can we self-host BrowserPod?
Yes. Enterprise covers self-hosting the runtime and the network stack, vendoring it into your build and redistributing it in your product.










