JustUp!

JustUp! is a self-hosted, single-container uptime monitoring app with built-in SQLite for home-lab operators that checks websites, APIs, hosts, TCP/UDP ports,…

  • Monitoring & Logging
  • Network Services
  • Tools & Utilities
JustUp! is a self-hosted, single-container uptime monitoring app with built-in SQLite for home-lab operators that checks websites, APIs, hosts, TCP/UDP ports, and TLS certificates, sends email or Signal alerts, and reduces false alarms with route inspection, PDF reports, and a quality gate.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

56/100 Fair

Maintained
100last commit 6 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-11-15
Latest release
v1.0.3
License
MIT
Activity
unknown

Checked 3 days ago - source: GitHub (Gill-Bates/justup)

Resources & Compatibility

Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 3 days ago - source: Docker Hub image tags and published docs

First-install notes

  • First start Set a persistent Secret Key environment variable before starting the container for the first time. Sign in as admin with the temporary password printed in the container log, then change the password at first login. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What must I set before the first start so encrypted data remains readable?

Generate and set a persistent SECRET_KEY environment variable before starting the container for the first time. Reuse the same key when recreating the container so stored secrets remain readable.

How do I log in the first time?

Sign in as admin using the temporary password printed in the container logs. justUp! requires you to change this password at first sign-in.

Where is state and history stored?

Application state and measurement history are stored locally using built-in SQLite and a built-in time-series store. Mount a persistent volume at /app/data to keep that data.

Which container port should I expose?

Expose container port 8000, for example by binding 127.0.0.1:8000:8000 when you plan to reach it through a reverse proxy.

How does justUp! reduce false alarm alerts?

Its Quality Index checks justUp!'s own connectivity, and when it falls below the configured minimum, due checks pause and affected targets show unknown instead of triggering misleading DOWN alerts.

Answers sourced from github.com

Community

Collected 3 days ago - public community threads