Uptime Kuma

What you can use it for

• Check websites, APIs and TCP ports at regular intervals and get notified when they stop responding.
• Publish a status page that shows users the availability of your services.

Choose the right configuration

Use this template for periodic availability checks and status pages. Decide which endpoints the deployment region can reach and prepare your notification credentials. If the monitor shares infrastructure with the services it watches, plan an independent check for outages that could stop both.

What this template creates

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

1. Select Configure deployment and sign in or create an account.
2. Choose a new or existing project and select an available region.
3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Check your deployment

Create the admin account, add a test monitor and confirm a successful check. Send a test notification and verify it arrives at the intended destination. Use a disposable target to simulate a failure and recovery, then check the alert history; a green monitor alone does not prove that notifications work.

Operating this application

• Open the generated domain right after deployment and finish Uptime Kuma's setup by creating the admin account, because the setup page is open to anyone until you do. Email and chat notifications need their own SMTP or service credentials.
• Monitors, notification settings and check history are stored under /app/data on the volume. Check your backup and recovery options and test a restore before relying on them.
• The louislam/uptime-kuma:2 tag moves with new 2.x releases, so read the release notes before redeploying. Checks run from the region where the service is deployed, and a monitor hosted alongside the services it watches may not alert you during a shared outage.

Hosting costs

This template runs one service with a data volume. Monitor count, check frequency and retained history influence resource needs. Include any charges from your chosen notification provider separately.

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-15

Upstream documentation ↗Template source and license ↗