Browser

Oya vs Anchor

Looking at browsers for AI agents that have to sign in? In Oya Browser an agent works signed in as your staff: stored passwords and TOTP seeds are sealed and never shown to the model, and a person can take over any session and hand it back. On Oya Cloud and the enterprise edition it is HIPAA compliant and we sign BAAs. Oya can also run browsers on Anchor, behind the same API.

Signed in, without showing the model a password

Most of the work worth automating sits behind a login, so Oya treats the login as part of the browser.

  • Stored passwords and TOTP seeds are sealed and never shown to the model.
  • A persona is one identity: a fingerprint, a cookie jar and a proxy, bound together and stable for its life.
  • Sign in once in the desktop app to the sites your agents need, and those cookies move to the browsers Oya runs, which keep the same fingerprint as that identity.
  • When a sign-in needs a person, such as a text-message code, staff take over the session and hand it back.

A record of every step

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 Anchor through Oya

One Oya API drives Oya Cloud, Anchor, Browserbase, Steel, Browser Use or your own Chrome. Keep Anchor as a provider behind that API, set its routing priority and session capacity next to your other providers, and move a workload without changing your code. The controls and BAA above cover Oya Cloud and the enterprise edition.

Questions

Is Oya an alternative to Anchor for agents that sign in?

Oya Browser runs agents signed in as your staff. Stored passwords and TOTP seeds are sealed and never shown to the model, and a person can take over any session. On Oya Cloud and the enterprise edition every action lands on a tamper-evident audit trail, and we sign BAAs.

Can I use Oya with Anchor?

Yes. Anchor is one of the providers Oya's API drives, next to Oya Cloud, Browserbase, Steel, Browser Use and your own Chrome.

Does the agent see my passwords?

No. Stored passwords and TOTP seeds are sealed and never shown to the model.

What about two-factor codes?

A persona can hold a TOTP seed, sealed like a password, and Oya completes the code step with it. When a sign-in needs a person, such as a text-message code, staff can take over the session and hand it back.

Is Oya HIPAA compliant?

On Oya Cloud and the enterprise edition, yes: we sign BAAs. Our SOC 2 Type II audit is in progress.

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.