HyperMeow is Polymorfa's production-focused fork of tulir/whatsmeow. It keeps the upstream Go package names and protocol foundation while adding the business-app surface, LID-first identity model, bounded state, PostgreSQL efficiency, and reliability controls needed for large multi-session deployments.
The upstream project remains the smaller choice for applications that only need its core WhatsApp messaging scope. HyperMeow deliberately accepts a broader API and maintenance surface in exchange for the capabilities below.
This comparison was last verified against upstream main at a23afe3 on 2026-08-11. Each upstream sync must update this section when the difference changes.
| Area | HyperMeow advantage over upstream main |
|---|---|
| Business app | Adds linked-account and eligibility reads, business-profile and cover-photo mutation, product and collection mutation, catalog creation, cart and visibility controls, appeal and merchant-compliance operations, and validated business message builders. |
| Native Flows | Adds typed address, list, order, and Flow message builders with payload limits, exact JSON-number preservation, UTF-8 validation, and response metadata handling. |
| Identity | Treats LIDs as the stable Signal identity, persists PN and username aliases, resolves aliases in batches, exposes phone-number consent messages, and generates LID identity verification codes. |
| App state | Adds atomic label replacement, label and quick-reply events, full-sync event controls, and independent history-sync receipt, storage, and media-deletion policies. |
| Channels | Adds newsletter deletion through generated MEX bindings. |
| Reliability | Hardens malformed binary-node handling, serializes device save/delete operations, surfaces participant-hash mismatches, bounds attacker-influenced caches, and redacts sensitive business payloads from node logs. |
| PostgreSQL | Batches Signal and metadata work, avoids empty PN-to-LID transactions, adds indexed alias lookups, and keeps PostgreSQL authoritative after bounded cache eviction. |
| Validation | Ships a reproducible Barback/PostgreSQL harness covering DM, group, history, media, mixed-message, security-code, phone-consent, resource, and saturation workloads. |
The repository retains the raw reports and methodology behind these numbers in benchmark/barback/testdata/results. They compare frozen revisions under the same local Barback, PostgreSQL, TLS, Noise, CPU, and memory constraints. They are engineering comparisons, not WhatsApp WAN or account-rate-limit claims.
| Measurement | Upstream WhatsMeow | HyperMeow | Result |
|---|---|---|---|
| Disconnected constructor heap, 2,000 clients | 78,929 B/client | 4,240 B/client | 94.6% less Go heap |
| Group-128 send p95 | 33.998 ms | 7.024 ms | 79.3% lower |
| Group-128 client CPU | 5.502 s | 2.301 s | 58.2% lower |
| Group-128 SQL calls | 165,053 | 3,456 | 97.9% fewer |
| Highest healthy encrypted ping-pong rate | 900 pairs/s | 1,700 pairs/s | 1.89x the rate |
The complete three-repeat system matrix documents allocation, RSS, CPU, latency, PostgreSQL, network, and I/O results across five workloads. It also records the trade-offs: history-heavy peak RSS was slightly higher in one comparison, and active-session capacity depends on contacts, groups, media, handlers, and application queues rather than constructor memory alone.
Install the newest reviewed commit from the authoritative main branch:
go get github.com/polymorfa/hypermeow@mainThe main query resolves to a commit pseudo-version. After the version correction,
v0.0.0 is the only selectable tagged version. dev is an integration branch and
is never a publication source.
The root package remains named whatsmeow, so use an explicit import alias:
import whatsmeow "github.com/polymorfa/hypermeow"Replace go.mau.fi/whatsmeow imports with github.com/polymorfa/hypermeow and remove any old module replacement:
go mod edit -dropreplace=go.mau.fi/whatsmeow
go get github.com/polymorfa/hypermeow@main
go mod tidyHyperMeow retains upstream's core support for:
- private, group, media, and status messages;
- group management and invite links;
- typing, delivery, and read receipts;
- app-state synchronization;
- retry receipts and message decryption recovery.
New exported functionality is additive unless called out in the changelog.
Join the WhatsApp Web ecosystem Discord and visit
#hypermeow for project discussion.
If you'd like business to enterprise-level support from Rajeh, you can book a video chat. Book a 1 hour time slot by contacting him on Discord or pre-ordering here. The earlier you pre-order the better, as his time slots usually fill up very quickly.
If you are a business, we encourage you to contribute back to the development costs of the project. You can do so by booking meetings or sponsoring below. All support is welcome from businesses of all sizes.
If you'd like to financially support this project, you can do so here.
Caution
This project is not affiliated, associated, authorized, endorsed by, or in any way officially connected with WhatsApp or any of its subsidiaries or its affiliates. The official WhatsApp website can be found at whatsapp.com. "WhatsApp" as well as related names, marks, emblems and images are registered trademarks of their respective owners.
The maintainers do not condone using this project in practices that violate the Terms of Service of WhatsApp, and call upon users to use it fairly.
Upstream-derived files retain their original Tulir Asokan and contributor copyright notices and remain licensed under MPL-2.0.
Polymorfa-added files: Copyright (c) 2026 Rajeh Taher, licensed under the MIT License.
See LICENSING.md for the file-level boundary.