No concurrency limits
As many pods as you have users
Every session runs on its own device, so there's no shared pool to exhaust, no queue and no quota to raise.
Scale that comes for free
Unlimited concurrency
A thousand users means a thousand pods, each on its own device.
No queue
Resources are reserved on the user's device the moment they open your app.
No degradation under load
Sessions don't compete for an aggregated pool of RAM and CPU.
Free at any scale
Compute costs you zero, whether you have ten users or ten million.
Why there's no limit
BrowserPod has no shared pool of machines. Each pod is the user's own browser doing the work, so more users never means more capacity to buy or a queue to wait in.
When a thousand people open your page, a thousand pods boot on a thousand devices, and none of them competes with another for CPU or memory. The only thing that grows with your users is the network traffic of pods connected through Edge.
So there's no concurrency quota to raise and no capacity to plan, however many people arrive at once.
What you need to know
Edge meters connected pod-hours, so network cost follows the pods that actually use the internet, and keyless pods cost nothing.
One pod per user
The same few lines boot a pod for every visitor. There's no capacity to configure.
import { BrowserPod } from "@leaningtech/browserpod";
// Boot a pod, no API key needed
const pod = await BrowserPod.boot();
const terminal = await pod.createDefaultTerminal(document.querySelector("#console"));
await pod.run("bash", [], { terminal, cwd: "/home/user" }); Questions
How many pods can run at once?
Unlimited. Pods run on your users' devices, so there's no server-side pool and no concurrency quota.
Do I pay more as I grow?
Not for compute, which is free. Only BrowserPod Edge, if your pods need the internet, is metered per connected pod-hour.
What happens during a traffic spike?
Pods boot on the devices of whoever arrives, so a spike needs no extra capacity from you.
Are boots or API calls limited?
Keyless pods aren't metered at all. With Edge, each connected pod uses time from your monthly hours, in one-hour blocks.










