For healthtech and RCM technology teams

Automate portal work. Keep control.

Tell Oya the task, then keep the steps as a playbook your team can run again with new case details.

HIPAA compliant · We sign BAAs · SOC 2 Type II audit in progress

Your first task becomes a reusable playbook.

Replayed, no model
Example prompt

Submit a prior authorization for member W2847-1193, CPT 72148.

Example payer portal

Prior authorization request

Member IDW2847-1193
CPT72148 · MRI lumbar spine
DiagnosisM54.50
Ordering NPI1487652309
Submit request

Describe the task

Send work through MCP or your application.

Record once

Oya records the agent’s portal actions.

Save the playbook

Keep readable Playwright code with variable inputs.

Saved playbook · prior-auth.ts

Inputs: Member ID · CPT · Diagnosis · Ordering NPI

Replay new inputs

Call the saved workflow through the SDK, without a model.

Submitted · Ref PA-30418 · Pending review
Agent running
Interactive simulation · Synthetic data

See what customers report.

Time per prior authorization.

By hand
22–26 minutes
With Oya
Under 2 minutes

Reported throughput

Customers report completing 10 to 30 times as many tasks per hour as they could manually.

Operate those workflows across agents and browsers.

The control plane connects your applications, browser fleet and healthcare portals.

Your browser workflows. One control plane.

Agents & apps

MCP · TypeScript · Playwright

Oya control plane

Projects · Policies · Queues

OrchestrateGovernObserve

Browser fleet

Oya · Other providers

Healthcare portals

Payers · EHRs · Registries

Illustrated routing · Runtime guarantees vary by provider

Control how the work runs.

Choose how tasks are queued, who can act and what your team can review.

Execution providers, queues, concurrency, estimated budgets, playbooks and scheduled routines.

  • Execution choice

    Oya Cloud, self-hosted browsers and connected providers behind common interfaces.

  • Sessions and capacity

    Durable session state, queued admission and project concurrency controls.

  • Repeatable work

    Playbooks, variables and scheduled routines, with estimated budgets for managed provisioning.

Read technical details

Choose where those workflows run.

Use Oya Cloud or deploy in your own infrastructure.

Managed deployment

Run browsers on Oya Cloud and connect through the same control interfaces.

Self-hosted deployment

Run the control plane and browser runtime in your own infrastructure.

Runtime limits
  • Strict host-policy enforcement requires the managed runtime. Other providers have different guarantees.
  • Budget controls use configured rates and estimated spend; they are not provider invoice guarantees.
  • Device-bound portal sessions may require sign-in again.
  • Lifecycle webhooks use at-least-once delivery. Consumers must deduplicate events.

Check the details before you deploy.

Talk to the founders