Platform Support Matrix

pageflare works with any platform that builds static sites. After your framework produces its output, pageflare optimizes those files before deployment. The integration method depends on how your platform runs builds.

Integration Methods

There are three ways to integrate pageflare into your deployment pipeline:

Method	When to use
Dedicated guide	Platform has a full walkthrough with platform-specific features (e.g., image optimization)
GitHub Action	Platform deploys from GitHub — add getappz/pageflare-cli@v1 as a build step
Build command	Platform lets you customize the build command — append && pageflare dist/ --in-place

All Platforms

Dedicated Guides

These platforms have full integration guides with platform-specific configuration, image optimization support, and troubleshooting.

Platform	Integration	Image Optimization	Guide
Vercel	Build command override in vercel.json	Vercel Image Optimization API	Vercel guide
Netlify	Build plugin or build command	Netlify Image CDN	Netlify guide
Cloudflare Pages	Build command override	Cloudflare Image Resizing	Cloudflare Pages guide
GitHub Pages	GitHub Actions workflow	—	GitHub Pages guide
AWS Amplify	amplify.yml post-build step	—	AWS Amplify guide
Azure Static Web Apps	GitHub Actions workflow	—	Azure Static Web Apps guide
WordPress	CLI or edge proxy	Cloudflare Image Resizing (proxy)	WordPress guide
Self-hosted	Any CI/CD pipeline, Docker, or manual	—	Self-hosted guide

GitHub Action

These platforms deploy from GitHub repositories. Add pageflare as a step in your GitHub Actions workflow using the official action:

- name: Build site
  run: npm run build

- name: Optimize with pageflare
  uses: getappz/pageflare-cli@v1
  with:
    args: "dist/ --in-place"

Platform	Build System	Output Directory
AWS via Flightcontrol	GitHub Actions	dist/ (varies by framework)
Azion	GitHub integration	dist/
Buddy	GitHub integration	dist/
Deno Deploy	GitHub Actions	dist/
EdgeOne Pages	GitHub integration	dist/
Render	GitHub auto-deploy	dist/
Stormkit	GitHub integration	dist/

Tip

Any platform that deploys from a GitHub repository can use the official GitHub Action. If your platform connects to GitHub but isn’t listed above, the same pattern applies — add the action step between your build and deploy steps.

GitLab CI

For platforms that deploy from GitLab, add pageflare to your .gitlab-ci.yml:

optimize:
  stage: build
  image: node:22
  script:
    - npm ci
    - npm run build
    - npx @pageflare/cli dist/ --in-place --no-progress
  artifacts:
    paths:
      - dist/

Platform	Notes
GitLab Pages	Use the pipeline above with the pages job name and public/ as the output directory

Build Command Override

These platforms let you customize the build command in their configuration file or dashboard. Append pageflare to your existing build command:

npm run build && npx @pageflare/cli dist/ --in-place --no-progress

Platform	Where to configure	Notes
AWS via SST	sst.config.ts or build command	Works with SST’s static site construct
Clever Cloud	Dashboard or CC_BUILD_COMMAND env var	Set output directory to match your framework
Firebase Hosting	Build before firebase deploy	Run pageflare after build, before deploy
Fleek	fleek.json or dashboard	Static sites only
Fly.io	Dockerfile	See self-hosted Docker guide
Google Cloud (App Engine / Cloud Run)	cloudbuild.yaml or build script	Add as a build step before deployment
Heroku	package.json build script	Add to "build" script in package.json
Railway	railway.json or dashboard	Customize the build command
Seenode	Dashboard build command	Static or Node.js hosting
Sevalla	Dashboard build command	Static site hosting
Surge	Local CLI	Run pageflare dist/ --in-place && surge dist/
Zeabur	Dashboard or zbpack.json	Customize build command
Zerops	zerops.yml build section	Add pageflare to the build pipeline
Zephyr Cloud	Build configuration	Static sites only

Other Platforms

For platforms not listed above, use the self-hosted guide. The pattern is always the same:

# 1. Build your site
npm run build

# 2. Optimize
npx @pageflare/cli dist/ --in-place --no-progress

# 3. Deploy with your platform's CLI or method

CI/CD Quick Reference

pageflare provides multiple install methods for CI environments:

Method	Command	Best for
GitHub Action	uses: getappz/pageflare-cli@v1	GitHub-based workflows
npm	npx @pageflare/cli	Any Node.js environment
Shell installer	curl -fsSL https://get.appz.dev/pageflare/install.sh | sh	Non-Node.js CI environments
Docker	docker run --rm -v $(pwd):/site pageflare/cli /site	Containerized pipelines

See the CI/CD guide for detailed configuration options.