Early access — join the waitlist

Uptime and Kubernetes,
in one place.

Monidori watches your endpoints and your clusters in one clean dashboard, alerts you the moment something breaks, and uses AI to tell you why.

monidori.com/dashboard

Monitors

24

Online

23

Down

1

Avg response

146 ms

Online

API

https://api.example.com/health

99.98%

142 ms

Down

Checkout

https://shop.example.com/checkout

97.41%

—

Online

Marketing site

https://example.com

100.0%

88 ms

Online

Auth

https://auth.example.com/ready

99.92%

203 ms

prod-eu-1

Kubernetes v1.33 · supported

Nodes

6 / 6

Pods

142 / 143

AI summary

1 pod is crash-looping: checkout-7d9f in shop restarted 14× after BackOff warnings, and its deployment is 0/2 ready. The nightly-backupCronJob hasn't succeeded since yesterday.

Features

One tool instead of four.

Uptime checks, cluster visibility, alerting and AI diagnosis — designed together, so they actually talk to each other.

Uptime monitoring that tells you why

HTTP and HTTPS checks with status code and keyword assertions, basic auth, response times and SSL expiry warnings. Every check is kept as a heartbeat you can scroll back through.

api.example.com/health

GET · expects 200 · keyword “ok”

Online

Uptime 30d

99.98%

Avg response

146 ms

SSL expires

in 62 days

Your clusters, without the kubectl

Nodes, pods, deployments, events, volumes and CronJobs in one view. Open pod logs, read clean YAML, see PVC disk usage and know when your Kubernetes version goes end-of-life.

NodesPodsDeploymentsEventsStorageCronJobs

api-6c8b9d-x2kq

api

Running0

checkout-7d9f-mp4s

shop

CrashLoopBackOff14

worker-5f7c-9wqz

jobs

Running1

migrate-28817-zt

shop

Succeeded0
10:42:07 ERROR connect ECONNREFUSED 10.0.4.12:5432
10:42:07 WARN  retrying in 5s (attempt 14)
10:42:12 ERROR giving up, exiting with code 1

AI that reads the cluster for you

Open a cluster and Monidori summarises what's actually wrong: crash-looping pods, unhealthy deployments, warning events and failing CronJobs. Plain English, not a wall of YAML.

AI summary

1 pod is crash-looping: checkout-7d9f in shop restarted 14× after BackOff warnings, and its deployment is 0/2 ready. The nightly-backupCronJob hasn't succeeded since yesterday.

Alerts where you already are

Telegram, or a JSON webhook to anything you run. Alert after N consecutive failures, repeat until fixed, and get told when it recovers. Cluster rules catch crash loops, NotReady nodes and failed CronJobs.

Checkout is DOWN

503 Service Unavailable · 2 consecutive failures

shop.example.com/checkout · 10:42

Pod crash loop in prod-eu-1

checkout-7d9f-mp4s restarted 14 times

Checkout recovered

Back online after 4 minutes

SSL certificate expiry
Keyword & status assertions
Basic auth checks
Monitor folders & bulk actions
Pod logs with container picker
Syntax-highlighted YAML
PVC disk usage
CronJob success tracking
K8s version & EOL tracking
Encrypted kubeconfigs
Read-only cluster access
Full alert history

How it works

Set up in minutes, not sprints.

01

Add your endpoints

Paste a URL, hit test, save. The first check runs immediately.

https://api.example.com/health

02

Connect a cluster

Apply our read-only RBAC manifest and paste the generated kubeconfig. It's encrypted at rest.

kubectl apply -f monidori-readonly.yaml

03

Pick where alerts go

Connect Telegram or a webhook, set your thresholds, and get back to work.

2 failures → notify · repeat every 30m

Pricing

Simple pricing that starts at free.

Early-access pricing. Start free, upgrade when you grow.

Free

For side projects and homelabs.

€0/ month

  • 1 Kubernetes cluster
  • 20 HTTP monitors
  • 5-minute check interval
  • Telegram & webhook alerts
  • AI summaries with your own API key
  • 7 days of history
Most popular

Pro

For small teams running production.

€9/ month

  • 5 Kubernetes clusters
  • 100 HTTP monitors
  • 1-minute check interval
  • Telegram & webhook alerts
  • AI cluster summaries included
  • 30 days of history

Scale

For fleets of clusters and services.

€39/ month

  • 25 Kubernetes clusters
  • 500 HTTP monitors
  • 30-second check interval
  • Telegram & webhook alerts
  • AI cluster summaries included
  • 90 days of history

Need more clusters or monitors? Tell us when you join the waitlist.

FAQ

Questions, answered.

Who is Monidori for?

Engineers running a handful of services on Kubernetes who want uptime checks and cluster health in one place, without setting up and maintaining a Prometheus + Grafana + Alertmanager stack.

What access does Monidori need to my cluster?

A dedicated service account with get, list and watch permissions only. It can read resources and pod logs, but has no permission to create, change or delete anything. Kubeconfigs are encrypted at rest.

Does it replace Prometheus or Datadog?

Not for deep metrics, tracing or log search. Monidori answers “is it up, is the cluster healthy, and what broke?” — quickly, and with far less setup.

Where is my data stored?

On a server hosted with Hetzner. We only store what's needed to run your checks: monitor and alert settings, check results and encrypted cluster credentials.

When can I sign up?

Monidori is in early access. Join the waitlist and we'll email you when your spot opens.

Stop finding out from your users.

Join the waitlist and be first to know when Monidori opens up.

No spam. One email when it's ready. See our privacy policy.