Comparisons

Vitrina Engine compared with Uptime Kuma

Uptime Kuma is excellent free, open-source software that you run yourself, and a great many people rely on it. So the real comparison is not feature against feature: it is a hosted service against running, securing and looking after your own monitor.

Checked on 13 September 2026, against Uptime Kuma 2.5.4. Our prices are list prices in US dollars before tax, set per country, so yours may differ.

Where Uptime Kuma is the better choice

  • It is free under the MIT licence, with no plan limits on monitors or pages.
  • It has a very wide range of checks, including databases, message brokers, Docker containers, game servers, gRPC, a real browser, SNMP and SIP.
  • It has about a hundred notification integrations, more than most commercial tools.
  • It runs inside your own network, so private addresses are reachable without opening anything, and your data never leaves your hands.
  • Intervals can go down to a second, if your hardware can take it.
  • Multiple status pages with custom domains and custom CSS cost nothing.
  • It is an active and very popular project that releases often.

Where Vitrina Engine is the better choice

  • There is no server to run. Nothing to patch, back up, upgrade or keep up, and the monitor does not live on the same network as the things it watches, so it is still there when that network is not.
  • Checks come from several locations, and a failure is confirmed by consecutive failures seen from different places. With one host, a fault on the path between it and your server looks exactly like an outage.
  • Teams, not one login. Members with roles, instead of a single admin account shared by everyone.
  • On-call schedules and escalation, from the Pro plan.
  • Status page subscribers, who are told when something happens.
  • An official, versioned REST API, and an MCP server for AI agents.
  • An audit log from the Business plan, and single sign-on on Enterprise.
  • Client workspaces, so an agency’s clients each see only their own monitors, pages and incidents.
  • Monitors declare what they depend on, so a failing upstream opens one incident for the root cause instead of one per symptom.
  • Checks Uptime Kuma does not have: SMPP and XMPP, IMAP and POP3, a TLS configuration audit, SPF, DMARC and DKIM, blocklist monitoring, and NetFlow, sFlow, J-Flow and IPFIX traffic analysis.
  • An alert when a monitor answers far slower than its own history, and private postmortems written in Markdown once an incident is resolved.
  • Sentry-compatible error tracking and cookie-free web analytics, in the same account.
  • Private probes, for when you do need to see inside a network, without giving up the view from outside it.

What running your own actually costs

The licence is free and the rest is not. You need a host to run it on, and it should not be the host it is watching. Upgrades are yours: moving from version 1 to 2 was a one-way database migration that could take hours and could not be interrupted. Backups are yours: copying the data directory is the supported method. TLS is yours. And nothing watches the watcher, so if the monitor stops, the first sign may be an outage nobody was told about.

Uptime KumaVitrina Engine
Software$0, MIT licenceFree plan $0 for 50 monitors; Starter $7 a month; Pro $19 a month
Somewhere to run itA small VPS, or a machine you already haveIncluded
Upgrades, backups, TLSYour timeIncluded
Knowing the monitor itself is downUp to you to arrangeOur job

Side by side

Uptime KumaVitrina Engine
CostFree, plus hosting and your timeFree plan; paid plans from $7 a month
Who runs itYouWe do
Fastest check1 second, hardware permitting1 minute on Free, 45 seconds on Starter, 30 on Pro, 15 on Business, 5 on Enterprise
Where checks run fromThe one host it is installed onSeveral locations, plus private probes inside your network
Confirming a failureFrom the same hostConsecutive failures seen from different locations
Kinds of checkVery wide, including databases, brokers, Docker and a browser30, including DNS, certificates, domains, heartbeats, a server agent, databases, Docker and network flow
Mail serversSMTPSMTP, IMAP and POP3, plus SPF, DMARC and DKIM
Telecoms protocolsSNMP and SIPSNMP, SIP, SMPP and XMPP
Users and rolesOne admin accountMembers with roles
On-call and escalationNoFrom Pro
Status pagesMultiple, own domains, custom CSS; no subscribersPassword protection on every plan; own domain and subscribers from Starter; white-label from Pro
NotificationsAbout a hundred integrationsEmail, Slack, Teams, Discord, Telegram, WhatsApp, PagerDuty, webhooks, and SMS from Pro
API and MCPNo official API; community MCP projectsOfficial REST API and MCP server
Audit log and SSONoAudit log from Business; SSO on Enterprise
Error trackingNoSentry-compatible, on every plan
Web analyticsNoCookie-free, on every plan

Watching internal networks and telecoms systems

Uptime Kuma is inside your network by nature, which is a real advantage for private systems, and it has SNMP and SIP checks. What it cannot give you is a second opinion: every check comes from the one machine it runs on, and there is no multi-location confirmation, so a problem on that machine’s path looks the same as a problem with the service.

Vitrina Engine does both. A private probe runs inside your network, leases its work over HTTPS without ever holding a database credential, and reports into the same dashboard as the checks we run from outside. The telecoms checks do the protocol rather than just the port: SNMP polls the OIDs you name and judges each against a threshold, SMPP binds and unbinds, SIP sends OPTIONS, and XMPP opens a stream and negotiates STARTTLS.

Sources

See pricing for every plan’s limits, the monitors guide for what each check proves, or start free.