Down on Friday, found on Monday
A shop that stops answering on a Friday evening loses the orders of the weekend, and the first sign is often a mail from a customer who gave up.
Caught by the HTTP status checkMonitoring you do not have to run. No agent, no server access, nothing to host. Lunolyte checks your websites and API endpoints around the clock, alerts you at the first check that fails, and keeps a public status page your customers can trust.
Most problems do not take a site down with a bang. They sit there until a customer, a browser or a search engine finds them first. These are the ones Lunolyte is built to catch, and the check that catches each.
A shop that stops answering on a Friday evening loses the orders of the weekend, and the first sign is often a mail from a customer who gave up.
Caught by the HTTP status checkA broken database often shows its error on a page that still answers 200 OK. A check that only asks whether the site is up says yes.
Caught by keyword monitoringBrowsers put a full-page security warning in front of a site whose certificate has expired. It happens when automatic renewal quietly stops working, and nobody notices until visitors do.
Caught by the SSL certificate checkA site rarely goes from fine to gone. It slows down first, and visitors give up on a slow page long before anyone calls it an outage.
Caught by the response time checkAfter a move to new hosting, a domain that ran out or a change nobody remembers making, your name can stop resolving or start pointing somewhere else.
Caught by the DNS checkA site that keeps answering with server errors is visited less often by Google, and pages that keep failing are dropped from its index in the end. Google says so itself.
Caught by the HTTP status checkThe screens you work in: screenshots of the product itself, not pictures made up for a brochure.
The real screens, with test clients in them. Our own status page is at status.lunolyte.com, public on the bad days too.
What you see when you log in: how much of your plan you are using, what needs your attention right now, and the last result from every check with the response time it came back in.
An incident opens by itself at the first check that fails, with what the check ran into, 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 lands on the status page with the time it happened. Nobody has to reconstruct it afterwards.
No agent to install, no server access, no configuration weekend.
Paste a URL. Your site, your shop, an API endpoint. That is the whole setup.
Around the clock: every minute or every five minutes, depending on your plan.
An alert at the first check that fails, by email or in the tools your team already has open.
Your status page updates itself, so nobody has to ask whether it is just them.
Not just up or down. Checks that read the answer, incident management, and alerts that reach your team where it already works.
Confirms the page returns the code it should. A server answering with a 500 is down as far as your customers are concerned. It can also look for a text you chose, because an error page that answers 200 is not up either.
Catches a site slowing down long before it goes fully down, with trends you can read at a glance.
A warning 30, 14, 7 and 1 days before a certificate lapses, and word when your domain name stops resolving or starts pointing somewhere new.
Email, Slack, Microsoft Teams or a plain webhook, all of them at once if you like.
A page with the current state of every service, the incident as it unfolds, and maintenance you announce in advance. Open to your customers, or private so that only the people you give access can open it.
A status page for every client under one account, each with the client's own name and logo, and logins for your own team. More for agencies.
A business that wants to know about its own site, and an agency that wants every client to have a status page. The checks are the same. What differs is how many sites, and whose name is on the page.
One site or a handful, a status page your customers can open, and an email when something breaks. Nothing technical to set up: you paste the address and that is it.
See the plansEvery client site under one account, a status page per client with their name and logo on it, and a monthly report, ready to send on, for every client you want one for. One pool of 250 services that you divide however you like.
How it works for agenciesWant the technical detail first? How a check works says where we check from, what opens an incident, and what each check tells you.
Every monitoring tool claims reliable checks and fast alerts. These are the things we put in writing, and each of them you can verify for yourself. Where a check comes from, how fast you hear and what it tells you is written down as well.
Lunolyte is a company in the Netherlands. The platform runs on our own servers in Nuremberg, Germany, and backups are stored encrypted at a second location in the EU. Card details go to Stripe and never reach us. Some of the providers we rely on belong to groups outside the EU, among them Cloudflare, which carries the traffic to the platform, and Stripe, both based in the United States. Every customer gets a data processing agreement. Every provider, where it processes data, and on what basis.
A status page for every client, on the client's own domain and with their logo, a monthly report as a PDF with their name on it, ready to send on, and one pool of services to divide over all of them, with up to 250 client pages and logins for 20 people of your own team. How it works for agencies.
Our own status page is public, including on the days it is not green. Where we check from, what a check tells you and where it stops is on this site, not in small print. And Lunolyte only watches and tells you: it never logs into your server, and never claims to have fixed something it did not.
No agent to install and no server access to hand over: you paste a URL. You pay by the month and can stop whenever you like, and the owner of an account can download everything in it, as JSON and CSV, at any time.
Per month, excluding VAT, or two months free when billed yearly. Every plan includes uptime and certificate checks, alerts, incident management and a status page.
Your first 14 days are free. Cancel before they end and nothing is charged.