Deploy / Hosting is your call

Just files. Any static host.

flame build writes flat .html files to one folder. There is no server runtime and no app to keep running: upload the folder, or let your host build it on every push.

No runtime. No server process.
01 / What the build writes

One command. One folder.

Every page is a flat .html file, and links carry the suffix, so navigation works on any host that serves files by path. Zero configuration.

Read the deployment guide
  1. # 01 Build the site$ bun run build
  2. # 02 Everything lands in one folder$ ls .docu/dist
  3. # 03 Or let Flame set up GitHub Pages$ bun run deploy
flame deploy adds .nojekyll and a GitHub Pages workflow.
02 / Pick a host

Pick a host.
Keep the folder.

All of them serve .docu/dist as it is
Zero configuration

Upload the folder.

These hosts drop the .html suffix on their own. Deploy the build output as it is.

  • Cloudflare Pagesnone
  • AWS Amplify Hostingnone
  • GitHub Pagesflame deploy
  • Clean URLs: automatic
One config file

Turn on clean URLs.

Clean URLs are one setting away. The file sits at the root of your repository.

  • Vercelvercel.json
  • Netlifynetlify.toml
  • Firebase Hostingfirebase.json
  • Azure Static Web Appsstaticwebapp.config.json
  • Renderdashboard rule
  • Herokustatic.json
  • Clean URLs: yes
Docker

Ship an image.

flame deploy --docker writes a Dockerfile, an nginx.conf and a .dockerignore for any host that runs images.

  • CoolifyDockerfile
  • Fly.iofly deploy
  • Railwayauto-detect
  • VPSdocker run
  • nginx
  • --ci builds on push
AWS S3 + CloudFront works too. The .html suffix stays visible without a CloudFront Function.
03 / Subpath ready

At /docs, a prefix, or the root.

meta.basePath sets the prefix inside the build output. meta.baseURL names where your host publishes it. Links, canonical URLs and the search index follow both.

Read the base path guideSee all providers
/docs · /handbook · "" for the root
docu.json
{
  "meta": {
    "title": "Acme Docs",
    "baseURL": "https://acme.github.io/handbook",
    "basePath": "/docs"
  }
}
→ https://acme.github.io/handbook/docs/…

Less platform. More publishing.

Write like a document. Keep plain Markdown. Ship a docs site.

Get StartedOr explore the source on GitHub ↗