Uptime Kuma for website and endpoint monitoring
The Uptime Kuma template includes a persistent data volume. Configure monitors, status pages, and notification providers in the application. Service creation is currently unavailable in the international sandbox.
Uptime Kuma template features
Monitor endpoints and configure supported notification channels. Resource use counts toward the selected monthly EUR package limits.
Monitor websites, ports, and services
Uptime Kuma can check HTTP(S), TCP, ping, and DNS endpoints and display response-time history. Check frequency and results depend on monitor settings and network conditions.
Notification integrations
Uptime Kuma supports notification channels such as Telegram, Discord, Slack, email, webhooks, and SMS. Each integration requires its own provider credentials and configuration; delivery depends on that provider.
Status pages
Uptime Kuma can publish status pages. Custom domains and access settings need to be configured for your deployment.
SSL/TLS certificate monitoring
Uptime Kuma can monitor SSL/TLS certificate expiry and send notifications when configured. Alert timing and delivery depend on monitor and notification settings.
Frequently asked questions about Uptime Kuma
Answers to common questions about monitoring websites and services, checking endpoints, and configuring notifications:
Uptime Kuma guide: monitor website and service endpoints
Monitoring can help teams notice when websites or services stop responding. Uptime Kuma checks configured endpoints and records results. Check intervals, alert delivery, and the view from a particular network depend on monitor settings and connectivity.
What is Uptime Kuma, and what can it monitor?
Uptime Kuma supports monitors for HTTP(S), TCP, ping, DNS, and other endpoint types. Depending on the monitor and settings, it can check response codes, response time, certificate expiry, or expected text.
You can use Uptime Kuma to monitor applications running in Cloud containers containers. For broader infrastructure monitoring, consider Zabix or combine it with dashboards such as Grafana to review metrics collected by those systems.
Hosted monitoring and self-hosted Uptime Kuma
Hosted monitoring services and self-hosted tools differ in monitor limits, check intervals, notification options, locations, and pricing. Compare current plans and service terms for the coverage you need.
The Deplomo template runs self-hosted Uptime Kuma. Monitor counts, intervals, and notifications depend on the application, package resources, and provider configuration; third-party notification services may have separate charges.
Uptime Kuma deployment options
The table summarizes general differences between the marketplace template, hosted services, and manual deployment. Features and limits depend on provider and configuration.
| Feature | Uptime Kuma template on Deplomo | Hosted monitoring service | Manual checks and scheduled scripts |
|---|---|---|---|
| Monitor capacity | Depends on the instance resources and configuration | Limits depend on the hosted plan | Depends on the scripts and infrastructure you maintain |
| Check interval | Configurable in the monitor settings; more frequent checks use more resources | Depends on the provider and plan | Depends on the schedule and resources available to your scripts |
| Status pages | Uptime Kuma supports status pages; page count, custom domains, and appearance depend on configuration | Options depend on the hosted service and plan | Requires building or integrating a status-page interface |
| Pricing and resource scaling | Fixed monthly EUR package with resource limits; third-party notification services may charge separately | Pricing and account requirements depend on the provider | Infrastructure and maintenance costs vary |
Self-hosted Uptime Kuma provides configurable monitors and status pages. Check its resource needs, monitor settings, notification providers, and the availability of your monitoring instance.
Set up Uptime Kuma on Deplomo
Service creation is currently unavailable in the international sandbox. When it becomes available, these are the general steps:
- Choose Uptime Kuma from the marketplace: In the console, select the Uptime Kuma marketplace template.
- Review package resources: Check the monthly package limits against the number and frequency of checks you plan to run.
- Open the dashboard: After deployment, use the service address shown in the console to open Uptime Kuma.
- Add monitors and notifications: Configure endpoint URLs, check types, and any notification providers you use. Notification delivery depends on those providers.
Uptime Kuma deployment: summary
Uptime Kuma can help you track configured service endpoints and review check history. Results depend on monitor settings, network conditions, and the availability of the monitoring instance.
Service creation is currently unavailable in the international sandbox.
Uptime Kuma marketplace template
The template runs Uptime Kuma with a persistent 1 GB data volume. Domain, TLS, and notification settings depend on your configuration.