LiveUptime, anomalies and visitor reports

Is it down, or is it open?

ItsOpen watches every project you run from the outside and from your visitors' own browsers, so you know something's wrong, and why, before the first support email.

  • Checks as often as every 30 seconds
  • No cookies on your visitors
  • Free plan, no card
StorefrontChecked 4s ago
99.98%Uptime · 60 days200 OK · 212 msEvery 30 seconds

How it decides

Four signals. One honest status.

A site can answer every check and still be broken for the people using it. ItsOpen listens to all four, each against that site's own normal, and tells you which one moved.

  • Checks

    Does it answer, from outside?

    Opens an incident: Two failed checks in a row

  • Speed

    Is it slower than it usually is?

    Opens an incident: Three checks far above its own baseline

  • Browser errors

    Are visitors' pages breaking?

    Opens an incident: Errors far above its usual rate per page view

  • Visitor reports

    Are people telling you?

    Opens an incident: More people reporting than usual in 15 minutes

OpenNothing is wrong
DegradedSlow, erroring, or being reported
DownAn outage is open

Product

Everything that tells you a site is broken

Outside checks, your own baseline, your visitors' browsers and their reports, in one place for every project.

Webhooks · visitor reportsIncident opened

About one report an hour is this site's normal. Nine people in fifteen minutes has a one-in-a-billion chance of being noise.

Anomaly detection

Down isn't the only way to be broken

Most bad days don't start with a 500. They start slow, or with a broken button only your visitors see. ItsOpen notices those too, without a single threshold to tune.

  • Slowdowns are judged against each site's own history, not one threshold for all
  • Reports count people, not clicks, so one frustrated visitor isn't an outage
  • Error spikes are weighed against traffic, so a busy afternoon isn't an incident
  • Every incident closes itself once the signal is quiet again
How detection works
Between checks, at the fastest
30s
Failures in a row confirm an outage
2
Cookies the browser script sets
0
Days of uptime on every status page
90

How it works

Watching in two minutes

Outside checks tell you whether a site answers. Your visitors tell you whether it works.

  1. 1

    Add a project and its URLs

    Group the site, API and docs of each product you run. We start checking each URL within seconds, and learn how fast it usually is.

  2. 2

    Paste one script tag

    Your visitors' browsers report errors and failed requests anonymously, and get a button to tell you when something's wrong. Turn on replay to watch their sessions.

  3. 3

    Hear about it first

    An outage, a slowdown, a wave of errors or reports opens an incident and alerts you by email, Slack, Discord or the dashboard, and closes it when it's fixed.

index.html
<!-- before </body> -->
<script
  src="https://api.itsopen.dev/v1/collect/script.js"
  data-key="pk_your_site_key"
  async></script>

// Open the report form from your own link
ItsOpen.report("broken")
Receiving page views from your site

Works with gyve

Built with an agent? Watched from day one

gyve, also from Arcaro Labs, keeps your coding agent on a designed path from an empty repository to production. Its last step sets up ItsOpen, so the agent that shipped the product is the first to know when it breaks.

Start building on gyveThe ItsOpen kit is in its catalog, ready for your agent.
gyve · saas-starter path8 of 9 done
  1. ✓Clone and name the product
  2. ✓Make your own secrets
  3. ✓Run the stack
  4. ✓Add your first domain model
  5. ✓Build its pages
  6. ✓Turn on billing
  7. ✓Prove it in a browser
  8. ✓Deploy
  9. 9Watch it in productionItsOpen

FAQ

Questions people ask before they sign up

Anything else, email us and a person will answer.

What does the browser script collect?

Counts of page views, load times, uncaught errors and the page's own failed requests, plus the path of the page. It sets no cookies and sends no IP address or visitor ID; error messages are stripped of email addresses before they're stored.

How does session replay work?

Turn it on for a site and the same script records visits with ItsOpen's own recorder; each report links to the moment in that visitor's session. What people type, passwords and email addresses are recorded as dots in their browser, you can mask or leave out any element, recordings are kept 30 days, and visitors with Do Not Track or Global Privacy Control on are never recorded. Already on OpenReplay? Choose it instead.

Why did I get a slow-response incident when nothing is down?

Each monitor learns how fast its site normally answers. When three checks in a row are far slower than that (at least twice as slow and a quarter second more), it opens a latency incident, and it resolves after three normal checks.

Can AI agents read my monitoring?

Yes. Make a scoped API key, or connect an app through Sign in with ItsOpen. Agents get one summary call that says what needs attention and why, and the key stops working if the person who made it loses access.

What happens when my trial ends?

Checks pause and the dashboard asks you to choose a plan. Nothing is deleted: subscribe and everything picks up where it stopped.

Get started

Keep the sign lit. Hear about it first when it flickers.

Add your first project in two minutes. Free for as long as you like, no card needed.