SynapSynapDocs

Synap Cloud

Hosted control-plane services that remove operational complexity while keeping your pod-centric model

Product: synap.live

Synap can be self-hosted end to end.
Synap Cloud exists for teams that want the Synap model without day-one ops burden.

Why Synap Cloud exists

For most teams, the hard part is not only running containers. It is lifecycle operations around them:

  • account and session management
  • pod creation and updates
  • subscription and plan transitions
  • integration onboarding (OAuth connectors, add-on services)
  • consistent policy/security boundaries between app, agents, and pod access

Synap Cloud handles these flows so users can move directly to capturing and operating data.

What Synap Cloud does (public view)

  • Identity and access lifecycle: managed sign-in/session and account lifecycle across Synap surfaces
  • Pod lifecycle orchestration: provisioning, updating, and operational workflows for hosted pods
  • Optional pod pairing (when enabled for your plan): link two pods you own as primary ↔ replica for event-log replication — see Pod replication & pairing
  • Commercial operations: billing/subscription lifecycle for hosted plans
  • Connector control plane: managed OAuth session flow for external providers
  • Optional managed add-ons: e.g. managed OpenClaw onboarding path when available

What Synap Cloud does not replace

  • Your data model still lives in the pod (entities, views, channels).
  • Your integration surface for external tools remains Hub Protocol on the pod.
  • You can still choose self-hosting for full infrastructure control.

Typical usage path

  1. Create account on synap.live
  2. Provision and access your workspace/pod
  3. Connect providers and automation paths as needed
  4. Enable intelligence layer (managed or self-managed)

When to choose Cloud vs self-hosting

Choose Synap Cloud when you want:

  • fastest onboarding
  • managed lifecycle operations
  • less operational overhead

Choose self-hosting when you need:

  • full infrastructure sovereignty and custom ops control
  • custom networking/compliance constraints
  • fully internalized deployment pipelines

Continue