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.
Your first task becomes a reusable playbook.
Submit a prior authorization for member W2847-1193, CPT 72148.
Prior authorization request
Submitted · Ref PA-30418 · Pending review
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
Replay new inputs
Call the saved workflow through the SDK, without a model.
prior-auth.ts
await page.goto(vars["portal"]);await page.getByLabel("Member ID").fill(vars["memberId"]);await page.getByLabel("CPT").selectOption(vars["cpt"]);await page.getByLabel("Diagnosis").fill(vars["icd10"]);await page.getByLabel("Ordering NPI").fill(vars["npi"]);await page.getByRole("button", { name: "Submit request" }).click();await expect(page.getByText("Pending review")).toBeVisible();
// 7 steps replayed. No model, no tokens, nothing to review.
audit trail Chain verified
- Opened payer portal 9f2c41
- Filled member ID b71e08
- Picked CPT 72148 4d93aa
- Filled diagnosis M54.50 e05b7c
- Filled ordering NPI 31c8f5
- Submitted request 7a60d2
- Read reference PA-30418 c2d9e4
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.
Agents & apps
MCP · TypeScript · Playwright
Oya control plane
Projects · Policies · Queues
Browser fleet
Oya · Other providers
Healthcare portals
Payers · EHRs · Registries
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.
Roles, scoped credentials, stable personas, sealed credentials, host policies and model-provider controls.
Project access
Administrator, operator and viewer roles, with scoped, revocable credentials.
Identity and authentication
Persistent personas, cookies and proxies, plus sealed passwords and TOTP secrets.
Data and host policy
Host rules in the managed runtime and project model-provider allowlists.
Live view, human control, hash-chained audit history and lifecycle webhooks.
Human control
Watch sessions, take control and explicitly resume the agent when you are ready.
Audit evidence
Trace actions to actors, roles and keys, with hash-chained history and export.
Operational events
Signed lifecycle webhooks, delivery retries and manual replay for your systems.
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 foundersYes. We sign BAAs. Our SOC 2 Type II audit is in progress.
Self-hosted, pages, recordings and audit records stay in your network. Recordings expire after 7 days by default, and the audit retention floor is 365 days. Recordings are not yet redacted for PHI in the community edition; turn recording off for sessions that show PHI.
Yes. The control plane is source-available and runs on Docker, ECS, GCP or Kubernetes, so HIPAA workloads stay in your own infrastructure. Every playbook also exports as Playwright code you keep.
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.
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 [email protected].