TL;DR: Token revocation and socket termination solve different problems. Revocation rejects the next authorization; it does not close a connection that is already carrying cursor events. For a fintech editor, logout should revoke the credential, disconnect the real client identity, and then confirm that identity has disappeared from channel presence.
This is a delivery-guarantee decision, not a cosmetic cleanup. If the server accepts a logout but an old tab can still fan out cursor positions, the UI and the security boundary disagree. I would make the server-side disconnect part of the logout transaction and treat presence as the recovery check.
That gap matters.
Infrai fits this workflow when a small team wants realtime alongside other backend services under one key and one bill.…