System Architecture
Data flows through five core components — from client SDK through the sync engine to persistence and cache — ensuring consistency and sub-5ms latency at 50,000 ops/sec.
Hover over nodes to explore component details
Performance at Scale
Battle-tested under load. Every metric backed by property-based tests and live benchmarks.
Key Features
Built for demanding real-time applications with strong consistency guarantees.
Live Interactive Demos
Every demo below connects to the live Sync Engine via WebSocket. Real operations, real metrics, real-time convergence.
Collaborative Whiteboard
Draw on the canvas — a simulated collaborator will mirror the multi-user experience in real-time.
Learn More →Live Metrics
Live metrics from all active sessions — ops/sec, latency percentiles, and connection counts.
Learn More →Conflict Resolution
0 eventsWatch how the CRDT engine resolves concurrent edits with LWW timestamps.
Learn More →Verified CRDT Properties
All 21 properties verified through property-based testing using fast-check
| # | Property | Explanation |
|---|---|---|
| 1 | Commutativity | Operations can be applied in any order and produce the same result |
| 2 | Associativity | Grouping of operations does not affect the final result |
| 3 | Idempotency | Applying the same operation multiple times has no additional effect |
| 4 | Convergence | All replicas eventually reach the same state |
| 5 | Causal Ordering | Operations respect causal dependencies via HLC timestamps |
| 6 | Last-Writer-Wins | Concurrent conflicts resolve deterministically by timestamp |
| 7 | Monotonic Clock | HLC timestamps always increase across operations |
| 8 | Bounded Drift | Physical clock drift is bounded and detectable |
| 9 | Add Uniqueness | Each add operation creates a unique item identity |
| 10 | Remove Semantics | Removes are tombstoned, preserving history |
| 11 | Update Atomicity | Field updates are applied atomically |
| 12 | Delta Minimality | Only changed fields are included in state deltas |
| 13 | Delta Completeness | All changes from an operation appear in the delta |
| 14 | Merge Determinism | Same inputs always produce the same merged state |
| 15 | State Validity | Merged state always satisfies invariants (non-negative qty, valid names) |
| 16 | Operation Integrity | Operations are validated before processing |
| 17 | Offline Accumulation | Operations queue correctly during disconnection |
| 18 | Reconnection Sync | Queued operations replay correctly after reconnection |
| 19 | Concurrent Safety | Concurrent operations from multiple clients merge safely |
| 20 | Snapshot Consistency | Snapshots reflect a valid point-in-time state |
| 21 | Ordering Preservation | Operation order is preserved within each client's stream |