Oya vs Browser Use
Weighing Oya against Browser Use for AI agents in a browser? In Oya Browser an agent does a task once in plain language, and Oya saves it as a playbook: Playwright code that replays with no model in the loop. On Oya Cloud and the enterprise edition it is HIPAA compliant and we sign BAAs. Oya can also run browsers on Browser Use, behind the same API.
Run it once with an agent, 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 inputs as variables), and the playbook replays with no model calls. When a page changes, the replay stops at the step that moved, the agent finishes from there, and its fix becomes the playbook.
Bring the agent you already have
Oya is the browser. The agent can be yours.
- MCP: Claude Code, Codex, Cursor or any MCP client.
- The Ask panel in the desktop app, on the ChatGPT or Claude plan you already pay for, or a model API key.
- The TypeScript SDK, @oya-ai/browser.
- Playwright, Puppeteer, Stagehand or browser-use, over the CDP URL each browser gives.
For regulated work
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.
Use Browser Use through Oya
Browser Use is one of the providers Oya's API drives, next to Oya Cloud, Browserbase, Steel, Anchor and your own Chrome: add it with your Browser Use API key and Oya starts browsers there behind the same API. It works the other way round too: point the browser-use library at an Oya browser's CDP URL. The controls and BAA above cover Oya Cloud and the enterprise edition.
Questions
Is Oya an alternative to Browser Use?
Oya Browser is a browser for AI agents that takes a task in plain language, or takes your own agent over MCP, the SDK or a CDP URL. What a run leaves behind is a playbook: Playwright code that replays with no model. On Oya Cloud and the enterprise edition it is HIPAA compliant and we sign BAAs.
Can I use the browser-use library with Oya?
Yes. Each Oya browser gives a CDP URL. Point browser-use, Playwright, Puppeteer or Stagehand at it.
Can Oya run browsers on Browser Use?
Yes. Browser Use is one of the providers Oya's API drives, next to Oya Cloud, Browserbase, Steel, Anchor and your own Chrome.
Does every run need a model?
No. The first run does. A saved playbook replays with no model calls, and the agent is called again only when a page has changed, to finish the task from the step that moved.
Is there a free way to try it?
Yes. The desktop app for macOS and Windows is free, and so are 500 agent steps a month.
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.