Skip to content

Deployment options

Every plan level can self-host the agent core. This page goes from lightest to heaviest.

No infrastructure at all — agents run in-process with in-memory adapters, ideal for evaluation and for individual engineers:

Terminal window
claude mcp add data-workers -- npx -y dw-claw

In-memory adapters are suitable for development and evaluation; production deployments should use real infrastructure adapters (below).

Terminal window
git clone https://github.com/DhanushAShetty/data-workers.git
cd data-workers
npm install
./start-agent.sh dw-connectors # any agent by name

Agents run from source via tsx — no build step. Cross-platform (Windows-safe) equivalents:

Terminal window
node plugin/scripts/install.mjs # prereq check + install
node plugin/scripts/start-agent.mjs <agent>

Single image:

Terminal window
docker pull ghcr.io/dhanushashetty/data-workers:latest
docker run -it ghcr.io/dhanushashetty/data-workers:latest

Full stack with real infrastructure via Compose:

Terminal window
docker compose -f docker-compose.yml -f docker/docker-compose.agents.yml --env-file .env up -d

The production profile expects PostgreSQL 16 (with pgvector) and Redis 7, plus one LLM provider key; Neo4j 5, Kafka, and Airflow are optional, enabled when the matching agents need them.

Requirements: Node.js ≥ 20, npm ≥ 10, Docker ≥ 24 (Kubernetes ≥ 1.28 for the manifests below).

Example manifests — per-agent Deployments plus the shared services — are in the repo’s deployment guide (DEPLOYMENT.md). Sizing guidance: agents are I/O-bound; start small and scale replicas on the agents your team actually uses (usage intelligence will tell you which those are).

Fully offline installs are supported and documented in the repo’s air-gap deployment guide (docs/DEPLOYMENT-AIRGAP.md): mirrored registries for npm and OCI images, offline licensing, and local model inference (Ollama/vLLM) so zero external network calls leave the boundary — including model calls. Air-gap installs are set up with our team as part of Enterprise onboarding.

SituationPath
Evaluating, or an individual engineerZero-install npx
A team rolloutZero-install per engineer + shared service credentials
You want to modify agentsFrom source
Production self-hosting with persistenceDocker Compose or Kubernetes
Regulated / offline environmentAir-gapped, with us