Architecture
Deep dives into how Synap is built — for technical readers and evaluators
This space holds technical depth: how the pod, events, graph, agents, and deployment fit together. Use Synap stays light (install, “what is it?”, guides); the long reads live here.
Who this is for
- Technical evaluators validating system design and trust boundaries
- Engineers implementing integrations or extensions safely
- Self-host operators planning deployment and operational posture
If you are evaluating Synap
- What is Synap? — product framing and pillars
- Architecture (system concepts) — system shape for technical buyers
- Data sovereignty — trust, boundaries, and ownership
If you are integrating
- API reference — Hub Protocol and REST surface
- Event catalog — event types and flows
- Integration fundamentals — webhooks, SDKs, and patterns
If you are self-hosting
- Deployment overview — environments and components
- Self-hosted data pod — run your own pod
- Pod replication & pairing — optional second pod / replica (event-log sync)
- API keys — authenticate automation and clients to your pod
Curated reads
- System concepts index — full library (events, graph, channels, AI, sovereignty)
- Event sourcing explained · Why events
- Hub and spoke · Composable architecture
Read next
- Build and integration guides: /docs/integrate
- Team-only deep operations and implementation detail: /team/platform/index
