Static Sites
Host static frontends — React, Vue, Svelte, Next.js exports, Hugo, Docusaurus, Astro, plain HTML — built from Git and served from a global edge with free managed TLS.
A static site on Muerte Cloud is a build pipeline plus a global CDN. Link a Git repository, tell us the build command and the output directory, and every push to the deployed branch produces a fresh atomic release. Each site gets a unique *.muerte.app subdomain and can attach any number of custom domains.
Get started#
- 1Create a static siteIn the dashboard, click
New → Static Siteand connect the Git provider that hosts your project. GitHub, GitLab and Bitbucket are supported. - 2Pick a repository and branchEvery push to the deployed branch triggers a new build.
- 3Configure the buildSet the build command that produces static artifacts, and the publish directory that contains them. Common values are shown below.
- 4Create the siteClick Create Static Site. Muerte Cloud runs the first build and publishes the result to the global edge — usually within a minute for small sites.
Common framework defaults
| Framework | Build command | Publish directory |
|---|---|---|
| Vite / React / Vue | npm ci && npm run build | dist |
| Create React App | npm ci && npm run build | build |
| Next.js (static export) | npm ci && npm run build | out |
| Astro | npm ci && npm run build | dist |
| SvelteKit (static adapter) | npm ci && npm run build | build |
| Docusaurus | npm ci && npm run build | build |
| Hugo | hugo --minify | public |
| Jekyll | bundle install && bundle exec jekyll build | _site |
| Plain HTML | (leave empty) | . |
Features#
Global edge network
Static sites are cached on edge nodes around the world. Muerte Cloud routes each visitor to the nearest node, so first-byte latency stays low regardless of where your build is stored.
Pull request previews In development
Per-PR preview sites with their own isolated URL are in development and not yet available.
Redirects and rewrites
Define redirect and rewrite rules from the dashboard, or check in a _redirects file at the root of your publish directory. Both approaches support permanent, temporary and SPA-fallback rules.
# Permanent redirect
/old-page /new-page 301
# SPA fallback — send unmatched routes to index.html
/* /index.html 200HTTP is redirected to HTTPS automatically — no rule needed.
Custom response headers
Attach security and caching headers per path pattern from the dashboard, or ship a _headers file with your build.
/*
X-Frame-Options: DENY
Referrer-Policy: strict-origin-when-cross-origin
/assets/*
Cache-Control: public, max-age=31536000, immutableAtomic deploys and instant cache invalidation
Every successful build is published as a single immutable snapshot. The edge switches all traffic to the new snapshot in one step and invalidates old assets immediately, so visitors never see a mixed version of your site.
Managed TLS
TLS certificates are issued and renewed automatically for the default *.muerte.app hostname and for every attached custom domain, including wildcards. There is no setup and no additional charge.
Custom domains
Attach any number of apex and wildcard domains from the site's Domains tab. Follow the DNS instructions shown for your registrar and TLS is provisioned within seconds of propagation. See Custom domains for the full walkthrough.
Dependency installation
Muerte Cloud auto-detects Node.js, Ruby, Python, Go, Elixir and Rust toolchains and installs dependencies before running your build command. To install them yourself — for example to pass custom flags — set the SKIP_INSTALL_DEPS environment variable to true and include the install step in your build command.
.nvmrc, .tool-versions or runtime.txt file to lock the exact toolchain used at build time. It's the most reliable way to keep builds reproducible.