Synapse AI — Multi-Agent Orchestration Platform

Build AI workflows that actually ship.

Wire agents, tools, and LLMs into deterministic pipelines — without the framework lock-in. Synapse is an open-source platform for creating, connecting, and orchestrating AI agents powered by any LLM — local or cloud. Agents use real tools: browsing the web, querying databases, executing code, reading files, managing emails, and anything else you can expose through an MCP server, a webhook, or a Python script.

🌐 Website · 📖 Documentation · 💬 Discord

---

Install

Quick Setup Script (recommended)

macOS / Linux:

curl -sSL https://raw.githubusercontent.com/synapseorch-ai/synapse-ai/main/setup.sh | bash

Windows (PowerShell):

irm https://raw.githubusercontent.com/synapseorch-ai/synapse-ai/main/setup.ps1 | iex

npm

npm install -g synapse-orch-ai
synapse

pip

pip install synapse-orch-ai
synapse

Docker

docker run -d \
  -p 3000:3000 \
  -v synapse-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  synapseorchai/synapse-ai:latest

Then open http://localhost:3000. See the Docker guide in the docs for custom ports and environment variable configuration.

Security: publish only the frontend port 3000 — the backend (8765) serves an internal API and should not be exposed on 0.0.0.0 (docker-compose binds it to 127.0.0.1). The container auto-generates a shared internal token so that surface is authenticated by default. For any network-reachable deployment, enable login (Settings → Security) and/or set allow_stdio_mcp=false, since registering a stdio MCP server launches local commands.

Upgrading

Install method	Upgrade command
Bash / PowerShell installer (recommended)	synapse upgrade
pip	pip install --upgrade synapse-orch-ai
npm	npm update -g synapse-orch-ai
Docker	docker pull synapseorchai/synapse-ai:latest

Upgrade note (security hardening): the backend now auto-generates a shared internal token and, under docker-compose, binds its port to 127.0.0.1 by default. The UI and its API are unaffected (the frontend proxies the backend internally). If you previously called the backend directly on :8765 (e.g. external API clients), either point them at the frontend instead — http://host:3000/api/v1|v2/... — or set SYNAPSE_BACKEND_BIND=0.0.0.0 in .env to keep publishing :8765.

---

Scale Mode

Run unlimited agents and orchestrations concurrently. When you need to go beyond a single process, the distributed scale layer handles the load:

• Redis Cluster — job queue, SSE event streams, pub/sub cancellation signals, auto-failover
• ARQ worker fleet — 1 to 100+ independent workers, each running up to 20 concurrent orchestrations; autoscale with KEDA on queue depth
• PgBouncer — multiplexes hundreds of worker connections into a small, stable Postgres pool
• S3 artifact storage — stream large file outputs directly to AWS S3, Cloudflare R2, or MinIO
• Multi-tenant quotas — per-team or per-customer concurrent run limits with HTTP 429 enforcement
• Per-step checkpoint recovery — worker crashes don't lose jobs; the next worker resumes from the last completed step