Checked every 15 minutes
Each uptime check records the status and response time. You get uptime over 24 hours, 7 days, 30 days, 90 days, and 12 months, every outage in the last 30 days, and response times for the last 24 hours.
Hear about an outage before your customers do.
Add the address of any site or health page. LopeBase checks it every 15 minutes, keeps a year of uptime history, and tells you the moment it stops answering. Give customers a public status page, free, and tell them what happened when it is over.
No key or account needed for a site check. Free for one product.
Uptime and incidents
Is it up? For every product, already answered.
One page for every site you run, next to the revenue and traffic that depend on it.
Every service, not just the home page
A home page can load while checkout is broken. List the database, queue, workers, or second API your app needs in the LopeBase Adapter, and one check watches each of them. One service down marks the product degraded and alerts you.
Alerts where you are
A site that stops answering alerts on the first failed check, by email or browser push, the way each person chose.
Errors beside uptime
Bring in Sentry, Bugsnag, Honeybadger, or Rollbar, or the Better Stack monitors you already run.
An incident review and a note for customers
One button reads 30 days of checks and each outage, plus your top Sentry errors, then says what went wrong and what to fix first. After downtime it drafts a calm status note. Read it, then post it to your status page in one click or copy it anywhere.
A public status page, free
Turn one on for any product with a single switch. Customers see live status, 90 days of history, a year of uptime, and the notes you post. Pick which parts show, follow it by RSS, and put a live status badge on your site. Paid plans can add their logo and colors and leave off the LopeBase footer.
How it works
The first check runs as soon as you add a site.
- 01
Add an address. Your home page or a health endpoint. No key or account needed.
- 02
Pick how to hear about it. Email, browser push, or both, per person.
- 03
See it with everything else. Outages show on Overview and in the weekly digest.
- 04
Close the loop. Run the incident review and post its note to your public status page.
How often are sites checked?
Every 15 minutes. Each check records whether the site answered and how long it took.
Do I need an account with another monitoring tool?
No. Uptime checks are built in and need only an address. If you already use Better Stack, you can connect it and see those monitors too.
Can one product have several things checked?
Yes. Point the product's check at the adapter's health address and declare each service there: the database, a queue, workers, payments, or another host you run. Each check uses your app's own credentials, so it shows your integration works, and a service you mark non-critical shows as degraded instead of down. The Uptime page and alerts then name the service that failed.
How do I know what is worth watching?
Run npx lopebase in the product's folder. It reads dependency names and lists the site, databases, queues, and email it finds, and your coding agent confirms the list against the code before adding anything.
How do alerts reach me?
By email, by browser push, or both. Each person picks what they hear about, and only for the products they can see.
Does LopeBase publish a status page?
Yes, if you want one. Turn it on from the Uptime page and you get a public link with live status, 90 days of history, a year of uptime, and your own notes. It shows your site's icon and is free on every plan. Paid plans can add their logo, pick colors and light or dark, and leave off the LopeBase footer.
Can customers follow updates?
Yes. Every status page has an RSS feed of your notes, and a badge you can put on your site or README that shows live status and links to the page. Your own team can also get each new note by email or browser push from their alert settings.
How long is uptime history kept?
Every single check for 35 days, and a total for each day for a year, so uptime over 90 days and 12 months stays on the page.
What else do you want to get done?
Every goal runs in the same console, on the same plan.
01 / Search
Get found on Google
See the searches you almost win and the pages to fix first, from Search Console and Bing.
Rank trackingSite auditOpportunity map See how it works 02 / ContentPublish without the weekly grind
Plan articles on a calendar. They are drafted in your voice, checked, and published on schedule.
CalendarYour voiceLink checks See how it works 03 / RevenueKnow your MRR and runway
MRR, past due, and cancellations for every Stripe and Polar account, next to cash in the bank.
MRRPast dueRunway See how it works 04 / GrowthTurn visitors into signups
Traffic from every analytics tool side by side, and a review of where people drop off.
TrafficSignupsConversion review See how it works 05 / AgentsLet your coding agent set it up
Run one command and your agent adds products and connects sources over MCP.
npx lopebaseMCP serverRead-only See how it worksNot sure where to start? Connect one tool and Overview shows what needs you first.
Start freeSleep through the night, and know if you should not.
EmDashFree for one product. No card.