Charles alternative with EU compute and no Business API.

Charles is a Berlin-based conversational commerce platform popular in DACH (Germany, Austria, Switzerland) and broader EU markets. It bundles WhatsApp, journey automation, and commerce features (catalog, checkout, abandoned cart) on top of Meta's WhatsApp Business API. The pitch is retail-grade conversational commerce with strong EU compliance posture.

Mossmoon does WhatsApp only, on the personal-API path that connects through the user's actual WhatsApp account, not Meta's Business API. EU compute, same residency story as Charles. No business verification, no template approval, no 24-hour customer service window, no per-contact tiering. Flat $15 per active line per month. We don't ship a journey builder, catalog UI, or checkout flow. You bring the orchestrator; we bring the connection.

Probably not for the brand-side commerce workload. If you're sending order updates, abandoned-cart broadcasts, and product-catalog messages from a verified brand WhatsApp number, the Business API path Charles uses is engineered exactly for that. Charles's catalog and journey UIs do real work for retail teams running conversational commerce campaigns. Ripping that out fragments the workflow.

Where switching makes sense: if your WhatsApp use is also (or primarily) conversational support, sales follow-up, or you're operating in a multi-tenant context (an agency running WhatsApp for multiple DACH clients), Mossmoon's path is structurally better for that lane. Many teams run both: Charles for the catalog/broadcast commerce lane, Mossmoon for the conversational lane.

Mossmoon runs on EU infrastructure by default. The WhatsApp connection layer, the database, and the webhook delivery infrastructure are all EU-hosted. We don't replicate message bodies outside the EU. For specific GDPR data-processing-agreement requirements or named-region commitments, email [email protected] and we'll provide whatever's needed for your compliance review.

Charles has a strong EU compliance story too, so this is essentially parity rather than a differentiator. The differentiator is the path: Charles routes through Meta's WhatsApp Business API, which means message content also touches Meta's infrastructure as it passes through. Mossmoon's path connects directly to the user's WhatsApp account without Meta in the middle.

Charles's plans tier by feature and contact volume, plus Meta's per-WhatsApp-conversation pricing on top of their platform fee. At scale in DACH and EU markets, contact volume grows fast and per-conversation pricing compounds across countries.

Mossmoon is flat $15 per active WhatsApp line per month. Unlimited inbound and outbound. No per-conversation fees. No per-contact tiering. No per-country rate cards. For conversational workloads, this is dramatically cheaper. For mass-broadcast workloads (where you really do want template-driven sends), the Business API path Charles uses fits better.

No. The 24-hour rule is a Meta WhatsApp Business API policy that Charles inherits because they sit on the Business API. Mossmoon connects through the user's actual WhatsApp on their phone, so the rule never applies. Send any message any time, the way a human would type it from the phone. No template categorization, no rejection queue, no concerns about the 25-hour follow-up.

Yes, for the brand-WhatsApp catalog UI specifically. Charles's catalog integration with Shopify and other commerce platforms is a native Business API feature; product-message format and checkout-link rendering are first-class on that path.

Mossmoon supports sending images, product cards as text + image messages with checkout links, and any other content format WhatsApp's normal experience supports. For pure conversational commerce on the user's number, this works well. For full structured product browsing inside WhatsApp on a brand number, the Business API's native catalog is more polished today. If catalog is core to your product, stay on Charles for the catalog lane.

Yes, you build them in an orchestrator instead of the Charles journey builder. The most common patterns for DACH teams switching: n8n (often self-hosted in EU for additional compliance reasons), Make.com, HubSpot workflows for CRM-integrated flows, or a custom Node.js / Go backend. We have step-by-step tutorials at /blog/how-to-add-whatsapp-to-n8n and /blog/how-to-add-whatsapp-to-make-com.

Trade-off: more flexibility, more setup. For teams already running an orchestrator, the trade is usually worth it. For teams whose flows live entirely in Charles's UI, building elsewhere is real engineering investment.

Yes, this is the strongest fit. Each client scans their own QR on a Mossmoon-hosted connect page. Under two minutes per client. No Meta business verification per client. No template queues per client. Flat $15 per client line means you can resell cleanly to your DACH retail clients on an agency markup.

Compare to onboarding each client through Charles's Business API path: days-to-weeks per client through Meta verification. The structural advantage compounds with every new client. See /for/marketing-agencies for the agency-specific framing.

Mossmoon integration is an afternoon. The slow parts: (1) asking each connected WhatsApp number to scan a fresh QR with Mossmoon's connect page (WhatsApp authorization lives on the user's phone, no backend transfer possible between providers), and (2) rebuilding any flows that lived in Charles's journey builder in your new orchestrator.

Most teams that switch run both side-by-side for a few weeks while flows get rebuilt. Once the new pipeline is stable, customers re-scan onto Mossmoon and the Charles side gets torn down.