For founders with side projects

You moved on. I kept watching.

Paste one URL. I’ll show you its page response and domain signals, then watch it daily and after detected deploys within your plan's daily allowance; for a check incident, I write only when that check breaks twice.

Show me one URL.

Show me one URL. I'll check its page response and domain signals.

First, I check the page response and domain signals. Checking a customer path in a browser comes after sign-up.

First look

Useful evidence before you connect.

01Page response

Does the address answer, and what came back?

02Certificate and domain

A separate lookup for the signals behind the address.

03Paths worth watching

I read your page and name up to three paths worth keeping an eye on.

Watch recorder

Replay the path that matters.

Record a signup, checkout, or another important path once. I replay it daily and after detected deploys within your plan's daily allowance, and include the evidence when something breaks.

  1. Record once
  2. Daily and after detected deploys
  3. Write with evidence

See the page-response result before sign-up · no install · read-only

When a project breaks, it comes first.

All your projects stay in one list. If the same check breaks twice, I move that project to the top and show you what needs attention.

Illustrative replay · example projects

  • ✕ brokenFit Meal Planfitmealplan.app4 checks · 1 brokensignupjust now2 h ago
  • stillReading Listreadinglist.club3 checks · all stillNone9 min agoyesterday
  • healedTiny Invoicetinyinvoice.co2 checks · all stillcheckout moved9 min ago3 h ago
  • unknownOld Side Projectoldsideproject.net1 check · not verifiedNone6 days agonever

stillEverything I checked worked.

brokenThe same check broke twice, so it needs you.

healedThe page changed; I found the same thing in its new place.

unknownI couldn’t verify it, so I won’t call it fine.

Watch recorder

Show me the path once. I'll replay it daily and after detected deploys.

Open your project in Watch recorder and show me the route that matters. I turn the clicks you keep into a reusable check, replay it daily and after detected deploys within your plan's daily allowance, and bring back the evidence if that check breaks twice.

  1. Walk it once

    Click through the route you want me to repeat. Each click becomes a step while you go.

  2. Shape the check

    Remove or reorder steps, add conditions, then try the whole path before you save it.

  3. I take it from here

    After detected deploys, and on the daily schedule, I run it within your plan's daily allowance. Only the second consecutive failure of that check becomes an alert.

I record the path you show me, not your visitors. The recorder and its checks stay outside your app.

Recording complete

You showed me the path once.

Pricing Growing Checkout

It took 8 seconds to capture. From now on, I can replay these 3 steps daily and after detected deploys within your plan's daily allowance — saving you one manual walkthrough every run.

Captured
3 steps
Your time
8 seconds
Future runs
Hands-free

Illustrative walkthrough · example project

After you connect

You build. I take the late shift.

Add a project once. I find a useful starting point, keep checking daily and after detected deploys within your plan's daily allowance, and open a check incident only when that check breaks twice.

  1. I find a useful place to start

    I open the homepage and look for paths worth checking. I try every suggestion once and keep only the ones that work. You can review what I kept or record your own path.

  2. I look after deploys and every day

    Once deploys are connected, I run your checks daily and after detected deploys within your plan's daily allowance. A daily run covers the days when you ship nothing.

  3. I check twice before I write

    One bad check run stays quiet. I try the same path again 10 minutes later. Only when that check breaks twice do I open an incident and write, with the evidence I captured.

Read how deploys start runs and why the first bad run stays quiet.

Clear boundaries

What I won't do

Useful watching needs clear boundaries. These are mine.

I won't ask for access to your systems
I read your application through a browser, from the outside. You never give me database access or put an agent on your servers. If I disappeared tonight, your application would keep working.
I won't write after one failed check run
One failed check run never reaches you. I retry that check first. I write about a check incident only when the same check breaks twice in a row; if the run broke on my side, it never counts against you.
I won't keep recordings past 30 days
I delete every recording after 30 days, on every plan. It may contain names or email addresses from the pages you showed me, so longer history keeps what happened — not the video of it.
I won't let AI decide what's broken
I use AI only to propose checks and, as a last resort, find an element that moved. It never decides whether your application is broken, creates a finding, or reads visitor errors. What worked or broke is always decided by the run, not by a model.

The full infrastructure and data route is documented on Security.

Pricing

A fair price for quieter nights.

Seven days on me. Then from $12 a month.No card. Every trial starts with Small and covers up to 3 projects. Pick a paid plan only when you decide to pay.

Deploy checks share one daily allowance

Shared across your whole account, the seven-day trial gets 20 deploy-triggered check runs per UTC day; the allowance for a paid plan is shown on its card. One check started by a detected deploy uses one run.

If five checks are eligible and only three runs remain, that deploy starts none of those five. Your usual daily checks continue as planned.

How deploy checks are counted
Pay for 10 months, get 12.Showing monthly prices.

Prices exclude VAT and similar taxes.

  • Small

    $12/month

    or $120 a year

    • Projects3
    • Active checks per project3
    • Alert destinations, any kind3
    • Deploy-triggered check runs per day20
    • Run history30 days
    Start seven-day trial

    Choose this plan when you decide to pay.

  • Growing

    $24/month

    or $240 a year

    • Projects10
    • Active checks per project5
    • Alert destinations, any kind5
    • Deploy-triggered check runs per day20
    • Run history90 days
    Start seven-day trial

    Choose this plan when you decide to pay.

  • Portfolio

    $59/month

    or $590 a year

    • Projects30
    • Active checks per project7
    • Alert destinations, any kind10
    • Deploy-triggered check runs per day100
    • Run history12 months
    Start seven-day trial

    Choose this plan when you decide to pay.

Included on every plan

The plan changes capacity and history, not the way I look after your projects.

  • Daily checks and checks after detected deploys, within your plan's daily allowance
  • Run recordings kept for 30 days
  • Certificate and domain checks
  • Findings on day one
  • Deploy timeline
  • Watch recorder
  • Self-healing checks
  • Visitor errors with an optional snippet
  • No surprise usage charges
Each destination can beEmailSlackDiscordYour own webhook

Refunds and billing details are on the pricing page.

Questions worth asking

What happens after the first look?

Do I have to install anything?

No. Start with a URL. The first look and outside checks need no install. An optional deploy signal helps me notice a deploy sooner. Visitor errors are separate and need an optional one-line snippet.

Will one bad run wake me up?

No. For a concrete check, I doubt the first failure and try the same path again ten minutes later. I open an incident and write only if that check fails twice in a row.

What can I check before paying?

Paste one URL on this page and see the first result. If you ask me to keep watching, you get seven days without entering a card.

Do you need my database or hosting login?

No. I never need a database key to watch a project. Checks run outside your systems and only use sign-in details when a path genuinely requires them.

How long do you keep screenshots and video?

Thirty days, and no longer. They can contain names or email addresses from your app, so I would rather not keep them indefinitely.

One URL. One useful answer.

You don't have to keep staring at it.

The same field you scrolled past. It costs you nothing to check the page response and domain signals.

Try the first look

Show me one URL. I'll check its page response and domain signals.

First, I check the page response and domain signals. Checking a customer path in a browser comes after sign-up.

The check starts now. The seven-day trial starts only when you ask me to keep watching.