Realtime application framework (Node.JS server)
Companies using Socket.IO
How Socket.IO is being used
  • Trello


    Where we have browser support (recent Chrome, Firefox, and Safari), we make a WebSocket connection so that the server can push changes made by other people down to browsers listening on the appropriate channels. We use a modified version* of the client and server libraries that allows us to keep many thousands of open WebSockets on each of our servers at very little cost in terms of CPU or memory usage. So when anything happens to a board you’re watching, that action is published to our server processes and propagated to your watching browser with very minimal latency, usually well under a second.

  • InstaGIS

    #<User:0x00007f7f16515a80> InstaGIS

    websocket for realtime communication and map sync

  • AyeDeals

    #<User:0x00007f7f16542648> AyeDeals

    We use to power Ayedeals business. More specifically for real time analytics.

  • Zube

    #<User:0x00007f7f165746c0> Zube

    Everything on Zube happens in real-time. We hooked Socket into all of our models.

  • DSP

    #<User:0x00007f7f16725fa0> DSP

    We use to notify user when long running UI tasks finish.

  • Patreon

    #<User:0x00007f7f1676cf90> Patreon

    Live chat server

  • Web Application Stack

    #<User:0x00007f7f176f5818> Web Application Stack

    Used for sending real-time updates to connected browsers; to give real-time feedback about e.g. messages assigned to you, resolves in the inbox, etc.