Your whole stack.
One calm glance.

Know what’s up, what’s down, and since when.
Free, open source uptime and API monitoring that runs on your own server.

Self-hostedNo monitor capsAGPL-3.0
THE DASHBOARD
Dashboard

Monitors

Fictional monitors covering HTTP(S), Ping, Push, TCP and SSL. Monitors needing attention are listed first. Newest checks appear on the right; full-height red bars are confirmed failures, amber bars are failures not yet confirmed.
StatusMonitorLast checksLatency24h
Needs attention (1)
Down Checkout APIunexpected status codehttps://api.example.com/v2/checkoutCheck type: HTTP(S) 252 ms 97.14%
Other monitors (5)
Up Docshttps://docs.example.comCheck type: HTTP(S) 120 ms 100.00%
Warning Edge routeredge.example.netCheck type: Ping No latency data 99.93%
Up Nightly backupexpects a report every 1 dCheck type: Push No latency data 100.00%
Paused Postgres stagingdb.staging.example.com:5432Check type: TCP 12 ms 100.00%
Expiring soon WWW certificatecertificate expiringwww.example.com:443Check type: SSL 79 ms 100.00%

Needs attention (1)

Down

Checkout API

https://api.example.com/v2/checkout

Check type: HTTP(S)

status 502, expected 200-299

Latency
252 ms
24h uptime
97.14%

Other monitors (5)

Up

Docs

https://docs.example.com

Check type: HTTP(S)
Latency
120 ms
24h uptime
100.00%
Warning

Edge router

edge.example.net

Check type: Ping
Latency
No latency data
24h uptime
99.93%
Up

Nightly backup

expects a report every 1 d

Check type: Push
Latency
No latency data
24h uptime
100.00%
Paused

Postgres staging

db.staging.example.com:5432

Check type: TCP
Latency
12 ms
24h uptime
100.00%
Expiring soon

WWW certificate

www.example.com:443

Check type: SSL

certificate expires in 12 days (on 2026-11-01)

Latency
79 ms
24h uptime
100.00%
Illustrative dashboard · fictional data.Six monitors across five check types.

6 illustrative monitors shown

One binary

The dashboard is already inside.

SQLite included

No database server to look after.

API first

Everything you can click, you can script.

FROM YOUR HOMEPAGE TO YOUR NIGHTLY BACKUP

If it matters,
keep an eye on it.

Seven check types. One clear picture.
Watch your public services, internal infrastructure, and the jobs that run out of sight.

HTTP(S)

More than a status code.

Check response codes, latency, keywords and JSON fields. Send custom headers and request bodies to watch your APIs, too.

TCP

Is the port answering?

Verify that a connection completes. Keep an eye on databases and services without sending a protocol payload.

Ping

A simple sign of life.

Check host reachability with ICMP echo. Requires your host or container to permit ICMP sockets.

SSL

Catch expiry before it hurts.

Verify certificate validity, hostname and trust. Hear about expiry days ahead, without it counting as downtime.

DNS · Domain

Is the name still yours?

Compare A, AAAA, CNAME, MX or TXT records with the values you expect, and hear before a domain registration runs out.

Push

Watch the work behind the scenes.

Let cron jobs, backups and workers check in. A missed window becomes a failure, even without a public endpoint.

Monitoring a private network? Enable private targets explicitly in your instance configuration

LESS NOISE. MORE SIGNAL.

A blip isn’t
always an incident.

SubGlance confirms failures before sounding the alarm. Because the next alert should still mean something.

  • Consecutive failures confirm an incident
  • Flapping suppression keeps repeat noise down
  • Related-in-time alerts arrive grouped per channel
  • Reminders continue until someone mutes them
  • A host that loses its own connection or DNS resolver is not mistaken for an outage
Follow a failure through the engine
Checkout APIHTTP STATUS
NOT MUTED

TIMELINE

  1. First failure observed
  2. Confirmed: this is when a human was told
  3. —Not recovered

LAST ERROR

HTTP 502 Bad Gateway
Illustrative incident · fictional data.
Get the alert where you already are.
WebhookDiscordSlackTelegramEmailntfyGotifySMS
Your terminal
curl -H "Authorization: Bearer $SUBGLANCE_TOKEN" \
  http://localhost:8080/api/v1/monitors
GET /api/v1/monitorsPOST /api/v1/monitors/{id}/checkGET /api/v1/stream
REST API v1OpenAPI 3.1

YOUR WORKFLOW. YOUR WAY.

A proper API.
For all of it.

The dashboard uses the same API you do. Create monitors, check a fix, acknowledge an incident, or subscribe to live events. Bring your scripts.

Explore the API

SMALL STACK. FULL PICTURE.

Running in one command.

One process. One SQLite database. An interface you’ll want to leave open.

Docker quick start
docker run -d -p 127.0.0.1:8080:8080 -v subglance:/data ghcr.io/frankgraave/subglance:0.1.0-rc7

Run it locally, create your administrator, add your first monitor.
The first visitor creates the admin account. Keep the loopback binding for setup.

Get started

BUILT IN THE OPEN

Useful today.
Still taking shape.

SubGlance is in early development. v0.1.0-rc7 is a release candidate, not a stable release. Here’s the honest picture.

Read the releases

Ready to use

  • All seven monitor types
  • Live dashboard, incidents, monitors, notifications and settings screens
  • Maintenance windows and latency charts
  • Eight notification channels
  • Public status pages
  • YAML configuration files, and an importer for Uptime Kuma
  • REST API, tokens and three user roles
  • Scheduled backups and signed builds for five platforms

On the radar

  • Multi-region checks
  • SSO and on-call schedules
  • Postgres and a mobile app

All on the roadmap, none in the first release. Expect rough edges before v0.1.0.

Try it on your own machine.

Free and open source. One container on your own hardware.

Get started