Multiplayer, built in.
Live cursors, presence, and shared state for docs, boards, and dashboards. One server syncs your rows and broadcasts who's online and what they're doing.
Adding multiplayer usually means bolting a realtime service onto your database and keeping two systems in sync: one for persistent data, another for ephemeral presence and broadcast. That seam creates stale cursors, ghosted users, and conflicting state.
Presence and live cursors
Join a room, publish a cursor position, selection, or typing indicator, and receive everyone else's presence in real time. Pylon handles join and leave events so users appear and disappear cleanly.
Shared state that persists
Ephemeral signals go over broadcast; the document itself is rows in your typed database, synced live to every participant. Because both run on the same server, the persistent state and the presence layer never disagree about who changed what.
Permissions that hold under concurrency
Row-level policies gate every collaborative write in the hot path for each participant. Viewers cannot edit, non-members cannot read, and access changes take effect across connected clients immediately.
Ship it on Pylon.
Scaffold an app in seconds, deploy free on Cloud, scale when you need to.