🧪 y-generic Test Experiments

Explore different transport providers for Yjs collaborative editing. Each experiment demonstrates real-time synchronization using a different backend technology.

In-memory simulation for testing. Configure network delay, packet loss, and jitter to test sync resilience under various conditions.

Local Testing Simulation

SimplePeer (WebRTC)

Direct peer-to-peer connection using WebRTC. Requires manual signal exchange via copy/paste. No server needed after connection.

P2P WebRTC Manual

PeerJS (WebRTC)

Simplified WebRTC with automatic signaling server. Uses PeerJS cloud servers by default. Easy peer-to-peer connections.

P2P WebRTC Cloud

Browser-based persistent storage. Data survives page reloads. Works offline, great for local-first applications with occasional sync.

Local Persistent Offline

Decentralized graph database with peer-to-peer sync. Distributed architecture, no single point of failure.

Decentralized P2P Graph DB

Serverless WebRTC with multiple strategies: Nostr, BitTorrent, MQTT, and IPFS. Choose your decentralized signaling method.

P2P Decentralized Multi-strategy

Real-time cloud pub/sub with automatic message chunking. Global CDN, high scalability, optional encryption and persistence.

Cloud Pub/Sub Scalable

Compatible with y-websocket servers. Classic client-server architecture with reliable bidirectional communication.

Client-Server y-websocket Standard

Matrix Protocol

Decentralized communication protocol. Federated architecture, end-to-end encryption support, accounts required.

Decentralized Federated Encrypted