event plane · live

Realtime state, synced everywhere.

Synqio is a sync engine for collaborative and offline-first apps: open one stream, publish events, and every client and server converges — automatically, conflict-free.

Get startedRead the docs
bash — subscribe to the event stream
# open a bidirectional event stream (HTTP/2, gRPC)
POST /sync.v1.Events
Authorization: Bearer <token>

# client → publish a change
{ "op":"patch", "doc":"board/42", "rev":1187 }

# server → fan-out to every subscriber, in order
◂ patch board/42 rev 1188  (3 peers, 6 ms)
◂ presence board/42 +2      (cursor sync)
26 k events / min peak
7 ms median fan-out
∞ offline, then merge
99.98% stream uptime

Why teams build on Synqio

⇄

One long-lived stream

A single HTTP/2 connection carries every publish and subscribe — no polling, no reconnect storms.

⌥

Conflict-free merges

CRDT documents converge regardless of order, so concurrent edits never clobber each other.

◴

Offline-first

Clients keep working offline and replay their event log on reconnect; the engine reconciles.

◈

Presence & cursors

Ephemeral presence, typing and cursor channels ride the same stream with zero setup.

⚿

Row-level auth

Signed tokens scope every subscription to the documents and channels a client may see.

⏻

Durable log

Every event is appended to a per-document log you can replay, audit or fork.

Status

●

Event plane

Operational · 6 ms p50 fan-out

●

Region · zrh

Operational · 3,400 live streams

●

Persistence

Operational · replication healthy