ReferenceSelf-host
Self-host
Run OpenWorking on your own server and connect the desktop app remotely.
Most people just use the desktop app. Self-hosting is for teams that want OpenWorking to run on their own server, VPC, or private cloud and then connect the desktop app to it remotely.
What you deploy
- The OpenWorking app — the desktop or web client people use.
- A worker runtime — where sessions actually run, with workspace and data on durable storage.
- A control plane (optional) — for accounts, teams, and remote worker creation, backed by a database.
If you only need one private remote workspace, deploy the worker runtime. For accounts and team features, add the control plane.
Production requirements
- Put HTTPS in front of every public service.
- Expose the OpenWorking server/worker URL, not the raw runtime.
- Keep workspace and data paths on durable, encrypted storage with backups.
- Configure public URLs, auth origins, CORS origins, tokens, and provider credentials via environment variables.
- Run database migrations before the control plane receives traffic.
Don't want to run infra?
Hosted workspaces, shared providers, and team management are available on the paid plans, and self-hosted / private deployment is part of Enterprise. See Pricing or talk to us about a larger rollout.