Start with npm for the fastest local setup, use source install for contributor workflows, or choose Docker for server and team deployments.
One default for most users, plus clear paths for contributors and servers.
⚡ 1 minute
The simplest way to install crewswarm locally and start the full stack.
npm install -g crewswarm
crewswarm
⚡ 3 minutes
Best for contributors, local debugging, and working on crewswarm itself.
git clone https://github.com/crewswarm/crewswarm
cd crewswarm
bash install.sh
npm run restart-all
⚡ 3 minutes
Best for servers, team boxes, and secure isolated deployments.
curl -fsSL https://raw.githubusercontent.com/crewswarm/crewswarm/main/scripts/install-docker.sh | bash
The fastest path for local use on a personal machine.
npm install -g crewswarm
crewswarm
✓ Installs the CLI globally
✓ Starts the dashboard and local services
✓ Best default for evaluating crewswarm quickly
Open dashboard → Providers tab → Add Groq key (free)
Get free key: console.groq.com/keys
Dashboard at http://127.0.0.1:4319 and Vibe at http://127.0.0.1:3333
Use Dashboard for setup and Vibe for coding work.
Use this when you want the repo checked out locally for development or debugging.
git clone https://github.com/crewswarm/crewswarm
cd crewswarm
bash install.sh
npm run restart-all
✓ Canonical contributor setup
✓ Full source available for edits and debugging
✓ Best path for hacking on crewswarm itself
Use Docker when you want the safest and most isolated deployment path.
curl -fsSL https://raw.githubusercontent.com/crewswarm/crewswarm/main/scripts/install-docker.sh | bash
✓ Auto-installs Docker (if missing)
✓ Clones repo
✓ Builds image (or pulls pre-built)
✓ Configures security
✓ Starts all services
Open dashboard → Providers tab → Add Groq key (free)
Get free key: console.groq.com/keys
Dashboard → Chat tab → Try:
"build me a REST API with JWT auth and tests"
Watch crew-pm plan → crew-coder write → crew-qa audit → crew-github commit
Time: ~3 minutes on Groq free tier
OpenClaw's security issues led to Meta bans and $450K losses. crewswarm provides enterprise-grade security.
| Feature | OpenClaw | crewswarm |
|---|---|---|
| Setup time | 30+ minutes (manual Node.js) | 3 minutes (one-line Docker) |
| Security | ❌ ClawJacked vulnerability | ✅ Docker + AppArmor + firewall |
| Production-ready | ❌ Banned by Meta | ✅ Enterprise-grade |
| Known vulnerabilities | ❌ Critical (WebSocket hijacking) | ✅ None |
| Deployment security | ❌ Weak defaults, manual config | ✅ Secure by default |
| Financial safeguards | ❌ None ($450K incident) | ✅ Approval required |
Read the full comparison: Security incidents, feature comparison, migration guide
crewswarm vs OpenClaw →Deploy to AWS, GCP, DigitalOcean, or any cloud provider.
# Launch Ubuntu 22.04 instance, then:
ssh ubuntu@your-ec2-ip
git clone https://github.com/crewswarm/crewswarm && cd crewswarm && docker compose up -d
Access at: http://your-ec2-ip:4319
# Launch Compute Engine instance, then:
ssh your-gcp-vm
git clone https://github.com/crewswarm/crewswarm && cd crewswarm && docker compose up -d
Access at: http://your-vm-ip:4319
# Launch Droplet (Ubuntu), then:
ssh root@your-droplet-ip
git clone https://github.com/crewswarm/crewswarm && cd crewswarm && docker compose up -d
Access at: http://your-droplet-ip:4319
Helm charts and Terraform modules are planned but not yet available. Today, crewswarm deploys via Docker, git clone, or npm on any VM or local machine.
We are planning Helm charts, Terraform modules (AWS ECS/EKS, GCP GKE, Azure ACI), and managed enterprise features. Star the repo to get notified when these ship.
Star on GitHub to follow progressAfter deploying, try these features: