Uptime monitoring, six ways

Find out first, not from your customer.

Dumza watches everything that can quietly take your site down: websites, APIs, TCP ports, SSL certificates, domain renewals and cron jobs. One dashboard, one flat price, and an alert in your pocket within a minute of something breaking.

10 monitors free, no credit card· Every monitor type on every plan· Import your existing setup in one pass

Live monitors
4 UP · 1 EXPIRING · 1 DOWN
HTTPProduction API
99.98%142ms
TCPPostgres :5432
99.99%12ms
HTTPPayment GatewayDOWN 2m
98.40%timeout
SSLacme.dev cert
valid9d left
CronNightly backup
on time03:14
Domainacme.dev
registered241d
Payment Gateway alert delivered 14s agoEmailTelegramSlackWebhook
// what you can monitor

Six ways to go down. Six things Dumza watches.

An expired certificate takes a site off the internet just as completely as a crashed server, and a backup job that silently stopped running is worse than both. Every type below is on every plan, including Free.

Monitor type
What it watches
What sets off the alert

Website & API

GET, HEAD or POST against any URL, as often as every minute. Send custom headers or a request body, and check for a keyword the response has to contain.

Wrong status code, timeout, or a 200 that's missing the keyword you expected

SSL certificate

The certificate on any hostname, checked daily. Dumza reads the real expiry date from the live handshake rather than trusting a renewal calendar.

Certificate expiring soon, already expired, or a broken chain

Domain expiry

Registration dates for the domains you own. The failure nobody monitors, because it happens once every few years and takes everything down at once.

Registration approaching its renewal date, well before the grace period

Cron & heartbeat

Scheduled jobs that should check in on a timetable. Your backup, your billing run, your nightly export. Add one line to the end of the script and Dumza expects the ping.

The job didn't call in inside its window, so it never ran or it died halfway

TCP port

A raw connection to any host and port. Databases, mail servers, game servers, SSH, message brokers, anything that answers on a socket but doesn't speak HTTP.

Connection refused, or the handshake takes longer than your timeout

Keyword & content

Part of the website check rather than a separate monitor, and worth calling out. A page that returns 200 while rendering a stack trace is still broken, and only a keyword check finds it.

Expected text missing from the response, or forbidden text present in it

Every type counts as one monitor against your plan. No separate heartbeat allowance, no add-on packs, no per-type pricing.

// who this is for

Built for people who look after more than one thing.

If you have one side project, most free tiers are fine. Dumza is for the point where you're responsible for a list, and the list has other people's money on it.

Agencies & freelancers

Every client site on one bill

Forty client sites means forty domains, forty certificates and forty chances to find out from an angry email. Dumza charges by plan, not per site or per person, so adding a client costs nothing until you outgrow the tier.

Client sitesCert renewalsStatus page per client
Small SaaS teams

The stack behind your product

Your API, your auth service, your webhook receiver, your database port and the nightly job that reconciles billing. One place to see all of it, without adopting an incident platform to get there.

API endpointsDatabase portsBilling cron
Solo builders

Ten monitors, no card

Start on Free and stay there as long as it fits. Every monitor type and all four alert channels are included, so the free plan is a smaller version of the product rather than a demo of it.

Side projectsPersonal domainsBackup jobs
// when something breaks

The alert reaches you. It doesn't wake you up forty times.

Detection is the easy half. The part that decides whether you keep a monitoring tool is what happens in the ninety seconds after.

Four channels, every plan

Email, HMAC-signed webhooks, Telegram and Slack. Connect Telegram or Slack once on your account and reuse it on every monitor. A Telegram alert is a push notification on your phone with no credit pack behind it.

Free plan included

Confirmed before it alerts

A single failed request is usually a network blip, not an outage. An incident opens after a set number of consecutive failures, closes on recovery with the duration logged, and acknowledging it stops the re-alerts entirely.

Public status pages

A live page on a custom slug with your logo and auto-generated incident history. Subscribers are emailed when a monitor drops and again when it recovers. Embed a compact version on your own site with one snippet.

Free plan included

Response times you can trust

Latency history with our own worker outages marked on the chart, so a gap in Dumza's infrastructure never gets recorded as your downtime. Uptime percentages sit next to it for the trend.

Checks that fit your endpoint

Custom request headers for authenticated endpoints, a request body for POST checks, the status code you actually expect rather than any 2xx, and your own timeout. Stored credentials are encrypted at rest.

Import instead of retyping

Drop in an Uptime Kuma backup or a spreadsheet exported from whatever you use now. An editable preview lets you fix bad rows before anything is created, and the file is parsed in your browser.

Free plan included
// switching

Bring your monitors with you.

One file instead of forty forms.

The reason people stay on a tool they have outgrown is usually the afternoon of re-typing URLs. Export what you have now, drop the file in, and check the preview.

  • Uptime Kuma backup .json, straight from Settings → Backup → Export
  • CSV or Excel export from UptimeRobot, Better Stack, Pingdom or a spreadsheet you built yourself
  • HTTP and TCP monitors both come across, so a database check doesn't get dropped on the way in
  • Rows are editable in the preview, so a bad URL is a fix and not a failed upload
  • Intervals faster than your plan allows get raised to your plan's floor, never rejected
  • Parsed in your browser. Only the monitors you confirm are sent to us
// how the bill works

Same monitoring. Simpler bill.

Monitor types are close to a solved problem across this category. Where the tools differ is what happens to your invoice as you add people, sites and channels. That comparison is worth making explicit.

How pricing worksDumzaUptimeRobotBetter Stack
Entry price for 1-minute checks$7/mo, 20 monitors~$12–13/mo, 10 monitors$29/mo per responder
Per-seat / per-responder feesNone ✓$15–19 per login seatEvery responder is a seat
Monitors sold in add-on packsNo, set by your planNo, set by your plan~$21 per 50-monitor pack
Metered SMS / voice creditsNo credits. Telegram push insteadOne-time packs, per-country burn rateFolded into the responder seat
Your bill is made ofThe plan price. That's itPlan + credits + seatsResponders + packs + add-ons
Product scopeUptime, alerts, status pagesMonitoring suite, incidents, IT alertingIncident and telemetry platform

UptimeRobot figures read from uptimerobot.com/pricing on 9 Aug 2026 (annual billing; monthly runs higher). Better Stack figures from its published responder and add-on pricing, same date. Both change their plans regularly, so check their current pricing pages before you decide.

// pricing

Flat pricing. Start where most people stay.

Every monitor type and every alert channel is on every plan. What you're buying as you move up is how many things you watch and how often.

// straight answers

The questions everyone asks first.

What do I actually get on the free plan?

10 monitors of any type at 5-minute checks, two alert channels per monitor from email, webhook, Telegram and Slack, a public status page, and bulk import. Commercial use is included, and there is no card required to start.

Do SSL and cron monitors cost extra?

No. Every monitor type is available on every plan and each one counts as a single monitor against your limit. There is no separate heartbeat allowance and no per-type surcharge.

Which alert channels work today?

Email, HMAC-signed webhooks, Telegram and Slack, all four on every plan. Webhooks also cover Discord and anything else that accepts an inbound hook. There is no SMS or phone call, and no plan to sell credit packs for them.

Where do the checks run from?

A single region in Europe today. If you need a check confirmed from several continents before it alerts, we are not the right tool yet, and we would rather tell you here than after you have moved your monitors.

Do you charge per team member?

No. Every plan is a single flat price for one account. We do not sell responder seats or login seats, so the price on the card is the whole bill.

Can I move my monitors from another tool?

Yes, and it costs nothing on any plan. Import an Uptime Kuma backup file, or a CSV or Excel export from whatever you use now. You review an editable preview before anything is created.

Is there a public API?

Not yet. Webhooks cover the outbound direction today, and a REST API for managing monitors is planned rather than shipped. We would rather say that than list it on a pricing card.

What happens when I cancel?

You keep your paid features until the end of the period you already paid for, then drop to Free automatically. No mid-cycle cutoff, no clawback.

Set it up before the next outage, not after.

Import your Kuma backup or a CSV, run Dumza alongside your current tool for a week, then switch. Start free, no card, commercial use included.