uptime-kuma 2.5.0

github.com / louislam / uptime-kuma · MIT

What this app does

A fancy self-hosted monitoring tool

What opens, and what to do first

The app opens on its setup screen and asks you to create the first account. A password will be generated for your session and shown to you when the demo starts. Use it, or choose your own.

What is already in it

It starts with an invented company inside it, so you are not looking at an empty app — Business · saas company v2, normal operations.

Everyone in it is invented and every address ends in .droplive.test, which can never resolve. What that means →

What it is talking to

All of it runs inside your session and never reaches the real vendor.

Mail

A genuine implementation, running inside your session.

REAL

Vendor APIs

Answers like the vendor, from inside your session.

STAND-IN

File storage

A genuine implementation, running inside your session.

REAL

The model

Answers like the vendor, from inside your session.

STAND-IN

Feeds and web pages

A genuine implementation, running inside your session.

REAL

How this demo runs

Your own machine

A virtual machine with its own kernel, started for you. Nobody else is in it.

The real thing

uptime-kuma's own published image, pinned to f0ebe6fa7f91, not a recording or a scripted tour.

Then it is gone

Yours for 15 minutes, and the clock starts when the app is ready. The machine is destroyed at the end, with everything in it.

Recorded, for you

Every hostname it reaches for is captured outside the machine, so the software cannot edit its own record. It is kept under History, readable only by you. How that works →

What past demos did

external destinations

Captured outside the sandbox, so the software cannot edit its own record. A destination seen in only one session is left out. We do not collect processes or file changes yet, so they are absent here rather than shown as zero. This is what happened, not a rating.