360dialog alternative without the Business API.

360dialog is a WhatsApp Business Solution Provider (BSP) based in Berlin. They're one of the technical BSPs Meta authorized to sit between developers and the official WhatsApp Business API. The product is a clean, developer-oriented gateway: you submit templates, hand them a business to verify, wire up a webhook, and your traffic flows through their endpoint to Meta and back.

Mossmoon doesn't sit on the Business API at all. Your customer scans a QR with the WhatsApp already on their phone, the connection goes live, every message flows through our REST API and webhooks in real time. No Meta onboarding, no template queue, no 24-hour customer service window, no per-conversation billing. The trade-off: we're not built for one-to-many transactional broadcasts at massive scale, which is exactly 360dialog's sweet spot.

Yes, with a different shape. Mossmoon is also API-first. One POST to provision a line, embed the returned connect_url in your product as a link, button, or iframe. From the moment your customer scans the QR, every inbound message hits your webhook with signed JSON and you send back through one REST endpoint. No SDK, no chat dashboard you're forced to use, no UI you didn't build.

The structural difference is what's behind the API. With 360dialog, your traffic is going through Meta's Business API and inherits every constraint of that path. With Mossmoon, your traffic is going through your customer's normal WhatsApp on their phone, so none of those constraints apply.

Yes, structurally. The 24-hour rule is a Meta WhatsApp Business API policy that 360dialog inherits because they're a BSP on top of that API. You can only freely message a user for 24 hours after they last messaged you, then every outbound send needs a pre-approved template categorized 'utility', 'marketing', 'authentication', or 'service'.

Mossmoon connects through your customer's actual WhatsApp on their phone, so the rule never applies. Send any message any time. No template categorization. No 'window resetting' game. Treat the channel like a phone and it behaves like one.

360dialog typically charges a flat monthly hosting fee per number plus Meta's per-conversation pricing on top (which varies by country and conversation category). Predicting your monthly bill at any meaningful scale is genuinely difficult because Meta's category rules and country list shift.

Mossmoon is flat $15 per active line per month. Unlimited inbound, unlimited outbound, no per-conversation fees, no per-country surprises. A line that sends 10 conversations costs the same as a line that sends 10,000. First line free for 7 days from when it actually goes ready (when your customer scans the QR), not from signup.

No. Mossmoon doesn't go through Meta Business Manager at all. No business verification, no display-name review, no Facebook business account requirement, no template categorization. Your customer just opens WhatsApp on their phone and scans a QR. End-to-end onboarding is under two minutes per line.

If you've ever had a Business API onboarding stall in Meta's verification queue for a week, you know how much of a product-roadmap-killer that step is.

Probably not, for that workload. Meta's Business API is engineered specifically for one verified business number sending high volumes of templated messages (OTPs, shipping notifications, transactional alerts) to a large recipient list. Templates make sense for that traffic pattern. Per-conversation pricing scales for that traffic pattern. 360dialog is a solid BSP for that workload.

If you have a mixed workload (some one-to-many broadcast, some real one-to-one conversation), the conversational leg is where Mossmoon wins decisively. A lot of teams run both: 360dialog or another BSP for the broadcast lane, Mossmoon for the conversational lane (their customers' own WhatsApp accounts staying connected to the product).

Yes, that's the primary use case. POST /api/v1/wa/lines with an external reference to your customer, embed the returned connect_url in your product, your customer scans the QR, line.ready fires to your webhook seconds later. Each customer's line is independent: its own line_id, its own QR, its own webhook payloads. Bill them whatever you want on top of our flat $15.

Compared to onboarding each customer through a BSP like 360dialog (every customer's business verification, every customer's template list, every customer's display-name review): hours vs weeks per customer onboarded.

Mossmoon runs on EU infrastructure for the WhatsApp connection layer. We don't replicate message bodies outside the EU. If you have specific compliance requirements (GDPR processing agreements, named-region commitments, audit logs), email [email protected] with the spec.

The Mossmoon integration itself is an afternoon. The slow part, the same as with any provider migration, is asking each of your customers to scan a new QR with Mossmoon's connect page. Because WhatsApp authorization lives on the user's phone and not in either provider's database, there's no backend transfer either side could do.

Most teams batch-message their client list, send the connect link, and clear the migration over a few days.