Skip to main content

Pick your integration. Install in a few minutes.

Open source under the Apache License 2.0 — free to install and run, in development and in production.

After install, open the admin console at /pagespeed_global_admin on your server.

Apache, nginx, Docker, Helm, IIS & ASP.NET Core

Every way to run it, in one place. mod_pagespeed 2.1's native module installs on Apache and nginx from the signed apt/yum repository, or runs as a Docker container fronting nginx — deploy that with Helm on Kubernetes. Windows/IIS ships from the 1.15 packaging channel, and ASP.NET Core apps get a NuGet middleware or a Linux sidecar. Each card shows which package it comes from and how it integrates.

v2.4.0 see release notes

Apache

mod_pagespeed 2.1

Native module

Prebuilt signed package from the apt/yum repository — apt-get on Debian and Ubuntu, dnf on Enterprise Linux. Drop-in replacement for the open-source build.

Debian 12/13, Ubuntu 22.04/24.04 (amd64 + arm64); RHEL/AlmaLinux/Rocky 9 (x86_64 + aarch64) & 10 (x86_64); Apache 2.4+.

Repo setup guide

nginx

mod_pagespeed 2.1

Native module

Prebuilt signed dynamic module from the apt/yum repository, pinned to each distro's stock nginx. Loads alongside your existing nginx binary — no rebuild, no traffic detour.

Debian 12/13, Ubuntu 22.04/24.04 (amd64 + arm64); RHEL/AlmaLinux/Rocky 9 (x86_64 + aarch64) via dnf, EL10 (x86_64). Each module is pinned to its distro's exact stock nginx — running a different nginx version? Contact us for a matching build.

Repo setup guide

nginx (Docker)

mod_pagespeed 2.1

Reverse proxy

Run the mod_pagespeed 2.1 worker as a Docker container in front of nginx. Same optimization pipeline, zero changes to your nginx binary or config.

Any host with Docker 24+ (Linux, macOS, Windows). Images: ghcr.io/we-amp/pagespeed-nginx:2.4.0 and ghcr.io/we-amp/pagespeed-worker:2.4.0.

Install guide

Helm

mod_pagespeed 2.1

Kubernetes

Official Helm chart deploys nginx and the worker as a two-container pod, sharing a Cyclone cache volume. Pulls the public images directly — no registry credentials required.

Kubernetes 1.28+, Helm 3.12+. Chart: pagespeed (https://modpagespeed.com/charts).

Helm guide

IIS

mod_pagespeed 1.15

Native module

MSI installer for Windows Server. Enable in IIS Manager, iisreset, and the optimization pipeline is live.

Running IISpeed? Uninstall it first — both modules cannot coexist on the same host.

Windows Server 2019 or later, IIS 10+, x64

Install guide

ASP.NET Core

mod_pagespeed 2.1

NuGet middleware

Two lines in Program.cs add the optimization pipeline to any ASP.NET Core app. Runs in-process — no sidecar, no Docker.

.NET 8 or .NET 10 on Windows, Linux, or macOS.

Install guide

ASP.NET Core Sidecar

mod_pagespeed 1.15

NuGet · Linux

WeAmp.PageSpeed.Sidecar adds the 1.15 module to your Kestrel app via middleware, with a bundled nginx optimizer on loopback behind it. One dotnet add package pulls the native binaries.

Now GA. Want the classic 1.x nginx-module behavior under .NET? Start here.

.NET 8 or .NET 10 on Linux (linux-x64, linux-arm64).

Sidecar guide

Also available: the Envoy HTTP filter (experimental, built from source) and the WordPress plugin.

The Apache and nginx packages keep their existing 1.15-line names — your apt/dnf upgrades them in place, no rename needed.

Direct downloads

The supported way to install is the signed package repositories; for IIS, download the Windows installer and follow the install guide. The worker packages (deb, rpm and Windows zip, with a checksum list) of every release are on the project's release listing. The signing key for the repositories is documented on the apt/yum page, and the public key is available as the GPG signing key.

Other integration paths

Running nginx specifically? ngxpagespeed.com has the nginx install walkthrough.

IISpeed customer? Contact us about moving to mod_pagespeed — IIS deployments run on the native Windows module from the 1.15 packaging channel. Arrange your no-cost transfer.

How licensing and support work

Pricing
Free — open source under the Apache License 2.0, with no usage registration. What We-Amp sells is support; Priority and Enterprise add a private package repository (being set up). No per-request fees, no bandwidth metering.
Evaluation
There is nothing to evaluate against a clock — the software is free, in full, under Apache-2.0. Install it, measure the results on your own pages, and add a support plan when you want support from the people who build it.
Hosting
Runs on your servers. No third-party proxy, no CDN dependency, no external service in your request path. The software is open source under the Apache License 2.0.

Search