Static sites and SPAs
Deploy a Eleventy site on Enzonic
Eleventy turns templates and Markdown into a static site in _site. Deploy runs your build script, or npx @11ty/eleventy when there is none, and serves the result from the edge.
At a glance
What Enzonic Deploy does with a Eleventy project when you connect it. You can override any of it in the project settings.
- Language
- JavaScript
- Detected from
- @11ty/eleventy in dependencies
- Build command
- npx @11ty/eleventy (or your build script)
- Output
- _site
- Runs as
- Static
Dependencies install with the package manager your lockfile names: npm ci, pnpm install --frozen-lockfile, yarn install --immutable (Berry) or --frozen-lockfile, or bun install --frozen-lockfile. Node.js 18, 20, 22 and 24 are available. Deploy reads engines.node in package.json, then .nvmrc or .node-version, and uses Node.js 22 when nothing pins a version.
How it runs
Static
Always.
Deploy Eleventy step by step
- 1Connect the repository and deploy; no configuration needed for the default _site output.
- 2If eleventy.config sets another output dir, set the same folder as the output directory in the project settings.
Connect a database to Eleventy
Create a database on Enzonic Databases (or from the project's settings) and its connection string is added to the project's environment variables. This example uses Valkey.
import { createClient } from 'redis';
const redis = await createClient({ url: process.env.REDIS_URL }).connect();
export async function POST(request) {
const { path } = await request.json();
return Response.json({ views: await redis.incr(`views:${path}`) });
}Postgres projects get two variables: DATABASE_URL through the connection pooler for the app, and DATABASE_URL_UNPOOLED for migrations.
Valkey on Enzonic DatabasesEvery database engineThings to know
- Changing the output folder in the Eleventy config without changing the project setting leaves Deploy looking for _site.
Plan limits that matter here
From the live plan data. Every plan includes previews for each branch, instant rollback, environment variables and logs.
| Limit | Free | Pro |
|---|---|---|
| Build minutes | 3,000/mo, 1 concurrent | 10,000/mo, 3 concurrent |
| Function memory / timeout | 1 GB / 300 s | 4 GB / 1800 s |
| Function invocations | 2 M/mo | 20 M/mo |
| Bandwidth | 150 GB/mo | 2 TB/mo |
Related guides
- Deploy a Hugo siteHugo sites built with hugo --gc --minify, Hugo extended included.
- Deploy a Astro siteStatic Astro sites by default, server output with @astrojs/node.
- Deploy a Static HTML sitePlain HTML, CSS and JavaScript, no build step.
Ship your Eleventy project tonight
Connect the repository and the build settings fill themselves in. Free plan, no card.