SolidPing vs OneUptime
If you want uptime checks, logs, traces, metrics, error tracking and incident management in one open-source product, pick OneUptime. It is the broadest tool in this list, and SolidPing does not try to match it. If you want uptime monitoring, status pages and on-call on a small machine, read on.
OneUptime is built by HackerBay, Inc. It is Apache-2.0, with an ee/ directory under
a separate Enterprise licence that the free Community image does not contain. Like
SolidPing, it is open source you can run yourself plus a hosted service you can buy. So
this page compares the two self-hosted builds first, then the two hosted plans.
OneUptime facts below come from its repository, its in-repo docs and its pricing page on 6 October 2026 (v14.0.14). It releases almost every day, so some of this will have moved. If we got a detail wrong, please open an issue.
Self-hosted, side by side
| SolidPing (self-hosted) | OneUptime Community (self-hosted) | |
|---|---|---|
| License | AGPL-3.0 | Apache-2.0 (the ee/ directory is excluded) |
| Cost | Free. Unlimited monitors, check rate, workers and status-page domains; 30 members by default | Free |
| What you run | One Go binary on SQLite or PostgreSQL | PostgreSQL, ClickHouse and Valkey (or Redis), plus the app, workers and probes |
| Suggested machine | A small VPS is enough | Docker Compose: 16 GB RAM, 8 cores, 400 GB disk recommended; 8 GB, 4 cores, 20 GB for a homelab |
| Scope | Uptime, status pages, incidents, on-call | Uptime, status pages, incidents, on-call, logs, traces, metrics, APM, error tracking, RUM, workflows, AI agent |
| Check types | 40, including UDP, SMTP, IMAP, POP3, SSH, FTP/SFTP, WebSocket, gRPC, SIP, NTP, RDP, VNC, Kafka, RabbitMQ, MQTT, SNMP, seven databases and Minecraft | Website, API, ping, port, SSL, DNS, DNSSEC, domain, SQL, synthetic (Playwright), custom JavaScript, heartbeat, incoming email, external status page, plus host, container and infrastructure monitors |
| Fastest interval | 10 seconds | 1 minute (issue #2937, open) |
| Multi-region | Workers and private agents you run anywhere | Custom probes you run anywhere |
| On-call & escalation | Rotations, overrides, multi-step escalation | Schedules and escalation policies |
| Status pages | Public, sections, custom domains, subscribers | Public and private, subscribers, scheduled maintenance |
| SSO | OIDC, SAML, LDAP, Google, GitHub, GitLab, Microsoft | SAML and OIDC |
| Automation | REST API, sp CLI, YAML apply, MCP server | REST API, CLI, Terraform provider, MCP server, no-code workflows |
Hosted, side by side
| SolidPing Cloud | OneUptime Cloud | |
|---|---|---|
| Free plan | 100 monitors, 10 checks a minute, 5 seats | 1 status page, 100 subscribers; monitors billed separately |
| Paid plans | €5 / €15 / €45 per month, per organisation | Growth $22 and Scale $99 per user per month ($20 and $84 billed yearly), Enterprise on quote |
| Monitors | Included in the plan | From $1 per active monitor per month, checked every minute |
| SMS and voice | Not included | $0.10 per SMS or WhatsApp message, $0.10 per call minute, or your own Twilio |
| Probe regions | Six shared regions | Multiple regions |
One worked example: 100 monitors checked every minute, three users. On SolidPing Cloud that is the Pro plan, €15 a month. On OneUptime Growth it is 3 × $22 + 100 × $1, about $166 a month. That OneUptime bill also buys logs, traces and the rest of its platform.
Where SolidPing is the stronger choice
Footprint. SolidPing is one binary and one SQLite file. OneUptime needs three datastores and, by its own docs, 8 to 16 GB of RAM for a single-server install.
Fast checks when self-hosted. SolidPing goes down to 10 seconds on both versions. OneUptime's self-hosted probes stop at one minute today.
Protocols. SolidPing has dedicated checks for mail servers, SSH, FTP, UDP, SIP, NTP, RDP, VNC, message queues and Minecraft servers. OneUptime covers these with port and ping checks.
Flat cloud pricing. SolidPing Cloud is priced per organisation, with monitors in the plan. OneUptime Cloud charges per user and per monitor, so the bill grows with both.
Where OneUptime is the stronger choice
Scope, by a wide margin. Logs, traces, metrics, error tracking, RUM, profiles, and agents for Kubernetes, Docker, Proxmox, VMware and Ceph. SolidPing has none of these.
Synthetic Playwright monitors and an external status page monitor. Our browser check is simpler, and we cannot watch a vendor's own status page.
Incident workflow. Post-mortems, runbooks, and no-code workflows into Jira, GitHub, Teams and many other apps.
Terraform. OneUptime has a Terraform and OpenTofu provider. SolidPing has YAML apply and an API, not a provider.
SMS and voice on the cloud plan. OneUptime sells them per message. SolidPing Cloud does not include them.
The other model, on both sides
OneUptime Cloud runs the same product. Monitors run every minute and are billed one by one, users are billed one by one, and SSO needs the Scale plan.
SolidPing Cloud runs the same binary as the self-hosted build. Going hosted brings plan caps on monitors, check rate, seats, agents and status-page domains, and drops SMS, voice and WhatsApp, which need your own Twilio account.
Which should you pick?
Pick OneUptime if you want one open-source tool for uptime and observability, you have the machine to run ClickHouse, and logs and traces matter as much as up or down.
Pick SolidPing if uptime is the job, you want it on a small VPS or a flat cloud price, you need checks faster than a minute when self-hosted, or your targets speak more than HTTP and TCP. SolidPing has no OneUptime importer, so moving means recreating checks through the dashboard, the API or a YAML file.