Give OpenWork a home on a Hostodo Linux VPS. Keep workspace files and tools on your server, open the web client in your browser, and connect the AI provider you choose.
Includes a Docker recipe, SSH access, persistent storage, and local test results. Hostodo VPS performance has not been benchmarked.
Deploy a Linux VPS
Choose a plan and an available region in the Hostodo console. Add your SSH key and prepare the server for the OpenWork deployment you intend to run.
Install your OpenWork services
Follow the current upstream instructions for the workspace server. If you need team administration, include the Den services and database. Keep application data on durable volumes.
Connect securely
Configure authentication, then use HTTPS or private access to reach the web client. Keep the database and internal services private. Connect your supported model provider separately.
Try a real task
Start with a small set of non-sensitive files. Check tool permissions and resource use, then arrange backups and verify a restore before relying on the workspace.
Size the server for what you do.
A document workspace, a browser-heavy workflow, and a container build need different resources. Compare CPU, RAM, and disk, then evaluate your workload. We have not established a tested OpenWork minimum on Hostodo.
VPS pricing covers hosting. AI usage and any paid OpenWork features are separate.
Yes. OpenWork documents a standalone workspace server with a web client that you can run on your own Linux infrastructure. Hostodo supplies an unmanaged KVM VPS with root access and NVMe storage. You install and operate OpenWork; it is not preinstalled.
Do I need a GPU or an AI subscription from Hostodo?
A GPU is not needed on the VPS when you use a remote AI model provider. Bring your own supported provider credentials and pay for model usage separately. Hostodo supplies the server and does not include OpenWork licenses, AI subscriptions, or GPU compute. Running models locally is a separate workload with its own hardware requirements.
Can I connect the OpenWork desktop app directly to this workspace?
For a standalone self-hosted workspace, use its web client. OpenWork currently documents that the desktop app does not offer Share workspace or Connect to remote workspace. A Cloud-style deployment with Den has a separate desktop configuration path.
Is OpenWork’s team evaluation Compose stack ready for production?
No. OpenWork labels its published Compose evaluation stack as evaluation-only. It uses a stub worker provisioner and does not provide production sandboxes. Keep it on loopback and access it through an SSH tunnel. Production requires a separately configured deployment, secure access, durable storage, and backups.
How much RAM should I choose?
Size the VPS for the work you will run: documents, browser tools, builds, containers, and concurrent sessions all have different requirements. We have not benchmarked OpenWork on Hostodo or established a minimum plan. Evaluate your workload before moving important data or committing to a larger rollout.
Who handles updates, backups, and OpenWork licensing?
You manage the software, access controls, updates, and backups on your VPS. OpenWork licensing is separate from hosting and depends on the edition, team size, and features you use. Check OpenWork’s current pricing and licensing terms before deploying for a team.