Skip to main content
ModPageSpeed 2.0 and mod_pagespeed 1.1 — Now available

One price per server. From $49/month.

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

14 days free. After day 15, your card is charged monthly — 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.

mod_pagespeed 1.1

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

Monthly · year one

$24.50 /mo

Renews at $49/mo

Annual · year one · save 20%

$19.50 /mo

Renews at $39/mo

Per server. Annual billed once a year.

  • nginx, Apache, IIS, Envoy
  • Drop-in from open-source
  • Cyclone Cache
  • Security patches
  • In-process module
  • Email support
Install — 14 days free

14 days free. No charge if you cancel before day 15.

Need more than 10 servers?

11+ servers

Volume pricing & MSA

Custom quote

Contact us

Reply within 1 business day (CET)

Self-serve covers up to 10 servers.

  • Volume discount
  • Master Services Agreement
  • SSO / SAML
  • Dedicated support
Contact us

Or email sales@we-amp.com for pre-purchase questions.

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 the trial starts

Two install paths. Pick the one that matches your stack.

  1. Step 1

    Install the 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.

  2. Step 2

    Open the admin console

    At /pagespeed_global_admin on your server.

  3. Step 3

    Start your 14-day trial

    From the console. Card required at checkout — cancel before day 15, no charge.

Money-back: cancel before day 15, no charge. After that, cancel anytime — billing stops at period end. Full refund policy →

Which edition should I choose?

Choose 1.1 if…

You're already running mod_pagespeed or ngx_pagespeed and want a maintained, supported release with the same config. Best for existing installations on Apache, nginx, IIS, or Envoy.

Choose 2.0 if…

You're starting fresh or want the latest architecture. New C++23 codebase with external worker process, variant-aware caching, and zero-copy serving. Two integrations in v1.0.0: Docker / nginx reverse proxy, and 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. The 14-day free trial covers evaluation in any environment; contact sales@we-amp.com about non-production licensing or multi-server volume pricing.
What happens when the 14-day trial ends?
The module stops optimizing. Your origin serves directly from that point on.
What happens after I cancel?
The module stops optimizing when your license expires (end of the current period). Your origin serves directly from that point on. Re-activate any time — your cache contents and configuration aren't touched.
Is there a free tier?
No free tier. We offer a 14-day free trial — full features. After install, start the trial from the admin console at /pagespeed_global_admin on your server.
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?
14-day money-back, no questions asked. Cancel before day 15 and we don't charge you. After day 15, cancel anytime through the FastSpring customer portal — billing stops at the end of the current period. Refund requests for charged-but-unused time are handled by FastSpring as Merchant of Record 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?
Three first-class integrations: a Docker / nginx caching reverse proxy in front of any HTTP origin (Apache, Node.js, Caddy, IIS, your CDN's origin), a bare-metal nginx dynamic module, and an ASP.NET Core middleware NuGet package. Same C++ optimization pipeline in all three.
Which nginx versions are supported?
We ship Docker images with a prebuilt dynamic module compiled against the latest stable and mainline nginx releases. You can also build the module from source for custom nginx versions.
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 →