# Pagerless for Cloudflare Pages

> Woken only when it matters, and one tap undoes a bad deploy: Pagerless rolls back to the previous Pages deployment.

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

## Set up

Pages Functions: one middleware file.

```js
import { withPagerless } from "pagerless";

export const onRequest = withPagerless((context) => context.next());
```

Store the key with `npx wrangler pages secret put PAGERLESS_KEY`. Or run `npx pagerless connect` and it finds your services and places the key for you.

## Fixes on Cloudflare Pages

| Fix | On Cloudflare Pages |
| --- | --- |
| Undo the update | Rolls back to the previous Pages deployment |
| Restart | Not available |
| Add capacity | Not available |
| Deploy events | From the SDK's deploy marker |
| Access it needs | a Cloudflare API token with Pages edit |

## Questions

### Can Pagerless roll back Cloudflare Pages automatically?

Yes, if your rules set undo to alone. By default it asks first, and approving an undo needs your passkey (Face ID or Touch ID). It then rolls back to the previous Pages deployment.

### Does Pagerless need admin access to Cloudflare Pages?

It needs a Cloudflare API token with Pages edit. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.