Start here
A self-hosted @computer is Cloudflare Workers and one VM per organization on Azure, AWS or Google Cloud
A self-hosted deployment runs the same stack as the hosted service, in your accounts:
The Computer VM connects out to the gateway Worker; nothing connects in. The diagram shows Azure, where the platform Worker creates the VMs. On AWS and Google Cloud you create them and there is no platform Worker.
What you need
| Account or tool | Used for |
|---|---|
| Cloudflare account with a zone (domain) you control | Workers, D1, KV, R2 and Durable Objects. The gateway Worker needs a custom domain on the zone: Worker-to-Worker requests on workers.dev do not arrive. |
| Azure subscription, AWS account or Google Cloud project | The Computer VMs and the storage for the Computer release. On Azure you need rights to create role assignments and app registrations. |
| WorkOS account | Sign-in to the dashboard |
| Slack workspace | A Slack app you create |
| GitHub account or organization | A GitHub App you create |
| Anthropic API key | Model calls from every session |
Git, Node.js 22 or newer, npm, Go, Wrangler 4, and your cloud’s CLI (az, aws or gcloud) | Building and deploying |
Choose where the VMs run
| Cloud | Who creates the VMs |
|---|---|
| Azure | The platform Worker, when an organization adds the Slack app. It also stops a VM that is idle, starts it on the next message, and resizes it. |
| AWS | You, one EC2 instance per organization. You stop, start and resize it. |
| Google Cloud | You, one Compute Engine instance per organization. You stop, start and resize it. |