Integrations

Languages

• Node.js

  One import at the top of your entry file covers any Node server. Framework hooks add the errors your framework catches itself.

• Go

  Standard library only. Init, defer Close, wrap your handler.

• Python

  One package, standard library only. Django, Flask, FastAPI and any ASGI or WSGI app, Celery, AWS Lambda and logging.

• HTTP and curl

  If it can make an HTTPS request, it can page you. The SDKs use the same API.

• OpenTelemetry

  Errors in your OTLP logs and traces become Pagerless problems: grouped, explained and routed to the right person. Any OpenTelemetry SDK, protobuf or JSON.

• Browser apps

  For dashboards and single-page apps: uncaught errors and promise rejections from the page, grouped by path.

JavaScript and TypeScript frameworks

• Next.js

  One line in instrumentation.ts covers pages, layouts, route handlers, server actions and middleware, on Node and the edge.

• Nuxt

  One server plugin hooks Nitro's error hook: API routes, server rendering and middleware.

• SvelteKit

  Export handleError from your hooks. Load functions, form actions, endpoints and rendering are covered; 404s and expected errors are skipped.

• Astro

  One middleware export, or the integration in astro.config. Errors from pages, endpoints and later middleware are reported and re-thrown.

• Remix and React Router

  Export handleError from the server entry. Shopify apps built on the Remix or React Router template work the same way.

• Express

  One error handler after your routes. Routes are grouped by Express's own pattern, so /orders/:id is one route, not thousands.

• Fastify

  One call registers an onError hook.

• Koa

  Add it as the first middleware. It reports and re-throws, so your error handling is unchanged.

• NestJS

  One line after NestFactory.create, or register the exception filter yourself.

• Hono

  One middleware right after new Hono(), on every runtime Hono runs on.

• tRPC

  One adapter option. Only INTERNAL_SERVER_ERROR is reported; bad input and auth errors are your users' business, not an alert.

• Bun

  The same one import as Node. Bun gets its own build.

• Deno

  One import from npm. Deno gets its own build.

• Electron

  Main-process crashes, crashed renderers and GPU or child processes, grouped into problems you can act on.

• React Native and Expo

  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.

• React

  An error boundary, or React's root error options. Start the client first with the browser or React Native SDK.

• Vite (React, Vue, Svelte)

  For single-page apps built with Vite. The key comes from VITE_PAGERLESS_KEY.

• Next.js on Vercel

  The most common stack for apps built with AI, and the one where Pagerless can do the most: catch it, explain it, roll it back.

• Hono on Cloudflare Workers

  One middleware reads the key from the Worker's env and sends in waitUntil. On pagerless 0.1, wrap app.fetch instead.

Go frameworks

• Gin

  One middleware, after Gin's recovery and before your routes.

• Echo

  One middleware after middleware.Recover(). Echo v4 and v5 each have an adapter.

• Fiber

  One middleware after recover.New(). Fiber v2 and v3 each have an adapter.

• chi and gorilla/mux

  One middleware each. Routes are reported by their pattern, so /orders/{id} is one route.

• gRPC (Go)

  Interceptors for both sides. Each method becomes a route like gRPC /shop.Orders/Get.

• Temporal

  One worker interceptor. Failed activities and workflows are reported, and every Temporal Schedule becomes a check-in.

Python frameworks

• Django

  Add the app and put the middleware first. Request rate, errors and latency per URL pattern, and every 500.

• Flask

  Two lines. Metrics per URL rule, and every exception Flask turns into a 500.

• FastAPI and Starlette

  One ASGI middleware for FastAPI, Starlette, Django on ASGI or any ASGI app.

• Celery

  One call. Task failures are reported, and every beat_schedule entry becomes a check-in named after it.

Hosts and clouds

• Vercel

  Undo · Restart

• Netlify

  Undo · Restart

• Cloudflare Workers

  Undo

• Cloudflare Pages

  Undo

• Railway

  Undo · Restart · Scale

• Render

  Undo · Restart · Scale

• Fly.io

  Undo · Restart · Scale

• Heroku

  Undo · Restart · Scale

• DigitalOcean App Platform

  Undo · Restart · Scale

• Koyeb

  Undo · Restart · Scale

• Northflank

  Undo · Restart · Scale

• Coolify

  Undo · Restart

• AWS ECS

  Undo · Restart · Scale

• AWS Lambda

  Undo · Scale

• AWS Amplify

  Undo

• Google Cloud Run

  Undo · Restart · Scale

• Firebase Hosting

  Undo

• Azure App Service

  Undo · Restart · Scale

• Azure Container Apps

  Undo · Restart · Scale

• Hugging Face Spaces

  Restart · Scale

• Appwrite

  Undo · Restart · Scale

Databases and backends

• Supabase

  Restart · Scale

• Neon

  Undo · Restart · Scale

• Convex

  Pause / unpause

AI app builders

• Lovable

  Alerts plus guided undo steps

• Replit

  Alerts plus guided undo steps

• Bolt

  Alerts plus guided undo steps

• Expo (EAS Update)

  Alerts plus guided undo steps

Alert sources

• AWS CloudWatch alarms

  Subscribe your SNS topic to Pagerless. ALARM opens a problem, OK closes it, and alarm-name rules decide who gets woken.

• AWS EventBridge

  Send EventBridge events through an SNS topic subscribed to Pagerless. Alarm state changes group with the same alarm's SNS actions.

• Terraform on AWS

  If your AWS lives in Terraform, connect reads it and writes one file, pagerless.tf, for you to apply.

• Prometheus Alertmanager

  Each alert with status firing (one problem per alert in a group).

• Grafana

  Firing alerts (unified alerting), or state alerting (legacy).

• Datadog

  Triggered, Warn and No Data transitions.

• New Relic

  Issue state ACTIVATED or CREATED (legacy: open).

• Google Cloud Monitoring

  Incident state open.

• Azure Monitor

  MonitorCondition Fired.

• Sentry

  Issue alerts, and metric alerts at critical or warning.

• Better Stack

  Incident status started.

• UptimeRobot

  Down alerts, and SSL alerts.

• Pingdom

  State DOWN or FAILING.

• Checkly

  Failure; degraded and SSL alerts as warnings.

• Stripe

  Failed payments, counted as errors on the payments route.

• GitHub Actions

  A workflow run on the default branch that ends in failure, timed out or startup failure.

• Any tool (JSON webhook)

  Status firing (title required); up to 100 alerts in {"alerts": [...]}.

Alert channels

• Phone calls through your Twilio

  Wake alerts call you after 5 minutes without a tap. Calls go through your Twilio account, so you pay Twilio and nothing more.

• Slack

  One message per problem in the channel you pick, with what broke and the fix waiting for approval.

• Telegram

  Alerts as messages from your own Telegram bot, on any phone, including Android.

• Webhooks

  Every alert as signed JSON to a URL you choose.

Tool not listed? Anything that can POST JSON can use the generic webhook or the events API.

Updated October 22, 2026.