Entry

Static Site

A published build, served fast, with certificates that renew themselves.

What this tier is

Static hosting should be the least interesting part of your week. You produce a directory of files; we serve it over HTTP/2 with compression, sensible cache headers, and a certificate that renews without anybody remembering to renew it.

This tier suits Hugo, Astro, Eleventy, Jekyll, Vite, and any framework that emits a static bundle, as well as hand-written HTML. There is no application runtime and no database, which is exactly why it is cheap and why it almost never breaks.

Specification

Static Site specification
RuntimeStatic file serving, no application runtime
Storage2 GB published tree
BandwidthFair use, no metered overage billing
Domains1 primary plus subdomain aliases
TLSManaged certificate, automatic renewal
BackupsDaily snapshot, 14-day retention
DeployGit pull or uploaded archive
SupportEmail, operator response within one business day

What is included

  • TLS certificate issued, installed, and renewed automatically
  • Apex redirects to www; HTTP redirects to HTTPS
  • HTTP/2 with gzip and brotli compression
  • Custom 404 page and cache-control policy
  • Deploy from a Git repository or an uploaded archive
  • Daily snapshot of the published tree, fourteen-day retention
  • One domain plus unlimited subdomain aliases onto the same site

Typical use cases

  • A business or portfolio site built with a static site generator
  • Product documentation published from a docs repository
  • A landing page that needs to be fast and needs to stay up
  • An event or campaign microsite with a short life and a real domain

Responsibility split

Written down so there is no argument about it later.

We handle

  • Certificate issuance and renewal
  • Reverse proxy configuration and redirect policy
  • Compression, caching, and HTTP-level tuning
  • Snapshots of the published tree

You handle

  • Building the site and producing the output directory
  • Registering the domain and pointing DNS at us, or delegating it to us
  • Site content, accessibility, and anything that runs in the browser

How provisioning works

Operator-provisioned. After payment we email you within one business day with the deploy target, DNS records to publish, and a checklist for cutover. Nothing goes live until you confirm the DNS change.

Order

Billing period

We use this for the invoice, provisioning updates, and account sign-in.

Leave blank if you want us to suggest one.

Migration deadlines, existing stack, constraints.

Payment is handled by Stripe. We never see or store card details. Continuing means you accept the Terms, Acceptable Use Policy, and Privacy Policy.

Ask a question first

Other tiers in Web hosting and sites

Most common

Business Site

A dynamic site with a runtime, a database, and somebody watching it.

$24 /mo

  • PHP or Node runtime with a managed database included
  • Authenticated SMTP so contact forms deliver
  • Staging hostname for changes before they are public

View details

WordPress with the maintenance treated as the actual product.

$32 /mo

  • Core, theme, and plugin updates applied on a monthly window
  • Staging clone refreshed from production on request
  • Restore tested, not merely configured

View details

Several sites, one operator, one invoice, one set of conventions.

$79 /mo

  • Up to eight sites under one account and one invoice
  • Shared staging conventions and deploy tooling across the portfolio
  • Quarterly review of certificate, DNS, and dependency health

View details