Monitor what standard checks can’t.
Write your own checks for content, APIs and business-critical flows, and run them on Upzilla infrastructure. Keep them private or share them with everyone.
Illustrative sketch — the final API may differ.
export default async function check({ http, assert }) {
const res = await http.get('/api/cart');
assert.equal(res.status, 200);
assert.ok(res.json.items.length > 0,
'Cart should not be empty after add-to-cart');
return { items: res.json.items.length };
}Three kinds of checks that need your logic
Content checks
Is the price visible? Does the page still include the legal notice? Catch silent content regressions.
API checks
Validate response shape, auth flows and webhooks — not just that the endpoint returns 200.
Business-flow checks
Add to cart, sign in, run a quote. Test the steps that make money, from outside.
From idea to running check in four steps
Get API access
Request a key and read the check specification.
Write your check
Describe what to test in a small script.
Keep it or share it
Run it privately, or publish it to the public catalog.
Pay per request
Usage-based pricing: you pay for the checks that actually run.
Your checks, your choice
Private checks
Visible only to you and your team. Ideal for internal APIs, staging flows and anything confidential.
Public catalog
Publish a check for the whole community to use, and let other teams monitor the same thing with one click.
Preview the catalog →Get early access
Leave your email and we will let you know when custom checks open up. One message when it’s ready — no spam.
From the blog
What to monitor beyond uptime
Five business-level signals that tell you more than a green status page: content, flows, APIs and freshness.
Read →MonitoringWhy HTTP 200 is not enough
A page can return 200 OK and still be broken. Here is what standard uptime checks miss, and how to cover it.
Read →