Plain SQL you own
Write or edit every check as plain SQL. Nothing is hidden or locked inside Alertee.
check.sql
SELECT region, count(*)
FROM orders
WHERE created_at > now() - interval '15 min'
GROUP BY region;Catch data issues before your users do
Alertee runs plain SQL checks that flag silent failures — a feed, tenant, or job quietly hitting zero while every dashboard stays green.
Read-only Postgres or ClickHouse · free for 5 checks · no credit card
611,626+ checks run4,148+ issues caught
Why Alertee
Most monitors tell you something broke. Alertee tells you what, where, and since when.
A check fires, and the alert can hand itself to your agent. It reads the check's SQL and recent history — your data, not guesswork — and tells you where the gap is and when it started.
A normal monitor
⚠ paid_payments_recorded failed
Something is wrong. Now go open a dashboard and work out what.
Alertee
Paid payments dropped to 0 at 14:05 while total payments held steady — the Stripe webhook stopped writing status = 'paid'.
What, where, and since when
What you get
SQL monitoring for the outcomes users notice
Independent SQL checks that stay understandable after setup.
Catch one tenant or region failing
Group one query by tenant, region, or job. Alertee flags the single slice that stopped reporting while the total still looks healthy.
orders_by_region
eu-west148 rows
us-east162 rows
ap-south0 rows
Turn repeated failures into owned incidents
Repeat failures become one Inbox item to acknowledge, assign, and resolve — not another stream of duplicate alerts.
Paid payments stopped
Open- Owner
- data-oncall
- Repeat failures
- 6 grouped
Setup flow
See how setup works
From a plain-English prompt to your first alert in three steps.
Describe it
Tell Alertee what should keep working
Plain English is enough. SQL stays editable.
Suggested monitors
Generated from your schema and prompt. Edit before enabling.
Paid payments are still being recorded
SELECT count(*) FROM payments WHERE status = 'paid'
ok
every 15m
Nightly import writes new rows
SELECT max(imported_at) FROM customer_events
ok
daily
Every region is still reporting orders
SELECT region AS name, count(*) AS value FROM orders
ok
every 15m
If Paid payments fails, Alertee opens one Inbox item.
Assign it, resolve it, and mark whether it was real, transient, expected, or noisy.
Agents & CLI
Your AI assistant can create, investigate, and resolve checks
Connect Claude, Codex, Cursor, or your own agent once. It can work with the same SQL, run history, and incident inbox you see in Alertee — or you can drive everything yourself from the CLI.
Point your client at the hosted server and sign in once — nothing to install. Pick yours:
claude mcp add --transport http alertee \
https://app.alertee.app/mcpThen run /mcp in Claude Code to sign in.
Your agent, connected to Alertee
Alert me if paid payments stop being recorded.
create_check — Paid payments recorded · every 15mDone. I drafted the SQL, set it to run every 15 minutes, and routed alerts to #data-oncall.
It just fired. What happened?
get_check_history — last 24hPaid payments dropped to 0 at 14:05 while total payments held steady — looks like the Stripe webhook stopped writing `status = 'paid'`.
Simple, Transparent Pricing
Start free, then upgrade when your monitoring grows.
Every plan includes
AI-assisted setup
Postgres, ClickHouse, and SQL checks
Email, Slack, and incident history
Free
$0/month
- 5 active monitors
- 2 data sources
- 15-minute intervals
- Email and Slack alerts
Practical details
Frequently asked questions
How checks are created, what database access is required, and what happens after an alert fires.
Start with one data outcome you should never miss
Connect a read-only database, describe what should keep happening, and turn the first SQL checks on in minutes. Free plan included. No credit card required.
Start monitoringCurrently requires a database that can accept a public connection; use a restricted read-only user and IP allowlist.