Install crewswarm Your Way

Start with npm for the fastest local setup, use source install for contributor workflows, or choose Docker for server and team deployments.

⚡ npm for most users • 🔒 Docker for secure deployments • 🌍 Linux, macOS, Windows
Install with npm → View on GitHub

Choose models · Open Vibe · Read crew-cli

Choose Your Install Path

One default for most users, plus clear paths for contributors and servers.

Recommended for Most Users

npm Install

⚡ 1 minute

The simplest way to install crewswarm locally and start the full stack.

npm install -g crewswarm
crewswarm
  • ✅ Fastest onboarding path
  • ✅ Best default for solo users
  • ✅ No repo clone required
Learn more →

Source Install

⚡ 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
  • ✅ Best for contributors
  • ✅ Full repo access for hacking and debugging
  • ✅ Canonical local development path
Learn more →

Docker

⚡ 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
  • ✅ Safest default for deployments
  • ✅ Isolation and restart discipline
  • ✅ Works on cloud VMs and team hosts
Learn more →

npm Install (Recommended for Most Users)

The fastest path for local use on a personal machine.

1

Install and start

npm install -g crewswarm
crewswarm

✓ Installs the CLI globally
✓ Starts the dashboard and local services
✓ Best default for evaluating crewswarm quickly

2

Add an API key

Open dashboard → Providers tab → Add Groq key (free)

Get free key: console.groq.com/keys

3

Open the main surfaces

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.

Source Install (Best for Contributors)

Use this when you want the repo checked out locally for development or debugging.

1

Clone and bootstrap

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

Docker Install (Best for Servers and Teams)

Use Docker when you want the safest and most isolated deployment path.

1

Run the installer

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

2

Add an API key

Open dashboard → Providers tab → Add Groq key (free)

Get free key: console.groq.com/keys

3

Start building

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

What's included:

  • 5-layer security: Docker + AppArmor + firewall + allowlist + read-only FS
  • Pre-built images: Docker Hub + GitHub Container Registry
  • Multi-arch: amd64 (Intel/AMD) + arm64 (Apple Silicon, Graviton, Raspberry Pi)
  • Auto-restart: systemd service (optional)
  • Health checks: Automatic verification

Why Teams Switch from OpenClaw

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 →

Cloud Deployment

Deploy to AWS, GCP, DigitalOcean, or any cloud provider.

AWS EC2

# 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

Google Cloud

# 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

DigitalOcean

# 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

Cloud deployment includes:

  • ✅ Auto-configured firewall (blocks cloud metadata endpoints)
  • ✅ Production-ready security (5 defense layers)
  • ✅ Health checks and auto-restart
  • ✅ Ready for reverse proxy (nginx, Caddy)

Kubernetes & Enterprise (Roadmap)

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.

Enterprise and Kubernetes support is on the roadmap

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 progress

What's Next?

After deploying, try these features:

🤖 Try the PM Loop

Chat tab → "build me a todo app with React frontend and Express backend"

Watch crew-pm break it into phases automatically

🔐 Review Security

Settings → Engines → Enable secure Docker config

AppArmor + firewall + read-only FS

📱 Connect Telegram

Dashboard → Communications → Setup bot

Control your crew from mobile

Ready to install?

npm install -g crewswarm
crewswarm