One price per server. From $49/month.

Or $39/server/month billed annually. No per-request fees. No bandwidth metering. All optimizations included.

Install and run it unlicensed to evaluate — it fully optimizes and just adds an X-PageSpeed-Warn: unlicensed header. A commercial license is required for production use; you're charged immediately on purchase for the term you pick — cancel any time, billing stops at period end. Prices are localized at checkout; local VAT is shown there.

Launch pricing through June 16, 2026 — year-one rates shown below on new mod_pagespeed 1.1 and ModPageSpeed 2.0 subscriptions. 15 days left.

Annual saves ~20% — two months free, every year.

mod_pagespeed 1.1

Drop-in upgrade from open-source — nginx, Apache, IIS (Envoy experimental)

$19.50 /server/mo Save ~20%

Billed once a year · year one. Renews at $39/mo

In-process native module — no sidecar, no extra hop
nginx, Apache, IIS (Envoy experimental)
Same mod_pagespeed directives and filters
Security patches and CVE maintenance
Runs on your existing Apache/nginx/IIS binary
cPanel / EasyApache 4 support
Classic filters: combine, sprite, IPRO, domain mapping
Cyclone Cache
Email support

Download & run

A commercial license is required for production use.

ModPageSpeed 2.0

Ground-up C++23 rewrite — any HTTP origin via the worker

$19.50 /server/mo Save ~20%

Billed once a year · year one. Renews at $39/mo

Any HTTP origin via nginx proxy
Zero-copy cache serving
Variant-aware caching — format, viewport, density, Save-Data, encoding
Security patches and CVE maintenance
Critical CSS extraction
ML image quality
Web console
ASP.NET Core
Email support

Download & run

A commercial license is required for production use.

Running 3 or more servers? Ask us about volume pricing.

What a flat per-server license replaces

~$3,500

Typical image-CDN bill at 10M monthly image requests, on published per-unit list pricing. It climbs with traffic.

$39/server/mo

Flat, annual. No per-request fees, no per-transformation fees, no bandwidth metering. The bill doesn't move with traffic.

~300–500K

Monthly image requests where self-hosting overtakes a CDN. Below that, a CDN is often cheaper.

Run your own numbers in the savings calculator, or read the full cost model in Image Optimization Cost: Self-Hosted vs CDN. Figures reflect published list-price models as of February 2026 — confirm current rates with each vendor.

What if I cancel?

The engine keeps optimizing when your license expires — it never locks you out. The installation returns to the unlicensed state (an X-PageSpeed-Warn: unlicensed response header, an admin-console notice, and a startup-log warning); production use then requires a license. Your cache and config aren't touched, so re-activating later picks up where you left off.

Will it break my site?

Transforms are safe by construction. JS minification only strips whitespace and comments — no variable renaming. CSS minification preserves semantics. If any optimization fails, the original is served. More in the FAQ.

One small company — what's the risk?

Source publication under the Business Source License 1.1 is on our roadmap — it converts to Apache 2.0 on a fixed change date. License validation runs offline; there's no kill switch in the request path. How licensing works.

11+ servers

Volume pricing and a Master Services Agreement

Self-serve covers up to 10 servers. Beyond that we quote a per-server volume rate and sign an MSA — same optimization pipeline, terms that fit a larger fleet.

Volume per-server discount
Master Services Agreement
SSO / SAML
Priority email support

Custom quote

Talk to sales

We aim to reply in about a business day (CET).

Pre-filled with the details that speed up a quote — edit before sending.

Prices on the cards are FastSpring's localized rate for your region — same number you'll see at checkout. VAT or GST is included where FastSpring is registered to collect it; elsewhere local tax is added at checkout.

One license covers one production server. Contact sales@we-amp.com for multi-environment or volume pricing.

How to get started

Install it, run it, and watch it optimize. License it when you go to production.

Step 1

Install

Server module — Apache on Debian/Ubuntu:
```
curl -fsSL https://packages.modpagespeed.com/install.sh | sudo sh
sudo apt install mod-pagespeed
```
nginx, IIS, or Envoy — see the install guide. On ASP.NET Core, add the NuGet package instead:
```
dotnet add package WeAmp.PageSpeed.AspNetCore
```
View on NuGet →
Step 2

Run it unlicensed

It fully optimizes out of the box — nothing is gated. Unlicensed responses simply carry an X-PageSpeed-Warn: unlicensed header, with a matching notice in the admin console and a startup-log line. Evaluate it against your real traffic for as long as you need.
Step 3

License for production

A commercial license is required for production use. Buy one from the admin console or the pricing cards above, paste the key, and the warning header clears. You're charged immediately for the term you pick.

Billing: evaluate it unlicensed for as long as you need, then buy a license for production. Subscriptions are charged immediately on purchase — cancel anytime, billing stops at period end. Billing & cancellation FAQ →

Which edition should I choose?

Choose 1.1 if…

For a native in-process module on Apache, nginx, IIS, or Envoy: the same mod_pagespeed directives, the classic filter set, and a built-in admin console, with no extra worker or proxy hop. Drop-in for an existing open-source mod_pagespeed install, and a clean fit for a new one.

Choose 2.0 if…

For new deployments and teams that want the reverse-proxy / worker model: a C++23 worker with variant-aware caching and zero-copy serving. Two integrations: a Docker / nginx reverse proxy in front of any HTTP origin, and an ASP.NET Core middleware.

Frequently asked questions

What counts as a server?

One license per machine running the module — whether that's nginx + worker (ModPageSpeed 2.0), an Apache, nginx, IIS, or Envoy host (mod_pagespeed 1.1), or an ASP.NET Core process. You can run the module unlicensed to evaluate it in any environment; contact sales@we-amp.com about non-production licensing or multi-server volume pricing.

What happens if I run unlicensed?

The engine keeps optimizing — it never locks you out. Unlicensed installs add an X-PageSpeed-Warn: unlicensed response header, show a notice in the admin console, and write a warning to the startup log. A commercial license is required for production use.

What happens after I cancel?

The engine keeps optimizing after your license expires — it never locks you out. The installation simply returns to the unlicensed state (the X-PageSpeed-Warn: unlicensed header, an admin-console notice, and a startup-log warning). Re-activate any time — your cache contents and configuration aren't touched.

Is there a free tier?

No free tier — a commercial license is required for production use. You can install and run the engine unlicensed to evaluate it: it optimizes fully and just adds an X-PageSpeed-Warn: unlicensed header. Buy a license from the admin console at /pagespeed_global_admin on your server when you're ready for production.

How does the license key work?

You receive an Ed25519-signed token via email. Set it as an environment variable. Signature validation runs offline at startup — no internet dependency in the request path. The product refreshes subscription state with our API every 12 hours; see Terms of Service for details.

mod_pagespeed is free. Why should I pay?

The original mod_pagespeed and ngx_pagespeed are no longer actively developed. We-Amp maintains both mod_pagespeed 1.1 (the drop-in continuation of the open-source project — CVE patches, modern nginx, IIS support) and ModPageSpeed 2.0 (the ground-up rewrite with zero-copy serving, variant-aware caching, and an out-of-process worker). Both come with direct email support.

What's your refund policy?

Subscriptions are billed immediately on purchase via FastSpring (our Merchant of Record). Cancel anytime through the FastSpring customer portal — billing stops at the end of the current period. Refund requests are handled by FastSpring under their standard refund policy. EU/EEA consumers have a 14-day right of withdrawal under EU Directive 2011/83/EU; see Terms of Service for details.

Which integrations are supported?

Two first-class integrations: a Docker / nginx caching reverse proxy in front of any HTTP origin (Apache, Node.js, Caddy, IIS, your CDN's origin), and an ASP.NET Core middleware NuGet package. Same C++ optimization pipeline in both. (For an in-process nginx or Apache module on bare metal, that's mod_pagespeed 1.1.)

How does the nginx integration work?

ModPageSpeed 2.0 runs in front of nginx as a Docker reverse proxy. The prebuilt nginx module ships inside the Docker image — there is no separate bare-metal module to install. Point the reverse proxy at your origin and all optimizations apply automatically.

Does it work with Apache?

Yes — as a reverse proxy. Deploy ModPageSpeed 2.0 in front of your Apache server via the Docker Compose setup, point BACKEND_HOST at your origin, and all optimizations apply automatically. If you need an in-process Apache module instead, that's mod_pagespeed 1.1.

Does it work with Kubernetes?

Yes. The Docker distribution uses separate nginx and worker containers, designed for Kubernetes pod deployments. The license key is passed as an environment variable, making it easy to manage via Secrets. A Helm chart is included.

Does it add latency?

No. On cache hit, serving is sub-millisecond — just a hash lookup and an mmap pointer. On cache miss, the original content is served immediately while the worker generates optimized variants in the background. There is no synchronous processing in the request path.

Can it break my site?

ModPageSpeed 2.0 uses conservative, safe-by-construction transforms. JS minification only strips whitespace and comments — no variable renaming. CSS minification removes redundant syntax without changing semantics. Image transcoding preserves visual quality. If optimization fails for any reason, the original content is always served.

Why not just use Cloudflare or another CDN?

CDN-based optimization requires routing your traffic through a third-party proxy. ModPageSpeed runs on your servers — your visitors' content stays on your infrastructure. Only a pseudonymous license heartbeat is sent to our API every 12 hours. Self-hosted by design; helps your GDPR posture and keeps you in control of caching, configuration, and data.

Running mod_pagespeed 1.1? See the 1.1 FAQ →