Skip to Content
v1.33.8 · shipped One-screen report · Looks like your app Read the changelog →
Mushi Mushi Cloud

Mushi Mushi Cloud

Mushi Mushi Cloud at kensaur.us/mushi-mushi is the hosted version. It runs the same code as the public repo, including the source-available enterprise folder. We run it; you pay by the number of apps, with one diagnosis allowance shared by your whole team.

Plans

PlanAppsCostDiagnoses includedNotes
Free1$0 / mo100 / moAll SDKs and the hosted console. No AI key needed; add your own AI or Cursor key if you want. Community support in GitHub Discussions
Builder3$29 / mo1,000 / moThree apps, plugin marketplace, usage alerts, email support; $0.03 per extra diagnosis
Studio10$79 / mo3,000 / moTen apps, 5 seats, weekly report, shared views; $0.03 per extra diagnosis
EnterpriseUnlimitedFrom $499 / moCustomSAML SSO, SOC 2 evidence collection, 365-day retention, help running it on your own servers
A diagnosis = one finished plain-English root cause written to your queue. Filtered noise and deduplicated groups do not count.

A plan belongs to your team, not to one app. Its diagnoses are shared by every app in the team, and so are the app limit, seats, history, plugins and the spend cap. Upgrade from any app’s card and the whole team moves to the plan. Pricing has the details.

No plan needs an AI key of your own: Mushi Mushi’s AI writes the diagnosis. You can add your own Anthropic, OpenAI or Cursor key on any plan, Free included. Mushi Mushi then uses your Anthropic or OpenAI key first for the diagnosis and for fix drafts; a diagnosis on your own key still counts toward your plan. The Integrations page (Sentry, Slack, GitHub, Linear, Jira) works on every plan; installing plugins from the Marketplace needs Builder or above, and team invites need Studio. Full details are on pricing.

Sign-up flow

  1. kensaur.us/mushi-mushi/admin: email and password, or a GitHub account when that sign-in is offered.
  2. Email confirmation (for email sign-up) → sign in → /onboarding wizard.
  3. Create your first app, then run npx mushi-mushi in its folder to install the SDK. The wizard makes the key for you.
  4. The Billing page in the console shows your team’s diagnoses used / limit, with an Upgrade team button (Change team plan once you pay).
  5. Stripe Checkout → on success, your subscription becomes active. Overage on monthly plans bills through Stripe meter events.

Why metered on diagnoses

A plan sets how many apps your team can have; diagnoses are the allowance under it. Free covers one app and 100 diagnoses a month, Builder three apps, Studio ten. Bug signals are bursty, so past the allowance each diagnosis is a few cents, with a monthly overage cap you set for the team. Duplicate reports collapse, so you pay once per root cause.

Spend controls

Every monthly paid plan has a hard cap on overage spend ($50 Builder, $200 Studio by default). The cap covers the whole team and is set in the console under Billing → Spending cap; set it to $0 for a fixed bill. When the cap is reached, Mushi Mushi pauses new diagnoses for the rest of the calendar month with an upgrade prompt. Annual plans have no overage and stop at the included diagnoses. You also receive email alerts at 50%, 80% and 100% of your included diagnoses.

Self-hosting

If you’d rather run Mushi Mushi on your own Supabase project, see Self-hosting. The Cloud code is in the public repo: the server is AGPLv3, and the enterprise features in packages/server/ee (SSO, audit export, retention policies) are source-available and need a license in production. Cloud also carries its own tuning data (prompt wording, evaluation sets) as configuration; the repo ships working default prompts. Self-hosting is free forever; you supply your own LLM keys.

Last updated on