The Uptime Kuma alternative, plainly priced.
Uptime Kuma is free software you run yourself, on a server you keep patched and backed up. All's Well runs the monitoring for you: Pro checks 75 endpoints with 30-second checks for $10 a month. Below, the two services plan by plan, where Uptime Kuma is the better choice, and how to move your monitors across.
All's Well and Uptime Kuma, side by side
| Feature | All's Well | Uptime Kuma |
|---|---|---|
| Cost | Free, then $5, $10 or $20 a month | Free (MIT licence), plus a server: DigitalOcean's 1 GB droplet is $6/mo |
| Who runs it | We do: hosting, updates, backups and the check workers | You do: install with Docker or Node.js, then keep it updated and backed up |
| Monitors | 5 on Free, 20 on Starter, 75 on Pro, unlimited on Business | Unlimited, as far as your server keeps up |
| Fastest checks | 30-second checks on Pro and Business | Every 20 seconds |
| Status pages | 1 on Free up to unlimited on Business, own domain on every plan | Several status pages, each of which can have its own domain |
| History kept | 3 days (Free), 30 days (Starter), 90 days (Pro), unlimited (Business) | As long as your server keeps it |
| Check types | HTTP, keyword, TCP port, ping, SSL, domain expiry, heartbeat | HTTP, keyword, JSON query, TCP, ping, DNS, WebSocket, push, Docker containers and game servers |
| Alert channels | Email, Slack, Discord, Telegram, webhooks | More than 90 notification services, including Telegram, Discord, Slack and email |
| Check locations | London | The one server you run it on |
Uptime Kuma prices and limits as published on the project's GitHub page on , free, open-source software you host yourself. Check their site for current details.
Where Uptime Kuma is stronger
- No subscription: unlimited monitors for the price of a small server.
- Checks every 20 seconds, faster than our fastest.
- More monitor types, including DNS records, JSON queries, WebSocket, Docker containers and game servers.
- More than 90 notification services.
- Everything stays on your own server, so it can watch internal services the internet cannot reach.
How to switch from Uptime Kuma
- 01
Create a free All's Well account
No credit card needed. If you are bringing more than 5 monitors, choose a paid plan as well.
- 02
List your Uptime Kuma checks
Note each check's URL or host, type, interval and any text it looks for, and who it alerts.
- 03
Recreate them in All's Well
Add each one on the Monitors page. For a long list, script it: the REST API and the MCP server both create monitors with an API token from Settings, API tokens. Uptime Kuma push monitors become heartbeat monitors with new ping URLs, so point each job at the URL shown on its monitor page.
- 04
Add your alert contacts
Add email, Slack, Discord, Telegram or webhook contacts and attach them to your monitors.
- 05
Set up your status page
Create a public status page for the monitors your customers care about, on your own domain if you like.
- 06
Switch Uptime Kuma off
When the new monitors have run cleanly for a day or two, pause or delete your checks in Uptime Kuma.
Questions about switching
Why pay when Uptime Kuma is free?
Uptime Kuma costs a server and the time to keep it updated and backed up. A monitor that runs on the same server or network as your sites also goes quiet when that server or network fails, which is when you need it most. All's Well checks from outside your infrastructure, and its own uptime is our job.
Is there a hosted version of Uptime Kuma?
The project does not offer an official hosted service. All's Well is a separate hosted monitoring service, not a copy of Uptime Kuma, with its own check types, alerts and status pages.
Can All's Well monitor internal services?
Only from the outside. Checks run from our servers on the public internet, so a service must be reachable from there. Heartbeat monitors work the other way round: a cron job or script on your network calls its ping URL, and you are alerted when the calls stop.
Can I move my monitors from Uptime Kuma?
There is no Uptime Kuma importer. Add each monitor on the Monitors page, or script it: the REST API and the MCP server both create monitors with an API token from Settings, API tokens. Push monitors become heartbeat monitors with new ping URLs.
Does All's Well check from multiple locations?
Checks run from London, and response times are measured from there. Uptime Kuma checks from wherever you host it.
Let someone else run it.
Create a free account and add your first monitors in a couple of minutes. No credit card needed.