Use the following command to start all necessary Jitsu services:

docker compose -f ./docker/docker-compose.yml up --force-recreate

This will start all Jitsu services. Once running, open http://localhost:3000 in your browser and login with admin@jitsu.com / admin123 (you can customize these via SEED_USER_EMAIL and SEED_USER_PASSWORD variables, see Configuration Variables section below).

Note: This setup is for exploration and development only. For production deployment, see https://docs.jitsu.com/self-hosting/production-deployment

For development with hot reload enabled, use: docker compose -f ./docker/docker-compose.yml --profile jitsu-services-dev up -d --force-recreate. This starts all Jitsu services with hot reload, allowing you to make changes to the code and see them reflected immediately without restarting containers. Note: clean all node_modules dir to avoid conflicts between docker and local installs: rm -rf .pnpm-store && rm -rf ./node_modules && rm -rf find . -iname node_modules -type d`

You can also start just 3rd-party services by: docker compose -f ./docker/docker-compose.yml --profile jitsu-dependencies up --force-recreate

If you want to start Jitsu in ordinary mode, but rebuild images from local sources use docker compose -f ./docker/docker-compose.yml up --force-recreate --build

Note: The dev mode uses:

• jitsucom/jitsu-builder:latest for Node.js services (Console, Rotor)
• golang:1.22-alpine for Go services (Bulker, Ingest) - lightweight Alpine Linux image

Override these variables via environment variables or by creating a .env.local file

Jitsu Connectors manages synchronization jobs in Kubernetes. If Kubernetes is not configured, syncctl service will exit gracefully without affecting other services, but syncs (aka Connectors) won't be available

• Start kubectl proxy on host machine: kubectl proxy --port=8001 --context my-context (you could use any port)
• Set environment variable to use proxy in SYNCCTL_KUBERNETES_CLIENT_CONFIG=http://host.docker.internal:8001

Alse set SYNCS_ENABLED to true

Note: When using kubectl proxy, SYNCCTL_KUBERNETES_CONTEXT is not needed - the proxy uses your host's current kubectl context.

You can use any k8s cluster to run syncs, just set following variables in .env.local

SYNCCTL_KUBERNETES_CLIENT_CONFIG=https://your-cluster-api:6443
SYNCCTL_KUBERNETES_CONTEXT=my-context
SYNCCTL_KUBERNETES_TOKEN=<your-service-account-token>

docker compose -f ./docker/docker-compose.yml --profile jitsu-dependencies up -d

docker compose -f ./docker/docker-compose.yml down

docker compose -f ./docker/docker-compose.yml logs -f console

docker compose -f ./docker/docker-compose.yml down -v
rm -rf ./docker/data/*

All persistent data is stored in ./docker/data/ directory:

• ./docker/data/postgres - PostgreSQL data
• ./docker/data/redpanda - Redpanda/Kafka data
• ./docker/data/mongodb - MongoDB data
• ./docker/data/clickhouse - ClickHouse data
• ./docker/data/cloudbeaver - CloudBeaver configuration (if used)

• Check Docker logs: docker compose -f ./docker/docker-compose.yml logs
• Ensure ports are not already in use
• Try rebuilding: docker compose -f ./docker/docker-compose.yml build --no-cache

• Wait for health checks to pass (can take up to 60 seconds on first start)
• Check if the database containers are running: docker ps