Note: Built-in SSH tunnels are not live yet. Today, use a tunnel tool (ngrok, Cloudflare Tunnel, etc.) to get a public URL, then open it in a session.

Test Local Sites in Real Cloud Browsers

Tunnel localhost → public HTTPS URL → paste into MyBrowser. Same interactive browsers (Chrome, Firefox, Edge, Brave, Tor), no deploy required.

Start Testing Free

Why this workflow matters

Cross-browser bugs are cheaper to fix before deploy. Remote browsers let you see real rendering and behavior without maintaining VMs. Until we ship native SSH integration, tunnels are the standard way to reach localhost from the cloud — the same pattern many teams already use with other tools.

Compare to Browserling

Browserling documents SSH tunneling for local testing. We intend to offer something similar; today MyBrowser is strongest on price (about half their published tiers for interactive desktop browsers),crypto checkout, and five Linux desktop browsers streaming over noVNC — not yet on one-click SSH parity.

Frequently Asked Questions

Expose your dev server with a public HTTPS URL (for example ngrok, Cloudflare Tunnel, or VS Code port forwarding), then start a normal MyBrowser session and paste that URL. Our backend blocks raw localhost/private IPs for security (SSRF protection). Native SSH tunneling from your machine into sessions is on our roadmap but not shipped yet.

Sessions load URLs from cloud browsers on our servers. Localhost on your laptop is not reachable from those containers. A tunnel gives you a public URL that forwards to your machine — then the remote browser can load your site safely.

Yes — we plan first-party SSH-style local testing similar to Browserling’s workflow. It is not available in the product yet; pricing and docs now describe only what is live today.

Paid plans remove short session limits and ads — same browser power on every tier today.

View pricing