Build a chatbot platform and sell it as your own SaaS
One command gives you an AI agent platform on Chatfuel’s infrastructure. Put your name on it, sign customers up and charge what you like.
Your SaaS, on Chatfuel’s infrastructure
If you are a chatbot creator, this is how you get an AI agent platform of your own and make money on it. The agent, the channels and the data run on Chatfuel; the app runs under your name; every customer who signs up pays you, and what you pay is one Chatfuel plan. Each customer gets an account like this.
Sign-up on your website
Anyone who opens your website can create an account, and it is ready the moment they finish the form. There is nothing for you to approve or set up.
An AI agent for every account
Each new account gets an AI agent of its own, created on Chatfuel and paid for by your plan. Your customers never need a Chatfuel account and never see one.
More agents when they need them
A customer adds, renames and deletes agents on their team page and switches between them in the top bar. Every agent takes one slot on your plan and no work from you.
Their team, their roles
Customers invite colleagues by link, choose which agents each person may open, change roles and hand over ownership. Owner, admin and member are built in; the table below says what each can do.
One customer cannot see another
Your server checks every request against the agents that customer may open. A request that names somebody else’s agent is refused before it reaches Chatfuel.
The screens come with it
Sign-up, sign-in, invite, password reset and the team page ship with the module, with your name and logo on them. Your Chatfuel token stays on your server and never reaches a browser.
Your name on the sign-in screen
The name and mark you give the wizard are the browser tab, the top bar and every signed-out screen your customers meet. Nothing on the way in says whose scaffold it was.
The accounts are yours, in your own database
Email and password on a Supabase project you own, with your data and your keys. The wizard can create and migrate it from an access token, or you paste the URL and keys and run the SQL yourself — and every table it adds is prefixed, so the project can hold your own alongside them.
You set the price, and they pay you
Your customers pay you directly, on your terms, at whatever you decide to charge — nothing in the app takes a cut, sets a floor or knows what you asked for. What you owe Chatfuel is the other side of it and stays the same shape: your own workspace balance, one balance behind every customer agent.
Any feature you want, in your own repository
It is a React app you own outright — chatbot software under MIT, in your repository — so a screen nobody else sells is a directory you add and a line in the menu table. The design system, the API client and the proxy are copied in as source rather than installed, so there is no release schedule between you and the thing you thought of.
From one command to a paying customer
AI agent development platforms built with the SDK stand on one module: Accounts. It is opt-in — the wizard never installs it unasked, because it needs a database it cannot invent. Pick it in the module list, or name it on the command line as auth.
- 01
Run the wizard
It asks what the app is called and what mark it wears, which modules go in it, and — the decision that matters here — which Chatfuel workspace it runs on. That workspace is the billing container: every customer’s agent is created inside it, so its plan is what pays for all of them.
- 02
It sets up the database behind sign-up
On the recommended path a Supabase access token creates or picks the project, waits for it to come up, runs the migrations and turns email and password on. The run also asks who may sign up — open, which takes the address on trust because a fresh project has no mail server, confirm-email, or closed — and --signup answers it on the command line. On the manual path you paste the URL and keys, and the SQL files are written into the app for you to run yourself.
- 03
Deploy it
The deploy script ships inside the app rather than in the wizard, so the same command still works a month later. It puts the project on Vercel, and the wizard then adds the live origin to your database’s redirect allowlist, without which signing in on the real domain would fail.
- 04
Sell it
What is left is distribution and a price. Everyone you bring in signs up on their own and pays you directly, at whatever you decided to charge, and none of it passes through anything of ours. What you owe Chatfuel stays what it was before they arrived: the balance on the workspace their agents live in.
The team system you ship rather than build
Roles, invite links and access granted agent by agent are already in the product you are selling. Your customers hand these out to their own colleagues inside their own workspace, and none of it reaches you — an owner is the owner of their account, not of anything on your side.
| Name | Who they are | Agents they reach | Who they can invite | How the role moves |
|---|---|---|---|---|
| Owner | The account that signed up. At most one per workspace, and it is a unique index in the database that makes it one rather than a rule somebody remembered to write. | Every agent in the workspace, by role | Admins and members | Only by transfer — the owner cannot be removed, demoted or leave until somebody else has it |
| Admin | Runs the workspace day to day: members, invite links, and the agents themselves — creating, renaming, deleting and handing out access. | Every agent in the workspace, by role | Admins and members | Set by the owner or another admin, and taken back the same way |
| Member | Works in the agents they were handed. Access is a row per person per agent, added when they accept an invite carrying it or afterwards from the team page. | Only the agents granted to them | Nobody | Set by the invite that brought them in, or changed by an admin later |
FAQs
Yes, if you pick the modules. Flow Builder is the chatbot maker in the classic sense: flows on the left, blocks and connections on a canvas, an inspector on the right to edit each one. AI Agent is where they write how the agent answers on each channel and entry point, with a test chat that runs on the real pipeline. Both are screens in the app you ship, under your name, and both are source in your repository.
Flow Builder