---
title: Deploy Uptime Kuma with AI on Blossom
url: "/deploy/uptime-kuma/"
canonical_url: https://docs.blossom88.com/deploy/uptime-kuma/
markdown_url: https://docs.blossom88.com/deploy/uptime-kuma.md
summary: Deploy Uptime Kuma with AI on Blossom. Self-host a private monitoring dashboard
  with managed data and uptime checks for your apps.
categories:
- deployment
- monitoring
---

# Deploy Uptime Kuma with AI on Blossom

[Uptime Kuma](https://github.com/louislam/uptime-kuma) is a self-hosted
uptime monitor that checks your websites and services and alerts you when
they go down.

Ask your agent to deploy a private monitoring dashboard on Blossom, keep
its data in a managed database, and help you add your first checks.

[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent


> **Ask your AI agent:** Deploy Uptime Kuma on Blossom with a private dashboard and managed database.
> Help me monitor my apps.

> Follow this guide: https://docs.blossom88.com/deploy/uptime-kuma/



Your agent selects a maintained official image and compatible database,
then saves the chosen versions in your deployment configuration.

| Part | Purpose |
|---|---|
| Kuma web Service | Runs the dashboard and monitoring checks |
| Managed MariaDB | Keeps monitors, settings, and history across app updates |
| Private HTTPS access | Protects the dashboard with Account membership and your Kuma login |

**Run one active Kuma instance.** Each process schedules its own monitors,
so extra replicas repeat probes. Keep autoscaling off; adjust the Container's
resources as your monitor count and check types change. Have your agent
confirm the release's supported scaling model before changing that setup.

Open the HTTPS URL your agent returns, sign into Blossom, and create your
Kuma administrator account.

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Your agent prepares configuration files using the current CLI help and
upstream requirements. Use the IDs returned by Blossom in these examples.

### Create the App and Database

    blossom profile:show
    blossom app:create --data '{"app":{"name":"uptime-kuma"}}'

The agent writes environment.yml with your App ID and the official image it
selected. Pin that image for your deployment:

```yaml
environment:
  app_id: app-100
  name: production
  source_type: prebuilt_image
  prebuilt_image: <official image pinned by your agent>
  access_mode: members
```

It also prepares database_instance.yml for managed MariaDB, selecting the
version, size, storage, and backups for your workload.

    blossom environment:create --data environment.yml
    blossom database_instance:create --data database_instance.yml --follow
    blossom environment_link:create --data '{"environment_link":{"environment_id":"environment-100","target_type":"DatabaseInstance","target_id":"database_instance-100","var_name":"DATABASE_URL"}}'

### Configure and Deploy Kuma

Blossom supplies `DATABASE_URL` over its private network. The agent maps it
to Kuma's database settings and writes service.yml with the image's startup
command, an HTTP health check, and one active Container. MariaDB keeps the
monitor configuration and history. For uploaded status-page images, also
configure [persistent file storage](/docs/reference/cli/service/create/#persistent-services).

    blossom service:create --data service.yml
    blossom environment:deploy --id environment-100 --follow
    blossom environment:show --id environment-100

</details>

## Add Your Domain


> **Ask your AI agent:** Put Kuma at uptime.example.com and help me set up DNS.

> Follow this guide: https://docs.blossom88.com/deploy/uptime-kuma/



<details class="optional-reading" markdown="1">
<summary>Command behind the custom domain</summary>

    blossom domain:create --data '{"domain":{"environment_id":"environment-100","dns_name":"uptime.example.com","main":true}}'

</details>

Add the returned DNS record at your provider. Blossom's
[domain setup](/learn/domains/) handles HTTPS. In Kuma's
**Settings → General**, set **Primary Base URL** to your custom HTTPS URL.
Account member access applies to the custom domain too.

## Start Monitoring Your Apps


> **Ask your AI agent:** Help me choose which Blossom apps to monitor and set up alerts.

> Follow this guide: https://docs.blossom88.com/deploy/uptime-kuma/



In Kuma, choose **Add New Monitor**, select HTTP(s), and enter the App's
HTTPS URL or health endpoint. Choose the interval, timeout, and expected
response for that endpoint. Set up your preferred notification channel in
Kuma and send a test alert.

An endpoint that intentionally returns 401 can be monitored as an **access
gate** check. To check protected content, configure authentication in Kuma.
Blossom [Environment access tokens](/docs/apps/environment-access/#environment-access-tokens)
let a monitor reach an App restricted to Account members.

<details class="optional-reading" markdown="1">
<summary>Commands behind the App inventory</summary>

    blossom app:list
    blossom environment:list

</details>

Read [how we deployed Uptime Kuma with AI](https://blog.boltops.com/2026/11/17/deploy-uptime-kuma-with-ai-on-your-own-cloud/)
for the companion article.

## What You Get

- A private HTTPS monitoring dashboard
- Monitor settings and history in managed MariaDB, with recovery backups
- A custom domain and uptime checks for your Apps
- Notifications through the channels you configure in Kuma
