Metabase alternative for alerts and flat pricing

Who each one is for

Metabase is a general-purpose BI tool. Analysts write SQL when they want to, and everyone else clicks through the question builder. You can run the open source edition yourself for nothing, or pay for Cloud. It has been around long enough that most questions you’d ask about it already have answers somewhere.

arcodash is narrower. It is SQL-first, hosted only, and built around the idea that a dashboard is only useful if the number on it is right. Its dashboards sit next to scheduled checks that watch your tables and tell you when something looks off. If your team lives in SQL and the pain is “the dashboard was wrong for two days and nobody noticed”, that’s the shape it’s built for.

Where Metabase is the better choice

Pick Metabase if any of these describe you:

• You want to self-host for free. The Open Source edition has unlimited users. arcodash can’t be self-hosted at all.
• Non-SQL people build their own questions. The question builder is the main reason teams pick Metabase. arcodash has nothing equivalent.
• Embedding is central. Metabase’s embedding is more mature than arcodash’s iframe embeds.
• A few analysts is the whole audience. If the people using it are a small, stable group and you are happy to run it yourself, the Open Source edition covers it.

Where arcodash is the better fit

• Checks that run on a schedule. A freshness, row count, null rate or duplicate check is a saved SQL query with a threshold on one column. It refreshes on a schedule and alerts when the condition flips. See data quality monitors for the four recipes. There is no check-type picker: you write the query, or let Suggest checks with AI draft it from your schema (it needs an AI provider key configured).
• Baseline monitors. If you don’t know the right threshold, a monitor can learn what’s normal for a column from its own history and flag outliers. It needs 7 observations before it starts flagging.
• AI on top of SQL. Ask with AI, Fix with AI, suggested checks, and a “Why did this fire?” analysis attached to alerts. You bring your own Gemini, OpenAI or Anthropic key.
• Unlimited viewers at one price. Metabase Cloud is priced per user, so the bill moves with headcount. arcodash is fixed: the price on the page is the bill. We wrote the longer version in flat-price BI.
• No ops. It’s hosted. Nothing to patch, back up or scale.

Alerts compared

Metabase alerts hang off a saved question. There are three kinds: a results alert that fires when the question returns any rows, a goal line alert for a time series crossing a line, and a progress bar alert. They go out by email, Slack or webhook, and you can check on a schedule from every minute up to a custom cron. Dashboards use dashboard subscriptions instead.

arcodash alerts (called monitors) hang off a saved query too. A monitor reads the first row of the published result, takes one column, and compares it with a value using >, <, >=, <=, == or !=. It notifies when the state changes, and a rearm period throttles repeats. Destinations include email, Slack, Teams, webhook, PagerDuty, Mattermost, Discord, Google Chat and Datadog.

The mechanics are close. The difference is what’s around them: arcodash ships the check recipes, baseline monitors, AI-suggested checks and incident tracking, and Metabase gives you finer control over a question’s chart-based alert types. The alerts overview has the exact semantics.

A “table stopped updating” check in arcodash is one query and one threshold:

SELECT extract(epoch from now() - max(loaded_at)) AS seconds_since_last_row
FROM orders;

Monitor seconds_since_last_row with > and 3600, and put the query on a schedule. Metabase’s alerts page doesn’t show a SQL example, so we haven’t written the same alert in its terms here.

Migrating from Metabase

There is no import tool. Be realistic about that.

• What ports directly: your SQL. Native questions are queries; copy the text into arcodash, check the dialect, and save it.
• What you rebuild: charts, dashboards, filters and any alert. Questions made in the builder have no SQL to copy, so you’d write that SQL fresh.
• What you drop: Metabase’s saved collections and permissions structure. You set up arcodash’s sharing instead.

A sensible start is to move the five dashboards people open most and leave the rest. Run both for a few weeks before you cancel anything.

Questions

On price, the difference is the model: arcodash is fixed, Metabase Cloud varies with users. If you’d rather decide on whether a wrong number gets caught before a stakeholder sees it, try a free arcodash trial and point one check at your busiest table.

The Superset comparison covers the other free open-source option, and flat-price BI explains the pricing model.