Start free →
No-KYC hosting

Host anything.
No identity check, ever.

Freehold’s signup form has two fields: email and password. There is no ID upload, no phone verification, and no “verify your identity” step that appears once you scale. Deploy a container, a repo, or a one-click app, and every app comes up with a free Tor .onion address.

Start free →Browse the app catalog

What “no KYC” actually means here

The whole signup form

Email and a password. Or continue with GitHub and skip even that. No legal name, no date of birth, no phone number, no company, no tax ID, no document upload — at signup or ever after.

No verification step waiting at scale

Most hosts skip ID for a small account, then add a “verify your identity” gate once you spend more or your card gets flagged. Freehold has no such step to introduce. There is no tier where KYC turns on.

Behaviour is what gets checked

No KYC doesn’t mean no rules. You agree to the Terms and the Acceptable Use Policy, and abuse still gets a container stopped. What we look at is what the workload does — not who you are.

No identity documents at the till

Payment is by card, through Stripe — that processor has its own checks, but Freehold adds none of its own. No legal name, no address verification, no ID upload on top.

No provider to lean on

You never pick a cloud, a region, or a server. Freehold places and moves workloads across its own infrastructure — so there is no single vendor whose compliance desk holds your off switch.

A free .onion on every app

Every deployment comes up with a Tor hidden-service address alongside its normal URL. No fixed IP in a DNS record, no add-on to buy.

The trade-off, stated plainly

Some payment processors and some enterprise buyers will always want KYC from a hosting provider, and Freehold loses that business. That is the deal: refuse to ask, and some doors close. Freehold is built for the people the form was keeping out — developers shipping side projects, journalists and researchers who can’t hand a vendor their real name, teams in places where “business email required” is a wall.

Read the longer version: Why Freehold Doesn’t Do KYC.

No-KYC hosting: common questions

Do I need to provide ID to sign up for Freehold?
No. Freehold asks for an email and a password, or a GitHub login. It never asks for a government ID, a passport scan, a phone number, a legal name, or a business registration — not at signup and not later as your usage grows.
Is there a KYC check once I scale up or spend more?
No. The point at which most hosts introduce identity verification — more usage, a bigger card, a flagged payment — is exactly where Freehold has nothing to introduce. There is no plan or threshold where KYC begins.
Can I use Freehold anonymously?
You can sign up and deploy without giving Freehold any identifying information. The exception is payment: a card is required and it goes through Stripe, which has its own requirements — that link Freehold can't remove. Every app also gets a Tor .onion address so it can be reached without touching the clearnet.
If there is no KYC, how does Freehold handle abuse?
By behaviour, not identity. Every workload runs isolated in its own container, usage is metered, and the Acceptable Use Policy is enforced per app — a container running a spam campaign or attacking other hosts gets stopped. Freehold does not need your passport to detect that.
Does "no KYC" mean Freehold is unregulated or offshore?
It means Freehold made a product decision not to collect identity documents, and structured its payments and infrastructure so it does not have to. You still get a real Terms of Service, a published Acceptable Use Policy, and a contactable support address.

Start free. No ID, ever.

One-click apps, GitHub repos, Docker images — hourly billing with a hard cap, Tor .onion free on every one.

Start free →See pricing