Qualimonitor

Platform

Private probes — monitor from inside your own network

app.qualimonitor.com

Monitors

  • api.acme.com 82 ms
  • acme.com 104 ms
  • db-primary (probe) 3 ms
  • mail.acme.com expires in 74 days
  • cdn edge — GRU loss 2.1%
  • legacy.acme.com timeout

uptime 30d · 6 regions · every 30s

One Docker command

`docker run qualimonitor/probe` with your organization token. The probe appears in your dashboard in seconds and is ready to run checks from inside your network.

Internal + external view

Compare the view from outside (global probes) with the view from inside (your probe). If outside fails and inside doesn't, the problem is network or transit — not your application.

Built for MSPs

Install a probe in each client's infrastructure and monitor everything from one multi-org account. Every client gets inside-view monitoring without giving you VPN access.

Requirements and security

Requirements: Docker and outbound HTTPS — nothing else. The probe only makes outgoing connections, so it works behind NAT and strict firewalls with zero inbound ports open.

Updates are automatic via probe-version checks. Authentication uses a per-organization token you can revoke at any time.

docker run -d --restart=always \
  -e QUALIMONITOR_TOKEN=<your-org-token> \
  qualimonitor/probe

Questions

FAQ

How many resources does a probe consume?

It's a small container: a slice of one CPU core and a modest amount of memory. It runs comfortably alongside other workloads on any host that runs Docker.

How many probes does each plan include?

Pro includes 1 private probe, Business includes 5, and Enterprise is custom. The Free plan uses our global probes only.

Does it work behind NAT?

Yes — the probe only makes outbound connections over HTTPS. No inbound ports, no port forwarding, no VPN required.

Start free