Deployment options

Choose a supported topology

The source deployment runs a long-lived API, worker, PostgreSQL, and a computer provider. Docker is the default local computer path; optional remote computer adapters exist for E2B, Daytona, and Box.

Web, Electron, and mobile connect to a configured product deployment. The marketing website in apps/www builds independently as a static Astro site.

Private Enterprise compute and semi-private Business compute are commercial deployment propositions. Isolation, resource limits, and provider boundaries must be configured and agreed for the actual environment.

For approved source access

Use the One source revision and setup instructions provided for your approved deployment. Do not assume upstream container images include One-specific capabilities. The source checkout expects supported Node.js (22.22.2+ within 22.x, 24.x, or 26+), pnpm, and Docker.

From the application directory, copy .env.example to a private .env. Set matching database credentials and independent strong values for BETTER_AUTH_SECRET, ENCRYPTION_KEY, SCREEN_PROXY_SECRET, and SANDBOX_SUPERVISOR_TOKEN. Never commit those values.

docker compose --env-file .env \
  -f infra/compose/docker-compose.yml \
  -f infra/compose/docker-compose.postgres-host.yml \
  up postgres -d
pnpm install
pnpm db:generate
pnpm db:migrate
pnpm sandbox:build
pnpm dev

Before a public deployment

Terminate TLS in front of the web origin. Set BETTER_AUTH_URL, WEB_ORIGIN, and API_URL consistently. Keep the raw API port and sandbox control listeners private. Configure backups and verify a restore before relying on the environment.

The phone subsystem uses a separate optional overlay and production policy. Expose only the carrier callback and tokened media allowlist; never proxy /api/calling/engine/* publicly.

The upstream self-hosting guide is useful architectural background. One-specific source, image versions, access, and commercial arrangements are provided by Lughlabs.