Render

Render provides static site hosting with automatic builds from Git. pageflare integrates as part of the build command — Render runs your build, pageflare optimizes the output, and Render deploys the result.

How It Works

Override the build command in Render’s dashboard or render.yaml to chain pageflare after your framework’s build step.

Step 1 — Install pageflare

Add pageflare as a dev dependency so Render installs it automatically:

npm install -D @pageflare/cli

Step 2 — Configure the Build

Dashboard

In your Render service settings, set the Build Command to:

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

Set the Publish Directory to dist/ (or your framework’s output directory).

render.yaml

render.yaml

services:
  - type: web
    name: my-site
    env: static
    buildCommand: npm install && npm run build && npx @pageflare/cli dist/ --in-place --no-progress
    staticPublishPath: ./dist

Step 3 — Pro License

1. Go to your service in the Render dashboard.
2. Navigate to Environment.
3. Add a variable named PAGEFLARE_LICENSE with your license key.

Step 4 — Verify

After deploying, check the Logs tab in the Render dashboard. Look for the pageflare summary near the end of the build:

  Done  145.2 KB saved (38.1%)  1.2s
  Files  42 total, 38 optimized, 4 unchanged, 0 errors

Framework Output Directories

Framework	Output directory
Astro	dist/
Next.js static export	out/
Hugo	public/
Vite	dist/
Eleventy	_site/
Docusaurus	build/

Troubleshooting

Build fails with “command not found” Make sure @pageflare/cli is in your devDependencies. Render installs dependencies before running the build command.

pageflare processes 0 files The output path in the build command doesn’t match where your framework writes output. Update the path to match your framework’s output directory.