Overview
The fastest way to understand Synapsor is the local runner demo. It needs no Synapsor Cloud account and uses disposable Postgres/MySQL fixtures.
The local path proves semantic MCP tools, evidence, exact proposals, source unchanged before approval, guarded writeback, idempotent retry, and stale-row conflict.
Cloud-linked mode uses the same concept but moves shared approvals, policies, runner status, hosted evidence, and replay into Synapsor Cloud. Database credentials still stay in the customer-controlled runner environment.
Developer notes
- Run the local demo before connecting a real database.
- Use read-only credentials for MCP reads.
- Use a separate write credential only in the trusted runner environment.
- Connect Cloud when team approvals, RBAC, hosted replay, and runner visibility are needed.
- Cloud connect registers runner id/version/source metadata and sends a heartbeat; it does not upload Postgres/MySQL URLs or write credentials.