What is HIPAA-compliant browser automation?
HIPAA-compliant browser automation is software, often an AI browser agent, that works on web pages showing PHI under a signed BAA, with access control and an audit trail of every action. Oya runs HIPAA-compliant browser automation on Oya Cloud and the enterprise edition: we sign BAAs, and every agent and person action lands on a tamper-evident audit trail.
What it needs
An agent on a payer portal or an EHR sees PHI, so HIPAA asks for these things.
- A BAA with the company that runs the browsers and the agents.
- Agents that reach only the systems you allow.
- Credentials the model never sees.
- An audit trail nobody can quietly change.
- A person who can watch and take over.
How Oya does each
On Oya Cloud and the enterprise edition, the controls live in the browser.
- We sign BAAs. Our SOC 2 Type II audit is in progress.
- Every action, by an agent or a person, is a hash-chained audit row the database refuses to edit or delete, kept for 365 days at least.
- Oya Cloud, or the enterprise edition in your own infrastructure (Docker, ECS, GCP or Kubernetes), so PHI can stay in your network.
- A person can watch any session live, take over and hand it back.
- Browsers reach only the hosts you allow.
- Stored passwords and TOTP seeds are sealed and never shown to the model.
Run it once, then replay it with no model
An agent does the task once in plain language. Oya saves it as a playbook (Playwright code, with the patient details and codes as variables), and the playbook replays with no model calls. When a portal changes, the replay stops at the step that moved, the agent finishes from there, and its fix becomes the playbook.
From the tools you already use
Start an agent or a playbook from your own stack.
- MCP: Claude Code, Codex, Cursor or any MCP client.
- The TypeScript SDK, @oya-ai/browser.
- Playwright, over the CDP URL each browser gives.
Questions
Is there a HIPAA-compliant AI browser agent?
Yes. On Oya Cloud and the enterprise edition, Oya runs AI browser agents under a BAA, with every action on a hash-chained audit trail and a person able to take over any session.
Does PHI go to the AI model?
A model sees the page while an agent works a task. A saved playbook replays with no model at all. Stored passwords and TOTP seeds are sealed and never shown to the model. Each project can allow only the model providers you choose.
Does Oya sign a BAA?
Yes, for Oya Cloud and the enterprise edition. Write to [email protected].
Can I keep my Playwright code?
Yes. Oya gives a CDP URL that Playwright connects to, and every playbook exports as a readable Playwright module you own.
Can I self-host a HIPAA-compliant agentic browser?
Yes, with the enterprise edition: it runs on Docker, ECS, GCP or Kubernetes, comes with a BAA, and keeps HIPAA workloads in your own infrastructure. Write to [email protected]. The source-available community edition self-hosts too, without the HIPAA offering. Every playbook exports as Playwright code you keep.