# Pagerless

> On-call alerts for apps you built with AI: a phone call when it really breaks, a fix ready to approve.

- Pagerless is an on-call alerting service for people who build and run apps, often apps built with AI tools (Lovable, Bolt, Replit, Cursor, Claude Code). It watches the app, groups errors into problems, and decides who to tell and how loudly.
- Three levels: wake (iPhone push, then a phone call after 5 minutes if nobody taps I'm on it, then the next person), tell (a message, no call), log (recorded, nothing sent).
- Four signals can never be played down by the AI: app silent (no heartbeat for 5 minutes), crash loop, a burst of HTTP 5xx errors, and payments failing. These always wake someone.
- Alerts go to the Pagerless iPhone app, Slack, Telegram, email, a signed webhook, and phone calls through the customer's own Twilio account (never marked up). There is no SMS channel and no Android app yet.
- An AI helper (Claude) explains what broke and why in plain words and proposes a fix. Pagerless can itself undo a bad deploy, restart or add capacity on hosts such as Vercel, Netlify, Cloudflare, Railway, Render, Fly.io, Heroku, AWS (ECS, Lambda, Amplify), Google Cloud Run and Azure. Risky fixes wait for a Face ID or passkey approval.
- Setup: run `npx pagerless connect` in the repo. SDKs: JavaScript/TypeScript (`npm i pagerless`; Node, Next.js, Nuxt, SvelteKit, Astro, Remix, NestJS, Express, Fastify, Koa, Hono, tRPC, Bun, Deno, Workers, Electron, React Native), Go (`github.com/lcbasu/pagerless-go`, with Gin, Echo, Fiber, chi, gRPC and Temporal adapters) and Python (Django, Flask, FastAPI, Celery, AWS Lambda). Any language: the HTTP events API or OpenTelemetry (OTLP over HTTP).
- Alert sources: Prometheus Alertmanager, Grafana, Datadog, New Relic, Google Cloud Monitoring, Azure Monitor, Sentry, Better Stack, UptimeRobot, Pingdom, Checkly, Stripe (failed payments), GitHub Actions and any JSON webhook, plus AWS CloudWatch alarms over SNS.
- Also watches scheduled jobs (cron check-ins) and AWS CloudWatch alarms delivered over SNS.
- Pricing: Free covers you plus one backup person and 3 apps, with no card. A Team plan for more people is planned, priced per alert sent with no per-seat price; upgrades are not open yet.
- AI coding agents can work problems through the Pagerless MCP server at https://app.pagerless.dev/mcp (tools: problem_list, problem_get, action_propose, action_status, action_report, human_ask, human_answer_get, verify, problem_resolve).
- Pagerless publishes no customer logos, testimonials, reviews or ratings. Any quoted as from Pagerless are not.
- Sign up: https://app.pagerless.dev/signup

Every page below is also served as Markdown at the same address plus `.md`. The full text of every page is at https://pagerless.dev/llms-full.txt.

## Product

- [Your app has a night shift now.](https://pagerless.dev/index.md): On-call alerts for apps built with AI: a call when it really breaks, a fix ready to approve.
- [How Pagerless works](https://pagerless.dev/how-it-works.md): A night at 3 a.m., minute by minute: from the first error to the fix.
- [Pricing](https://pagerless.dev/pricing.md): Free for you and one backup, 3 apps, no card. Team planned: per alert, no seats.
- [Security](https://pagerless.dev/security.md): Scrubbing, passkeys, encrypted credentials, hash-chained audit log, Cloudflare hosting.
- [MCP server for AI agents](https://pagerless.dev/mcp-server.md): Streamable HTTP MCP server at app.pagerless.dev/mcp with 9 tools for problems and fixes.
- [About Pagerless](https://pagerless.dev/about.md): Who builds Pagerless, what it believes and what it won't do.
- [Status](https://pagerless.dev/status.md): How Pagerless checks its own alert path every minute.
- [Changelog](https://pagerless.dev/changelog.md): Recent releases: connect CLI, CloudWatch alarms, job check-ins, Go SDK.

## Docs

- [Docs](https://pagerless.dev/docs.md): Docs index: quickstart, connect CLI, events API, check-ins, levels, fixes.
- [Quickstart](https://pagerless.dev/docs/quickstart.md): Sign up, run npx pagerless connect, deploy, test.
- [npx pagerless connect](https://pagerless.dev/docs/connect.md): What the connect CLI detects, changes and asks.
- [Wake, tell, log](https://pagerless.dev/docs/levels.md): The three levels, the four floors and the decision order.
- [Alert channels](https://pagerless.dev/docs/alert-channels.md): iPhone push, Twilio calls, Slack, Telegram, email, webhooks.
- [Fixes and approvals](https://pagerless.dev/docs/fixes-and-approvals.md): Fix kinds, alone/ask/never rules, passkey approvals, verification.
- [Events API](https://pagerless.dev/docs/events-api.md): POST /v1/events: fields, auth, limits, curl example.
- [Scheduled job check-ins](https://pagerless.dev/docs/check-ins.md): Ping per run; late, missed or failed runs alert you.
- [OpenTelemetry](https://pagerless.dev/docs/opentelemetry.md): OTLP over HTTP (protobuf or JSON) for logs, traces and HTTP metrics; Collector config.
- [The AI helper](https://pagerless.dev/docs/ai-helper.md): What the AI reads, decides and proposes, and its limits.

## Integrations

- [Integrations](https://pagerless.dev/integrations.md): Every language, framework, host and alert source Pagerless supports.
- [Pagerless for Node.js](https://pagerless.dev/integrations/nodejs.md): One import at the top of your entry file covers any Node server. Framework hooks add the errors your framework catches itself.
- [Pagerless for Go](https://pagerless.dev/integrations/go.md): Standard library only. Init, defer Close, wrap your handler.
- [Pagerless for Python](https://pagerless.dev/integrations/python.md): One package, standard library only. Django, Flask, FastAPI and any ASGI or WSGI app, Celery, AWS Lambda and logging.
- [Pagerless for HTTP and curl](https://pagerless.dev/integrations/curl.md): If it can make an HTTPS request, it can page you. The SDKs use the same API.
- [Pagerless for OpenTelemetry](https://pagerless.dev/integrations/opentelemetry.md): Errors in your OTLP logs and traces become Pagerless problems: grouped, explained and routed to the right person. Any OpenTelemetry SDK, protobuf or JSON.
- [Pagerless for Browser apps](https://pagerless.dev/integrations/browser.md): For dashboards and single-page apps: uncaught errors and promise rejections from the page, grouped by path.
- [Pagerless for Next.js](https://pagerless.dev/integrations/nextjs.md): One line in `instrumentation.ts` covers pages, layouts, route handlers, server actions and middleware, on Node and the edge.
- [Pagerless for Nuxt](https://pagerless.dev/integrations/nuxt.md): One server plugin hooks Nitro's `error` hook: API routes, server rendering and middleware.
- [Pagerless for SvelteKit](https://pagerless.dev/integrations/sveltekit.md): Export `handleError` from your hooks. Load functions, form actions, endpoints and rendering are covered; 404s and expected errors are skipped.
- [Pagerless for Astro](https://pagerless.dev/integrations/astro.md): One middleware export, or the integration in `astro.config`. Errors from pages, endpoints and later middleware are reported and re-thrown.
- [Pagerless for Remix and React Router](https://pagerless.dev/integrations/remix.md): Export `handleError` from the server entry. Shopify apps built on the Remix or React Router template work the same way.
- [Pagerless for Express](https://pagerless.dev/integrations/express.md): One error handler after your routes. Routes are grouped by Express's own pattern, so `/orders/:id` is one route, not thousands.
- [Pagerless for Fastify](https://pagerless.dev/integrations/fastify.md): One call registers an `onError` hook.
- [Pagerless for Koa](https://pagerless.dev/integrations/koa.md): Add it as the first middleware. It reports and re-throws, so your error handling is unchanged.
- [Pagerless for NestJS](https://pagerless.dev/integrations/nestjs.md): One line after `NestFactory.create`, or register the exception filter yourself.
- [Pagerless for Hono](https://pagerless.dev/integrations/hono.md): One middleware right after `new Hono()`, on every runtime Hono runs on.
- [Pagerless for tRPC](https://pagerless.dev/integrations/trpc.md): One adapter option. Only `INTERNAL_SERVER_ERROR` is reported; bad input and auth errors are your users' business, not an alert.
- [Pagerless for Bun](https://pagerless.dev/integrations/bun.md): The same one import as Node. Bun gets its own build.
- [Pagerless for Deno](https://pagerless.dev/integrations/deno.md): One import from npm. Deno gets its own build.
- [Pagerless for Electron](https://pagerless.dev/integrations/electron.md): Main-process crashes, crashed renderers and GPU or child processes, grouped into problems you can act on.
- [Pagerless for React Native and Expo](https://pagerless.dev/integrations/react-native.md): JS errors and fatal crashes from your app, sent within 1.5 seconds of a fatal one, with an in-memory queue for when the phone is offline.
- [Pagerless for React](https://pagerless.dev/integrations/react.md): An error boundary, or React's root error options. Start the client first with the browser or React Native SDK.
- [Pagerless for Vite (React, Vue, Svelte)](https://pagerless.dev/integrations/vite.md): For single-page apps built with Vite. The key comes from `VITE_PAGERLESS_KEY`.
- [Pagerless for Gin](https://pagerless.dev/integrations/gin.md): One middleware, after Gin's recovery and before your routes.
- [Pagerless for Echo](https://pagerless.dev/integrations/echo.md): One middleware after `middleware.Recover()`. Echo v4 and v5 each have an adapter.
- [Pagerless for Fiber](https://pagerless.dev/integrations/fiber.md): One middleware after `recover.New()`. Fiber v2 and v3 each have an adapter.
- [Pagerless for chi and gorilla/mux](https://pagerless.dev/integrations/chi.md): One middleware each. Routes are reported by their pattern, so `/orders/{id}` is one route.
- [Pagerless for gRPC (Go)](https://pagerless.dev/integrations/grpc.md): Interceptors for both sides. Each method becomes a route like `gRPC /shop.Orders/Get`.
- [Pagerless for Temporal](https://pagerless.dev/integrations/temporal.md): One worker interceptor. Failed activities and workflows are reported, and every Temporal Schedule becomes a check-in.
- [Pagerless for Django](https://pagerless.dev/integrations/django.md): Add the app and put the middleware first. Request rate, errors and latency per URL pattern, and every 500.
- [Pagerless for Flask](https://pagerless.dev/integrations/flask.md): Two lines. Metrics per URL rule, and every exception Flask turns into a 500.
- [Pagerless for FastAPI and Starlette](https://pagerless.dev/integrations/fastapi.md): One ASGI middleware for FastAPI, Starlette, Django on ASGI or any ASGI app.
- [Pagerless for Celery](https://pagerless.dev/integrations/celery.md): One call. Task failures are reported, and every `beat_schedule` entry becomes a check-in named after it.
- [Next.js on Vercel](https://pagerless.dev/integrations/nextjs-vercel.md): Pagerless for Next.js on Vercel: the instrumentation file, Edge route handlers, the key in Vercel env, and rolling back a bad deployment with one tap.
- [Hono on Cloudflare Workers](https://pagerless.dev/integrations/hono-cloudflare-workers.md): Pagerless for Hono on Cloudflare Workers: one middleware (or withPagerless), the key in a Wrangler secret, and one-tap undo of a bad Worker version.
- [Pagerless for Vercel](https://pagerless.dev/integrations/vercel.md): Vercel: one-tap undo or restart.
- [Pagerless for Netlify](https://pagerless.dev/integrations/netlify.md): Netlify: one-tap undo or restart.
- [Pagerless for Cloudflare Workers](https://pagerless.dev/integrations/cloudflare-workers.md): Cloudflare Workers: one-tap undo.
- [Pagerless for Cloudflare Pages](https://pagerless.dev/integrations/cloudflare-pages.md): Cloudflare Pages: one-tap undo.
- [Pagerless for Railway](https://pagerless.dev/integrations/railway.md): Railway: one-tap undo or restart or add capacity.
- [Pagerless for Render](https://pagerless.dev/integrations/render.md): Render: one-tap undo or restart or add capacity.
- [Pagerless for Fly.io](https://pagerless.dev/integrations/fly-io.md): Fly.io: one-tap undo or restart or add capacity.
- [Pagerless for Heroku](https://pagerless.dev/integrations/heroku.md): Heroku: one-tap undo or restart or add capacity.
- [Pagerless for DigitalOcean App Platform](https://pagerless.dev/integrations/digitalocean.md): DigitalOcean App Platform: one-tap undo or restart or add capacity.
- [Pagerless for Koyeb](https://pagerless.dev/integrations/koyeb.md): Koyeb: one-tap undo or restart or add capacity.
- [Pagerless for Northflank](https://pagerless.dev/integrations/northflank.md): Northflank: one-tap undo or restart or add capacity.
- [Pagerless for Coolify](https://pagerless.dev/integrations/coolify.md): Coolify: one-tap undo or restart.
- [Pagerless for AWS ECS](https://pagerless.dev/integrations/aws-ecs.md): AWS ECS: one-tap undo or restart or add capacity.
- [Pagerless for AWS Lambda](https://pagerless.dev/integrations/aws-lambda.md): AWS Lambda: one-tap undo or add capacity.
- [Pagerless for AWS Amplify](https://pagerless.dev/integrations/aws-amplify.md): AWS Amplify: one-tap undo.
- [Pagerless for Google Cloud Run](https://pagerless.dev/integrations/google-cloud-run.md): Google Cloud Run: one-tap undo or restart or add capacity.
- [Pagerless for Firebase Hosting](https://pagerless.dev/integrations/firebase-hosting.md): Firebase Hosting: one-tap undo.
- [Pagerless for Azure App Service](https://pagerless.dev/integrations/azure-app-service.md): Azure App Service: one-tap undo or restart or add capacity.
- [Pagerless for Azure Container Apps](https://pagerless.dev/integrations/azure-container-apps.md): Azure Container Apps: one-tap undo or restart or add capacity.
- [Pagerless for Hugging Face Spaces](https://pagerless.dev/integrations/hugging-face-spaces.md): Hugging Face Spaces: one-tap restart or add capacity.
- [Pagerless for Appwrite](https://pagerless.dev/integrations/appwrite.md): Appwrite: one-tap undo or restart or add capacity.
- [Pagerless for Supabase](https://pagerless.dev/integrations/supabase.md): Supabase: one-tap restart or add capacity.
- [Pagerless for Neon](https://pagerless.dev/integrations/neon.md): Neon: one-tap undo or restart or add capacity.
- [Pagerless for Convex](https://pagerless.dev/integrations/convex.md): Convex: alerts.
- [Pagerless for Lovable](https://pagerless.dev/integrations/lovable.md): Lovable: step-by-step undo.
- [Pagerless for Replit](https://pagerless.dev/integrations/replit.md): Replit: step-by-step undo.
- [Pagerless for Bolt](https://pagerless.dev/integrations/bolt.md): Bolt: step-by-step undo.
- [Pagerless for Expo (EAS Update)](https://pagerless.dev/integrations/expo.md): Expo (EAS Update): step-by-step undo.
- [AWS CloudWatch alarms](https://pagerless.dev/integrations/aws-cloudwatch.md): Subscribe your SNS topic to Pagerless. ALARM opens a problem, OK closes it, and alarm-name rules decide who gets woken.
- [AWS EventBridge](https://pagerless.dev/integrations/aws-eventbridge.md): Send EventBridge events through an SNS topic subscribed to Pagerless. Alarm state changes group with the same alarm's SNS actions.
- [Terraform on AWS](https://pagerless.dev/integrations/terraform-aws.md): If your AWS lives in Terraform, connect reads it and writes one file, `pagerless.tf`, for you to apply.
- [Prometheus Alertmanager to Pagerless](https://pagerless.dev/integrations/prometheus-alertmanager.md): Prometheus Alertmanager: each alert with status firing (one problem per alert in a group) open a problem.
- [Grafana to Pagerless](https://pagerless.dev/integrations/grafana.md): Grafana: firing alerts (unified alerting), or state alerting (legacy) open a problem.
- [Datadog to Pagerless](https://pagerless.dev/integrations/datadog.md): Datadog: Triggered, Warn and No Data transitions open a problem.
- [New Relic to Pagerless](https://pagerless.dev/integrations/new-relic.md): New Relic: issue state ACTIVATED or CREATED (legacy: open) open a problem.
- [Google Cloud Monitoring to Pagerless](https://pagerless.dev/integrations/google-cloud-monitoring.md): Google Cloud Monitoring: incident state open open a problem.
- [Azure Monitor to Pagerless](https://pagerless.dev/integrations/azure-monitor.md): Azure Monitor: monitorCondition Fired open a problem.
- [Sentry to Pagerless](https://pagerless.dev/integrations/sentry.md): Sentry: issue alerts, and metric alerts at critical or warning open a problem.
- [Better Stack to Pagerless](https://pagerless.dev/integrations/better-stack.md): Better Stack: incident status started open a problem.
- [UptimeRobot to Pagerless](https://pagerless.dev/integrations/uptimerobot.md): UptimeRobot: down alerts, and SSL alerts open a problem.
- [Pingdom to Pagerless](https://pagerless.dev/integrations/pingdom.md): Pingdom: state DOWN or FAILING open a problem.
- [Checkly to Pagerless](https://pagerless.dev/integrations/checkly.md): Checkly: failure; degraded and SSL alerts as warnings open a problem.
- [Stripe to Pagerless](https://pagerless.dev/integrations/stripe.md): Stripe: failed payments, counted as errors on the payments route open a problem.
- [GitHub Actions to Pagerless](https://pagerless.dev/integrations/github-actions.md): GitHub Actions: a workflow run on the default branch that ends in failure, timed out or startup failure open a problem.
- [Any tool (JSON webhook) to Pagerless](https://pagerless.dev/integrations/generic-webhook.md): Any tool (JSON webhook): status firing (title required); up to 100 alerts in `{"alerts": [...]}` open a problem.
- [Phone calls through your Twilio](https://pagerless.dev/integrations/twilio.md): Pagerless places on-call phone calls through your own Twilio account, at Twilio's price with no markup. Press 1 to acknowledge.
- [Slack](https://pagerless.dev/integrations/slack.md): Send Pagerless tell alerts and the first step of wake alerts to a Slack channel: what broke, why and the fix, in plain words.
- [Telegram](https://pagerless.dev/integrations/telegram.md): Get Pagerless alerts as Telegram messages from your own bot: what broke, why and what to do, in plain words, on any phone including Android.
- [Webhooks](https://pagerless.dev/integrations/webhooks.md): Send Pagerless alerts to any URL as JSON, signed with HMAC-SHA256 in the Pagerless-Signature header, so you can route them anywhere.

## Comparisons

- [Compare](https://pagerless.dev/compare.md): Every Pagerless comparison page.
- [Pagerless vs PagerDuty](https://pagerless.dev/vs/pagerduty.md): PagerDuty vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Opsgenie](https://pagerless.dev/vs/opsgenie.md): Opsgenie vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs incident.io](https://pagerless.dev/vs/incident-io.md): incident.io vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Better Stack](https://pagerless.dev/vs/better-stack.md): Better Stack vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Rootly](https://pagerless.dev/vs/rootly.md): Rootly vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs FireHydrant](https://pagerless.dev/vs/firehydrant.md): FireHydrant vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Grafana OnCall](https://pagerless.dev/vs/grafana-oncall.md): Grafana OnCall vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Squadcast](https://pagerless.dev/vs/squadcast.md): Squadcast vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Splunk On-Call](https://pagerless.dev/vs/splunk-on-call.md): Splunk On-Call vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Zenduty](https://pagerless.dev/vs/zenduty.md): Zenduty vs Pagerless: prices, phone calls, schedules, setup.
- [Pagerless vs Sentry](https://pagerless.dev/vs/sentry.md): Sentry vs Pagerless: prices, phone calls, schedules, setup.

## Alternatives

- [Alternatives](https://pagerless.dev/alternatives.md): Alternatives to each major on-call tool.
- [PagerDuty alternatives](https://pagerless.dev/alternatives/pagerduty.md): Alternatives to PagerDuty, with prices and a migration guide.
- [Opsgenie alternatives](https://pagerless.dev/alternatives/opsgenie.md): Alternatives to Opsgenie, with prices and a migration guide.
- [incident.io alternatives](https://pagerless.dev/alternatives/incident-io.md): Alternatives to incident.io, with prices and a migration guide.
- [Better Stack alternatives](https://pagerless.dev/alternatives/better-stack.md): Alternatives to Better Stack, with prices and a migration guide.
- [Rootly alternatives](https://pagerless.dev/alternatives/rootly.md): Alternatives to Rootly, with prices and a migration guide.
- [FireHydrant alternatives](https://pagerless.dev/alternatives/firehydrant.md): Alternatives to FireHydrant, with prices and a migration guide.
- [Grafana OnCall alternatives](https://pagerless.dev/alternatives/grafana-oncall.md): Alternatives to Grafana OnCall, with prices and a migration guide.
- [Squadcast alternatives](https://pagerless.dev/alternatives/squadcast.md): Alternatives to Squadcast, with prices and a migration guide.
- [Splunk On-Call alternatives](https://pagerless.dev/alternatives/splunk-on-call.md): Alternatives to Splunk On-Call, with prices and a migration guide.
- [Zenduty alternatives](https://pagerless.dev/alternatives/zenduty.md): Alternatives to Zenduty, with prices and a migration guide.

## Use cases

- [Use cases](https://pagerless.dev/solutions.md): Every use case page.
- [On-call for apps you built with AI](https://pagerless.dev/solutions/vibe-coded-apps.md): You shipped a real app without being an ops team. Pagerless is the ops team: it watches, explains in plain words, and wakes you only when it must.
- [On-call for solo founders](https://pagerless.dev/solutions/solo-founders.md): You are the whole on-call rotation. Pagerless makes that survivable: quiet by default, loud for the four things that really matter, and one tap to fix.
- [On-call for small teams](https://pagerless.dev/solutions/small-teams.md): Small teams don't need an incident command system. They need the right person woken, with enough context to fix it in minutes.
- [On-call for Shopify apps](https://pagerless.dev/solutions/shopify-apps.md): Merchants notice before you do when a Shopify app breaks. Pagerless notices first.
- [SaaS on Vercel and Supabase](https://pagerless.dev/solutions/saas-on-vercel-supabase.md): The most common stack for new SaaS. Pagerless covers both halves: roll back the deploy on Vercel, restart or add compute on Supabase.
- [On-call for AWS](https://pagerless.dev/solutions/aws.md): Your alarms already exist. Pagerless decides which ones should wake someone, explains them, and can roll back ECS or Lambda through a least-privilege role.
- [Payments down alerts](https://pagerless.dev/solutions/payments-down-alerts.md): Failing payments are one of four floors in Pagerless: the AI is never allowed to call them noise. If checkout breaks at 3 a.m., someone gets a call.
- [Cron job monitoring](https://pagerless.dev/solutions/cron-job-monitoring.md): The job that silently stopped three weeks ago is the most expensive bug there is. One ping per run, and Pagerless tells you when a run is late, missed or failed.
- [Less alert noise, nothing missed](https://pagerless.dev/solutions/alert-noise-reduction.md): Alert fatigue comes from treating every error as an alert. Pagerless treats every error as evidence and decides, per problem, whether anyone needs to know.
- [Alerts for side projects](https://pagerless.dev/solutions/side-projects.md): Three apps, free. You hear about a side project once a week in an email, unless it is really down.

## Answers

- [Answers](https://pagerless.dev/answers.md): Short answers to common on-call questions.
- [What is the best on-call tool for a solo developer?](https://pagerless.dev/answers/best-on-call-tool-for-solo-developer.md): For one person, pick a tool that is free for you plus a backup, calls your phone only for real outages, and explains what broke. Pagerless does that: free for you and one backup, a call after 5 minutes without a tap, and a one-tap undo for bad deploys.
- [How do I get a phone call when my app is down?](https://pagerless.dev/answers/get-a-phone-call-when-app-is-down.md): Use an on-call service that calls you. With Pagerless, add the SDK (or run npx pagerless connect), add your Twilio number, and install the iPhone app. If your app goes silent, crash-loops, returns a burst of 5xx errors or payments fail, you get a push, then a call after 5 minutes.
- [Is there a free PagerDuty alternative?](https://pagerless.dev/answers/free-pagerduty-alternative.md): Yes. Pagerless is free for you and one backup with up to 3 apps, and calls you through your own Twilio account at Twilio's price. PagerDuty itself has a free plan for up to 5 users with one schedule. Grafana Cloud IRM is free for 3 active users.
- [What should I replace Opsgenie with?](https://pagerless.dev/answers/opsgenie-replacement.md): Atlassian ended Opsgenie sales on June 4, 2025 and shuts it down on April 5, 2027. Atlassian points customers to Jira Service Management or Compass. If you want something not tied to Jira, Pagerless is free for you and a backup, and PagerDuty, incident.io and Grafana Cloud IRM also have free tiers.
- [How do I monitor an app I built with Lovable or Bolt?](https://pagerless.dev/answers/monitor-app-built-with-lovable.md): Add a small error-reporting snippet and an on-call service that explains problems in plain words. With Pagerless, ask your AI builder to add the pagerless/browser snippet with your key. When errors spike, you get a plain-words alert and the exact steps to revert in Lovable or Bolt.
- [How do I know when my Vercel app is down?](https://pagerless.dev/answers/know-when-vercel-app-is-down.md): Vercel does not page you when your app breaks. Add an error and heartbeat reporter plus an on-call service. With Pagerless, one Next.js instrumentation file reports errors and 5xx per route; a 5xx burst or silence wakes you, and you can roll back to the previous deployment with one tap.
- [How do I get alerted when Stripe payments fail in my app?](https://pagerless.dev/answers/alert-when-stripe-payments-fail.md): Report errors from your checkout code and treat payment failures as an outage. Pagerless does this by default: failing Stripe calls are tagged automatically by the Node SDK, and 3 or more payment errors that are at least 2% of payment requests always wake someone with a push, then a call.
- [How can I monitor cron jobs for free?](https://pagerless.dev/answers/monitor-cron-jobs-free.md): Have each run ping a check-in URL, and alert when a ping is late, missing or reports failure. Pagerless check-ins are free on its free plan: up to 200 jobs per app, cron or interval schedules in any time zone, with a message by default or a phone call for critical jobs.
- [How do I roll back a bad deploy quickly at night?](https://pagerless.dev/answers/roll-back-bad-deploy-at-night.md): Have the alert carry the rollback. Pagerless links each error spike to the deploy before it and offers to undo it: tap Approve on your phone, confirm with Face ID, and it rolls back through your host's API on Vercel, Netlify, Cloudflare, Railway, Render, Fly.io, Heroku, AWS, Google Cloud and Azure.
- [What does being on call mean for a software developer?](https://pagerless.dev/answers/what-is-on-call.md): Being on call means you are the person who responds if a production system breaks during a set period, including nights and weekends. An alerting tool reaches you by push, call or message; you acknowledge, fix or escalate. Good on-call wakes people only for problems that need a human now.
- [How do I set up on-call when I'm the only developer?](https://pagerless.dev/answers/on-call-for-one-person.md): Decide what deserves a call (app down, crash loop, error burst, payments failing), make everything else a message or a weekly summary, name one backup, and use a tool that calls your phone. Pagerless sets this up with one command and ships with those four rules built in.
- [How do I reduce alert fatigue?](https://pagerless.dev/answers/reduce-alert-fatigue.md): Alert on symptoms users feel, not every error; group duplicates into one problem; send non-urgent things as messages during the day; and review every page that woke someone. Pagerless automates the first three: grouping, baselines, and wake, tell or log levels, with four floors that always wake.
- [How do I get a phone call from an AWS CloudWatch alarm?](https://pagerless.dev/answers/cloudwatch-alarm-phone-call.md): CloudWatch alarms publish to SNS, which can't call you by itself. Subscribe the SNS topic to an on-call service. With Pagerless, add the HTTPS subscription with ?wake= and your alarm-name pattern: matching alarms push, then call you after 5 minutes, and the alarm's OK state closes the problem.
- [Do I need PagerDuty for a small app?](https://pagerless.dev/answers/do-i-need-pagerduty.md): Usually not. PagerDuty is built for teams with rotations, schedules and formal incident roles. A small app with one or two people needs reliable alerts, a phone call for real outages and a backup. Pagerless covers that for free; PagerDuty's own free plan is another option.
- [Do I need Sentry or an on-call tool like PagerDuty?](https://pagerless.dev/answers/sentry-or-pagerduty.md): They do different jobs. Sentry tracks and helps debug errors; its free plan alerts by email only and it doesn't call your phone. On-call tools decide who to wake and reach them by push and phone. Many teams use both; Pagerless adds diagnosis and one-tap undo to the on-call side.
- [How do I get alerted when my app stops responding entirely?](https://pagerless.dev/answers/alert-when-app-goes-silent.md): Use heartbeats: the app sends a small signal every minute, and an alert fires when they stop. Pagerless SDKs send one every 60 seconds automatically, and 5 minutes without one is a floor: it always wakes someone, with a push and then a phone call.
- [Are there AI tools that diagnose production incidents?](https://pagerless.dev/answers/ai-incident-response-tools.md): Yes. Several incident tools now add AI. Pagerless uses Claude to explain each problem in plain words from scrubbed samples and recent deploys, pick how loud the alert should be within fixed rules, and propose a fix such as undoing the last deploy, which waits for your approval.
- [Can my AI coding agent fix production errors?](https://pagerless.dev/answers/let-ai-agent-fix-production.md): It can help, with guardrails. Through the Pagerless MCP server, an agent like Claude Code or Cursor can read a production problem, propose a fix, ask you a yes/no question and verify the result. It never acts on production directly: your rules and a passkey approval decide.
- [How do I get alerts for Cloudflare Workers errors?](https://pagerless.dev/answers/monitor-cloudflare-workers-errors.md): Wrap your Worker's default export with withPagerless from the pagerless npm package and store the key with wrangler secret put. Errors from fetch, scheduled and queue handlers are reported and re-thrown unchanged, and Pagerless can undo a bad Worker version with one tap.
- [Can I do on-call without a rotation schedule?](https://pagerless.dev/answers/on-call-without-rotation.md): Yes, for small teams. Use an escalation order instead: the first person gets the alert, and if they don't answer within a few minutes, the next person does. Pagerless works this way, with the first person called after 5 minutes without a tap and the next person after that.
- [Is uptime monitoring enough, or do I need error alerting?](https://pagerless.dev/answers/uptime-vs-error-alerting.md): Uptime monitoring checks from outside that a URL answers. It misses failing checkouts, broken background jobs and errors behind login. Error alerting watches from inside the app. Most apps need both signals; Pagerless covers the inside, plus heartbeats that catch a dead app.

## Guides

- [Guides](https://pagerless.dev/guides.md): Practical on-call guides.
- [On-call for small teams](https://pagerless.dev/guides/on-call-for-small-teams.md): A practical setup for one to ten people, in the order you'd do it.
- [Designing an escalation policy](https://pagerless.dev/guides/escalation-policies.md): Who gets the alert, by what channel, how long before the next person, and what never escalates.
- [Writing a blameless postmortem](https://pagerless.dev/guides/postmortems.md): A postmortem is for the next incident, not the last one. Keep it short, specific and blameless.
- [SLOs for small apps](https://pagerless.dev/guides/slos-for-small-apps.md): You don't need a reliability team to use SLOs. Two indicators and one honest target are enough to start.
- [Alerting checklist for apps built with AI](https://pagerless.dev/guides/alerting-for-ai-built-apps.md): Ten minutes of setup that saves your first bad night.
- [Monitoring scheduled jobs](https://pagerless.dev/guides/cron-monitoring.md): Jobs fail silently. Here is how to make them fail loudly, without a pager for every hiccup.

## Glossary

- [Glossary](https://pagerless.dev/glossary.md): Definitions of on-call and incident terms.
- [On call](https://pagerless.dev/glossary/on-call.md): Being the person responsible for responding when a production system breaks during a set period, including outside working hours.
- [Escalation policy](https://pagerless.dev/glossary/escalation-policy.md): The rules for who is alerted, in what order, and how long to wait before moving to the next person when nobody acknowledges.
- [Acknowledgement](https://pagerless.dev/glossary/acknowledgement.md): A responder's signal that they have seen an alert and are handling it, which stops further escalation.
- [Paging](https://pagerless.dev/glossary/paging.md): Interrupting a person to demand attention now, usually by push notification, phone call or SMS, named after the pagers on-call engineers once carried.
- [Alert fatigue](https://pagerless.dev/glossary/alert-fatigue.md): When responders receive so many alerts, many not actionable, that they start ignoring or muting them and miss the ones that matter.
- [Alert grouping](https://pagerless.dev/glossary/alert-grouping.md): Combining many related signals, such as the same error repeated, into one problem so a responder sees it once.
- [Fingerprint](https://pagerless.dev/glossary/fingerprint.md): A stable key computed from an error's type, stack and route, used to decide which events belong to the same problem.
- [Alert noise](https://pagerless.dev/glossary/noise.md): Alerts that don't need anyone to act: duplicates, known background errors, bots probing dead URLs, flapping checks.
- [Flapping](https://pagerless.dev/glossary/flapping.md): A check or alarm that switches between failing and healthy repeatedly in a short time, producing a stream of open and close alerts.
- [Incident](https://pagerless.dev/glossary/incident.md): An unplanned interruption or degradation of a service that needs a response.
- [Postmortem](https://pagerless.dev/glossary/postmortem.md): A written review after an incident: what happened, the impact, the cause, and what will change so it doesn't recur. Usually blameless.
- [Blameless culture](https://pagerless.dev/glossary/blameless.md): Reviewing incidents by asking how the system allowed the failure rather than who caused it, so people report problems honestly.
- [MTTR](https://pagerless.dev/glossary/mttr.md): Mean time to recovery (or restore, or resolve): the average time from an incident starting to service being restored. DORA now uses failed deployment recovery time for deploy-caused failures.
- [MTTA](https://pagerless.dev/glossary/mtta.md): Mean time to acknowledge: the average time from an alert being sent to a responder acknowledging it.
- [Failed deployment recovery time](https://pagerless.dev/glossary/failed-deployment-recovery-time.md): DORA's measure of how long it takes to recover from a deployment that fails and needs immediate intervention.
- [Rollback](https://pagerless.dev/glossary/rollback.md): Returning a service to its previous known-good version after a bad deploy.
- [Deploy marker](https://pagerless.dev/glossary/deploy-marker.md): A record of when a new version went live, used to connect errors to the change that caused them.
- [SLI](https://pagerless.dev/glossary/sli.md): Service level indicator: a carefully defined quantitative measure of some aspect of service, such as the share of requests served successfully.
- [SLO](https://pagerless.dev/glossary/slo.md): Service level objective: a target value or range for an SLI, such as 99.9% of requests succeeding over 30 days.
- [SLA](https://pagerless.dev/glossary/sla.md): Service level agreement: a contract with users that includes consequences for meeting or missing the SLOs it contains.
- [Error budget](https://pagerless.dev/glossary/error-budget.md): The amount of unreliability an SLO allows over a period: with a 99.9% target, 0.1% of requests may fail. Spending it slows releases; saving it allows risk.
- [Uptime](https://pagerless.dev/glossary/uptime.md): The share of time a service is available. 99.9% allows about 43 minutes of downtime in 30 days; 99.99% about 4.3 minutes.
- [Heartbeat monitoring](https://pagerless.dev/glossary/heartbeat-monitoring.md): Detecting a dead service by expecting a regular signal from it and alerting when the signal stops.
- [Check-in (cron monitoring)](https://pagerless.dev/glossary/check-in.md): A ping a scheduled job sends when it runs, so a monitor can alert when a run is late, missed or failed.
- [Runbook](https://pagerless.dev/glossary/runbook.md): Written steps for handling a known kind of problem, so whoever is on call can act without deep context.
- [Severity](https://pagerless.dev/glossary/severity.md): A label for how bad an incident is, often SEV1 to SEV4, used to decide who responds and how fast.
- [Floor signal](https://pagerless.dev/glossary/floor.md): A Pagerless term: a signal that always wakes someone and can never be played down by the AI. There are four: app silent, crash loop, 5xx burst and payments failing.
- [Crash loop](https://pagerless.dev/glossary/crash-loop.md): A process that starts, crashes and is restarted repeatedly, usually after a bad deploy or a missing configuration value.
- [Time-Sensitive notification](https://pagerless.dev/glossary/time-sensitive-notification.md): An iPhone notification level that breaks through Focus modes and notification summaries, but not the ring/silent switch.
- [MCP (Model Context Protocol)](https://pagerless.dev/glossary/mcp.md): An open protocol that lets AI assistants and coding agents call tools on external services in a standard way.
- [Observability](https://pagerless.dev/glossary/observability.md): How well you can understand a system's internal state from what it emits: logs, metrics and traces.
- [OpenTelemetry](https://pagerless.dev/glossary/opentelemetry.md): A vendor-neutral standard and set of SDKs for producing logs, metrics and traces, sent over the OTLP protocol.

## Free tools

- [Free tools](https://pagerless.dev/tools.md): Free on-call tools.
- [On-call schedule maker](https://pagerless.dev/tools/on-call-schedule.md): Make a fair weekly on-call rotation with backups.
- [Uptime and SLA calculator](https://pagerless.dev/tools/uptime-calculator.md): Allowed downtime for any availability percentage.
- [Postmortem template generator](https://pagerless.dev/tools/postmortem-template.md): Generate a blameless postmortem in Markdown.
- [Cron to check-in helper](https://pagerless.dev/tools/cron-check-in.md): Convert cron, AWS cron() and rate() to check-in code.