Chatbase alternative for agencies: build and white-label your own AI chat widget

Chatbase works. That's not the complaint. The complaint is the invoice: $19 to $399 a month, per bot, under Chatbase's brand, for a widget you configured with your client's documents and your client's colors. You did the work. Chatbase gets the recurring line item.

The margin ceiling every reseller hits

Agencies reselling Chatbase (or SiteGPT, or DocsBot, or any of the dozen clones) run into the same wall eventually: the software is rented, not owned. Add a second client and you're paying a second subscription. Add ten and you're paying ten, with no volume discount on the part that actually costs Chatbase nothing marginal, the inference is metered separately, the seat fee is pure margin for them.

The alternative agencies reach for is "just build our own chatbot." Then they hit the actual hard part.

What "white-label" requires that a single-tenant chatbot doesn't have

A basic AI chatbot tutorial gets you one bot, one account, one set of documents. That's a demo. A resellable product needs:

• A multi-tenant data model. Not "one chatbot," but a bots table: one row per client, each with its own public embed key, its own domain allowlist, its own branding (name, color, welcome message), and its own document scope so client A's uploaded pricing sheet never leaks into client B's answers.
• An embed that doesn't break the host site. The widget has to sit on a client's WordPress site, their Webflow site, their custom Next.js app, without CSS fighting either direction. That means an iframe, not injected DOM.
• Abuse protection on a public endpoint. The chat API has to accept messages from anonymous visitors with zero login, which is exactly the kind of endpoint that gets hammered by a bot or a curious competitor running up your client's bill. Rate limits and a real credit-balance check are not optional here.

None of this is exotic engineering. It's just the specific set of things a "build me a chatbot" tutorial skips, and the reason most agencies give up and pay the Chatbase tax instead.

What that architecture looks like

• bots table: public key, allowed domains, branding, system prompt, active flag, per client
• Documents scoped per bot: retrieval filtered by bot_id, not account-wide
• Sandboxed iframe widget: one <script data-bot-key> tag, zero CSS collisions in either direction
• Rate limits + credit caps: per-visitor, per-bot-hourly, per-bot-daily, plus a check against the actual owner balance before generating a response
• Lead capture: contact details a visitor shares in chat land in a table and trigger an email to the bot's owner, immediately

That's the shape Deskly ships pre-built, not as a hosted service you rent, but as source code you buy once and run yourself. See how to build this from scratch if you want the architecture walkthrough.

The pricing math

One agency account, five clients, Chatbase's mid-tier plan (roughly $99/month per bot at the time of writing, verify current pricing before quoting a client): that's real recurring cost stacking per client, forever, with your margin being whatever you mark up on top. The same five clients on a self-hosted, white-label widget: one one-time purchase, then whatever AI provider costs you actually incur (typically a few dollars per client per month at normal usage), and the full markup is yours, every month, with no vendor able to raise prices on you mid-contract.

Buy once, own the repo, resell it under your own brand: that's the actual alternative, not another hosted tool with a different logo.