Self-host
Run Crewaid yourself
One command installs the server on your own machine or cloud server. Your bots, their computers and your data stay there, and you bring your own model keys.
01What you get
- Your server, your data. The orchestrator, its database and your bots’ computers run on your machine or your own cloud server.
- Your own model keys. Add a key from OpenAI, Anthropic, OpenRouter or any compatible provider; calls go straight from your server to them.
- Email and password accounts, with nothing else to set up: no identity provider, no mail service.
- No subscription and no usage limits beyond what your machine can run.
02What you need
- Docker. Docker Desktop on macOS or Windows, or Docker Engine with Compose on Linux.
- About 2 CPUs and 4 GB of memory for each computer running at once, plus a little for the server. Two at once is the default.
- About 5 GB of disk for the server, plus your bots’ files.
03Install the server
On macOS or Linux, in a terminal:
curl -fsSL https://downloads.crewaid.io/install.sh | shOr, anywhere you have Node.js 18 or later:
npx crewaid-selfhost initThe installer checks Docker, asks how you will reach the server, generates every key, writes two files to ~/crewaid and starts it. The first start downloads about 2 GB.
04Get the app
Self-hosted servers pair with Crewaid Self-Hosted, the edition of the app that asks for your server’s address:
- Download for macOS (Apple silicon and Intel)
- Download for Windows (Windows 10 and 11)
Open it, enter the address the installer printed (for example http://localhost:3000), and create your account. It installs next to the regular Crewaid app without touching it, and updates itself.
05Who can reach it
- This computer only (the default): nothing outside your machine can connect.
- Your local network: other computers on it can use the server. The connection is not encrypted, which is fine on a network you trust.
- The internet: point a domain at the machine and the installer sets up HTTPS with a free certificate.
- Anyone who can reach the address can create an account. Each account’s bots, files and keys are its own.
06How the computers are fenced
- Each bot works in a browser on a sandboxed computer that can reach the internet on the web ports and nothing else: not your machine, not your local network, not other computers.
- Nothing about a computer is exposed on your machine. Only the server can open its screen, and the server starts only once that fence is in place, including after a restart.
- This holds on Linux and on Docker Desktop for macOS and Windows alike.
- Model keys and plugin tokens stay on the server and never enter a computer, and they are encrypted with keys kept in your install folder, outside the database.
07Updating and looking after it
Move to a new release (your accounts, bots and keys stay):
npx crewaid-selfhost updateCheck what is running:
npx crewaid-selfhost statusSomeone forgot their password? There is no email to send, so reset it from the server:
npx crewaid-selfhost reset-password [email protected]The app tells you when your server is older than it. Back up the crewaid_postgres-data volume, the crewaid_artifacts volume (files attached in chat and skill recordings), your bots’ crewaid-workspace-* volumes, and the .env file in your install folder, which holds the keys that decrypt everything else: keep it with the backup, never inside the database dump.