Self-host Healthchecks with Levelrail

Cron job and scheduled task monitoring: get alerted the moment a periodic job stops checking in.

  • Authorhealthchecks
  • LicenceBSD-3-Clause
  • Memory256 MiB
  • Archarm64
  • Services2

How to self-host Healthchecks

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • healthchecks/healthchecks:v4.2
  2. Create the app

    2 services start in a single Compose app, with 1 named volume mount for your data, on port 8000.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Healthchecks requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
8000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
BSD-3-Clause, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 8000 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Healthchecks. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Healthchecks docs page.

Deploy Healthchecks your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Healthchecks from the CLI

levelrail-cli templates deploy healthchecks --name my-healthchecks

Deploy Healthchecks with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/healthchecks/deploy

Healthchecks configuration

Healthchecks services

ServiceImagePortsVolumes
db postgres:16-alpine none healthchecks_db_data -> /var/lib/postgresql/data
healthchecks healthchecks/healthchecks:v4.2 8000 none

Healthchecks environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
ALLOWED_HOSTS healthchecks Preset by the template
DB healthchecks Preset by the template
DB_HOST healthchecks Preset by the template
DB_NAME healthchecks Preset by the template
DB_PASSWORD healthchecks Generated at deploy
Show all 10 variables
  • DB_USERhealthchecksPreset by the template
  • SECRET_KEYhealthchecksGenerated at deploy

Ports and volumes

Ports
8000
Volumes
1 named mount: healthchecks_db_data -> /var/lib/postgresql/data

Healthchecks FAQ

How much memory does Healthchecks need?

The catalog lists about 256 MiB of memory for Healthchecks across its 2 services.

Does Healthchecks run on arm64?

For Healthchecks, an arm64 image is published; amd64 is image published.

What licence is Healthchecks under?

Healthchecks is licensed under BSD-3-Clause, which is permissive, with few conditions on reuse.

Does Healthchecks need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Healthchecks bundle?

The template includes Postgres, running as its own service.

Which ports does Healthchecks use?

Healthchecks listens on port 8000 inside the stack.

Where does Healthchecks keep its data?

In a named volume: healthchecks_db_data mounted at /var/lib/postgresql/data.

Can I deploy Healthchecks on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id healthchecks for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, healthchecks/healthchecks:v4.2 is what you deploy there.

levelrail-cli templates deploy healthchecks --name my-healthchecks