Official Docker image / dockerized BrowserOS runtime for self-hosted automation

[agiancon]

Hi BrowserOS team,

I am integrating BrowserOS into a self-hosted automation/orchestration flow where each user session runs in an isolated container.

From the public repo, I can see the desktop distributions and the CLI/MCP setup, but I could not find an official Docker image or a supported containerized runtime for BrowserOS itself.

This is currently the main blocker for my use case.

What I need is a dockerized BrowserOS runtime that can be started per session, ideally with:

• an official image published on GHCR or Docker Hub
• stable version tags
• documented ports and environment variables
• a health endpoint
• support for headed and/or headless operation
• CDP / WebSocket connectivity
• optional persistent profile volumes
• guidance for GPU and non-GPU deployments
• at least x86_64 support first, with ARM as a future extension

My concrete use case is:

• one BrowserOS instance per automation session
• an orchestrator that starts and stops ephemeral containers
• predictable startup and packaging, without depending on desktop-only installation flows

So my questions are:

1. Is an official dockerized BrowserOS runtime on the roadmap?
2. If yes, is there an approximate timeline or an interim recommended approach?
3. If not, would you be open to contributions or to a reference Dockerfile for a supported self-hosted deployment?

If this is already available somewhere and I missed it, a pointer to the right repo or docs would be enough.

Happy to test early versions and provide feedback.

Thanks.
AlgoFin Team