Static sites are now a first-class resource on Miget, and they are free. Not free-tier free, not free-until-you-grow free: a static site costs nothing, on any plan, with no cap on how many you run.
A built site does not need a container, a replica or a port. It is served straight from object storage, so it does not need a compute resource - and it does not consume the one you are already paying for. Your applications keep the whole plan to themselves.
Four ways in
- GitHub. Connect a repository, pick a branch, and every push builds and publishes.
- Git Push. Push to a Miget remote, same as an application.
- Zip upload. Drag a built bundle onto the page.
- SFTP. Upload a directory with the tooling you already use.
Builds with nothing to configure
For the git-based sources, Miget detects the framework across 33 generators and builds with that generator's defaults. When detection gets it wrong, override the generator, the build command, the output directory, or the path to a site inside a monorepo.
SPA mode serves /index.html for unknown paths, so client-side routes survive a refresh instead of returning a 404.
Deployment history you can act on
- Cancel a running build without waiting for it to fail.
- Roll back a GitHub site to the commit a previous deployment shipped.
- Browse the files currently deployed, to confirm what actually landed rather than what you think you pushed.
Custom domains work exactly as they do for applications, with the same automatic TLS.
What it costs
Nothing. There is no per-site charge, no build-minute charge, and no bandwidth charge - Miget does not meter bandwidth on any plan. A static site is not a component on your subscription, so adding one does not change your bill and deleting one does not reduce it.
That also means a static site does not need a paid plan behind it. An account on the free tier can run them.
When to use one
A static site is the right resource for documentation, a marketing site, a landing page, a client's brochure site, or the built output of any front-end framework that produces files rather than a server. Anything that has to run code on request - server-side rendering, an API, a form handler - is still an application.
The practical effect is that the small sites that used to sit awkwardly on a compute plan stop competing with your applications for it.