Ask most hosting platforms where your app actually runs, and you'll get a specific answer: a named cloud, a named region, sometimes a named data center. That specificity is normally sold as a feature — predictability, compliance, choice. It's also a single point of failure: one company's policies, one company's compliance department, one company that can be subpoenaed, pressured, or simply decide your app violates a term you didn't know existed.

Deploying on Freehold doesn't involve choosing a provider, a region, or a specific server. You pick an app — one of the hundreds in the marketplace, or your own image or repo — and it goes live. That's a deliberate removal of a decision, not a missing feature: Freehold's backend places and moves workloads across its own infrastructure automatically, and you never manage or choose individual servers.

The same design that removes the "which provider" decision also means there's no single provider whose policies determine whether your app stays up. Nobody owns the off switch. If a decision needs to get made about what stays online, it isn't a call one infrastructure vendor's terms-of-service team gets to make unilaterally.

You give up the ability to say "put this specific app on this specific box in this specific region" — if you need that level of control for compliance reasons, Freehold isn't the right fit. What you get instead is a platform where the infrastructure layer isn't a lever anyone can pull against you.

Provider-Agnostic Infrastructure: No Lock-In, Either Direction

Deploy anything on Freehold — Nextcloud, an app you pushed straight from GitHub, one of the hundreds of marketplace templates — and it comes up with two addresses. One is the public URL you'd expect. The other is a Tor .onion address, live from the first deploy, at no extra cost.

Most platforms that support Tor treat it as advanced configuration: a reverse proxy you wire up yourself, a sidecar container you have to know to add, sometimes a paid tier. That framing quietly filters out everyone who isn't already deep enough into infrastructure to go looking for it. Freehold generates the onion service automatically at deploy time, the same way it provisions the public URL and TLS certificate — same step, no extra decision.

A working onion address means your app is reachable without ever touching the clearnet — no DNS record pointing at a fixed IP, nobody between your users and your app watching where the traffic goes. That matters differently depending on what you're running: a private Vaultwarden vault, a Mattermost instance for a group that doesn't want its server logged as a normal website, or just a personal Nextcloud you don't want indexed anywhere.

There's no "Tor" line item on Freehold's pricing page. It ships with every size, on every app, because treating privacy as a premium feature would defeat the point of offering it at all.

Tor Onion Services, Free, on Every App

Most hosting platforms start you off with just an email and a password. Then, at some threshold — more usage, a bigger card, a support ticket that touches billing — the form changes. A "verify your identity" step appears: a government ID upload, a phone number tied to a real name. It's rarely announced up front, because it doesn't need to be — it happens gradually enough that most people don't think of it as a rule, just a growing pain.

Freehold's signup form has two fields: email and password. Or you can skip both and continue with GitHub. That's the whole form — not a streamlined version of a longer one, the entire thing. No legal name, no date of birth, no phone verification, no business tax ID, no passport scan.

The easy version of this promise is free: any platform can skip ID checks for a small hobby account. The commitment is what happens as you scale — more apps, more traffic, a card that gets flagged for review. That's exactly the point at which most platforms introduce KYC, framed as a compliance requirement rather than a product decision. Freehold doesn't have that step to introduce. There's no tier where it turns on.

No KYC doesn't mean no accountability — you still agree to Freehold's Terms of Service and Acceptable Use Policy, and abuse still gets accounts suspended. It just means what gets checked is behavior, not identity documents. We don't need your passport to tell that a container is running a spam campaign.

This is a real trade-off, not a hidden win. Some payment processors, and some enterprise customers, will always want KYC from a hosting provider, and Freehold will lose that business. That's the deal: refuse to ask, and some doors close. We'd rather build for the people the form was actually keeping out.

Notes on how Freehold works,
and why.

Provider-Agnostic Infrastructure: No Lock-In, Either Direction

Tor Onion Services, Free, on Every App

Why Freehold Doesn't Do KYC

Notes on how Freehold works,and why.

Provider-Agnostic Infrastructure: No Lock-In, Either Direction

Tor Onion Services, Free, on Every App

Why Freehold Doesn't Do KYC

Notes on how Freehold works,
and why.