Open source · cloud or self-hosted

Follow the trail.

The customer feedback loop for B2B product teams. Prioritize by the revenue behind each request, and the customer who asked hears back when it ships.

Start free Read the docs
Crumb Cloud: free plan, no credit card Or self-host: your Postgres, one command

Crumb features: triage by revenue, capture in context, AI triage, ship to your tracker, and a public roadmap

↓ Everything below is interactive. Hover, click, and poke around.

Triage by revenue, not volume

Inbox
Southbeam · all feedback $82k open
Bulk export from cohort view as CSV Acme · $48k
SSO via Okta, more groups Stratus · $34k
Slack DM when status changes Lumen · $21k
Per-cohort retention math seems off Lumen · $21k

Every request carries the account and its ARR. Tap a status to move it through the flow, and the open total reprioritizes itself.

Capture in context

Widget
Share feedback
Let me export a cohort as CSV without screenshotting…
Posting as Maya · Acme Co

Their account and identity ride along. No "which company are you with?"

AI does the triage grunt-work

Cluster
Export funnel as XLSX Download cohort data CSV from the dashboard?
CSV & funnel exports 1 item
Bulk export as CSV
AI suggests a match for new feedback as it arrives.

Ship where eng lives

Push
SOU-241 Drafted by AI
Bulk CSV export from cohort view
From Acme's request, your recent tickets, and your repo's README. You edit it before it's sent.

The ARR behind it

$0k
ARR across 3 accounts asking for one export.

A roadmap customers can actually see

Public roadmap
Now
CSV & funnel exports
12 following
Real-time notifications
8 following
Next
Enterprise SSO & SAML
6 following
API rate-limit headroom
4 following
Later
Mobile & localization polish
3 following

From a customer's note to a closed loop

Every request is an open loop until the customer hears how it ended: heard, answered, decided, shipped, told. Crumb tracks your median loop time, from speaking up to hearing back. That's the number that matters.

01

Heard, in context

A customer sends a bug, idea, or question from the widget inside your app, already tied to their account and its ARR.

02

Answered and decided

Reply in-thread so they know a person read it. Then weigh the ARR behind it and decide: planned, set aside, or won't ship.

03

Shipped, and they're told

Push it to Linear, Jira, or GitHub and follow its status from Crumb. Mark it Shipped and the customer who asked hears back by email and in the widget.

They hear back, by email or in the widget.

Reply in-thread or move an item through your status flow, and customers who sent it through the widget are notified the moment it changes, on every plan, Free included. This is the step most feedback tools quietly skip.

Reply in-thread, and it reaches them where they left it.
Flip an initiative public so every account can follow along.
Status hits "Shipped" → the loop closes itself.

Plays nicely with your tracker, your chat, and your CRM

Push an item to Linear, Jira, or GitHub as a ticket and Crumb reads its status back. Slack DMs or a Teams channel keep your team posted, and HubSpot or Salesforce keeps each account's ARR current.

Trackers

Linear Jira GitHub

Chat notifications

Slack Microsoft Teams

CRM

HubSpot Salesforce
On Team and up, AI drafts each ticket from the request and your recent tickets, so it reads like the rest of your backlog.

Frequently asked questions.

Is Crumb really open source?
Yes. AGPL-3.0, self-hosted, no Crumb account required. The whole stack runs from one docker compose file, and on a fresh install you create the first admin at /onboard with a one-time setup link. Self-hosting for your own company is fully permitted.
What’s the difference between self-host and Crumb Cloud?
Submit, triage, replies, the status flow, customer emails, magic-link sign-in, and the embed widget are in both. Self-host connects integrations through your own OAuth apps and sends email through your own provider. Crumb Cloud adds managed email on every plan, one-click integrations and the AI suite (clustering, ticket and reply drafts, Ask) on Team and up, and session replay on Growth.
How does it tie feedback to revenue?
Every item links to the account that submitted it, and each account carries its ARR, so your inbox shows the dollars behind a request instead of a raw upvote count. Connect HubSpot or Salesforce and that ARR syncs in automatically.
Which tools does it connect to?
Linear, Jira, and GitHub for tickets: Crumb pushes the ticket and reads its status back. Slack for teammate DMs, the /crumb command, and @mention request sizing. Microsoft Teams for a channel feed through an incoming webhook. HubSpot or Salesforce for a one-way sync of accounts and ARR. On Team and up, Crumb also pulls feedback from Zendesk, Intercom, Freshdesk, and Gong, and feedback can arrive by forwarded email or the API too.
Do customers actually get notified?
Yes, for feedback sent through the widget. Reply in-thread or change its status and that customer hears back by email or in the widget, on every plan, Free included. It’s the step most feedback tools quietly skip.
How do customers submit without leaving our app?
A small embed widget: one <script> tag. Your server signs a short-lived token that says who the customer is and which account they belong to, so there’s no form asking for their email or company. Crumb Cloud requires the token; a self-hosted install can pass the email and account name as attributes instead.

Stop watching feedback vanish.

Free and open source to self-host. One click to start on Crumb Cloud.

Start free Star on GitHub