Polymorfa vs whatsmeow

Three reasons teams move from whatsmeow

1. 01

   The same foundation, operated for you

   Polymorfa runs HyperMeow, its engine built on whatsmeow, for linked-device numbers and puts an HTTP API, webhooks signed with HMAC-SHA256 and hosted pairing in front of it. You pay only for days a number is online.^4,9,7

   whatsmeow: whatsmeow gives you a client with a device store, event handlers and a SendMessage method. You run the process, back up the store and update the module when WhatsApp changes.¹⁰

   jid := types.NewJID("15550001111", types.DefaultUserServer)
   _, err := client.SendMessage(ctx, jid, &waE2E.Message{
   	Conversation: proto.String("Your order shipped."),
   })

   curl -X POST https://api.polymorfa.com/messaging/support/messages/send \
     -H "Authorization: Bearer $POLYMORFA_API_KEY" \
     -H "Idempotency-Key: order-1042-shipped" \
     -H "Content-Type: application/json" \
     -d '{"conversation":{"phoneNumber":"+15550001111"},"content":{"text":"Your order shipped."}}'

2. 02

   Calls from code and over SIP

   Polymorfa places and answers calls on linked-device numbers in a browser, in server code that reads and writes the audio, or on your PBX through a SIP trunk. Video and group calls are included.^1,2

   whatsmeow: whatsmeow's README lists calls under features not yet implemented. The library reports incoming calls and can reject them.^11,10

3. 03

   Multi-tenant pieces you would build yourself

   Polymorfa includes a hosted QuickLink pairing page, a Customers API for grouping numbers and tokens, scoped API keys and an audit log with export.^3,12,13,14

   whatsmeow: whatsmeow is a protocol client. Pairing pages, customer separation, API keys and audit records are yours to build.¹¹