Nagios Alternative for Website and API Checks With No Server to Run
Nagios is the monitoring tool many ops teams learned on, and for internal infrastructure it still earns its place: host and service checks through plugins, NRPE on the machines you own, and a configuration model you can keep in version control. The trouble starts when Nagios is also the thing watching your public website and API. Those checks come from the server that runs Nagios, so you get one vantage point, inside or next to your own network. If that network, that server or that DNS resolver has a bad hour, you either miss a real outage or page yourself for a false one. Someone also has to own the plugin updates, the object config, the notification commands and the box itself, and each new URL means editing files and reloading the daemon. UptimeHub takes over only that external slice. HTTP, keyword, API, ping, port, SSL expiry and cron heartbeat checks run from two regions outside your infrastructure, a failure is confirmed from the second region before anyone is alerted, and the public status page updates from the same checks. Adding a monitor is a form, not a config reload. It does not replace Nagios for CPU, disk, process and database checks inside your servers, because it is read-only and installs nothing. The setup most teams settle on keeps Nagios for the inside and moves customer-facing endpoints to an external monitor, so the alert still arrives when your own network is the thing that broke.
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
Side by side
UptimeHub vs Nagios
| Capability | UptimeHub | Nagios |
|---|---|---|
| Nothing to install, patch or reload | Server, plugins and config to maintain | |
| Checks from 2 regions outside your network | One location, where Nagios runs | |
| Auto-retry from a second region before alerting | Retry settings per check, same location | |
| Add a URL in seconds from a form | Edit object config and reload | |
| Branded public status page | Not included | |
| Cron heartbeat and SSL expiry checks | Through plugins you configure | |
| Host CPU, memory, disk and process checks | ||
| Custom plugins for any protocol | ||
| Free open-source core | Paid, flat per monitor | Core is free to license |
Comparison reflects general product positioning and is provided in good faith. Verify current capabilities with each vendor.
What moves off Nagios and what stays
Split the checks you run by who they protect. A check that asks "can a customer load this page, call this API, trust this certificate" belongs outside your network, because only an outside probe sees what the customer sees. A check that asks "is this disk filling up, is this daemon alive, is replication lagging" belongs inside, next to the machine, and Nagios with NRPE or an agent is the right tool for it.
In practice that moves a handful of definitions out of Nagios: the HTTP and HTTPS checks, the certificate expiry check, the keyword check on the login page and the heartbeat for the nightly job. Everything else keeps running as it does today. Nothing about moving the external slice forces a migration of the rest.
What the cost looks like for 30 external checks
Take a team that runs Nagios mostly to watch 30 public endpoints: 12 sites, 10 API routes, 6 certificates and 2 cron heartbeats. On Nagios Core the licence is free, so the real cost is the server, the time spent on config and upgrades, and the single vantage point. On Nagios XI, the licence is priced per node. The figures below come from the vendor price list read in September 2026 (see the Nagios XI pricing breakdown) and from our own plans.
Thirty monitors are over the Starter limit of 20, so the realistic pick is Pro with 100 monitors, which leaves room to grow. Plans are priced per monitor allowance, never per seat, and the full price list shows both billing options.
| Option | Year one | Five years | What you also carry |
|---|---|---|---|
| Nagios XI Standard, 100 nodes | $2,595 | About $11,011 | Server, plugin and config upkeep, one location |
| Nagios Core | $0 licence | $0 licence | Server, plugin and config upkeep, one location, admin hours |
| UptimeHub Pro billed yearly, 100 monitors | $588 | $2,940 | Nothing to host, two regions, status page included |
| UptimeHub Pro billed monthly, 100 monitors | $1,188 | $5,940 | Same plan, cancel any month |
Where Nagios is the better choice
Choose Nagios when most of your monitoring is internal: hosts, daemons, network gear and custom plugins for protocols a hosted tool does not speak. Choose it when policy says monitoring data stays inside your network, or when you already have engineers who keep the configuration in version control and like it that way. Vendor documentation is at nagios.org.
Choose UptimeHub when the pain is the public side: a status page you update by hand, alerts that arrive only if your own network is up, and a config file every time marketing launches a new landing page. For the same job priced across vendors, see the uptime monitoring pricing comparison, and for another self-run tool teams swap out, read the Uptime Kuma alternative.
See it live
Monitoring and a status page, self-serve
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
FAQ
Questions buyers ask about switching from Nagios
For public websites, APIs, SSL certificates and cron jobs, a hosted external monitor is the closest swap. UptimeHub runs those checks from two regions, confirms a failure from the second region, and alerts Slack, Teams, Discord, Telegram, PagerDuty, webhook or email. It does not read server internals, so keep Nagios or an agent tool for CPU and disk.
The Core software is open source with no licence fee. The cost moves to the server it runs on, the plugins you keep updated, the configuration files you maintain and the engineer time to do all of it. Nagios XI, the commercial product, is sold by node count and renews yearly, so price both before you compare.
Nagios lists XI Standard at $2,595 for 100 nodes, with a renewal near $2,104 a year after the first. Five years is about $11,011. A hosted plan for 100 monitors is $588 a year billed yearly, or $2,940 over five years. The two cover different ground, so the right comparison is for the checks you move.
Yes, and it is the common setup. Nagios keeps watching hosts, services and internal ports with NRPE or agents, while UptimeHub watches what customers reach from outside: the homepage, the login, the API, the certificate and the cron heartbeats. If the datacenter network drops, the external alert still gets out.
There is nothing to install on Linux or anywhere else. Checks come from outside, so any server, container or serverless host works as a target. For internal Linux metrics such as load, memory and disk you still need an agent, which UptimeHub deliberately does not use.
What Nagios actually costs, before you decide
Other comparisons
Still drawing up a shortlist? Our roundup of the best uptime monitoring tools compares 13 of them on check types, regions, status pages and pricing model.
See it on your own site
Transparent per-monitor pricing, all check types in one plan, and a branded status page included. Read-only external checks that never touch your servers, live in minutes. Decide for yourself.