Browser

Oya Browser docs

Self-hosting: the whole stack in your network

Run the whole Oya stack in your own network with git, Docker and Node 20 or later: install it, connect a browser, and the settings that tune it.

Self-hosting

Run the whole stack in your own network, for HIPAA and SOC 2 workloads or anywhere data may not leave. It needs git, Docker and Node 20 or later.

Terminal
curl -fsSL https://raw.githubusercontent.com/OyadotAI/oya-browser/main/install.sh | sh

A wizard asks six questions, writes the config, starts the stack, waits until it is ready, and prints an API key. Add --dry-run after sh -s -- to see the plan without writing anything.

For agents and CI, --yes asks nothing: SQLite, the server and one browser worker in Docker on this machine. It ends by printing OYA_BASE_URL and OYA_API_KEY.

Terminal
curl -fsSL https://raw.githubusercontent.com/OyadotAI/oya-browser/main/install.sh | sh -s -- --yes
ChoiceOptions
Control planeDocker on one machine; Amazon ECS, Kubernetes or Google Cloud for production
DatabaseSQLite (default, one replica), Postgres (many replicas) or JSON files
BrowsersDocker workers, one container or pod per session, Oya Cloud, or your own Chrome over CDP
LLMAnthropic, OpenAI, Gemini, any OpenAI-compatible endpoint, or a local model (Ollama, vLLM)

To update to the latest version, run the update script. It keeps your settings and browser workers, rebuilds, restarts, and waits until the server is ready; with local edits in the checkout it stops and changes nothing.

Terminal
curl -fsSL https://raw.githubusercontent.com/OyadotAI/oya-browser/main/update.sh | sh

Point your code at it

Terminal
oya login --url http://localhost:3100 --key <the key it printed>
oya ls                             # the browsers that enrolled
oya goto https://example.com

In code, set OYA_BASE_URL next to OYA_API_KEY; everything else in these docs works unchanged.

Settings that matter

VariableWhat it does
OYA_PROFILE_SECRETEncrypts cookies, passwords and TOTP seeds at rest. Generated into the data volume when unset, so keep that volume.
API_KEYSComma-separated tenant keys. The control plane needs nothing else.
OYA_STORAGEsqlite, postgres or file: where every table lives.
DATABASE_URLThe Postgres connection string, with OYA_STORAGE=postgres.
OPENAI_API_KEYThe default model for agents. Each API key can set its own.
Keep the oya-data volume, or set OYA_PROFILE_SECRET yourself. Lose the secret and every stored login becomes unreadable.

Databases, cloud browser runtimes, upgrades and every setting are in the full self-hosting guide.