Cloud or Self-Host
The same engine either way. What differs is who runs the infrastructure and what you get on top.
SynapseOrch Cloud and a self-hosted install run the same engine. A workflow built in one works in the other, and export/import moves it across.
What differs is who operates it.
| Cloud | Self-hosted | |
|---|---|---|
| Infrastructure | Ours | Yours |
| Upgrades | Continuous | When you choose |
| Models | Platform models or your keys | Your keys, or local models |
| Team | Workspaces, roles, seats | One workspace |
| Scaling | Automatic | Scale mode, configured by you |
| Google Workspace | Connect in one click | Your own OAuth client |
| API | https://api.synapseorch.com, keys from the Developer page | http://localhost:3000, keys from Settings → API Keys |
| Notifications | By role, in the app and by email | In the app and the browser |
| MCP servers | Remote servers, added by URL | Remote and local (stdio) servers |
| Knowledge bases | Built in: OCR for scanned pages, a layout reader for PDFs, legacy Office files, SynapseOrch's reranker while it answers, webhooks | Built in; add the knowledge extra for PDF layout and LibreOffice for legacy Office files; no OCR |
| Python tools and Transform steps | Team and Business plans | Always |
| Cost | Credits, Free tier available | Free — you pay infrastructure and models |
| Licence | Commercial | AGPL-3.0 |
| Support | Included | Community — GitHub and Discord |
Choose Cloud when
- You would rather not operate Redis, Postgres, object storage and a worker fleet
- More than one person builds workflows, and you want roles and audit
- You want to use models without holding provider contracts
- You want someone to call when a run misbehaves
Choose self-hosting when
- Data must not leave your network — a hard requirement rather than a preference
- You want local models through Ollama with nothing leaving the machine
- You are evaluating, learning, or building something personal
- You already run this kind of infrastructure and would rather own it
Self-hosting is the full product, not a trial. The engine is AGPL-3.0 and there is no feature held back to make Cloud look better.
Things worth knowing before you choose
AGPL applies if you offer it as a service. Running SynapseOrch internally imposes nothing on you. Offering a modified version to others over a network means publishing your modifications. If that is a problem, Cloud is the answer.
A few things are cloud-only for structural reasons. The hosted Google connection is one — self-hosting uses your own OAuth client, because the credential belongs to whoever runs the deployment. These are consequences of who operates the software, not features withheld.
Moving later is expected. Start self-hosted and move to Cloud, or leave Cloud and take your workflows with you — export is a portable bundle, not a hostage arrangement.
Next
- Cloud — Quick start · Get started
- Self-hosted — Install · Quick start