Discord-style realtime chat on Cloudflare (no VPS)

Why builders search for this

Show HN posts and CF tutorials keep winning with one message: realtime rooms without running your own WebSocket VM. Discord-style here means many clients in a room, ordered messages, presence — not cloning Discord’s entire product.

FluxyChat targets teams who want that architecture for in-app SaaS chat, not a gaming social network.

The Cloudflare stack (Accord-style)

• Workers — HTTP API, JWT mint, WebSocket upgrade routing.
• One Durable Object per room — fan-out, typing, live connections.
• D1 — message history, search, tenant metadata.
• R2 (optional) — attachments; your Worker signs uploads.
• No Socket.io cluster on a VPS; no second realtime vendor if you self-host on CF.

Build a real-time chat application on Cloudflare Workers →

Replacing Socket.io or a VPS fleet

• Socket.io on Node: you operate processes, regions, and sticky sessions.
• Room-per-DO: Cloudflare routes clients to the object that owns that room’s state.
• Client: @fluxy-chat/sdk (reconnect, loadMore) instead of hand-rolled socket.io client glue.
• Tradeoff: you learn CF billing and DO patterns — not a managed Pusher dashboard.

Where FluxyChat fits

MIT monorepo with RoomDurableObject, operator console, agents on the same room WebSocket, hosted beta or deploy to your account. Use the demo to feel the UX, then self-host when you need control.