Deploy anything on Freehold — a one-click app, a repo, a Docker image — and it comes up with two addresses: the public URL you’d expect, and a Tor v3 hidden-service address, live from the first deploy, at no extra cost. No sidecar, no torrc, no reverse proxy to configure.
Most platforms that support Tor treat it as advanced configuration — a proxy you wire up, a 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 provisions the onion service the same way it provisions the URL and the certificate: one step, no decision.
The onion service is provisioned in the same step as your public URL and TLS certificate. No sidecar to add, no torrc to write, no reverse proxy to wire up.
There is no “Tor” line item on the pricing page. It ships with a 512 MB app the same as an 8 GB one, because charging extra for privacy would defeat the point of offering it.
A working .onion means your app can be visited with no DNS record pointing at a fixed IP, and nobody between the user and your app watching where the traffic goes.
You still get the ordinary HTTPS address for everyone else. The onion is additive — use it, ignore it, or make the app onion-only if that fits.
A private Vaultwarden vault, a Mattermost for a group that doesn’t want its server logged as a normal website, a personal Nextcloud you don’t want indexed anywhere.
Signup is an email or a GitHub login. There is no identity check to deploy an app, and therefore none to get its onion address.
Tor Onion Services, Free, on Every App — the reasoning, and what a working onion address gets you in practice.
Free on every plan, generated automatically, no ID to sign up.