Start with a public room and a publishable key. Add the console when you need member JWTs, agents, or invoices. Self-hosting is optional, and the hosted beta does not pretend to be an enterprise contract.
Scaffold a chat-only Vite app, or install the React SDK into the app you already have. A public room needs a publishableKey; private rooms need a member JWT minted on your server.
SDK quickstart
pnpm add @fluxy-chat/reactNEXT_PUBLIC_FLUXYCHAT_CLOUD_URL=https://api.fluxychat.comimport { FluxyRealtimeProvider, useChat } from "@fluxy-chat/react";
<FluxyRealtimeProvider workerUrl={workerUrl} publishableKey="pk_...">
<Chat />
</FluxyRealtimeProvider>
function Chat() {
const { messages, sendMessage } = useChat({ roomId: "general" });
}Custom bots: FluxyMessageStream. See docs/cookbook/bot-streaming-fluxy-message-stream.md
Public rooms use publishableKey on the provider, or guest on FluxyChatWidget. No card. Free hosted is beta. For headless control, use useChat.
npx @fluxy-chat/create-fluxy-chat@latest my-chat --minimal
pnpm add @fluxy-chat/ui-kitStep-by-step afternoon guide in the repo: docs/quickstart-afternoon.md.
npx @fluxy-chat/create-fluxy-chat@latest my-room --example shared-ai-room. Guest join, two tabs. Console signup is later, for ops.
pnpm add @fluxy-chat/react. FluxyRealtimeProvider plus publishableKey (pk_). No token endpoint on public rooms.
wrangler deploy on your Cloudflare account. Hosted cloud is beta if you want us to run the Worker.
Sign in when you need JWT minting, agents, or invoices. Not required to try a public room.
POST /auth/token with X-Fluxy-Api-Key (fc_ stays on the server). pk_ cannot mint member tokens.
Deploy the Worker and D1 from the monorepo when you need your own Cloudflare account or an isolated tenant. Most teams start on hosted cloud and move here when compliance or scale asks for it.
apps/workerNEXT_PUBLIC_FLUXYCHAT_WORKER_URL in your appdocs/cookbook/auth-jwt.mdDeploy Worker to CloudflareWorker README on GitHubManual setup wizard
Read the contract, then build.
Hosted is beta. Pin the SDK versions and run your own load review before production. For procurement, start with the legal pages, not a badge.