Tool profile
Lume: cost, fit and limits
Lume is a static site generator for Deno, maintained by Óscar Otero, that turns Markdown and many template languages into websites using a single configuration file, with plugins and processors for assets. Output carries no extra client-side JavaScript of its own.
What to know first
Lume reads a single _config.ts or _config.js file and builds pages from many template engines, including Markdown, Vento, Nunjucks, Liquid, JSX, TSX, Pug and Eta. Data can come from JSON, YAML, or JavaScript and TypeScript modules that query databases or APIs. The page says it outputs only your code, with no extra client-side JavaScript. It gives no price and mentions sponsorship through GitHub Sponsors and Open Collective.
Lume at a glance
| Maker | Óscar Otero (maintainer; no company named on the vendor page), Not stated on the vendor pages |
|---|---|
| Free plan | Yes |
| Entry price | Quote only |
| API access | No |
| Category | Best AI Static Site Generators in 2026, rank 10 of 13 |
| Website | lume.land |
Who Lume is best for
TypeScript developers
Configuration can live in _config.ts, and TSX and JSX templates are among the supported engines, so a developer can stay in typed code from settings to templates.
Sites that pull data from APIs
JavaScript or TypeScript modules can fetch data from databases or APIs, which suits a site whose pages depend on external records instead of only local files.
Authors who want clean output
The page says Lume outputs only your code with no extra client-side JavaScript. That suits a plain, fast site where the developer wants full control over what ships to the browser.
Lume plans and pricing
| Plan | Price | What it includes |
|---|---|---|
| Open source | Free, sponsorship options | Sponsorship runs through GitHub Sponsors and Open Collective. The homepage gives no price information or license terms, so the free label reflects the absence of any listed fee. |
Checked November 2026.
What Lume does
- Many template engines
- Markdown, Vento, Nunjucks, Liquid, JSX, TSX, JavaScript, TypeScript, Pug and Eta are supported, and custom engines can be added through the plugin system. Teams can reuse templates from other tools.
- Flexible data sources
- JSON and YAML files are accepted, and JavaScript or TypeScript modules can pull data from databases or APIs. Pages can then be generated from that data, not only from local files.
- Single config file
- Settings and plugins sit in one _config.ts or _config.js file. A reviewer can see the entire setup in one place, which helps when onboarding a new contributor.
- Asset processors
- Processors compile and optimize CSS and JavaScript and transform HTML through the DOM API. Optimization therefore happens in the build, with no separate asset tool listed on the page.
- Event scripts
- Scripts or JavaScript can run after events such as afterBuild. That allows steps like copying files or notifying a service once a build ends, without leaving the Lume configuration.
How Lume handles your data
The vendor homepage states no data practices, retention terms or certifications, and gives no hosting region because Lume only builds files. The page names GitHub, GitLab, Codeberg Pages, Netlify, Vercel or a VPS as places to deploy, so reader data depends on whichever host a site owner picks. The generator runs on the developer's machine and the page says its output adds no client-side JavaScript of its own. Nothing about telemetry or training on customer content is stated.
Where Lume falls short in practice
- Deno-oriented tooling. The page lists Deno among its integrations and configures through TypeScript or JavaScript. Teams standardized on other runtimes face an extra tool to maintain on build machines.
- Single named maintainer. The vendor page names an individual and no company. Buyers who need a supplier for a contract, support or an escalation path do not find one described on the page read.
- No pricing or AI feature. The homepage mentions sponsorship only and names no AI feature. A buyer evaluating budget or machine assistance must look elsewhere for answers. A buyer comparing budget or machine assistance must look to other sources for answers, since the homepage gives no help.
Works with
Alternatives to Lume
Lume: common questions
What does Lume need to run?
The page lists Deno among its integrations and configures through a _config.ts or _config.js file. It does not give a minimum Deno version, so check the project documentation before setting up a build machine. Pin the Deno version in your CI configuration so builds on other machines match your local one.
Which template languages does Lume support?
Markdown, Vento, Nunjucks, Liquid, JSX, TSX, JavaScript, TypeScript, Pug and Eta are named, and custom engines can be added through plugins. That is a wider list than most generators show on a homepage. Teams can reuse templates they already wrote for another generator, and add engines through plugins when the list falls short.
Where can a Lume site be deployed?
The page names GitHub, GitLab, Codeberg Pages, Netlify, Vercel or a VPS. Since the output is static files, any host that serves them should work, but those are the ones the page names. Pick one of those hosts and test the first deploy, because the page documents the list only briefly.
Does Lume cost anything?
The homepage gives no price. It mentions sponsorship through GitHub Sponsors and Open Collective, which are voluntary, and it does not describe license terms, so confirm the license in the repository before commercial use. Sponsorship is voluntary, so budget hosting and maintainer time yourself rather than a license fee.
Does Lume add JavaScript to my pages?
The page says Lume has zero runtime overhead and outputs only your code with no extra client-side JavaScript. Any scripts that reach the browser come from your own templates, processors or plugins. Review the output folder for scripts before launch, since the claim covers Lume itself, not your add-ons.