Core PWA

Caching that

just works.

Service workers are powerful and notoriously tricky to get right. A misconfigured one can serve stale content indefinitely or break your entire site. pageflare generates, registers, and updates your service worker automatically — with caching strategies configured per route, not per developer.

Zero boilerplate
No SW code to write
Per-route rules
Granular cache control
Auto-update
No stale SW risk
Caching strategies

The right strategy
for every resource.

How it works

One script tag.
Full SW coverage.

1

Add the pageflare script

Paste one script tag into your HTML head. pageflare's loader detects browser support and registers the service worker with the correct scope — no bundler changes, no build step modifications.

<script src="https://cdn.pageflare.com/pwa.js" data-site="your-site-id"></script>
2

Configure caching rules

In the dashboard, define which URL patterns use which caching strategy. Set cache TTLs, precache lists for critical assets, and the offline fallback page — all without touching a JavaScript file.

3

pageflare serves the SW

Your service worker is generated and served by pageflare's edge infrastructure. Updates deploy instantly — no new build, no CI pipeline needed. The new worker activates when users next visit.

Get started

Set it once. Cache forever.

Install the CLI, point it at your build output, and see results in under two seconds.