[{"data":1,"prerenderedAt":105},["ShallowReactive",2],{"pseo:compare:evolution-api-vs-wapito":3},{"a":4,"b":10,"faqs":16,"pick_a_when":26,"pick_b_when":27,"related":28,"rows":36,"seo":88,"slug":101,"tier":102,"updated":40,"url":97,"verdict":103,"wapito_in_pair":11,"why_compared":104},{"is_wapito":5,"name":6,"slug":7,"type":8,"url":9},false,"Evolution API","evolution-api","self-hosted","\u002Falternatives\u002Fevolution-api\u002F",{"is_wapito":11,"name":12,"slug":13,"type":14,"url":15},true,"Wapito","wapito","unofficial-saas","\u002Fwhatsapp-api\u002F",[17,20,23],{"a":18,"q":19},"Yes, and that is the sensible way. Each number is a separate session on both sides, so you can move one instance, watch it for a week, and move the rest once you are confident. Keep your own record of group ids and contact mappings so the new channel starts with the context it needs, and never point two providers at the same number at once, because a linked device slot belongs to one client.","Can I migrate from Evolution API to Wapito one instance at a time?",{"a":21,"q":22},"The event names and payload shapes differ, so your receiver needs a mapping layer or a rewrite. Wapito publishes a stable event schema, signs every delivery, lets you filter events per webhook and retries with backoff behind a circuit breaker. Evolution API configures a webhook URL and an event list per instance. Moving is a good moment to add signature verification if your current receiver trusts whatever arrives at the URL.","What happens to my webhooks in the move?",{"a":24,"q":25},"For a handful of numbers, rarely, once the server, the database, the media storage and the upgrade hours are counted. Self-hosting becomes genuinely cheaper at volume or when the sessions are required to stay on your own infrastructure. Compare total cost of ownership over a year, and include the additional licence terms in the assessment, because a commercial licence requirement changes the arithmetic.","Is self-hosting cheaper than paying per channel?","Data residency or policy requires the sessions on your own servers, you already run Docker and a database in production, and you accept the additional licence terms for commercial use.","You want a documented contract, signed webhooks with retries, engine updates that are not your problem, and a price that scales with channels rather than with hours.",{"alternatives":29,"hub":31,"pillars":32},[30],{"title":6,"url":9},"\u002Fcompare\u002F",[33],{"title":34,"url":35},"Create Group","\u002Fwhatsapp-api\u002Fcreate-group\u002F",[37,45,52,56,63,71,76,82],{"a":38,"a_source":39,"b":42,"b_source":43,"dimension":44,"feature":43},"Apache-2.0 with additional terms: a visible notice to administrators that Evolution API is in use, and the producer may require a commercial licence.",{"as_of":40,"url":41},"2026-09-16","https:\u002F\u002Fgithub.com\u002Fevolution-foundation\u002Fevolution-api\u002Fblob\u002Fmain\u002FLICENSE","Proprietary hosted service under its terms of service.",null,"License",{"a":46,"a_source":47,"b":50,"b_source":43,"dimension":51,"feature":43},"Self-hosted REST server over Baileys, pinned to 7.0.0-rc.9 (five release candidates behind upstream on 14 September 2026).",{"as_of":48,"url":49},"2026-09-14","https:\u002F\u002Fgithub.com\u002Fevolution-foundation\u002Fevolution-api","Hosted. whatsmeow (GOWS) by default with a per-channel switch to Baileys (NOWEB). No browser.","Engine and protocol",{"a":53,"a_source":43,"b":54,"b_source":43,"dimension":55,"feature":43},"Your own Docker deployment with a database and media storage. You run the upgrades and the on-call.","Hosted by Wapito. Nothing to run.","Hosting",{"a":57,"a_source":58,"b":59,"b_source":43,"dimension":60,"feature":61},"Groups (create, participants, invites, settings) and status posts (sendStatus) as REST endpoints.",{"as_of":48,"url":49},"Groups, communities, Channels and status posts as REST endpoints, each on its own reference page.","Groups, Channels and status",{"name":34,"slug":62,"url":35},"create-group",{"a":64,"a_source":65,"b":66,"b_source":67,"dimension":70,"feature":43},"Free to download. The cost is the server, the database, the storage and the hours; read the additional licence terms before commercial use.",{"as_of":48,"url":49},"Sandbox free (one channel, 150 messages a day). Premium $24 per channel per month, or $19 a month billed yearly, with a five-day trial.",{"as_of":68,"url":69},"2026-09-15","https:\u002F\u002Fwapito.com\u002Fpricing\u002F","Pricing",{"a":72,"a_source":73,"b":74,"b_source":43,"dimension":75,"feature":43},"0 public commits in the 90 days to 14 September 2026. Newest tag 2.4.0-rc2; last stable release 2.3.7 (December 2025).",{"as_of":48,"url":49},"Managed by Wapito. Engine updates are ours; breaking API changes are announced in the changelog before they ship.","Maintenance cadence",{"a":77,"a_source":43,"b":78,"b_source":79,"dimension":81,"feature":43},"Per-instance webhook URL with a configurable event list.","Signed deliveries with an event filter per webhook, retries with backoff and a circuit breaker.",{"as_of":68,"url":80},"https:\u002F\u002Fwapito.com\u002Fdocs\u002Fwebhooks\u002F","Webhooks",{"a":83,"a_source":43,"b":84,"b_source":85,"dimension":87,"feature":43},"REST only. No first-party SDK packages are listed in its documentation.","An OpenAPI 3.1 document at \u002Fopenapi.yaml and code samples in 12 languages on every endpoint page. Packaged SDKs are not shipped yet.",{"as_of":68,"url":86},"https:\u002F\u002Fwapito.com\u002Fopenapi.yaml","SDKs and client code",{"breadcrumb":89,"canonical":98,"description":99,"h1":96,"lastmod":40,"title":100},[90,93,95],{"name":91,"url":92},"Home","\u002F",{"name":94,"url":31},"Compare",{"name":96,"url":97},"Evolution API vs Wapito","\u002Fcompare\u002Fevolution-api-vs-wapito\u002F","https:\u002F\u002Fwapito.com\u002Fcompare\u002Fevolution-api-vs-wapito\u002F","Evolution API if sessions must stay on your infrastructure and you can staff a stateful service; Wapito if you want the REST API, the webhooks and the engine…","Evolution API vs Wapito (2026): WhatsApp API | Wapito","evolution-api-vs-wapito","t5b","Evolution API if sessions must stay on your infrastructure and you can staff a stateful service; Wapito if you want the REST API, the webhooks and the engine upkeep handled, at a per-channel price. Both are unofficial and carry ban risk. We build Wapito, so read the rows rather than the verdict.","Both offer a REST API over a linked WhatsApp number with groups, Channels and status posts; the difference is who runs it. Evolution API is self-hosted on top of Baileys, with Docker, a database and the on-call rota on your side. Wapito is hosted, runs whatsmeow by default with a per-channel engine switch, and bills per channel. Teams compare them when they know they want REST rather than a library.",1790464905474]