👁️ Real visible tabs
RTO controls normal browser tabs the user can see, focus and inspect. It is designed for supervised workflows, not hidden browser farms.
🧰 Local automation guide
Local browser automation without Selenium for practical visible flows
RTO is not a blanket replacement for Selenium or WebDriver. It is a lighter option when the real need is local, visible browser control with named tabs, clear operator feedback and less infrastructure.
🏠 Local-first setup
A trusted page talks to the local extension bridge. For many internal flows, that is simpler than maintaining drivers, grids or remote runners.
🛡️ Explicit boundaries
RTO is built around visible control and allow-listed hosts. The user should understand what is being controlled and why.
🎬 See the model before installing
Watch visible tab automation without installing the plugin
The live simulation shows the RTO model in the browser: a master tab, controlled visible tabs, a warning bar, a safety overlay and a result returned to the master page.
It helps you evaluate whether your need is a supervised local workflow or a full Selenium-style automation stack.
Launch the live simulation✅ Where RTO fits
RTO is strongest when Selenium’s infrastructure is not the part you actually need
Good fit for RTO
- You want a real browser tab that stays easy to inspect.
- You do not want to maintain a driver stack or automation grid.
- You need named workflows launched from a trusted page.
- You want a small browser-native toolchain for internal operations.
Better fit for Selenium
- You need large-scale cross-browser test automation.
- You need CI pipelines, grids, parallel runs and test orchestration.
- You want a WebDriver-compatible test stack.
- You are validating many browser versions automatically.
🧭 Why this approach
Three reasons teams choose local visible browser automation
⚡ Lower setup cost
For many practical workflows, a browser extension and a page script are easier to deploy than a full Selenium-based environment.
👁️ Visible execution
The target tab remains real, visible and understandable during demos, support sessions, internal operations and QA checks.
🔒 Bounded control
Explicit host boundaries and local execution keep the model readable instead of moving everything into hidden remote infrastructure.
RTO and Selenium answer different needs. If your priority is visible, supervised, local browser control, RTO may be the lighter and clearer tool.
🚀 Next steps
Move from comparison to a first working flow
SDK
Start fast with the browser-side SDK.
Open SDKDocumentation
Read the public contract, allow-list notes and examples.
Open docsExamples
Try copy-paste starter examples and live demos.
Browse examplesCompare
See where RTO fits against recorder tools and Selenium-style stacks.
Open compare