Uptime checks and status pages you host yourself
Lantern watches your websites, APIs and servers from a machine you control and tells you when something breaks. One binary, one configuration file, no account and no data leaving your network.
Open source, MIT licence
What Lantern checks and how it tells you
Every check runs on your own server at the interval you choose. Results stay in a local database.
HTTP and HTTPS
Status codes, response times, redirects and the text a page must contain.
Certificates
Warns 21 days before a TLS certificate expires, and again on the last seven days.
TCP ports
Databases, mail servers and anything else that listens on a port.
E-mail and webhooks
Alerts by SMTP or as JSON to any URL, with quiet hours and repeat limits.
Status page
A static, accessible status page that Lantern rewrites after every check.
REST API
Read results and pause checks from scripts, with a token per client.
We replaced a hosted monitor with Lantern on a ten euro server. It found an expiring certificate in the first week, and our data never left the building.
Jorinde Maas, operations lead at a fictional city utility
From download to first alert in four steps
01
Install
Download one binary for Linux, macOS or Windows, or run the container image.
02
Configure
Describe your checks in lantern.yml: what to call, how often and what counts as healthy.
03
Start
Run lantern serve. The first round of checks starts at once, the status page follows.
04
Get notified
Add an e-mail address or webhook, and Lantern tells you when a check fails and when it recovers.
Support
Stuck? Ask the people who build Lantern.
Questions about setup, bug reports and ideas reach the maintainers directly. We answer within two working days.
- Write to support@example.org
- Security reports to security@example.org
- Release notes in the changelog of this documentation