Portals
A public URL for a server in the tab
When a program in a pod opens a port, Portals give it a public URL. Anyone you send the link to can reach the running server.
Share what's running
A URL for every port
Bind a port and BrowserPod hands you a public hostname that routes to it.
HTTP and WebSockets
Inbound requests and WebSocket connections reach the server inside the pod.
Demos that are the product
Send a link to a working build instead of a video, with no environment to set up.
Part of BrowserPod Edge
Portals come with Edge, which connects pods to the internet, with 1,000 hours free every month.
How Portals work
When a process in a pod binds a port, BrowserPod Edge gives it a public hostname of the form <id>-<port>.browserportal.io. HTTP requests and WebSocket connections to that hostname are routed through our network into the pod, to the server listening on the port.
Your page hears about each Portal through onPortal, with its URL and port, so you can show a live preview, copy a link or open it in a new tab.
Portals are part of BrowserPod Edge, the network service that connects pods to the internet, so they need a pod booted on an Edge network. Every Portal is logged to your account and kept for 12 months.
What you need to know
Every server in a pod running in a user's browser gets its own Portal, at a random hostname. Share it like any other URL.
Edge includes 1,000 connected hours a month at no cost. Pro adds more hours, at $0.01 per connected hour beyond its allowance, and custom egress allowlists.
Listen for Portals
Boot on an Edge network, start a server, and BrowserPod reports the public URL for each port.
import { BrowserPod } from "@leaningtech/browserpod";
// Edge connects to the internet
const network = await BrowserPod.createEdgeNetwork({ apiKey: "your-key" });
const pod = await BrowserPod.boot({ network });
const terminal = await pod.createDefaultTerminal(document.querySelector("#console"));
pod.onPortal(({ url, port }) => console.log(port, url));
await pod.run("bash", ["-c", "npm run dev"], { terminal, cwd: "/home/user/app" }); Questions
Who can reach a Portal?
Anyone with the URL. Each Portal gets a random hostname.
What is BrowserPod Edge?
Edge connects your pods to the rest of the internet: Portals, GitHub and APIs. npm works without it. It's the one paid part, from $0.01 per connected pod-hour, with 1,000 hours free every month.
Do Portals support WebSockets?
Yes. Both HTTP requests and WebSocket connections are routed to the server in the pod.
Where does the server actually run?
In the user's tab. Edge only routes the traffic between the public URL and the pod.
Can Portals use our own domain?
Yes, with self-hosted Edge on Enterprise, which runs on your own Cloudflare account with your own domain.










