Deny first
If a host is not approved, the flow should stop and explain what is missing. Silent cross-domain control is not the model.
🛡️ Allow-listed browser automation
Automation should only run where you explicitly allow it.
RTO treats allow-listing as part of the product contract, not as an afterthought. A page cannot drive arbitrary domains by default: trusted hosts are declared explicitly, and that trust boundary stays visible in the extension itself.
🚫 Deny by default
✅ Explicit trusted hosts
👁️ Visible browser tabs
🔒 No vague permission model
Trust boundary
A clear allow-list makes browser automation easier to trust
Approve deliberately
Trusted hosts are declared by the user. This keeps the control surface understandable, reviewable and bounded.
Keep it visible
RTO works with visible tabs and visible safety signals, so the user can see what is being controlled.
Try it now
See the allow-list boundary in practice
Minimal connection + allow-list check
Start with the minimal demo and observe the deny-by-default behavior if the target host has not been allowed yet.
Why this matters
Control is explicit. If a host is not allowed, the flow should stop, explain the missing approval, and retry only after the user authorizes it.
Where this page fits
Deny-by-default allow-listing is one of RTO’s strongest trust signals
When RTO is a strong fit
- It makes cross-domain browser control explicit instead of vague or hidden.
- It helps users understand what is trusted and what is not.
- It supports safer internal workflows for admin and operator pages.
- It gives the product a clearer privacy and security story.
What to tell a new evaluator
RTO does not ask for vague trust. It exposes a clear rule set where allowed hosts are explicit and everything else stays outside the control surface.
RTO works best when you want real visible tabs, local orchestration, and explicit allow-list control rather than background relay infrastructure.
Why RTO
Three reasons teams pick this approach
Only explicitly allowed hosts can be controlled. That makes the product easier to explain and easier to approve internally.
The extension remains the visible control point for allowed domains, localhost policies and related safeguards.
Bounded browser control is a commercial advantage when users are cautious about automation plugins.
Next steps
Move from search to 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