Facts read November 7, 2026
Cached polling (no realtime service) vs Liveblocks
Liveblocks is Cuely's default realtime pick when your description doesn't favor either one: rooms, presence and shared state for collaborative boards and documents, with React hooks. Pick Cached polling (no realtime service) if you care most about viral traffic spikes.
Side by side
| Fact | Cached polling (no realtime service) | Liveblocks |
|---|---|---|
| What it is | Clients re-fetch one results endpoint every few seconds, and the host caches its answer so every player shares it. | Hosted realtime collaboration: rooms, presence, shared state, comments. |
| Free plan | No service to sign up for. On Vercel, a function response with Cache-Control: s-maxage is served from the CDN, and a cached response doesn't run the function; on Cloudflare Workers, cache the answer with the Cache API, and each poll is a Worker request. | Free: unlimited monthly active users, 500 monthly active rooms, 10 simultaneous connections per room, 3,000 realtime collaboration minutes. |
| Paid from | Not stated | Pro: $25/month billed annually. |
| At 1,000 users | $0/month | $0/month |
| Open source | No | No |
| Self-hostable | Yes | No |
| Best for | Live vote percentages and leaderboards; Traffic that spikes when something is shared; Staying on one bill | Collaborative boards, whiteboards and documents; Presence and live cursors; React apps |
| Watch out | Players see numbers up to the cache time old (a few seconds); use a push service for chat, cursors or fast multiplayer. | The free plan allows 10 simultaneous connections per room and 500 monthly active rooms. |
Where they differ
The published scores, from −3 to +3, that decide which one Cuely picks for each need.
| Need | Cached polling (no realtime service) | Liveblocks |
|---|---|---|
| traffic comes in viral spikes | +3 Every player reads the same cached answer, so a viral day adds cheap cached requests, not connections or messages. | −1 Built for rooms of collaborators (10 at once per room on Free), not one broadcast to a crowd. |
| realtime features | −1 Updates every few seconds rather than instantly: fine for crowd numbers, not for presence, chat or shared editing. | +3 Rooms, presence and conflict-free shared state are the product. |
| keep costs as low as possible | +2 No extra vendor or bill. | 0 No particular strength here. |
| votes, scores, leaderboards or streaks (many writes to the same numbers) | +2 Fits tallies and leaderboards that only need to be a few seconds fresh. | 0 No particular strength here. |
| Next.js or React | 0 No particular strength here. | +1 React hooks and Next.js examples. |
| sells to businesses (organizations, roles, SSO) | 0 No particular strength here. | +1 A room per team session maps well onto team tools. |
Sources: Cached polling (no realtime service) pricing (read November 9, 2026), Liveblocks pricing (read November 7, 2026). No vendor pays for placement.