Telegram
Bot API. Fastest to set up, fewest messaging restrictions.
Comment-to-DM, broadcasts, sequences and a shared inbox. Everything you use ManyChat for, in an alternative that doesn't charge per contact.
No credit card. $0/month.
Replaces a ManyChat bill that grows with your list
Features
Pick a trigger, map out the replies, hit Test. When it works, set it live. Edits stay in a draft, so the live flow keeps running while you change it.
Comments and DMs from every channel land in one queue. Anything the bot can't handle is marked "Needs a person." Take over, and the automation pauses for that contact.
Send to everyone, a saved segment or your own rules. Before anything goes out, you see exactly who gets it and who's skipped, and why.
Sign in with the accounts you already run. Every flow and broadcast works on each one, with no extra setup and no upgrade.
Channels
ManyChat spreads these across four paid tiers. Here they all ship in the open-source build.
Bot API. Fastest to set up, fewest messaging restrictions.
DMs, story mentions, comment-to-DM, follow triggers. Inside Meta's messaging window.
Page inbox, ref URLs, keyword triggers. Same window rules, enforced per platform.
Cloud API. ManyChat keeps this on paid plans. Here it's in the free build.
Twilio. STOP and HELP handled for you.
SMTP, Resend or SES. One-click unsubscribe on every send.
Pricing
ManyChat runs four paid tiers priced by contact band, and keeps its AI features for Pro and above. We run one tier, and it counts nothing.
Self-hosted
$0/month, forever
Hosted · Free
$0/month
Hosted · Unlimited
$144 /year $180
Per workspace. Billed annually.
Comparison
ManyChat built this category, and it's a good product. 12 of the features you'd use are the same here. The other 6 are where the two differ, and two of those go ManyChat's way.
| Feature |
|
|
|---|---|---|
| Same on both | ||
| Visual flow builder | Yes | Yes |
| Keyword triggers | Yes | Yes |
| Comment-to-DM | Yes | Yes |
| Story mentions and replies | Yes | Yes |
| Ref URLs and QR codes | Yes | Yes |
| Shared team inbox | Yes | Yes |
| Broadcasts | Yes | Yes |
| Drip sequences | Yes | Yes |
| Tags, custom fields, segments | Yes | Yes |
| Template library | Yes | Yes |
| REST API and webhooks | Yes | Yes |
| Instagram, Messenger, Telegram | Yes | Yes |
| Where they differ | ||
| WhatsApp, SMS and email | When you self-host | Paid plans only |
| AI reply generation | Not yet | Included from Pro |
| Agency partner directory | No | Large ecosystem |
| Self-hosting | Free, no limits | Not available |
| Source code | Public, AGPL-3.0 | Closed |
| One price at any list size | Yes | Priced by contacts |
Get started
We run the servers, you build the flows. Free for your first 25 contacts a month, no credit card.
Three commands bring up the app and PostgreSQL. No Redis, no broker. For production, there's a Caddy setup with automatic HTTPS, or one-click deploys to Heroku and Render.
$ git clone https://github.com/brightbeanxyz/brightbean-chat.git
$ cd brightbean-chat
$ docker compose up
Then open http://localhost:8000.
Flows, broadcasts, sequences, the inbox and all six channels are free on GitHub. Nothing is held back for a paid version.
Your DM list is the one audience you own. It shouldn't depend on someone else's pricing page.
View on GitHubQuestions
It covers the same ground: keywords, comment-to-DM, flows, broadcasts, sequences, a shared inbox. ManyChat has years of polish and a directory of certified agencies that we don't. What you get instead is the source code and a bill that doesn't move when your list does.
It matches ManyChat's on purpose, so the two are easy to compare. 25 contacts a month, 4 live automations and 2 channels are enough to build a flow and watch it run. If you want real headroom for nothing, self-host instead. That build has no caps.
No feature held back, no contact band. You still pay Twilio, Meta or your email provider directly for messages sent, same as any other tool. The $15 a month covers running the app.
Yes. No open-core split: all six channels, broadcasts, sequences, the inbox and the API are in the AGPL-3.0 repo. Hosted is the same code with the servers handled.
The concepts map closely. Keywords, flows, sequences, broadcasts, tags and custom fields all exist under the same names. You'll have to rebuild the flows by hand, though. There's no importer yet.
Run it for your own business, modify it, publish nothing. The licence only bites if you offer a modified copy to other people as a network service. Then those users get your source. Marketing your own products doesn't count.
A server with Docker and PostgreSQL. No Redis, no message broker. Then your own credentials for whichever channels you switch on.
It's pre-1.0, so treat it that way. The core is complete and the security baseline is documented. Read SECURITY.md, start on a channel where a mistake is cheap, and check the roadmap before you move anything critical.
Start free on the hosted version, or clone the code and run it with no limits.
AGPL-3.0 License · Django 5 + HTMX + Tailwind 4 + PostgreSQL
We use optional cookies to understand how this site gets used and whether our ads work. Nothing optional loads until you choose, and declining changes nothing about how the site works.
There are exactly two optional things on this website. Here they are, in full.
One entry: your answer to this question. We keep it in your browser's local storage under
bb_consent for 180 days so we don't ask
again. It never leaves your device and identifies nothing about you. That is the entire
list.
| Cookie | Purpose | Duration |
|---|---|---|
| _ga | Random ID so repeat visits count as one person | 180 days |
| _ga_* | Keeps the analytics session state | 180 days |
| Cookie | Purpose | Duration |
|---|---|---|
| __oppref | Which OpenAI ad brought you here, if any | 30 days |
| __obref | Recognises your browser so a later sign-up can be matched to an ad | 1 year, deleted when you withdraw consent |
Full detail in our Privacy Policy and Legal Notice.