webapp.mk
Features

Static sites

Publish a static website from GitHub, any Git repository or a zip archive. It is served over HTTPS.

Static sites

How it works

  1. Git branch or zip
  2. Fetched on a timer
  3. Served by the load balancer
  4. HTTPS
Smallest size
  • cpu0.1 vCPU
  • ram0.12 GB
  • storage50 MB
In plans

6 of 6

paid plans include it

Static sites

Four ways to deploy

Pick the source when you create the site. You can later serve another branch, folder or archive on the same address.

GitHub repository

Connect your GitHub account, then pick a repository and a branch from a list. Private repositories work through the connection.

  • Serve the whole branch or one folder of it, such as dist
  • Checked on a timer, and Redeploy fetches it at once

Any Git repository

GitLab, Bitbucket, Gitea or your own server, over HTTPS or SSH.

  • Public, or with an access token or an SSH key
  • A branch and an optional folder

Archive URL

A zip the realm downloads from an address you give, such as a release artifact from your CI.

  • Downloaded and unpacked again on every sync
  • Private downloads with a bearer token, a login or a header of your own

Uploaded archive

Upload a zip of the built site in the control panel, or with webappmk sites upload.

  • Checked before it goes live
  • index.html at its root, or inside its single top-level folder
Static sites

How it is served

Each site has its own storage and serving options, set when you create it and changed later.

Routing

Plain static files, a single-page app that answers every path with index.html, or clean URLs without .html.

HTTPS

A certificate is issued and renewed for its address, whether a platform hostname, a subdomain or your own domain.

Fast by default

Compression, caching of static assets and blocking of common exploit paths, each one a switch.

Export it

Export the site definition as a file and import it elsewhere.

Static sites

Who it is for

Designers and freelancers

Portfolios, landing pages and client sites.

Docs and blog authors

Documentation, changelogs and blogs.

Developers

A front end that talks to your own API.

  • Portfolio
  • Landing page
  • Documentation
  • Blog
Static sites

Build elsewhere, publish the output

The platform does not run builds. Build on your machine or in CI and commit the output folder to the branch the site follows. There is no push webhook: the branch is checked on a timer, and Redeploy fetches it at once.

ToolBuild commandOutput folder
AsAstronpm run builddist
ViVite (React, Vue, Svelte)npm run builddist
NeNext.jsnext build (with output: export)out
HuHugohugopublic
JeJekylljekyll build_site
ElEleventynpx @11ty/eleventy_site
DoDocusaurusnpm run buildbuild
PlPlain HTML—the folder itself

Start with a free static site

Add resources when you need them.