Sovereign Static Hosting: A Small Business That Doesn't Need Scale

The niche is the promise

A one-person hosting business can stay small if the offer fits on one page. The customer sees the stack, the price, and the support limit before asking for a call. That clarity is the product: where the files sit, who touches them, and what happens when the customer leaves.

Static sites are a useful starting point because the workload is boring in the best way. Pages, images, styles, scripts, maybe a small form. No database, no server-side logic, no nightly migrations. The operator can promise a small set of behaviors and keep them.

The offer can be stated as a short rule.

• Static files only: any git provider or static site generator that outputs static files works.
• European-owned infrastructure: the git-deploy and CDN layers operate on it.
• No AWS or Cloudflare: both are excluded from the hosting stack.
• Simple pricing with capped support.

The rule works because it is easy to check. A prospect can look at the site, inspect the build output, and see that the product matches the stated scope. When the promise is narrow, trust becomes a feature.

Scale adds work

Growth usually adds work faster than it adds margin. More customers bring edge cases, more features bring dependencies, and more dependencies bring on-call hours. A small host can avoid that by refusing the parts of hosting that turn a website into a system.

A short customer list is easier to support than a long tail of edge cases. The operator can learn each site, know its build, and answer questions without a ticket queue.

The refusal is the business model. Static sites remove application servers, database patches, and runtime upgrades. Named infrastructure keeps the stack explainable. Capped support keeps the operator out of free consulting.

Margin comes from saying no early. A contact form can be served. A member area, a payment flow, or a custom API can be declined. The business stays small because the product stays legible.

The objection is real, but narrow

The strongest objection is that sovereignty sounds like a sysadmin burden. You tell customers you care about ownership, then they expect you to own the whole stack. The fear is fair. Self-hosting comments make it concrete.

atoav said on July 27, 2025 that he self-hosts his web servers because his web host charged a premium for SSL certificates. poisonborz said on July 27, 2025 that he had 15 years of self-hosting experience. irishloop said on July 27, 2025 that self-hosting still depends on service providers, hardware, UPS battery backup, RAID drives, and backups. Those comments describe a different job: owning machines, not selling a boundary.

The scope protects the operator from extra work. A customer who wants a new feature can be told that the product is for static sites. That answer is the product working. The customer is buying a clear line: what is included, what is excluded, and what support looks like.

A written scope does the selling

A scope page lists the included behaviors, the excluded behaviors, and the support window. When a prospect reads it, the easy customers self-select.

Keep support inside the promise. Answer questions about the promise, not about every possible web problem. Help a customer connect a repository, build a site, or read a status page. Do not become a general web agency.

If a customer needs a database, a server-side app, or a custom integration, that is a different business. Say so. Run the business like a small shop with a clear sign. The sign says what you will do, what you will not do, and how much it costs. If the next customer would require a new system, a new platform, or a new support queue, the answer is no.