Skip to content

What do you need to do?

Docs

RealUptime + Coolify

Coolify runs on a server you own (your own VPS or dedicated box), which means the Monitor agent has somewhere real to live: install it once on the Coolify host, and it reports both the host's own health and, with a small addition, every app Coolify deploys there.

What you are setting up

Three pieces: the Monitor agent on the Coolify host, an HTTP check for each app you deployed with Coolify, and a status page. Because Coolify is Docker underneath, the agent runs the same way any other Coolify service does.

Install the agent

Register an agent from Monitor settings in the dashboard first; the token is shown once, with the exact command below already filled in. On the Coolify host itself, as a one-liner (Docker if present, a hardened systemd service otherwise):

bash
curl -fsSL https://realuptime.io/agent/install.sh | sh -s -- --token rua_your_token_here

Or add it as one more service in Coolify's own Docker Compose resource type, so it is managed the same way your other Coolify services are:

services:
  realuptime-agent:
    image: ghcr.io/realuptimehq/agent:latest
    restart: unless-stopped
    environment:
      REALUPTIME_TOKEN: rua_your_token_here

See Monitor agent for the full install matrix (Kubernetes, Windows, macOS) and for the container-vs-host caveat if you run the agent inside its own isolated container rather than with host networking.

Create the checks

One HTTP check per app Coolify deployed, watching the public domain, not the internal Coolify network address:

bash
export REALUPTIME_API_KEY=ru_live_...

realuptime checks create \
  --name "My app (Coolify)" \
  --url https://myapp.example.com/ \
  --interval 60 \
  --regions iad,fra

If an app is code you control, wire in RealUptime Errors as well; the HTTP check catches "the app is down", the SDK catches "the app is up but throwing".

Add a status page

Create a status page from the dashboard and add both the agent's host and your app checks as components, so a visitor can tell "the box is fine but this one app is down" from "the whole host is unreachable". See Status pages.

What RealUptime does and does not see

The agent reports the Coolify host's CPU, memory, disk, and load, exactly like any other server it runs on; see Monitor agent. It does not read Coolify's own database, its deployment history, or the source of the apps it manages, and it never runs a command RealUptime sends: see the same page's "Outbound only" section for the full list of what it is and is not capable of.

HTTP checks see exactly what a visitor to each app sees. They do not see anything behind Coolify's reverse proxy that is not exposed publicly, and they do not read Coolify's own health checks or build logs.