Polymorfa vs Baileys
Baileys is the MIT-licensed TypeScript library for the WhatsApp Web protocol that many gateways are built on. It gives you the protocol; you build and run the API, storage, webhooks and operations. Polymorfa is that operated layer, with the official Cloud API route beside it.
Disclosure: Polymorfa's founder is the current maintainer of Baileys. Baileys stays free and MIT-licensed.
Choose Baileys if
- You want the protocol inside your own Node.js process, with full control.
- You have the people to run session storage, reconnects and upgrades.
- You only need linked-device numbers.
Choose Polymorfa if
- You want an HTTP API and webhooks instead of an in-process library.
- You want someone else to handle reconnects, protocol changes and on-call.
- You need official Cloud API numbers, calls or customer onboarding too.
- You want to bring existing Baileys sessions over (in preview) without rescanning.
The library is the start of the work.
A library connects one number in one process. A product also needs an HTTP API, durable session storage, reconnects, signed webhooks, media storage and upgrades when WhatsApp changes.
Polymorfa runs all of that as a service, and adds the official Cloud API route beside it.
Keep the sessions you already run.
Session import is in preview: bring existing Baileys sessions over without asking customers to scan again. whatsmeow imports are assisted by our team.
- Existing session foundyour current auth state
- Imported into Polymorfakeys stay encrypted at rest
- Connectedno QR rescan on the phone
Calls the libraries do not place.
The libraries surface call events and let you reject calls. whatsmeow's README lists calls as not yet implemented. Polymorfa places and answers voice and video calls on linked-device numbers.
Polymorfa and Baileys, feature by feature.
Hover a feature name for a definition.
Checked against each vendor's public website and documentation on 24 September 2026. “Not listed” means we did not find the capability on those pages. It does not mean the product lacks it. Prices are list prices shown publicly on that date and exclude Meta's fees and taxes unless stated.
Spotted something out of date? Tell us and we will correct it.
More comparisons
- KapsoThe closest managed developer platform, built only on the official Cloud API.
- WhatsApp API providersHosted WhatsApp APIs: Z-API, Green API, 1MSG, Sent, NotificaMe Hub and ClickAPI.
- Inbox and CRM appsFinished apps for teams: BotConversa, Whaticket, TimelinesAI and Rasayel.
- WhatsApp callingCalling APIs and apps: Wavoip, ZapLigue, Z-API and the Meta Calling API.
- Self-hosted gatewaysFree software you run yourself: Evolution API, WAHA and OpenWA.
- Meta Cloud API directBuilding straight on Meta's official API, with no platform in between.
Ship a WhatsApp integration this afternoon.
Free on the sandbox. No credit card. The projects you start here migrate straight into production.