Asopitech With · Design tool
Figma multiplayer with Alopex Chirps
Figma multiplayer is how Figma, the design tool, lets several people edit the same design at once. What if we rebuilt it by applying Alopex Chirps?
Updated: Oct 13, 2026
What the service does
In Figma, several people edit the same design document at once. According to Figma’s engineering blog, clients talk to a cluster of servers over WebSockets, a separate process runs for each document, and everyone editing that document connects to it. The server keeps the latest value sent for each property of each object. The data is the document’s tree of objects and each person’s cursor and selection.
How the communication is built
- Node membership: the servers that host documents join the mesh as nodes. Through gossip, every node knows which nodes are running.
- Forwarding edits: edits from people connected to another node are sent, addressed, to the node that hosts the document.
- Cursor delivery: cursor and selection positions are sent on the ephemeral delivery profile, which tolerates staleness. They flow separately from edits.
- Node departure: when the node hosting a document stops, a leave event arrives, and another node can reopen the document.
Which node hosts which document, and how property values are decided, are the application’s code.
Deployment
Chirps is embedded in each server node. Nodes connect over QUIC with mutual TLS.
Why Alopex Chirps fits
A multiplayer server carries two flows of different nature: edits that must arrive and cursors that can be thinned out. Chirps sends them on separate delivery profiles, and reports nodes joining and leaving through gossip.
Build a multiplayer server with Alopex Chirps, sending edits and cursors between nodes on separate delivery profiles. Start from the quickstart on GitHub.