Service line

Web hosting run by the people who run the proxy

Every site we host sits behind the same reverse proxy, certificate automation, and DNS discipline we use for our own production properties. You get a real hostname, a real certificate, and a deploy that does not involve a control panel guessing at your intent.

How we approach it

Most web hosting problems are not web server problems. They are certificate renewal problems, DNS problems, redirect-loop problems, and cache problems. We treat those as the actual product: canonical host selection, HTTP to HTTPS enforcement, apex to www redirection, and certificate lifecycle are configured once and then monitored, rather than left as a checkbox you discover was wrong six weeks later.

Underneath, sites run on our Kubernetes tier behind NGINX Proxy Manager. TLS terminates at the edge; your workload speaks plain HTTP inside the cluster and never has to care about certificate rotation. Static publishing, dynamic application containers, and PHP content platforms all use the same routing path, so moving up a tier does not mean changing how your domain works.

Who this is for, and what is included

Who this is for

  • Small businesses and studios who need a professional site without hiring an ops person
  • Agencies maintaining several client sites who want one operator and one invoice
  • Technical owners who already build a static bundle and just want it served correctly
  • Anyone leaving a shared host where support tickets go into a void

Included across every tier

  • Managed TLS certificates with automated renewal
  • Canonical hostname policy: apex redirects to www, HTTP redirects to HTTPS
  • HTTP/2, gzip and brotli compression, and sane cache headers
  • Deploy from a Git repository or an uploaded build artifact
  • Daily snapshot of the published tree, retained for two weeks
  • Direct operator contact by email, not a ticket queue robot

Tiers in this service line

Every tier is operator-provisioned and every specification below is what we build to.

Comparison of Web hosting and sites tiers
Tier Monthly Annual Best for Details
Static Site Entry $9 $90 −17% A published build, served fast, with certificates that renew themselves. Details
Business Site Most common $24 $240 −17% A dynamic site with a runtime, a database, and somebody watching it. Details
Managed WordPress $32 $320 −17% WordPress with the maintenance treated as the actual product. Details
Multi-site Portfolio $79 $790 −17% Several sites, one operator, one invoice, one set of conventions. Details
Entry

Static Site

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

$9 /mo

  • Managed TLS and canonical hostname policy
  • Deploy from Git or an uploaded build artifact
  • Daily snapshot of the published tree

View details

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

Other service lines