Browser

For teams automating payer portals, EHRs and registries

The portal has no API.
Your agent still gets in.

Oya is a real browser your agents use without being flagged. Record a task once, and every run after that is pure compute: no model, no token bill, signed in like your staff.

Download the app Start building Talk to FoundersRead the docs
portal.payer.example/eligibility Replaying, no model

Eligibility and benefits

Member ID
Date of birth
Provider NPI
Service type
Check eligibility

Coverage active · PPO Gold

eligibility-check.ts

  1. 1await page.goto(vars["portal"]);
  2. 2await page.getByLabel("Member ID").fill(vars["memberId"]);
  3. 3await page.getByLabel("Date of birth").fill(vars["dob"]);
  4. 4await page.getByLabel("Provider NPI").fill(vars["npi"]);
  5. 5await page.getByLabel("Service type").selectOption("30");
  6. 6await page.getByRole("button", { name: "Check eligibility" }).click();
  7. 7await expect(page.getByText("Coverage active")).toBeVisible();

// 7 steps replayed. No model, no tokens, nothing to review.

Step
1 of 7
Model calls
0
Tokens
$0.00
Signed in as
your staff
$ npm i @oya-ai/browserawait browser.play("eligibility-check", { memberId })

Get started in 2 minutes

Download Oya Browser. It's free.

  1. 1Download

    Pick your computer. The desktop app is free.

  2. 2Install and open

    Mac: drag it to Applications. Windows: run the .exe. Linux: chmod +x the AppImage.

  3. 3Sign in with Oya

    It opens your web browser. Sign in or sign up free, then click Connect.

  4. 4Log in to your sites

    In Oya Browser, as usual. Your agents reuse those sessions.

  5. 5Give Oya a task

    Type it on the start page, or drive the browser from the SDK, MCP or Playwright.

Stuck? Read the install guide.

95%+
task success on the portal runs Oya has measured
0
model calls on a replayed run: pure compute
0%
flagged as a bot on CreepJS
10
browsers started in under five seconds, and scaling on

Your browser. Your choice.

  • Oya Cloud
  • Browserbase
  • Browser Use
  • Steel
  • Anchor
  • Your own Chrome

Why teams switch

Three problems.
One browser that solves them.

Everyone elseheadless Chrome over CDP

Blocked. Verify you are human

Oyaa real browser, signed in

Eligibility: active
Same portal, same task. The difference is where the automation runs.
  1. 01

    Blocked as a bot.

    Headless Chrome driven over the debugging protocol is exactly what anti-bot systems look for.

    With Oya

    Oya is the browser. No CDP, no headless Chrome: it passes iphey and CreepJS like a person would.

  2. 02

    Paying the model every run.

    An agent that reasons through the same steps every night pays for them every night, and drifts.

    With Oya

    Record the task once. Every run after that is pure compute, with no model, and it heals itself when a page moves.

  3. 03

    No real browsers at scale.

    Agents need a real, signed-in browser each, and they need hundreds of them on demand.

    With Oya

    Go from zero to thousands of real browsers, each on its own profile with your team’s cookies and sessions.

How it works

Do it once.
Replay it forever.

  1. 01

    Ask.

    Describe the task in plain language, in the console, the SDK or your own agent. Oya does it in a real browser, signed in like your staff.

  2. 02

    Save.

    Keep the run as a playbook. The values you gave become variables, the steps become Playwright code you own, and free-text answers stay with your model.

  3. 03

    Replay.

    Run it with new inputs and no model in the loop. It signs in by itself, and when a portal changes, the agent fixes the step and the playbook heals.

Why Oya

Everyone drives Chrome.
We built the browser.

The automation lives inside it, not attached over the debugging protocol.

Not flagged as a bot.

Chrome’s own emulation sets the device. 0% on CreepJS.

Sign in once.

Log in by hand. Every browser after that starts signed in, cookies and localStorage both.

Signs itself back in.

A replay that meets a login uses the profile’s stored credentials and second factor, then carries on.

Writes the free text fresh.

Comments and question answers are written by your model on every run, never replayed word for word.

Proves what happened.

A hash-chained audit trail. Allow-list the hosts a browser may reach.

Runs in your cloud.

Source-available. Self-host on Docker, ECS, GCP or Kubernetes for HIPAA and SOC 2 workloads.

Weighing Browser Use, Anchor or Browserbase?

They all replay runs.
Only one keeps your portal work in your network.

 OyaBrowser UseAnchorBrowserbase
What the portal seesA real headful browserChromium over CDPA stealth Chromium forkCloud Chromium over CDP
Signed in as your teamYour staff’s real sessions, synced as profilesBrowser profilesManaged loginStored contexts
Replays without a modelYes, with no model at allYes, checked by an LLM each runYesYes
Runs in your own cloudYes, source-availableThe library onlyEnterprise plan onlyNo
HIPAA, data in your networkSelf-host on any planEnterprise planEnterprise planScale plan

From each vendor's public site, docs and pricing page, September 2026.

Questions

Before you wire it in.
Straight answers.

Is Oya a real browser, or Chrome driven from outside?

A real headful browser with the automation inside it. Sites see an ordinary Chrome, not a harness attached over the debugging protocol.

Where does it run?

In Oya Cloud, in your own cloud with the control plane self-hosted, on your team’s machines with the desktop app, or on Browserbase, Browser Use, Steel and Anchor.

What happens when a portal changes?

The replay stops at the step that moved, the agent finishes the task from there, and its fix becomes the playbook, so the next run is model-free again.

Does the model see our passwords?

No. Secrets are typed through placeholders and redacted from everything the model reads, and they never enter a saved playbook.

Can we host it ourselves?

Yes. The control plane is source-available and runs on Docker, ECS, GCP or Kubernetes, so HIPAA and SOC 2 workloads stay in your own infrastructure. Every playbook also exports as Playwright code you keep.

How much does it cost?

The desktop app is free, and so are 500 agent steps a month. Oya Cloud: Free gives 1 cloud browser hour; Developer is $20 a month for 100 hours, 1 GB of proxy and 5,000 agent steps; Startup is $99 a month for 500 hours, 5 GB and 50,000 steps. Past that, $0.10 or $0.08 a browser hour, $8 a GB and $0.002 a step. Self-hosting is free up to 5 cloud browsers at once. For more, write to sales@getoya.ai.

Stop writing integrations
for portals that don't want you.

Start a browser in a minute, record the run your team already does by hand, and replay it on every case.

Start building Talk to Founders