Server-Sent Events streaming
Every board has a dedicated SSE connection. When any team member creates a card, moves a column, or posts a comment, every connected client sees the change instantly - no polling, no refresh.
// Real-time Collaboration
Flux uses Server-Sent Events to stream every board mutation to every connected client in real time. Optimistic updates make the UI feel instant. Conflict resolution handles the rest.
Every board has a dedicated SSE connection. When any team member creates a card, moves a column, or posts a comment, every connected client sees the change instantly - no polling, no refresh.
The UI updates immediately when you act, then reconciles with the server response. If a conflict is detected (another user edited the same card), the client rolls back and applies the authoritative state.
Every card, column, and board carries a version number. Edits include the expected version - if it does not match, the server rejects the mutation and the client resolves the conflict automatically.
When a browser tab goes hidden, the SSE connection closes to save resources. When you return, Flux reconnects and fetches any changes you missed - no stale data, no manual refresh.
Open the same board in multiple tabs or devices. SSE ensures every instance stays in sync. Drag a card on your laptop and see it move on your phone.
Flux uses Server-Sent Events (SSE) to stream updates from the server to every connected client. When any user makes a change, the server broadcasts an event and all clients invalidate their local cache, fetching fresh data automatically.
Flux uses optimistic concurrency control. Each entity has a version number - if your edit is based on a stale version, the server rejects it with a conflict error and your client automatically fetches the latest state.
Yes. SSE works in all modern browsers including mobile Safari and Chrome. The connection lifecycle is managed automatically - it disconnects when the tab is backgrounded and reconnects when you return.
Changes propagate to other clients within milliseconds of hitting the server. The UI updates optimistically on the acting client, so there is zero perceived latency for the person making the change.
// Try it live
Open the same board in two tabs and drag a card. You'll see why teams switch.