---
title: "Deploy Uptime Kuma on StackBlaze"
description: "Deploy Uptime Kuma with managed MariaDB, email alerts that send, and a public HTTPS URL. Add a monitor in seconds, watch it go green, and share a public status page. The admin account is created for you at deploy, so nobody else can claim the setup page."
category: "monitoring"
url: https://www.stackblaze.com/templates/uptime-kuma
---

# Deploy Uptime Kuma

Deploy Uptime Kuma with managed MariaDB, email alerts that send, and a public HTTPS URL. Add a monitor in seconds, watch it go green, and share a public status page. The admin account is created for you at deploy, so nobody else can claim the setup page.

**[Deploy Uptime Kuma on StackBlaze](https://dashboard.stackblaze.com/new/template/uptime-kuma)**

## This stack

- **Uptime Kuma**: Web service
- **MariaDB**: managed database · TCP:3306
- **Email**: platform add-on

## What you get

- **Monitors for everything**: Check websites, keywords on a page, JSON APIs, TCP ports, DNS records and more on an interval you choose, with response times and certificate expiry tracked.
- **Public status pages**: Group monitors into a status page with your own title, description and logo, and share its link with your users. Logos stay on the app volume.
- **Email alerts included**: An Email (StackBlaze) notification is wired to the platform Email add-on. Enter your address once and tick it on the monitors you care about.
- **Alerts where you work**: Besides email, Uptime Kuma sends alerts to chat apps, webhooks and many other notification services, all configured in its own settings.
- **No open setup page**: The admin account is created on first start with a password generated at deploy, before the app is reachable. Nobody else can claim your instance.
- **Browser checks too**: Real browser monitors load a page in the bundled Chromium, for sites that only work with JavaScript.

## After you deploy

1. **Open the public URL**: The hostname is on the app page after deploy. The first start sets up the database and creates the admin account, which takes about a minute.
2. **Sign in as admin**: Copy ADMIN_PASSWORD from the app’s Variables in the dashboard and sign in as admin. Change the password under Settings, Security if you like.
3. **Add your first monitor**: Click Add New Monitor, paste a URL and save. Then enter your address in the Email (StackBlaze) notification and build a status page to share.

## How it is wired

- **MariaDB holds the data**: Monitors, check history, status pages and settings live in the attached MariaDB database, with passwords generated at deploy.
- **Files are on the volume**: Status page logos and browser monitor screenshots live on a 5 GB volume at /app/data, so they stay after a restart or redeploy.
- **Mail goes through the Email add-on**: The Email (StackBlaze) notification uses the platform relay and your project’s sending address. Its settings follow the add-on on every restart.
- **One instance, always on**: Uptime Kuma runs as a single replica that checks your monitors around the clock and serves the dashboard over HTTPS.

## Common questions

### How do I sign in after deploy?

Open the public URL and sign in as admin with the password generated at deploy, shown as ADMIN_PASSWORD in the app’s Variables in the dashboard. The account exists before the app goes live, so there is no setup page to finish.

### How do I get email alerts?

Open Settings, Notifications and edit Email (StackBlaze). Enter your address in To, save, and tick the notification on your monitors. It sends through the platform Email add-on, so there is no mail server to set up.

### Can I get alerts in chat apps instead?

Yes. Uptime Kuma has many notification services built in, such as chat apps and webhooks. Add them under Settings, Notifications with the details from that service.

### Can my users see a status page?

Yes. Create one under Status Pages, pick the monitors to show and publish it. It is public at /status/<slug> on your app URL, without a login.

### Where is my data stored?

Monitors, history and settings are in MariaDB. Status page logos and browser monitor screenshots are on the app volume.

### Can I use my own domain?

Yes. Attach a custom domain from the dashboard, for example status.example.com, and point your status page at it.

### What does it cost?

You pay for the compute, storage and bandwidth Uptime Kuma and MariaDB use, and for the emails it sends, not per monitor or per seat.


Source: https://github.com/louislam/uptime-kuma