Beta build. Report issues to your operator channel.

Documentation

Guides and reference

Auth, SDK, and deployment notes for Fluxychat. Long-form guides live under /guides. This page is public — no account required (same as /compare).

Auth & JWT

API key (fc_...): server-to-server, identifies your project. Store in env on your backend only.

JWT: for browsers and the SDK. Mint with POST /auth/token and header X-Fluxy-Api-Key. Claims include sub (user id), tid (project id), and roles.

With Clerk enabled, the dashboard provisions your tenant and mints operator JWTs server-side — you do not paste bootstrap keys in the browser.

SDK

pnpm add @fluxy-chat/sdk

import { FluxyChatClient, useChat } from "@fluxy-chat/sdk";

const client = new FluxyChatClient({
  baseUrl: process.env.NEXT_PUBLIC_FLUXYCHAT_CLOUD_URL,
  userId: "user_123",
  token: memberJwtFromYourBackend,
});

Webhooks & billing

Configure outbound webhooks per project in the console. Stripe checkout and usage quotas are enforced on the Worker upgrade plans from Billing after you connect an account.

Web Push (browser notifications)

VAPID + RFC 8188 encrypted browser push, self-hosted — wire-compatible with Pusher Beams. Fetch the project public key from GET /push/web/vapid-public-key and register the browser's PushSubscription via POST /push/web/subscribe. No third-party push service required. Full protocol notes, SDK usage, and service worker snippet in docs/web-push-vapid.md.