In-app chat for Cloudflare
Ship in-app chattoday.
Sign up, add @fluxy-chat/sdk, and run rooms, agents, and webhooks on hosted cloud. No Worker deploy required to start.
Later, deploy the Worker in your own Cloudflare account from the monorepo. Why we built it.
Works with npm and yarn too — same package name @fluxy-chat/sdk.
Your app
Live preview
The same hooks power your production UI: wire the client once, then iterate on layout and copy — the preview mirrors the room your users join in your app.
Works with stacks you already use
One SDK across common frontends and runtimes. Fork the repo when you want full control.
Deploy in your account. Quotas live in D1. Console access can require a one-time ack — usage still runs through your Worker with your keys.
Edge-first
Workers, Durable Objects, and D1 keep chat logic next to your data.
Hooks + REST
Build UI with @fluxy-chat/sdk. Manage keys and quotas in the dashboard.
Multi-tenant
Many projects and rooms on one deployment, with per-project billing hooks.
Messaging basics, on the edge
Hover a row to preview it. Channels, presence, mentions, webhooks, and AI hooks without a separate realtime stack.
Threads, polls, and translation are up to your product layer. Fluxychat ships the realtime core.
From blank repo to live threads
Install, connect, hooks, live messages — loops below and pauses when you scroll away.
Step 1
Install
One dependency. No native binaries, no sidecar.
Step 2
Point at your edge
Worker URL + scoped JWT — the client never sees admin keys.
Step 3
Open a room
Hooks subscribe, send, and reconcile — you keep your UI primitives.
Live
Ship the inbox
Typing, delivery, and history — already moving on the wire.
What ships in the box
Edge delivery, clear quotas, and a console for the day-two work. You own the UI; we handle rooms, delivery, and ops hooks.
Already set up? Open the console for rooms, agents, and billing.
Runs on your edge
WebSockets and Durable Objects handle presence, typing, and delivery. No socket fleet to babysit.
GDPR tools included
Export, erasure, audit trails, and signed webhooks when you need to answer security questionnaires.
Agents and webhooks
Invoke AI in rooms, retry webhook delivery, and fall back to SSE when WebSockets are blocked.
Middleware
Transform messages before they land
Moderate, validate, enrich, and fan out from the edge. Policy code stays on the data path, not in a sidecar you forget to deploy.
// hooks run on your Worker before delivery — policy stays on the edge.
Developers
SDK, docs, and console in one repo
Auth, rooms, and retries sit behind hooks and route handlers. When you need keys, quotas, or billing, open the operator UI instead of wiring another admin surface.
Where teams start
Pricing
Monthly limits for messages, agent invokes, and webhook deliveries. Each project stores enforcement in D1.
Console routes can require a one-time ack on your dashboard host. Billable usage still needs your Worker credentials.
Free
Try the stack without a card.
- 50,000 messages / month
- 1,000 agent invokes / month
- 10,000 webhook deliveries / month
- SDK and dashboard access
- Help via GitHub issues
- One project, fair-use limits
- Upgrade without migrating data
Starter
Production traffic with fixed monthly limits.
- 500,000 messages / month
- 10,000 agent invokes / month
- 100,000 webhook deliveries / month
- Higher quotas than Free
- Signed webhooks with retries
- GDPR export and erasure endpoints
- Email support (best effort)
Pro
Heavy rooms, agents, and webhook volume.
- 5,000,000 messages / month
- 100,000 agent invokes / month
- 1,000,000 webhook deliveries / month
- 5M messages, 100k agent invokes, 1M webhook deliveries per month
- Priority support
- Custom retention and audit (contact us)
- Annual invoicing on request
Need enterprise SSO, VPC-style isolation, or custom SLOs? Email fluxychat@outlook.com.
Why Fluxychat
Rough positioning, not a shootout. Check each row against what you actually need.
| Capability | Typical stream APIs | Typical Ably-style | Typical Channels (Pusher-style) | Fluxychat |
|---|---|---|---|---|
| Edge-native (Cloudflare-style) deployment | Managed cloud | Managed cloud | Managed cloud | Designed for Workers + DO + D1 |
| Operator dashboard (projects, keys, billing hooks) | Separate product area | Console + APIs | Channels dashboard | First-party console in this repo |
| SDK focus (drop-in hooks, minimal ceremony) | Strong SDKs | Strong SDKs | Channels SDKs | Opinionated @fluxy-chat/sdk + examples |
| Self-host / fork friendliness (MIT-style workflow) | Proprietary stack | Managed-first | Managed-first | Monorepo you can run end-to-end |
FAQs
Questions we hear when teams compare hosted chat APIs and edge deployments.
What is the chat API vs the SDK?▾
Your backend calls the Worker over HTTP. The browser uses @fluxy-chat/sdk to subscribe, send, and render. Same product, two surfaces.
How is this different from a fully managed vendor?▾
You can run the Worker and D1 in your Cloudflare account. Data stays where you deploy it, and you control upgrades. Hosted cloud is there when you want to skip infra on day one.
Can I add moderation and webhooks?▾
Yes. Run middleware on the edge, sign webhooks for downstream systems, and use the console for admin tasks.
Where should I start?▾
Copy the install command, run the quickstart wizard for a JWT and first room, then use the console for projects, agents, and billing.
Does a public dashboard mean public spend?▾
No. Billable calls need your JWTs and API keys on the Worker. Enable DASHBOARD_ACCESS_MODE=ack (and optional CONSOLE_GATE_SECRET) so console routes require a one-time acknowledgment first.
Read the guides
Auth, SDK setup, and self-host notes are on /docs. After sign-up, the quickstart wizard walks you through JWT and your first room.