Free WhatsApp bot hosting.
The same allocation as everything else here, and a warning we would rather give you before you sign up than after you lose a number.
We will host it. We do not recommend it.
Automating a personal WhatsApp account is not something WhatsApp supports. The tools that do it work by pretending to be the official app, they break whenever the protocol changes, and using one can get your number banned — sometimes permanently, sometimes without warning, and always without an appeal you can rely on.
That risk is yours, not ours. We accept no responsibility for a number, an account, or a set of contacts lost while running a bot hosted here, and nothing on this page should be read as advice that it is safe to do. If losing the number would be a problem, do not use one you care about.
If your use is commercial, the officially supported business API exists precisely so you do not have to take that risk, and a bot that receives its messages through official channels has no ban exposure of this kind at all.
Choose a runtime
Pick your language
All three are installed and tested. Each page covers the libraries, the deployment and what fits in 256 MB for that runtime specifically.
What will not run in 256 MB
Anything that drives a headless browser. A meaningful share of the WhatsApp automation approaches out there work by launching a full browser engine and driving the web client inside it. A browser engine alone wants several hundred megabytes before your code exists; on 256 MB it does not start, and there is no configuration that changes that.
What does fit is anything that talks to WhatsApp over a socket or an HTTP API without a browser in the middle. If you are evaluating an approach and its setup instructions involve installing a browser, it is not going to work here.
Session state is the part people get wrong
A bot that links to an account holds credentials it obtained when you paired it, and those credentials have to survive a restart. Written to disk, a restart is invisible and the bot reconnects on its own. Held in memory, every restart means pairing again by hand — which on a host that restarts your process after a crash means doing it at three in the morning.
You have 512 MB of disk and it persists across restarts, crashes and redeploys, so there is no excuse for keeping session state anywhere else. Treat those files as credentials, because that is what they are: anyone who copies them has your session.
What the acceptable use policy says about this
The rules that apply to every bot here apply with more force to this one. Unsolicited messaging is the fastest way to lose a number and it is prohibited outright: no bulk sending to people who did not ask, no scraping contacts, no automated adding to groups, no scams.
A bot hosted here that is used to spam is suspended, and we do not need WhatsApp to tell us first. That is the same standard we apply to every platform; it just happens to be the standard WhatsApp enforces most aggressively.
FAQ
Questions
Can my number really get banned?
Yes, and you should assume it will eventually. Automation of a personal account is against WhatsApp's terms, enforcement is automated, and bans arrive without warning or a meaningful appeal. Use a number you can afford to lose, and do not link an account that matters to you.
Are you responsible if I lose my account?
No. We provide the server; what you connect it to and what happens to that account is entirely yours. This is set out in the terms of service as well as here, because it is the single most likely bad outcome of hosting this kind of bot anywhere.
Why do you host it at all if you do not recommend it?
Because it is a Node.js, Python or Bun program like any other, and refusing to run it would be pretending we can tell what your code connects to. What we can do is be honest about the risk on the page where you decide, rather than quiet about it and helpful later.
Would the official business API be safer?
Considerably, and if you are doing anything commercial it is the right answer. A bot that receives messages through official channels is not pretending to be a phone, so the ban risk described on this page does not apply to it. It also involves an approval process and costs that a personal account does not.
Node.js, Python or Bun for a WhatsApp bot?
Node.js has the larger and better-maintained set of options for this, which is worth knowing given how quickly these tools break. Python is workable and the runtime pages cover what changes. Bun runs the same npm packages as Node.js with a faster start; if a library misbehaves under it, Node.js is the fallback. None of these choices affects the ban risk in the slightest.
Hosting something else?