What do you need?
A Linux VPS with SSH access, Docker Engine and the Compose plugin, outbound internet access for package downloads, and credentials for a model provider supported by OpenWork. You do not need a GPU when the model runs at a remote provider. Hosting and model usage are billed separately.
This recipe runs one standalone workspace. It does not install Den accounts, team administration, SSO, or a fleet of isolated workers. OpenWork’s separate team evaluation stack uses stub provisioning; it is not the recipe below.
| Hostodo VPS | Monthly price | How to evaluate it |
|---|---|---|
| 2 vCPU / 2 GB / 32 GB NVMe | $3.50 | Smaller than our test allocation. We have not validated a 2 GB limit. |
| 2 vCPU / 4 GB / 64 GB NVMe | $7.00 | Matches our container’s CPU/RAM limits. A starting point for a trial, not a workload guarantee. |
| 3 vCPU / 8 GB / 128 GB NVMe | $9.00 | More room for browser tools and builds. Size against your own tasks. |
These are a dated snapshot of the public plan catalog. Check current plans and availability before ordering. Add your provider’s usage charges, backup storage, and any paid OpenWork features to the VPS cost. The standalone server package is MIT-licensed; team and enterprise features have separate licensing terms.
What did we actually test?
We ran the downloadable recipe in a local Linux/amd64 container under Docker Desktop on Apple Silicon, using emulation and limits of 2 CPUs and 4 GiB RAM. This is an installation smoke test, not a Hostodo VPS benchmark or a minimum-system specification.
| Web UI and health | HTTP 200; health returned ok: true. The browser opened the workspace and task composer without a Cloud login. |
|---|---|
| Workspace API access | 401 without a token or with an invalid token; 200 with the client token. The web page supplies that token automatically to visitors who can reach it. |
| Persistence | Workspace test file and client token survived container replacement. |
| Idle memory | 1,014–1,015 MiB (about 1 GiB) across six samples with a five-second pause between readings. No model task was running. |
| Local disk | 380 MiB image; 543 MiB persistent home after first setup. Allow additional space for builds, downloads, backups, and your files. |
We did not run a paid model request, browser automation task, concurrent workload, or local model. Idle memory does not predict peak memory. The host OS needs RAM too; monitor actual use before putting important work here.
1. Install the standalone workspace
Start with a dedicated Linux VPS and an SSH key. Install Docker Engine and the Compose plugin using the official instructions for your distribution. The commands below assume your user can run Docker. Check that both commands work:
docker version
docker compose version
On the VPS, download the Dockerfile and Compose file into a new directory. Review them before building:
mkdir -p ~/openwork
cd ~/openwork
curl -fSLo Dockerfile https://hostodo.com/downloads/openwork/Dockerfile
curl -fSLo compose.yaml https://hostodo.com/downloads/openwork/compose.yaml
Dockerfile: pinned server and runtime
FROM node:24.22.1-bookworm-slim
RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates git curl unzip && rm -rf /var/lib/apt/lists/*
RUN npm install --global [email protected] && npm cache clean --force
RUN mkdir -p /home/node/workspace /home/node/.cache/tmp && chown -R node:node /home/node
USER node
WORKDIR /home/node/workspace
ENV OPENWORK_NO_UPDATE_CHECK=1 TMPDIR=/home/node/.cache/tmp
EXPOSE 8787
CMD ["openwork-server", "web", "--host", "0.0.0.0", "--port", "8787", "--workspace", "/home/node/workspace"]
Compose: private port and persistent home
services:
openwork:
build: .
ports:
- "127.0.0.1:8787:8787"
volumes:
- openwork-data:/home/node
restart: unless-stopped
cpus: 2
mem_limit: 4g
security_opt:
- no-new-privileges:true
cap_drop:
- ALL
healthcheck:
test: ["CMD", "curl", "--fail", "--silent", "http://127.0.0.1:8787/health"]
interval: 30s
timeout: 10s
retries: 5
start_period: 180s
volumes:
openwork-data:
The image runs as the unprivileged node user. The named volume holds its entire home, including workspace files, OpenWork tokens, the downloaded engine, and application state. TMPDIR is inside that volume because version 0.18.71’s engine installer can fail with EXDEV when it renames files across mount boundaries.
docker compose -p openwork up -d --build
docker compose -p openwork ps
curl --fail http://127.0.0.1:8787/health
The first boot downloads OpenCode 1.18.33. Health can return 503 while it starts; wait and retry until it returns 200 with "ok":true. The health check allows extra startup time. If it stays unhealthy, use the troubleshooting section below.
2. Connect through an SSH tunnel
The container listens on all interfaces internally, but Docker publishes its port only on the VPS loopback address. Keep port 8787 closed to the public internet. From your own computer, replace the username and address and leave this command running:
ssh -N -o ExitOnForwardFailure=yes \
-L 127.0.0.1:8787:127.0.0.1:8787 your-user@your-vps-ip
Open http://localhost:8787 on your computer. The local browser URL travels through the encrypted SSH connection. This also provides the localhost context the web UI needs. No domain name or public reverse proxy is needed for this setup.
The browser should open your workspace without a separate OpenWork Cloud login. Configure a supported model provider, then try a small task with non-sensitive files. Prompts and relevant content go to your chosen provider when you use a remote model. Provider configuration and a completed model task were outside our smoke test.
3. Keep the workspace recoverable
restart: unless-stopped brings the service back after a restart when Docker itself starts. It does not guarantee that an interrupted agent task resumes. OpenWork’s documented automatic task recovery is specific to the desktop integration.
Back up the named volume
From ~/openwork on the VPS, stop the service for a consistent archive. Run this when no task is active. The backup contains access tokens and any saved provider credentials; encrypt it and keep a protected off-server copy.
umask 077
docker compose -p openwork stop
backup="openwork-home-$(date -u +%Y%m%dT%H%M%SZ).tgz"
docker compose -p openwork run --rm -T --no-deps \
--entrypoint tar openwork -C /home/node -czf - . > "$backup"
docker compose -p openwork start
Check the archive and test a restore before relying on it. To restore into a new, unused Compose project, stop the original service, then use the backup file path in place of BACKUP.tgz:
docker compose -p openwork stop
docker compose -p openwork-restore build
docker compose -p openwork-restore run --rm -T --no-deps \
--entrypoint tar openwork -C /home/node -xzf - < BACKUP.tgz
docker compose -p openwork-restore up -d
Verify the health endpoint, sign-in, and your files. The restored instance retains the saved token. If you continue using it, use -p openwork-restore for subsequent commands. Keep the original project stopped while the restored one uses port 8787. Do not use docker compose down -v on data you want to retain: it deletes the named volume.
Update deliberately
Back up first. Read the OpenWork release notes and Node.js requirements, update the version pins in your Dockerfile, and rebuild with docker compose -p openwork up -d --build. Check health, authentication, and a representative task after an update. Keep the old recipe and backup together; newer state may not work with an older release.
Common setup problems
The engine download fails with EXDEV
Keep TMPDIR=/home/node/.cache/tmp and the directory creation step in the Dockerfile. Both temporary extraction and the engine destination must be on the persistent home volume for this version. Rebuild after changing the recipe.
The page loads but cannot connect
Wait for health to return 200 and use http://localhost:8787 through the active SSH tunnel. A bare VPS IP over HTTP is not the secure browser context the UI expects. Check that another local service is not already using port 8787. Keep the recipe’s default browser bootstrap enabled: with --no-bootstrap-token, our test of 0.18.71 reached the general welcome screen rather than a working token-entry flow.
The container stays unhealthy or exits
Inspect docker compose -p openwork logs --tail=100 privately; startup logs can contain tokens. Check outbound download access, free disk, volume permissions, and docker stats for memory pressure. The health response may show a null installed-engine version even when the engine is present; our test verified the binary’s version separately.
Can I use manual approval in this web setup?
The current web mode has no approval responder. Switching it to manual approval can cause gated operations to time out. Use a dedicated workspace with narrowly scoped credentials, and review upstream changes before changing approval mode.
Does this include a managed OpenWork service?
No. Hostodo provides an unmanaged VPS. You handle OpenWork installation, access, updates, backups, and troubleshooting. Team services and model usage are separate.
Sources and scope
Installation details were checked against the OpenWork server README and the published [email protected] package. See OpenWork’s self-hosting architecture, team evaluation guide, and licensing for the broader product.
The downloadable Dockerfile and Compose file are Hostodo’s standalone example. They are not an upstream team deployment or a claim of production certification. Results above apply to the pinned versions and local environment tested on November 19, 2026.