Skip to content
AI Primer
release

Vercel supports WebSockets in Fluid with Socket.IO and 30-minute reconnects

Vercel rolled out native WebSocket support so Node.js libraries like Socket.IO can run from CDN to Fluid. Existing sessions still reconnect at the 30-minute function limit, so teams should test long-lived connections before migrating.

2 min read
Vercel supports WebSockets in Fluid with Socket.IO and 30-minute reconnects
Vercel supports WebSockets in Fluid with Socket.IO and 30-minute reconnects

TL;DR

  • Vercel's announcement says WebSockets now run natively on Vercel, with support for standard Node.js libraries including Socket.IO.
  • In Guillermo Rauch's post, Vercel framed the rollout as end-to-end support, from CDN to Fluid.
  • Malte Ubl's reply says live connections still hit the current 30-minute function max duration, which forces a reconnect about twice per hour.

You can jump from Vercel's launch post into the linked product page, and Rauch's note adds the useful architectural framing: this is meant to work across Vercel's edge-facing CDN layer and its Fluid compute layer. The less-advertised caveat came in a follow-up reply, where Vercel confirmed the current session limit is still tied to function duration.

WebSockets in Fluid

Vercel says developers can now build realtime apps on the platform with standard Node.js WebSocket libraries, including Socket.IO. That matters mostly because teams no longer need a separate realtime provider just to keep familiar server-side connection code running on Vercel.

Rauch described the feature as support "from CDN to Fluid," which is the clearest clue about scope in the launch-day evidence. The rollout is being presented as a platform capability, not a narrow framework-specific integration.

Socket.IO compatibility

The launch post in Vercel's announcement explicitly names Socket.IO, which is the practical detail most Node teams needed. Vercel also says WebSockets work with standard Node.js libraries, so the compatibility story is broader than a single package.

That leaves two concrete launch claims:

30-minute reconnects

The current catch is session length. In a reply to a user asking about duration, Malte Ubl said the function max duration is 30 minutes today, though he added that it "will soon rise."

Because the connection is still bounded by that limit, Vercel currently enforces a reconnect at the 30-minute mark. Ubl quantified it as "2 per hour until we go higher" in his reply.

Share on X