Show an example state

savetheworld.comis working.needs a look.is broken.

savetheworld.com Checked 40 seconds ago WorkingNeeds a lookBroken

Everything is working.All checks passing · 3/3 pages 200 · p95 412 ms

Working, and one thing needs a look.1 advisory · next@14.2.3 · CVE-2025-29927 (CVSS 9.1)

People cannot pay.POST /api/checkout 5xx rate 64% (9/14 req, 15m)

412visitors this weekuniques, 7d
$193paid, 11 paymentsStripe net, 7d
$0paid since 14:020 succeeded, 9 failed
3saw an error5xx, 7d, 0 on pay routes
12saw an error, 9 at checkout5xx, 15m
99.98%pages loadedsynthetic uptime, 30d
4/4jobs on timecron + queue heartbeats
Needs a looknext 14.2.3

next 14.2.3 has a security fix (14.2.25). Your agent can update it.

next@14.2.3 → 14.2.25 · middleware authorization bypass · package-lock.json

Found 09:12 today by the daily package check · task T-11
BrokenPOST /api/checkout500 × 9
since 14:10, 12 min after deploy fd19bea
What brokeCheckout answered with an error for 9 visitors in the last 15 minutes. Since when14:10, twelve minutes after your deploy at 13:58. Who9 visitors, all trying to pay. No payment since 14:02. What to doPaste the line below into your coding agent, or roll back.
RoutePOST /api/checkout · 9 × 500 of 14 First seen14:10:42Z · deploy fd19bea (13:58) ExceptionKeyError: 'price_id' at billing/views.py:88 Nextnpx prodbat next → task T-12
Run `npx prodbat next` in this project, fix it and deploy, then run `npx prodbat done T-12`.

Where visitors came fromReferrers, 7d

Direct189
Google148
ChatGPT52
Claude23

Coming upScheduled

Certificate renewsTLS expiryin 61 days
Domain renewsRDAP expiryin 287 days
save-the-world02:00
Your Monday emailWeekly summaryMon 08:00
Prodbat All quiet. 2,016 checks since Monday, and nothing worth waking you for. Nothing is broken. One package needs an update before someone finds the hole. Checkout is down. I've emailed you, posted in Slack, and handed your agent the steps.

Monitoring for apps built with AI

Know within 5 minutes when your app breaks.

Prodbat watches your live app day and night: whether it loads, whether people can sign in and pay, and whether anything is crashing or out of date. When something breaks, you get an email in plain English and your coding agent gets the steps to fix it. Then Prodbat checks the live app again to confirm the fix worked.

Synthetic checks every 5 min (1 min from 3 regions on Pro). Server 5xx and browser errors with file:line, sign-in and checkout failures raised as Broken, cron and queue heartbeats, and a daily lockfile scan against OSV.dev and endoflife.date. Alerts go out by email and Slack. Your agent pulls each one as a task with npx prodbat next, and npx prodbat done re-checks from outside before the task closes.

Open source. Read every line on GitHub, or run it yourself for free.

Paste this into your coding agent

Install Prodbat on this project. Run npx prodbat init, do what it prints, deploy, then run npx prodbat verify.

Works in Claude Code, Cursor and Codex. Free for 30 days, and no card needed.
Every package your app uses is checked daily against public security databases:
  • OSV.dev
  • deps.dev
  • endoflife.date
How most AI-built apps are watched today

Right now, your customers are your monitoring.

  • Friday, 23:40A payment webhook fails silently, and you find out from a pile of customer emails on Monday.
  • Any afternoonYour agent says "Fixed!" and nothing checks the live app to see if that's true.
  • Since MarchA package your agent added has a known security hole, and nobody told you.
  • Day oneThe big monitoring tools expect you to build dashboards, write alert rules and read stack traces.

The fix usually takes minutes. Winning back the customers who found the bug before you did is the hard part. Prodbat watches the live app for you, tells you what broke in a sentence, and gives the fix to the agent that wrote the code.

Paste it into your agent. Monitoring is live when it finishes.
Eight checks, one page

The checks the big monitoring tools run, in plain English.

Each check shows its industry name and the alert Prodbat would send you about your app. Want the numbers? Switch to Engineer, bottom right.

Uptime monitoring

Is your site loading?

"Your sign-in page is not loading. The home page loads."

GET /, /login, /pricing every 5 min (every 1 min from 3 regions on Pro; regions must agree). TLS expiry at 14 d, domain at 30 d.

Error tracking

Is anything crashing?

"People cannot pay." One failed checkout or sign-in is enough to alert you.

Browser errors, failed fetches and server 5xx with file:line. A single failure on a pay or auth route opens a Broken incident.

Checkout and sign-in

Can people pay and get in?

ok POST /api/login
ok POST /api/signup
fail POST /api/checkout

Recognised by name, or listed in prodbat.json.

Routes matched by name (checkout, billing, login, signup) or declared under "flows" in prodbat.json.

Cron and job monitoring

Is the background work getting done?

late save-the-world
last ran Tue 02:00
queue heroes · 0 waiting

"The job that saves the world every night hasn't run since Tuesday."

Heartbeats via POST /api/ping/<job>?every=24h. Queue depth, oldest-job age and failures for Celery, RQ, BullMQ, Sidekiq, Laravel.

Security and update scanning

Anything out of date or unsafe?

node 20.11 → 24
next 14.2.3 CVE → 14.2.25
stripe 17.4.0 ok

"Node.js 20 no longer gets security fixes. Move to 24."

Lockfiles checked daily against OSV.dev, deps.dev and endoflife.date: CVEs, deprecations, end-of-life runtimes.

Log management

What was your app saying?

14:10:42 ERROR
price_id missing
from cart {"cart":991}

When something breaks, your agent gets the log lines from that moment along with the task.

POST /api/logs; search by text, level and time. Lines near an incident are attached to its task.

Web analytics

Who's visiting, and from where?

Counted without cookies. AI assistants are named, so you can see which ones recommend you.

No cookies; visitors are a salted hash that rotates daily. Referrers classified, with AI assistants named.

Revenue tracking

What are people paying for?

Pro, monthly
4 payments · $76

Read from Stripe, so it matches to the cent.

Stripe webhook events forwarded after the signature check; per product, with payment-to-source attribution on Pro.

Alerting

Will you actually hear about it?

Broken: people
cannot pay on
savetheworld.com

Email and Slack at once, a text on Pro when customers are affected, and again when it's working.

One email thread and one Slack thread per incident; SMS on Pro when customers are affected. Recovery posts in-thread.

All eight checks on every plan. Your agent picks what applies to your app.
Understand it in ten seconds

Alerts that tell you what happened and what to do next.

Every alert says what broke, since when, who is affected and what to do, always in that order. Then it gives you one line to paste into your agent.

One email per problem. Repeats join the same thread.
Broken:

Customers are affected right now. Email, Slack, text.

Needs a look:

Something will become a problem if nobody fixes it. One email, no texts, no 3 a.m. anything.

Working again:

Arrives in the same email thread, and the same Slack thread, once Prodbat has checked the fix from outside.

Get it fixed

Prodbat tells your agent what to fix, then checks the work.

Your coding agent can see your code but not the live app, which is where real problems show up. Prodbat turns what it sees into a to-do list your agent works through, most urgent first.

  1. 1A broken checkout or sign-in comes first, then anything else failing, then security updates and outdated software.
  2. 2Each task has numbered steps and the error details, so your agent starts from the evidence.
  3. 3When your agent says it's done, Prodbat loads your live app again and marks the task fixed only if it is.
Any agent that can run a command or connect over MCP.
Why not Sentry or Datadog?

What the big tools catch, without the setup.

Sentry and Datadog are excellent tools, and they expect someone to install SDKs, build dashboards and tune alerts. Prodbat sets itself up from one prompt and sends alerts anyone on the team can act on. Here's what changes.

ProdbatSentry, Datadog and friends
Alerts written as sentencesAlerts written as stack traces and status codes
Set up by your agent from one promptSet up by you: SDKs, dashboards and alert rules
A to-do list your agent can work throughGraphs and traces for a person to investigate
The live app is checked again after each fixYou decide whether the fix worked
One page covering eight checksA separate product for each kind of check
$19 a month, flatPriced by events, hosts or seats
Free for 30 days. Keep your other tools running alongside it.

Set up in one prompt. Your agent does the rest.

1

Paste one prompt

Whichever agent built your app sets up the monitoring too. It adds a line to your pages, a few lines to your server, and a prodbat.json file listing what's watched.

2

Sign in while it works

Your agent gives you a link as it starts. Sign in, and monitoring is live by the time your agent finishes.

3

Stop checking your app

Close the laptop. If something breaks, you'll hear within 5 minutes, and your agent will already have the steps to fix it.

Works with whatever your agent built. You don't need to know which of these your app uses; your agent does.

Coding agents

Claude Code, Cursor, Codex, Replit, and any agent that can run a command or connect over MCP.

Frameworks

Next.js, Express, Supabase Edge Functions, Cloudflare Workers, FastAPI, Django, Flask, Rails and Laravel in a few lines. Anything else with one web request.

Package managers

npm, pnpm, Yarn, pip, uv, Poetry, Bundler, Composer, Go and Cargo.

Background jobs

Celery, RQ, BullMQ, Sidekiq and Laravel queues built in. The rest with a web request.

Pricing

Less than one lost sale a month.

One subscription covers uptime, errors, background jobs, security updates and analytics, which would cost about $45 a month as separate tools. Prodbat is open source, so you can also run it on your own server for free.

Self-hosted

$0
The whole product, on your own server
  • One container and a Postgres database
  • Every feature, with no limits from us
  • You choose how long logs are kept
Read the install guideAll the power, all the responsibility.
Best for one app

Starter

$19 a month
Or $190 a year instead of $228, so two months are free. A web app and its phone app count as one project.
  • 100,000 page views a month, and counting never stops at the limit
  • All eight checks, every alert, every agent task
  • Alerts by email and in Slack
  • Uptime checked every 5 minutes
  • Logs kept 7 days, everything else kept a year
Free for 30 days, and no card needed.

Pro

$49 a month
Up to five projects. Or $490 a year, so two months are free.
  • 1 million page views a month
  • Which source each payment came from
  • Uptime checked every minute, from three regions
  • Alerts by email, in Slack, and by text message when customers are affected
  • Logs kept 30 days, everything else kept 3 years
Free for 30 days, and no card needed.
TodayMonitoring goes live with every check switched on.
Day 25We email you a summary of everything we checked, and that the trial ends in five days.
Day 30Pick a plan to keep going. We never had your card, so nothing is charged by surprise.

Plain answers

What is monitoring, and do I need it?

Monitoring means software is watching your app while you're not. Without it, you find out your checkout broke when a customer emails you, if they bother. If people use your app or pay you, you need it.

I'm not very technical. Can I still use this?

Yes, it was written for you. Your agent installs it, alerts are written in plain English, and every alert ends with a line you can paste into your agent to get it fixed.

Will it slow down or break my app?

The browser script is 3.7 KB and loads after your page does. Your server sends reports in the background. If Prodbat is ever unreachable, your app carries on as normal.

Is it safe to let Prodbat instruct my agent?

Prodbat's instructions are fixed text, filled in only with checked values like a page address or a version number. Anything written by someone else, like an error message or a log line, is marked as evidence, and your agent is told not to follow it.

What will my agent change?

A script line in your pages, a few lines in your server code, and a prodbat.json file that lists your checkout and sign-in pages. Ask your agent to walk you through it before you deploy.

Do I need a cookie banner?

Prodbat sets no cookies and counts visitors with a code that resets every day. Whether that exempts you depends on where your visitors are. We describe the method and leave the legal call to you.

Do you hold my Stripe key?

No. Your agent adds one line to the payment code you already have, which forwards each event after Stripe's signature is checked.

What do you see of my code?

Only the names and versions of the packages you use, and the errors and log lines your app chooses to send.

Can I leave?

Yes. It's open source, so you can move to your own server at any time. Removing it is a few lines your agent can take out.

Why a bat?

Bats work nights, hear trouble before they see it, and eat bugs. We didn't need a fourth reason.

Not ready to install? Check your site now.

We'll load your home page from outside, check its certificate and domain renewal, and look for obvious holes like exposed config files, missing security headers and outdated frameworks. Free, and no account needed.

Get early access to hosted Prodbat.

Hosted sign-ups open in batches. Leave your email and you'll get one message when your spot opens, and one short update a month until then.

Does your app take payments yet? (optional)
Apps that already take payments are let in first. Can't wait? Run it yourself today.

Open source. Free to run yourself, $19 a month when we run it.

Is checkout broken right now? Find out from Prodbat, not from a customer.

Paste this into your coding agent

Install Prodbat on this project. Run npx prodbat init, do what it prints, deploy, then run npx prodbat verify.

Free for 30 days, and no card needed. Live when your agent finishes.

Same alerts, fewer adjectives.

Explain it like