Ship Eleventy (11ty) in ~2 minutes.

Why Percher fits

• Build output ships as a slim Caddy container (multi-stage Docker — Bun runs `npx @11ty/eleventy`, Caddy serves `_site/`). Cold start is instant.
• Bun's `npx` runs eleventy as fast or faster than Node's; redeploys with unchanged dependencies finish in seconds.

Quick start

bunx percher create my-app --template eleventy
cd my-app
bunx percher publish

The first command scaffolds a working Eleventy (11ty) project plus a percher.toml. Publish builds and deploys it, then prints the live URL.

percher.toml

The canonical config for a Eleventy (11ty) app on Percher. bunx percher init generates this automatically when it detects Eleventy (11ty) in your project.

[app]
name = "my-site"
runtime = "docker"
framework = "eleventy"

[web]
port = 8080
health = "/"

Common gotchas

• The output directory is `_site` (Eleventy's default) — that's what the generated Dockerfile copies into the Caddy image.
• Don't set the SPA `try_files` fallback in the Caddyfile — Eleventy emits a real HTML file per route, and the fallback would mask real 404s.

Related docs

• Recommended setup →