Healthchecks VPS plans currently listed

ProviderPlanvCPURAMDiskRegionsBillingPrice
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesFixed price$5.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAmsterdam, NetherlandsFixed price$5.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAmsterdam, NetherlandsFixed price$9.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesFixed price$9.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAmsterdam, NetherlandsFixed price$16.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAshburn, United StatesFixed price$16.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAmsterdam, NetherlandsFixed price$32.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAshburn, United StatesFixed price$32.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesHourly$0.007/hr
EnzonixShared Compute - General Compute12 GB40 GBAshburn, United StatesHourly$0.01/hr
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesHourly$0.015/hr

Healthchecks Instant App

Self-hosted Healthchecks VPS hosting

Healthchecks is an open-source cron monitoring service for jobs, backups and heartbeats. Compare live VPS prices, CPU, RAM, disk and regions, launch Healthchecks on the plan you choose, and keep root access so your check history stays on your server.

Healthchecks

Instant App on marketplace VPS

Live marketplace offers

Compare Healthchecks VPS plans

Choose billing and size, compare providers side by side, pick a location, then launch.

Enzonix

Shared Compute - General Compute

$5.00/mo

1 vCPU · 1 GB · 20 GB

Choose location

Ashburn, United States

1 provider

Inside Healthchecks

Healthchecks watches cron jobs and other periodic tasks by expecting a ping on schedule. Use it instead of paying for Dead Man's Snitch. Sign in as admin after boot, create a check, and wire your scripts to the ping URL. No Instant App form fields are required at create time. Public registration stays off.

  • Healthchecks home after Instant App setup

    Admin ready after login

    Open Healthchecks and sign in with the prepared admin account. Checks stay behind login on your VPS.

  • Healthchecks checks list

    Checks and projects

    Create checks, group them into projects and watch last ping times. Keep cron monitoring on hardware you control.

  • Healthchecks integrations

    Integrations and settings

    Configure email and other notification channels from the UI. Grow from a personal watchdog to a team cron hub.

  • Healthchecks search

    Search and filter

    Find failing or quiet checks as the list grows. Keep search and history on your VPS instead of a SaaS tenant.

Why use the NodeRings marketplace?

Compare live Healthchecks VPS plans from independent providers, then self-host cron job monitoring on the offer you pick. Use it instead of paying for Dead Man's Snitch.

  • Compare Healthchecks VPS offers in one place

    See live prices, regions and plan sizes before you buy. Shop cron-monitoring hosts across independent providers, including 1 GB boxes that fit Healthchecks.

  • Self-host Healthchecks without a manual install

    Pick a plan and Healthchecks is prepared on that VPS for you, including the admin account. You still get root access.

  • Put cron checks in a region you choose

    Compatible offers list cities and countries. Keep ping latency low for your jobs or keep check history in a place that matches policy.

  • Own checks, projects and notification channels

    Checks, projects and alert settings live on your VPS volume. You control SSH, DNS and who can open Healthchecks.

Healthchecks hosting as a marketplace, not a single hoster

Most Healthchecks VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted cron-monitoring offers by price, size and region, then launch on the one that fits.

Healthchecks Instant App prepares Healthchecks on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.

Single-provider Healthchecks hosting

  • One company catalogue and renewal pricing
  • One set of regions and support paths
  • One vendor panel for that host only

NodeRings marketplace

  • Healthchecks VPS offers from independent providers
  • Compare resources, prices and regions side by side
  • Deploy Healthchecks on the plan you pick

How it works

Compare plans, pick a provider offer, and launch Healthchecks on that server.

  1. 01

    Compare Healthchecks VPS plans

    Browse live offers below. A 1 GB plan is a solid start for Healthchecks alone. Sort by provider, size, price and region.

  2. 02

    Pick the offer that fits

    Choose the provider plan and region. There are no Instant App form fields to fill for Healthchecks.

  3. 03

    Deploy and sign in

    Confirm checkout and wait for the server. Then open the site URL and sign in with the admin email and password from your server notes. You keep root SSH.

On the VPS after Healthchecks deploys

NodeRings Instant App brings Healthchecks up with Docker and prepares first-boot access for you. Use the sections below to reach the UI, find passwords, and operate the stack.

Open the web UI

  • In a browser, go to http://YOUR_SERVER_IP/ using the IPv4 from your order.
  • Sign in with healthchecks_admin_email and healthchecks_admin_pass from the credentials file.
  • Create a check and copy the ping URL into your cron job after you sign in.

Where the password is

Credentials are written on first boot to:

/root/.noderings_password

Read them over SSH:

cat /root/.noderings_password
  • Keys in that file include healthchecks_admin_email, healthchecks_admin_pass and site_url.
  • SSH in as root with the create-flow password or key, then run the command above.
  • SUPERUSER_* only apply on first database create. Change the password in the UI afterward.

Where files live

Compose project directory

/opt/noderings/healthchecks
/opt/noderings/healthchecks/docker-compose.yml
/opt/noderings/healthchecks/.env

Working directory for compose, the stack file, and generated secrets.

Credentials file

/root/.noderings_password

Written once on first boot.

Boot unit

/etc/systemd/system/noderings-healthchecks.service

Brings compose up after Docker is ready.

What runs in Docker

Compose runs a single Healthchecks server with data under /config. The UI is on HTTP port 80 (container port 8000).

  • healthchecks

    Healthchecks web UI and API on HTTP port 80.

Container status

cd /opt/noderings/healthchecks && docker compose ps

Live logs

cd /opt/noderings/healthchecks && docker compose logs -f

Restart containers

cd /opt/noderings/healthchecks && docker compose restart

systemd unit status

systemctl status noderings-healthchecks

Add HTTPS with Cloudflare

Your Healthchecks app starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.

  1. Add your domain

    Sign up at Cloudflare and add the domain you want to use.

  2. Point it at your VPS

    Create an A record to your server IP and leave the orange cloud on.

  3. Open the https site

    Visit https://your-domain and sign in with the admin credentials from your server notes. If the UI misbehaves, update SITE_ROOT and CSRF_TRUSTED_ORIGINS in the .env to the https URL and recreate the Healthchecks container.

  4. Only allow Cloudflare

    Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:

    curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; done

That is enough for a first secure visit. You can tighten SSL in Cloudflare later if you need it. Keep port 22 allowed for SSH; leave other ports denied except this Cloudflare allow for 80 and 443.

More detail

  • NodeRings does not sell Healthchecks as a product and is not the Healthchecks project.

Healthchecks VPS requirements and sizing

Healthchecks is a light Django app with SQLite by default under LinuxServer. A quiet personal set of cron checks needs about 1 GB of RAM; busy teams with many projects need headroom. These are starting points, not guarantees.

Illustrative starting points for Healthchecks VPS sizing
WorkloadIllustrative starting pointNote
Personal or small team cron checks1 vCPU / 1 GB RAM / 20+ GB diskSuggested Instant App floor for Healthchecks with SQLite.
Active team with many projects1–2 vCPU / 2 GB RAMMore headroom when many checks and notification channels are active.
Heavy ping volume2 GB+ RAM; disk for historyHigh-frequency pings and longer retention need extra disk and RAM.
External database (optional)Same size; Postgres elsewhereDefault Instant App uses SQLite under /config. Point Healthchecks at Postgres later if you outgrow it.

These are starting points, not guarantees. Needs depend on check count, ping rate and how many notification channels you fire.

Root access and who does what

This is self-hosted Healthchecks on a provider VPS, not managed Dead Man's Snitch. You pick the plan. Healthchecks is prepared on that server. Day-to-day care stays with you.

  • What you get ready

    Healthchecks is prepared on the VPS with no Instant App form variables. The admin account is created for you via SUPERUSER_EMAIL and SUPERUSER_PASSWORD on first boot. Public registration is disabled.

  • What you keep

    Root SSH on the VPS. You own checks, projects, integrations, DNS, TLS, OS updates and backups unless a provider product says otherwise.

  • What is not included

    Managed SMTP, automatic TLS and SaaS-style on-call routing are not bundled in. Add a mail relay and finish TLS after the server is up if you need them.

  • Support boundaries

    NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after Healthchecks on the server is yours.

Healthchecks VPS FAQs

What is Healthchecks?

Healthchecks is a free, open-source cron monitoring service. Teams use it so backups and scheduled jobs ping a URL on time, and alerts fire when a ping is late or missing.

Do I need to fill Instant App variables for Healthchecks?

No. Healthchecks Instant App asks for no form variables at create time. After the VPS is ready, sign in with the admin email and password from your server notes.

Does NodeRings run the Healthchecks server?

No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, Healthchecks is prepared on that provider server, and you manage checks from there.

Is this managed Healthchecks hosting?

No. You get a virtual machine with Healthchecks prepared for you, plus root access. That is different from Dead Man's Snitch or a managed product that owns updates and support for you.

What is Healthchecks Instant App?

It prepares Healthchecks on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.

How do I sign in after deploy?

Open http://YOUR_IP/ and sign in with healthchecks_admin_email and healthchecks_admin_pass from /root/.noderings_password. Public registration is disabled on purpose.

Can I change the admin password?

Yes. Sign in and change the password in your profile. SUPERUSER_* only applies when the database is first created.

What size Healthchecks VPS do I need?

A common starting point is about 1 vCPU, 1 GB RAM and 20 GB disk for Healthchecks alone. Larger teams and high ping rates usually need more RAM. Use the sizing guide above and compare plans in the list.

What happens after I click Deploy Healthchecks?

You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the admin credentials from your server notes.

Can I choose the server region?

Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and compliance needs.

Back to live Healthchecks plans

Compare provider offers, then launch Healthchecks on the plan that fits.