The whatsmeow alternative for teams that ship
Go teams that want a fast, actively maintained protocol library and are comfortable running a stateful service with a Postgres-backed device store.
Who whatsmeow is for
A library gives you the protocol itself: every field, every event, and every job that comes with holding a live WhatsApp session in your own process. Nothing is hidden, and nothing is done for you.
Why people switch
- Status posting is documented as experimental, so an automation built on it is building on a moving part rather than on a settled API.
- There is no label-writing support and no catalogue support, which rules out the WhatsApp Business objects some teams specifically need.
- There is no forwarding helper, so forwarding a message means assembling the context yourself rather than calling one method.
- The device properties default to an operating-system string that identifies the library, which has to be overridden deliberately or every linked device announces itself.
- The licence is file-level copyleft; using it inside a hosted service is not distribution, but the obligation is worth a legal read before it ends up in a product.
What whatsmeow is missing
| Feature | In Wapito |
|---|---|
| Post Status | Post text, image and video status updates. |
| Group Events | Announce and track events inside a group. |
Migrating from whatsmeow: the concept map
| In whatsmeow | In Wapito |
|---|---|
Client.CreateGroup(req) | POST /groupsCreate a group |
Client.UpdateGroupParticipants(jid, ids, add) | POST /groups/{id}/participantsAdd participants to a group |
Client.GetGroupInviteLink(jid, reset) | GET /groups/{id}/inviteGet the group invite link |
Client.SendMessage(ctx, jid, msg) | POST /messages/textSend a text message |
Client.IsOnWhatsApp(numbers) | POST /contacts/checkCheck numbers for WhatsApp registration |
Client.AddEventHandler(handler) | POST /webhooksCreate a webhook |
Pricing and hosting
The library is free under a file-level copyleft licence. Costs are the Go service you run, the Postgres instance behind its device store, and the operational work of keeping a stateful process healthy across deploys.
Source: whatsmeow pricing checked
Three alternatives to whatsmeow
Node and TypeScript developers who want direct protocol access and are willing to own the session, the storage and the upgrades themselves.
JavaScript developers who want the quickest possible path from an idea to a working bot, and who can live with a headless browser in production.
A hosted unofficial WhatsApp API with groups, Channels, status posts and template-free sends over one documented REST contract, with signed webhooks. This is our product, so weigh its place in the ranking accordingly.
Frequently asked questions
Why move off a library that is actively maintained?
Maintenance is a genuine strength here, and it is a reason to stay if Go is your stack and the session is your product. Teams move when the WhatsApp service is a supporting feature rather than the core: at that point running a stateful Go process and a device-store database for it is overhead without a payoff.
Can I run both during a migration?
Not on the same number - a linked device slot belongs to one client at a time, and pointing two at one number produces duplicate sends and confused state. Migrate number by number, or run the new provider on a second number until you are confident.
Does the device store come across?
No. The device store holds credentials bound to the linked device, so it cannot be imported anywhere else. Keep your own records - group ids, contact mappings, message ids - in your database rather than relying on the device store, and the migration becomes a re-pairing rather than a data loss.
Related
Head to head
More alternatives
What Wapito adds
Try it on your own number
Create a channel, link a WhatsApp number by QR or pairing code, and call the API in a couple of minutes. The Sandbox plan is free and needs no card.