Guide
Remote Browser Isolation (RBI): A Practical Guide
Remote browser isolation moves risky web browsing off your device and into a sandboxed browser running in the cloud. This guide explains how it works, what it protects against, and why disposable cloud browsers are the most accessible form of RBI today.
What is remote browser isolation?
Remote browser isolation (RBI) is a security model where every webpage you open runs inside a browser hosted on a remote server — never on your laptop or phone. You see and interact with a live stream of that browser, but the actual page rendering, JavaScript execution, and any downloaded resources stay contained in an isolated environment. When you close the session, the environment is destroyed.
The core idea is simple: the browser is the most attacked surface on any device. Instead of hardening it endlessly, RBI assumes the browser will get compromised and puts it somewhere disposable, where a compromise doesn't matter.
How RBI works under the hood
An RBI system has three moving parts:
- A remote sandbox — typically a fresh container or micro-VM spun up on demand. It contains a real Chromium (or Firefox) instance with no persistent storage.
- A rendering transport — pixels, a DOM mirror, or a WebRTC stream is sent back to your device. Clicks and keystrokes are relayed the other way.
- A teardown mechanism — when the session ends (or a timer expires), the entire sandbox is deleted along with cookies, cache, downloads, and any malicious payloads.
Nothing the remote page does can reach your local filesystem, keyring, extensions, or network. Even a zero-day browser exploit only compromises a throwaway container that's about to be shredded anyway.
RBI vs. VPNs, antivirus, and incognito mode
It's easy to lump these together — they all sound like "privacy tools" — but they solve different problems:
Hides your IP from the destination. The site still runs on your device with full access to your browser.
Scans files after they arrive on your machine. Reactive, not preventive.
Doesn't save history locally. The page still executes locally and can fingerprint your device.
Moves execution off your device entirely. Nothing the site does — scripts, downloads, trackers — touches your local system.
RBI is the only one of these that assumes the page is hostile and simply doesn't let it near you.
What RBI protects against
- Drive-by malware — pages that try to install something the moment they load.
- Browser zero-days — even an unpatched exploit only reaches the throwaway sandbox.
- Phishing kits with device fingerprinting — the fingerprint they collect belongs to the sandbox, not you.
- Persistent trackers — cookies, localStorage, and service workers die with the session.
- Malicious downloads — files land in the sandbox and are wiped before they can reach your disk.
Disposable cloud browsers: RBI for individuals
Historically RBI was enterprise-only — sold to banks, governments, and large IT teams through platforms like Menlo Security, Cloudflare Browser Isolation, or Zscaler. The plumbing was the same, but the packaging assumed you had an IT department.
A disposable cloud browser is RBI stripped down to what an individual actually needs: paste a suspicious link, it opens in a fresh sandboxed browser in the cloud, you see it streamed to your tab, and when you close it the whole environment is destroyed. No install, no policies, no admin.
This is exactly what Tempbrowser does. Every session runs in an isolated cloud sandbox with its own IP, its own browser profile, and a hard time limit. When the session ends — or when you close the tab — the sandbox is torn down and nothing survives.
Try RBI in one click
Paste any link. It opens in a disposable cloud browser, not on your device. The whole environment is wiped when you're done.
When RBI is the right tool
- Opening links from unknown senders (email, DMs, Discord, Telegram).
- Reviewing a URL a colleague flagged as suspicious.
- Visiting sites you'd rather not associate with your real browser profile.
- Testing how a page behaves without polluting your cookies or extensions.
- Journalists, researchers, and analysts touching sites they don't trust.
The trade-offs
RBI isn't free — there's latency between your click and the remote render, video and audio are re-encoded, and some sites that lock down iframes or WebRTC can misbehave. For everyday browsing you'd still use your normal browser. RBI shines when you specifically don't want a page anywhere near your device.
Bottom line
Remote browser isolation flips the browser-security model: instead of trying to make your local browser bulletproof, it makes the browser disposable. For teams that means an enterprise RBI platform; for everyone else, a disposable cloud browser gets you the same isolation in a single click.