Early access

Write a query. Get pinged when the answer changes.

SQL Notifier runs your read-only queries on a schedule and messages you the moment a result crosses the line you set — by email, Slack, Telegram or webhook. No dashboard to keep refreshing.

Live demo

Drag the line. Watch it ping.

The chart is a query running every minute. Move the threshold and see when the alert would fire — and when it would tell you things are fine again.

failed_payments.sqlevery 1 min
SELECT count(*) AS failed FROM payments WHERE status = 'failed' AND created_at > now() - interval '10 min';
notify when failed > 5 · then again when it recovers
2failed payments
last 10 min
quiet
# opsSlack

    Dashboards wait for you to look. SQL Notifier taps you on the shoulder when a number moves — and stays quiet when it doesn't.

    How it works

    Three steps. No agent to install.

    01

    Connect a read-only user

    Create a database user that can only SELECT. Connections come from fixed IPs you can allowlist.

    postgres://notifier_ro@db.internal/shop
    ✓ read-only verified
    02

    Ask your question in SQL

    Any query that returns a number or a set of rows. Run it every minute or once a day.

    SELECT count(*) FROM signups
    WHERE created_at > now() - '1 hour'
    every 15 minalert when = 0
    03

    Choose who hears about it

    One message when the condition trips, one when it recovers. Never a stream of duplicates.

    EmailSlack · #opsTelegramDiscordTeamsWebhook
    Examples

    Questions your database can already answer.

    If you can write it as a query, you can be told when the answer changes.

    
            

    notify when

    Destinations

    Pings land where you already are.

    • Emailany address, digest optional
    • Slackchannel or DM
    • Telegrambot message
    • Discord · Teamsincoming webhook
    • Webhooksigned JSON POST
    POST your-endpointapplication/json
    {
      "alert": "failed_payments",
      "state": "triggered",
      "value": 7,
      "condition": "failed > 5",
      "previous": 3,
      "checked_at": "2026-10-07T14:02:00Z"
    }
    Built carefully

    It touches your database. We take that seriously.

    Read-only by design

    Connections are checked for write permissions before the first run. If a user can write, it's refused.

    Keeps the number, not your rows

    Only what's needed to decide whether to alert is stored: the query, its schedule and the last result summary.

    Quiet by default

    Alerts fire on change, not on every run. Quiet hours and snoozing keep 3 a.m. for real problems.

    FAQ

    Questions, answered.

    Can I use it today?

    Not publicly yet. We're onboarding a small number of teams by hand so we can shape it around real use. Email us with the database you use and what you'd like to be alerted about.

    Which databases are supported?

    PostgreSQL, MySQL, MariaDB, Microsoft SQL Server and ClickHouse to start. If yours speaks SQL and isn't listed, tell us.

    Does my data leave my database?

    Only the result of your query, and only long enough to compare it with the condition. Result rows aren't kept; we store a short summary so we can tell when the answer changes.

    What about databases behind a firewall?

    Allowlist our fixed outbound IPs, or connect through an SSH tunnel to a bastion host.

    How much will it cost?

    Pricing will be announced before public launch. Teams in early access will hear about it first.

    Stop refreshing dashboards.

    Tell us what you'd want to be pinged about. We read every email — hello@sqlnotifier.com

    Request early access