SolidPing vs Maintenant
Maintenant is the closest thing to SolidPing we have found. Both are self-hosted, both are a single Go binary, both run on SQLite with no other dependency, both are AGPL-3.0, and both ship an MCP server. It is built by Benjamin Touchard (kOlapsis), an independent developer in Bordeaux, and its pitch is "Monitor everything. Manage nothing."
Where they differ is focus. Maintenant leads with container observability: it finds your Docker and Kubernetes containers by itself, shows their CPU, memory, network and disk, streams their logs, and flags restart loops, newer images and risky configurations. SolidPing leads with protocol coverage: 40 check types, multi-region workers, users, roles and on-call.
Both sides here are self-hosted. The subject is SolidPing self-hosted, free, with no plan attached. Our hosted version is described at the end and is not in the table.
Maintenant facts below are from its site, docs and repository as of June 2026 (v1.3.2). It releases often, so some of this will have moved. If we got a detail wrong, please open an issue.
At a glance
| SolidPing (self-hosted) | Maintenant | |
|---|---|---|
| License | AGPL-3.0 | AGPL-3.0 or commercial |
| Editions | One build, no caps | Community (free), Pro (€29/mo or €290/yr), Enterprise |
| Stack | Single Go binary | Single Go binary with a Vue frontend |
| Database | SQLite or PostgreSQL | SQLite only |
| Check types | 40 | HTTP, TCP, TLS certificates, cron heartbeats |
| Free-tier limits | None | 10 endpoints, 5 heartbeats, 5 certificates, 1 status page with 3 components |
| Container observability | Docker and Kubernetes checks (up or down) | Auto-discovery, live CPU / memory / network / disk, log streaming, restart-loop detection, Compose grouping |
| Image updates and security | No | Newer-image detection, exposed ports, privileged containers, risky Kubernetes exposure. CVE enrichment in Pro |
| Built-in authentication | Yes, with organisations and admin / user / viewer roles | None. Meant to run behind a reverse proxy that handles auth |
| Multi-region checks | Distributed workers you run anywhere | Single instance. Pro adds remote agents that collect per-host data |
| Heartbeats | Ping URL, missed-deadline alerts | Ping URL with start / finish time, duration and exit code |
| Alert channels | 16 channels, SMS and voice through your own Twilio account | Webhook and Discord. Slack, Teams and email in Pro |
| On-call & escalation | Rotations, overrides, iCal feeds, multi-step escalation | Escalation policies in Pro |
| Maintenance windows | Yes | Silence rules. Maintenance windows in Pro |
| Status pages | Public, sections, custom domains, subscribers, Atom feed | Public. Incidents and subscribers in Pro |
| Config as code | YAML export / import / apply, REST API, sp CLI | Environment variables and Docker labels, REST API |
| MCP server | Built in | Built in, with OAuth2 |
Where SolidPing is the stronger choice
Protocol coverage. Maintenant probes HTTP, TCP, certificates and cron heartbeats. SolidPing adds ICMP, UDP, DNS, SMTP, IMAP and POP3, SSH, FTP, SFTP, WebSocket, gRPC, six database engines, Kafka, RabbitMQ, MQTT, SNMP, game servers, browser checks and sandboxed JavaScript checks.
Users and access control are in the product. Maintenant has no login, no users and no roles. Anyone who can reach the port can read everything, unless a reverse proxy stops them. SolidPing has accounts, 2FA, organisations and roles out of the box.
No caps on the free build. Maintenant Community stops at 10 endpoints, 5 heartbeats, 5 certificates and 3 status-page components. Slack, Teams, email, escalation, maintenance windows, incidents, subscribers and multi-host all need Pro at €29 a month. SolidPing self-hosted has no edition and no limits.
Checks from more than one place. SolidPing's workers run wherever you deploy them and check the same targets from several regions. Maintenant's Pro agents collect data from the hosts they run on. They are not geo-distributed probes.
PostgreSQL when you need it. Maintenant is SQLite only, with no HA. SolidPing runs on SQLite for a small box and on PostgreSQL when you want a managed or replicated database.
Where Maintenant is the stronger choice
Container observability, by a wide margin. Zero-config discovery of Docker and Kubernetes workloads, live resource metrics per container, log streaming with search, restart-loop detection and Compose grouping. Our container checks tell you if a container is up. Maintenant tells you what it is doing.
Security and update insights. It flags containers bound to 0.0.0.0, exposed database
ports, privileged containers, Kubernetes services exposed without a NetworkPolicy, and
images that have a newer version. SolidPing has no equivalent.
A tiny footprint. About 17 MB of RAM by the project's own figure. SolidPing uses more.
Configuration from Docker labels. Add a label to a container and the endpoint is monitored. That is a lighter path than our YAML files for a Compose stack.
Richer cron heartbeats. Maintenant records start and finish time, duration and exit code. We record that the ping arrived, so a job that hangs mid-run looks fine to us until it misses its window.
Read-only by design. The Docker socket is mounted read-only and Maintenant never acts on a container.
The other model, on both sides
Maintenant has no hosted service. Pro and Enterprise are licences for the same self-hosted binary, with a 14-day Pro trial.
SolidPing has one, running the same binary. SolidPing Cloud is free for 100 monitors and 10 checks a minute, then €5 / €15 / €45, probing from six shared regions. Going hosted brings back plan caps on monitors, check rate, seats, agents and status-page domains, and drops SMS, voice and WhatsApp, which need your own Twilio account. On those axes the self-hosted build compared here is the more capable of the two.
Which should you pick?
Pick Maintenant if you run a Docker, Compose or Kubernetes host and want container health, logs, resource charts, image updates and a few endpoint and certificate checks in one tiny container, and you already have a reverse proxy doing auth. For that job it is better than SolidPing.
Pick SolidPing if you need to watch more than HTTP and TCP, if several people or teams need their own logins and roles, if checks have to come from more than one place, or if you want Slack, email, escalation and status-page subscribers without paying for an edition. The two also run side by side without stepping on each other.