Skip to content
Oxynus OnbrowEarly access

Browsers without boundaries. Infrastructure without friction.

Onbrow is an isolated, programmable browser environment for developers and QA teams. Start sessions from an API, route them through Oxynus Proxy, keep every profile separate — and end each one cleanly.

Request early accessSee how it works
Not available yet. No pricing, no dates, no checkout — a short list we write to when there is something real to try.Built on Botonomus, existing OxynusAI browser technology.
Interactive preview

One window. Every session.

A concept of the Onbrow console. Launch, pause and end sessions, pick a route — nothing here is connected to anything, and every value is an example.

Onbrow console Sample data
qa-checkoutRunningProfile · qa-checkout · keeps storage
Proxy route

Pause or end the session to change its route.

staging.example.com/checkoutResidential · DE
Activity
Open tabs
2
Pages loaded
14
Data via route
3.2 MB
  1. Running via Residential · DE
  2. Starting an isolated browser
  3. Session created from profile qa-checkout

Session management

Launch it. Watch it. End it properly.

A session has a beginning, a visible middle and a real end. No orphaned browsers quietly running up a bill. These buttons drive the console above.

Selected session
Controls the console above
  1. Ready
  2. Launching
  3. Running
  4. Paused
  5. Terminated
Running

Running: pages load through the selected proxy route. The route is locked while it runs.

Proxy integration

Sessions ride on Oxynus Proxy.

Each session is planned to use an Oxynus Proxy route you already have: the product, the country, the session type. One account, one set of keys, one usage view.

  • Pick the route per session, not per machine
  • Proxy credentials stay server-side — never pasted into scripts
  • Usage shows up next to your other proxy usage
See Oxynus Proxy
qa-checkoutRunningPlanned Sample data

Try it: pick a route for the selected session. The console above follows.

Proxy route

Pause or end the session to change its route.

Profiles & isolation

Nothing leaks between sessions. By design.

Each session runs in its own runtime. Profiles decide what carries over; everything else is thrown away at the end.

qa-checkoutRunning Sample data
Profile
qa-checkout
Proxy route
Residential
Country
Germany
Session persistence
keeps storage
Developer automation

Drive it with the code you already write.

A session is a browser you can reach over the Chrome DevTools Protocol, from Python, or with plain HTTP. Bring Playwright, Puppeteer or your own client.

CDP
Attach any DevTools Protocol client to a running session.
Python
A small SDK for sessions, profiles and routes.
API-driven
Create, list and end sessions with idempotent HTTP calls.
Preview · planned API
# preview: planned SDK, not published yet
from oxynus import Onbrow

onbrow = Onbrow(api_key=OXY_KEY)

session = onbrow.sessions.create(
    profile="qa-checkout",
    route={"product": "residential", "country": "DE"},
)

page = session.open("https://staging.example.com/checkout")
page.screenshot("checkout.png")

session.terminate()  # runtime discarded, profile kept

Not a live endpoint. Names and shapes will change before release.

Use cases

Built for work you’re allowed to do.

  1. 01

    Authorized browser testing

    Check your own sites and staging environments from the regions your users are in.

  2. 02

    QA automation

    Run regression suites in clean, repeatable sessions instead of a shared, tired browser.

  3. 03

    Web workflows

    Automate routine steps in tools and accounts you own or are permitted to operate.

  4. 04

    Authorized data collection

    Collect public or licensed data where the site’s terms and the law allow it.

Onbrow is for authorized testing and permitted automation only. The acceptable use policy applies, and we enforce it.

Architecture

Three layers. Clear seams.

Botonomus orchestrates, the runtime executes, Oxynus Core keeps the account honest. Each layer does one job.

  1. 1Orchestration

    Botonomus

    • Session lifecycle
    • Scheduling & queues
    • Automation engine
  2. 2Execution

    Browser runtime

    • One isolated browser per session
    • Profiles & persistence
    • CDP endpoint
  3. 3Account & routing

    Oxynus Core

    • API keys & scopes
    • Oxynus Proxy routes
    • Usage, audit & billing records
Planned · Oxynus Intelligence

Say what you want done. Review it before it runs.

Later, Oxynus Intelligence is planned to turn a plain-language request into session steps you can read, edit and confirm. Nothing runs until you press the button.

Concept. Oxynus Intelligence is not built yet. Sample data
YouOpen the staging checkout, add the test product, and save a screenshot of the receipt page.
Proposed steps
  1. 1Launch session · profile qa-checkout
  2. 2Open staging.example.com/cart
  3. 3Add product TEST-001
  4. 4Screenshot /receipt
Early access

Want in early?

Tell us what you would automate. We will write when there is something real to try — not before.

Request early accessExplore Oxynus Proxy

Cookies, itemised.

Necessary ones, plus two optional. Both stay off until you say so.