Tissue Mast vs Uptime Kuma
Uptime Kuma costs nothing and it’s good. It runs on your own server, checks as often as every 20 seconds, and sends to Telegram, Discord, Slack, Pushover, email and about 90 other services. It doesn’t decide who to wake, and it can only see your sites from the network it runs on.
Uptime Kuma is open source under the MIT license and you host it yourself. It checks HTTP, keywords, JSON queries, TCP, ping, DNS, push and Docker containers at intervals down to 20 seconds, and it has multiple status pages on your own domains. There’s no price.
It has no rotation or escalation. A notification goes where you point it, and if you need someone on call you add a pager such as PagerDuty, at $21 a user a month on Professional. Tissue Mast is hosted, checks from eight places with a vote before anyone is woken, and pages whoever is on call. The free account is five people, ten probes every 5 minutes and ten vitals.
What each one is
Two sentences each, before any numbers.
- Uptime Kuma
- A self-hosted uptime monitor with a web dashboard, status pages and a long list of notification services. You run it in Docker or with Node.js on a machine you look after.
- Tissue Mast
- A hosted uptime monitor with a pager attached. Probes fetch your URLs from eight places, vitals page you when a cron job does not check in, and a page rings the Mast Pager app on iPhone and Android, escalating through an on-call rotation until someone answers.
Side by side
Every figure below came off the other company’s own pages, on one day, and is dated underneath.
| Uptime Kuma | Tissue Mast | |
|---|---|---|
| Price | Free. You pay for the machine it runs on. | Free: up to 5 people, 10 probes checked every 5 minutes, 10 vitals, 10 alert sources. Team, $290 a year or $29 a month, for the account. No limit on people; 100 probes. |
| Where it runs | Your server. | Ours. |
| Where it checks from | The network your server is on. | Eight places; a page needs more than half to fail on two networks, twice. |
| Shortest interval | 20 seconds. | 5 minutes on Free, 30 seconds on Team. |
| Notifications | 90-plus services, including Telegram, Discord, Slack, Pushover and email. | Mast Pager on iPhone and Android. |
| On call | None. | Rotations, overrides and escalation on every paid plan. |
| When the monitor itself goes down | You find out some other way. | We run it and get paged for it. |
| Open source | Yes, MIT. | No. |
Checked 18 November 2026 against Uptime Kuma’s GitHub repository. Both of us move; if a figure here has gone stale, tell us and we will correct it.
Where Uptime Kuma is the better choice
It’s free and the code is yours. If you have a server you trust and you like running your own tools, it’s a good choice.
Shorter intervals for nothing. Twenty seconds, on as many monitors as your machine can handle.
Where it sends. Ninety-odd services, including chat tools we don’t post to. If a Discord message is how your team hears about an outage, Uptime Kuma does that out of the box.
Internal services. It runs inside your network, so it can check things that aren’t on the internet. Our probes only reach what’s public.
Where Tissue Mast is the better choice
It doesn’t run on your machine. When your Uptime Kuma box loses power or its network goes down, it can’t tell you. Our probes run from eight places that aren’t yours.
A vote before anyone is woken. One location timing out doesn’t page anyone; most of the eight have to fail on two networks, twice.
On call. A failed probe rings whoever is on the rotation, then the next person. Uptime Kuma can send to Pushover, which rings the same way, but it sends to everyone you named.
The free account takes an email address. If you already run Uptime Kuma, point it at a Mast alert source and let Mast decide who to wake, or add a few probes here as a second opinion from outside your network.