Why we built muro.chat

Most teams discover live chat the same way: they need a way to talk to visitors, they pick a tool, they roll it out. A few quarters later there's a quiet line item on the SaaS spreadsheet that grew faster than it should have, and a vague sense that you're paying for the same thing twice.

That sense was the seed of muro. Not anger at any one product, every team makes its own pricing call. Just a personal feeling that the chat tool I wanted to use should make hiring easier, not harder.

The two principles

We wrote two rules on a whiteboard before any code: the pricing should never punish hiring more humans, and the install should be one paste, no SDK, no provider, no framework component.

What's in muro

• Two flat plans: Solo $19 for up to ten projects, Fleet $59 for unlimited projects
• Unlimited agents on every plan, including the trial
• A 9 KB widget, vanilla JS, Shadow DOM, async-loaded
• Email forwarding so offline messages reach your inbox
• EU hosting, signed DPA, GDPR export and erasure baked in
• Real-time messages, audit log, webhooks, REST API

What we deliberately left out

• AI add-ons that double the bill at quarter-end (we'll add the option later if it makes sense, never as a forced upsell)
• "Talk to sales" buttons, every plan is buyable with a card
• Per-message limits that make you think before answering
• Email-based account ownership, workspaces are first-class, with proper roles and invitations

If you read this and thought "yes, that's about right," the trial is 14 days with no charge up front, and you can cancel in one click before it ends. We mean it, that's the kind of trust we're trying to build.