Metabase StrawberryEvery number it reports comes from a card your team approved
Ask why two tiles disagree and get the answer out of both card definitions: one counts sessions, the other counts users with an event. Saved questions run with parameters, on a schedule if you want.
The dashboard loads, it has numbers on it, and three people in the room privately think it is wrong, because somebody changed what “active” meant in March and the card feeding the top tile still uses the old definition.
A companion reads every card definition and tells you which is which. It searches your cards, dashboards and collections, reads the query behind any of them, and runs a saved card with parameters. It writes no SQL of its own.
Every number traces back to a card somebody named
The run-card tool is the whole design.
A companion executes content a person on your team already wrote, reviewed and named, so a figure it reports carries your definition of the metric. For a data team that spent two years curating a collection, that is what makes this safe to hand to the rest of the company.
When no saved card covers the question, it says so and points at the closest ones it found. Authoring the new card is a step you take with the companion in the Metabase you are signed into.
Why do two Metabase cards show different numbers?
Search finds the four questions whose names mention retention.
Reading each card’s definition shows which one filters to paying accounts and which does not. Database metadata explains what the underlying tables and fields contain.
Then it names the divergence: one counts sessions, the other counts users with an event. A specific, checkable answer instead of a shrug. Analysts doing that kind of research spend most of their time on this archaeology.
Can the Monday numbers assemble themselves?
A routine runs the four cards on a schedule, writes the results into your doc or sheet with a link back to each card, and drafts the commentary as a diff against last week that a human can argue with.
When a card errors or returns nothing, the routine stops and says which card and what Metabase returned. A report that arrives with “card 218 failed” at the top is a two-minute fix. Teams running weekly operations reviews get the assembly back and keep the reading.
Fresh numbers, and a new card when you need one
Ask for fresh numbers and it runs the saved question with the cache bypassed, so the figure in your doc is the one the card returns right now. Search, dashboards, card definitions and database metadata read the same way, bounded by what your Metabase API key is permitted to see.
When you genuinely need a new card, the companion builds it with you in the Metabase you are signed into, one step at a time. Strawberry is free to download for Mac and Windows.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents