SYNAPSE CHANNEL Fleet
Commercial multi-machine fabric

Operate every hub as one governed fleet.

SYNAPSE CHANNEL Fleet turns the open-source coordination Core into a durable multi-machine operating fabric—with restart-safe sync, per-peer trust, offline licence admission, and evidence that survives disconnection.

synapse-fleet doctorREAD ONLY
hub-a → hub-bcaught_up
mirror integrityverified
trust generationcurrent
remote claimsobserved only
v0.8.1Fleet alpha
v0.99.13Required Core
Private wheelNever public PyPI
OfflineNo phone-home licensing
01 / Capabilities

Production operations without weakening local authority.

The open-source Core owns the wire protocol and federation primitives. Fleet adds the durable service, operator controls, trust lifecycle, and commercial deployment boundary.

01

Durable hub-to-hub sync

Restart-safe per-peer mirrors, bounded concurrent drains, backoff isolation, checksummed journal segments, and fail-closed cursors.

02

Live trust reload

Changed mTLS and Ed25519 trust material is validated as one immutable generation before any socket opens.

03

Per-peer operations

Strict versioned configuration, separate credentials and cadence, protocol negotiation, status snapshots, and a read-only doctor pass.

04

Offline licence admission

Named-license documents are verified locally before credentials are read or network connections begin. No account lookup or telemetry.

05

Lease-correct forwarding

Remote claims route only through the configured owner; denials and malformed or expired verdicts are never cached.

06

Signed audit equality

Independently signed commitments let operators verify equal Core log state offline across deployment boundaries.

02 / Evidence

Claims stay inside the proof boundary.

Fleet includes automated protocol-path and replay evidence. Physical host separation and observability captures remain explicit deployment evidence—not assumed product facts.

Implemented and automated

Durable sync and recovery, trust rotation, partition-denial replay, audit-equality verification, protocol negotiation, and OTLP export paths.

Deployment evidence remains local

Three physically separate machines, site-specific custody, and Grafana or Jaeger views must be captured and approved for each deployment.

Commercial boundary

Private delivery. Named licensees. Explicit custody.

  • Fleet is proprietary software under the SYNAPSE Enterprise Licence Agreement.
  • It is distributed as a private wheel and is never published to public PyPI.
  • The product is currently alpha; deployment scope and support terms are agreed before delivery.
  • Fleet does not replace the open-source Core or redefine its wire and federation contracts.
  • Contact Anulum Research for architecture review, licensing, and deployment planning.