# Integrations

> Pick your language, framework or host. Every page has the real setup line and exactly what Pagerless can fix there.

URL: https://pagerless.dev/integrations
Updated: 2026-10-22

## Languages

- [Node.js](https://pagerless.dev/integrations/nodejs): One import at the top of your entry file covers any Node server. Framework hooks add the errors your framework catches itself.
- [Go](https://pagerless.dev/integrations/go): Standard library only. Init, defer Close, wrap your handler.
- [Python](https://pagerless.dev/integrations/python): One package, standard library only. Django, Flask, FastAPI and any ASGI or WSGI app, Celery, AWS Lambda and logging.
- [HTTP and curl](https://pagerless.dev/integrations/curl): If it can make an HTTPS request, it can page you. The SDKs use the same API.
- [OpenTelemetry](https://pagerless.dev/integrations/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](https://pagerless.dev/integrations/browser): For dashboards and single-page apps: uncaught errors and promise rejections from the page, grouped by path.

## JavaScript and TypeScript frameworks

- [Next.js](https://pagerless.dev/integrations/nextjs): One line in `instrumentation.ts` covers pages, layouts, route handlers, server actions and middleware, on Node and the edge.
- [Nuxt](https://pagerless.dev/integrations/nuxt): One server plugin hooks Nitro's `error` hook: API routes, server rendering and middleware.
- [SvelteKit](https://pagerless.dev/integrations/sveltekit): Export `handleError` from your hooks. Load functions, form actions, endpoints and rendering are covered; 404s and expected errors are skipped.
- [Astro](https://pagerless.dev/integrations/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](https://pagerless.dev/integrations/remix): Export `handleError` from the server entry. Shopify apps built on the Remix or React Router template work the same way.
- [Express](https://pagerless.dev/integrations/express): One error handler after your routes. Routes are grouped by Express's own pattern, so `/orders/:id` is one route, not thousands.
- [Fastify](https://pagerless.dev/integrations/fastify): One call registers an `onError` hook.
- [Koa](https://pagerless.dev/integrations/koa): Add it as the first middleware. It reports and re-throws, so your error handling is unchanged.
- [NestJS](https://pagerless.dev/integrations/nestjs): One line after `NestFactory.create`, or register the exception filter yourself.
- [Hono](https://pagerless.dev/integrations/hono): One middleware right after `new Hono()`, on every runtime Hono runs on.
- [tRPC](https://pagerless.dev/integrations/trpc): One adapter option. Only `INTERNAL_SERVER_ERROR` is reported; bad input and auth errors are your users' business, not an alert.
- [Bun](https://pagerless.dev/integrations/bun): The same one import as Node. Bun gets its own build.
- [Deno](https://pagerless.dev/integrations/deno): One import from npm. Deno gets its own build.
- [Electron](https://pagerless.dev/integrations/electron): Main-process crashes, crashed renderers and GPU or child processes, grouped into problems you can act on.
- [React Native and Expo](https://pagerless.dev/integrations/react-native): 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](https://pagerless.dev/integrations/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)](https://pagerless.dev/integrations/vite): For single-page apps built with Vite. The key comes from `VITE_PAGERLESS_KEY`.
- [Next.js on Vercel](https://pagerless.dev/integrations/nextjs-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](https://pagerless.dev/integrations/hono-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](https://pagerless.dev/integrations/gin): One middleware, after Gin's recovery and before your routes.
- [Echo](https://pagerless.dev/integrations/echo): One middleware after `middleware.Recover()`. Echo v4 and v5 each have an adapter.
- [Fiber](https://pagerless.dev/integrations/fiber): One middleware after `recover.New()`. Fiber v2 and v3 each have an adapter.
- [chi and gorilla/mux](https://pagerless.dev/integrations/chi): One middleware each. Routes are reported by their pattern, so `/orders/{id}` is one route.
- [gRPC (Go)](https://pagerless.dev/integrations/grpc): Interceptors for both sides. Each method becomes a route like `gRPC /shop.Orders/Get`.
- [Temporal](https://pagerless.dev/integrations/temporal): One worker interceptor. Failed activities and workflows are reported, and every Temporal Schedule becomes a check-in.

## Python frameworks

- [Django](https://pagerless.dev/integrations/django): Add the app and put the middleware first. Request rate, errors and latency per URL pattern, and every 500.
- [Flask](https://pagerless.dev/integrations/flask): Two lines. Metrics per URL rule, and every exception Flask turns into a 500.
- [FastAPI and Starlette](https://pagerless.dev/integrations/fastapi): One ASGI middleware for FastAPI, Starlette, Django on ASGI or any ASGI app.
- [Celery](https://pagerless.dev/integrations/celery): One call. Task failures are reported, and every `beat_schedule` entry becomes a check-in named after it.

## Hosts and clouds

- [Vercel](https://pagerless.dev/integrations/vercel): Undo · Restart
- [Netlify](https://pagerless.dev/integrations/netlify): Undo · Restart
- [Cloudflare Workers](https://pagerless.dev/integrations/cloudflare-workers): Undo
- [Cloudflare Pages](https://pagerless.dev/integrations/cloudflare-pages): Undo
- [Railway](https://pagerless.dev/integrations/railway): Undo · Restart · Scale
- [Render](https://pagerless.dev/integrations/render): Undo · Restart · Scale
- [Fly.io](https://pagerless.dev/integrations/fly-io): Undo · Restart · Scale
- [Heroku](https://pagerless.dev/integrations/heroku): Undo · Restart · Scale
- [DigitalOcean App Platform](https://pagerless.dev/integrations/digitalocean): Undo · Restart · Scale
- [Koyeb](https://pagerless.dev/integrations/koyeb): Undo · Restart · Scale
- [Northflank](https://pagerless.dev/integrations/northflank): Undo · Restart · Scale
- [Coolify](https://pagerless.dev/integrations/coolify): Undo · Restart
- [AWS ECS](https://pagerless.dev/integrations/aws-ecs): Undo · Restart · Scale
- [AWS Lambda](https://pagerless.dev/integrations/aws-lambda): Undo · Scale
- [AWS Amplify](https://pagerless.dev/integrations/aws-amplify): Undo
- [Google Cloud Run](https://pagerless.dev/integrations/google-cloud-run): Undo · Restart · Scale
- [Firebase Hosting](https://pagerless.dev/integrations/firebase-hosting): Undo
- [Azure App Service](https://pagerless.dev/integrations/azure-app-service): Undo · Restart · Scale
- [Azure Container Apps](https://pagerless.dev/integrations/azure-container-apps): Undo · Restart · Scale
- [Hugging Face Spaces](https://pagerless.dev/integrations/hugging-face-spaces): Restart · Scale
- [Appwrite](https://pagerless.dev/integrations/appwrite): Undo · Restart · Scale

## Databases and backends

- [Supabase](https://pagerless.dev/integrations/supabase): Restart · Scale
- [Neon](https://pagerless.dev/integrations/neon): Undo · Restart · Scale
- [Convex](https://pagerless.dev/integrations/convex): Pause / unpause

## AI app builders

- [Lovable](https://pagerless.dev/integrations/lovable): Alerts plus guided undo steps
- [Replit](https://pagerless.dev/integrations/replit): Alerts plus guided undo steps
- [Bolt](https://pagerless.dev/integrations/bolt): Alerts plus guided undo steps
- [Expo (EAS Update)](https://pagerless.dev/integrations/expo): Alerts plus guided undo steps

## Alert sources

- [AWS CloudWatch alarms](https://pagerless.dev/integrations/aws-cloudwatch): 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): 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): If your AWS lives in Terraform, connect reads it and writes one file, `pagerless.tf`, for you to apply.
- [Prometheus Alertmanager](https://pagerless.dev/integrations/prometheus-alertmanager): Each alert with status firing (one problem per alert in a group).
- [Grafana](https://pagerless.dev/integrations/grafana): Firing alerts (unified alerting), or state alerting (legacy).
- [Datadog](https://pagerless.dev/integrations/datadog): Triggered, Warn and No Data transitions.
- [New Relic](https://pagerless.dev/integrations/new-relic): Issue state ACTIVATED or CREATED (legacy: open).
- [Google Cloud Monitoring](https://pagerless.dev/integrations/google-cloud-monitoring): Incident state open.
- [Azure Monitor](https://pagerless.dev/integrations/azure-monitor): MonitorCondition Fired.
- [Sentry](https://pagerless.dev/integrations/sentry): Issue alerts, and metric alerts at critical or warning.
- [Better Stack](https://pagerless.dev/integrations/better-stack): Incident status started.
- [UptimeRobot](https://pagerless.dev/integrations/uptimerobot): Down alerts, and SSL alerts.
- [Pingdom](https://pagerless.dev/integrations/pingdom): State DOWN or FAILING.
- [Checkly](https://pagerless.dev/integrations/checkly): Failure; degraded and SSL alerts as warnings.
- [Stripe](https://pagerless.dev/integrations/stripe): Failed payments, counted as errors on the payments route.
- [GitHub Actions](https://pagerless.dev/integrations/github-actions): A workflow run on the default branch that ends in failure, timed out or startup failure.
- [Any tool (JSON webhook)](https://pagerless.dev/integrations/generic-webhook): Status firing (title required); up to 100 alerts in `{"alerts": [...]}`.

## Alert channels

- [Phone calls through your Twilio](https://pagerless.dev/integrations/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](https://pagerless.dev/integrations/slack): One message per problem in the channel you pick, with what broke and the fix waiting for approval.
- [Telegram](https://pagerless.dev/integrations/telegram): Alerts as messages from your own Telegram bot, on any phone, including Android.
- [Webhooks](https://pagerless.dev/integrations/webhooks): Every alert as signed JSON to a URL you choose.

> Tool not listed? Anything that can POST JSON can use the [generic webhook](https://pagerless.dev/integrations/generic-webhook) or the [events API](https://pagerless.dev/docs/events-api).
