OpenWork + Puter: VPS setup without Docker
Learn how OpenWork connects to remote workers and OpenCode, with a Docker-free VPS setup using Rust, pnpm, URLs and access tokens.
Player not loading? Watch on YouTube
This tutorial presents OpenWork as an open source alternative to Claude Cowork and demonstrates a simplified web application on a VPS. The speaker also says it can run on localhost. The focus is a self-hosted collaboration environment, with a front end that connects to remote workers through a worker URL and access token.
The walkthrough explains how an OpenWork worker uses OpenCode as its coding assistant. Each worker points to a workspace folder on the remote machine. The speaker describes connecting one client to several workers, or several clients to a shared worker. In the demonstration, OpenWork and the OpenCode web interface show the same conversation. A document-drafting task uses Puter as the model provider; this example does not establish offline model execution.
A second example creates a file in the remote workspace, edits it through the browser and checks the saved change on the server. The interface also exposes remote skills, plugins and MCP server connections.
The installation section covers cloning the repository, installing OpenCode and Rust, adding dependencies with pnpm and installing the OpenWork Orchestrator. It then explains front-end URLs and tokens, worker host and port settings, and CORS origins. OpenCode runs on the same machine as the worker in this setup, so the worker connects through a local address and port. The tutorial demonstrates configuration without Docker rather than a complete production deployment guide.