Lunolyte
A look at the product

See it before you pay for it

No form, no sales call, no sandbox that quietly differs from the real thing. These are the screens, drawn from the ones you would actually be using.

Examples, not live readings. The real thing is at status.lunolyte.com, public on the bad days too.

Your dashboard

Every site on one screen

What you see when you log in: how much of your plan you are using, whether anything is broken right now, and the last result from every check with the response time it came back in.

An incident

The whole story, with timestamps

An incident opens by itself at the first check that fails and closes by itself when the check passes again. In between, your team moves an outage through investigating and implementing a fix, and every step carries the time it happened. Nobody has to reconstruct it afterwards.

Your status page

The page your customers see

Public, honest, and kept current by the checks rather than by a person remembering to update it. Current state per service, the incident as it unfolds, and maintenance announced before it starts instead of after.

Lunolyte Live status of our services
Partial system degradation
Main websiteOperational
Customer PortalOperational
Status ApplicationOperational
Notification ApplicationDegraded
Response time above threshold on Notification Application Minor Detected
Detected 4 minutes ago
End to end

What happens between a URL and a customer who already knows

The whole loop, in the order it actually runs.

1

You add a URL

Your site, your shop, an API endpoint. No agent, no server access, no configuration weekend.

2

We keep checking it

Every minute on Pro and Agency, every five minutes on Starter. HTTP status and the certificate on every plan; response time, your domain name and the text on the page on Pro and Agency.

3

Something breaks

An incident opens by itself at the first check that fails, with the time it started and what the check ran into. Your status page says so without anyone touching it.

4

You hear about it

Email on every plan, Slack, Teams or a webhook on Pro and Agency. The alert goes out with the incident, without waiting for a second check to agree; a slowdown tells you once rather than at every check.

5

You work the problem

Move the incident to investigating, then to implementing a fix. Your customers watch that happen instead of guessing.

6

It recovers

The check passes, the incident closes itself, and the timeline keeps the whole thing on record for the next time somebody asks what happened.

The status page in those screens is ours

We monitor Lunolyte with Lunolyte, and the page is public on the bad days too. Go and look before you decide anything.