Looking for a Metabase Alerts alternative.

Start with what you're actually trying to avoid

Most people land on this page after one of two experiences: they've read about Metabase Alerts and are weighing whether to stand up Metabase just for that, or they already have Metabase and find the Alerts workflow, saving a question first, then configuring the alert against it, heavier than they'd like for a quick check. Both are reasonable starting points, and the answer looks a little different depending on which one you're in.

What Metabase Alerts actually do

Metabase's own documentation describes Alerts clearly: pick a saved question, choose a condition (a value crosses a goal line, or a table gets new results), and Metabase checks it on a schedule and notifies email or a Slack channel. This is a genuinely useful, well-built feature, not a workaround. The catch isn't the feature, it's the prerequisite: the question has to be a Metabase question, saved inside a running Metabase instance.

The prerequisite is the actual cost

If your team already runs Metabase for dashboards, the marginal cost of adding an Alert on top is basically zero, it's a feature you're already paying the infrastructure cost for. If you don't run Metabase at all, and you're evaluating it purely because you want one number watched, standing up a Metabase instance (self-hosted with its own database, or a paid cloud plan) just to get an alert is a lot of surface area for a small job.

The same check, without standing up Metabase

Say you want to know when weekly active sellers on your Shopify-adjacent Postgres database drops below a floor:

SELECT COUNT(DISTINCT seller_id) AS active_sellers
FROM public.orders
WHERE created_at >= NOW() - INTERVAL '7 days';

In QueryFlow, run it against your Postgres connection, click Watch this, choose A value on active_sellers, condition Less than your floor, check every 1d, and destination Slack. That's the whole setup, no dashboard tool underneath it.

Side by side

When Metabase's own Alerts are the right call

If a team of non-technical stakeholders already build their own questions in Metabase's visual builder, and dashboards are already part of how the team works, Metabase Alerts are the natural extension, no new tool needed. This page is aimed at the narrower case: someone who doesn't need a BI tool at all and just wants a SQL-literate way to be told when a number moves.

What you'd be signing up for with Metabase

Standing up Metabase means a running instance, a database behind it to store questions and dashboards, user accounts and permissions to manage, and updates to keep current. None of that is unreasonable for a tool a whole team relies on daily. It's a specific, ongoing commitment that's easy to underweight when the immediate reason you're looking is a single alert you want working by this afternoon.

A worked example against Redshift

Say you want to know if refund requests spike above a normal day. In QueryFlow, run this against your Redshift connection:

SELECT COUNT(*) AS refund_requests
FROM analytics.public.refunds
WHERE created_at >= GETDATE() - INTERVAL '1 day';

Click Watch this, choose A value on refund_requests, condition Greater than whatever a normal day tops out at, check every 1h, destination email or Slack. The whole thing takes about as long to set up as writing the query itself, no Metabase question, no dashboard, no separate BI login for anyone to manage.

If a team is already deciding between the two

A team evaluating Metabase specifically because they saw Alerts mentioned, rather than because they need a shared BI layer, is worth a second look before committing to the whole platform. Standing up Metabase for dashboards a handful of technical people will use anyway, when a native Watch would do the same alerting job with far less to maintain, is a common case of picking a bigger tool than the actual job calls for.