No-KYC Hosting for operators who need privacy on signup.

Know Your Customer is a regulatory framework that originated in financial services to combat money laundering. Banks, exchanges, brokerages, and payment processors collect identification under explicit legal mandates. The expectation is that they will refuse service or report suspicious activity based on the identity collected.

Over the last decade, KYC has crept into industries where it has no legal basis. Hosting providers started requesting government IDs because their fraud-detection tooling failed at scale, not because regulation required it. Email service providers started demanding incorporation documents because they were sued under DMCA and wanted a name to point at. Domain registrars started verifying phone numbers because their resellers asked for it.

The compounding effect is that running a normal commercial operation now requires handing identity attestations to dozens of providers, each of which becomes a potential leak surface. A single security incident at one of them exposes the connection between your operational and commercial identities. This is unhelpful when the threat model is anything beyond "consumer with nothing to hide."

We push back against this drift. We require only what we functionally need to deliver the service: a way to reach you (email) and a way to receive payment (crypto). Anything beyond that is either compliance theatre or data we'd rather not hold.

No-KYC at signup does not mean we will host anything. Our acceptable use policy excludes specific categories: child sexual abuse material (CSAM), malware command-and-control infrastructure, phishing operations that target consumers, and infrastructure deliberately built to facilitate fraud. These exclusions are categorical and we enforce them through operational monitoring and abuse reports.

We also reserve the right to ask additional questions before provisioning if the service requested has high abuse potential. A bulk SMS infrastructure order will involve a brief conversation about use case. A high-IP-count email setup will involve discussing your sender domains. These conversations do not produce identity records on our side; they exist to ensure we deliver to operators who will run the infrastructure responsibly.

For payments, we work with self-hosted BTCPay Server and our own Monero node, which means no third-party processor sees the transaction. But the source of your crypto, the wallet that sends payment, and the on-chain (for Bitcoin) trail are not under our control. If you need stronger privacy on the payment side, we recommend Monero specifically because its confidential-transactions design addresses this gap.

Finally: no-KYC hosting is not a license to commit fraud against others. If you defraud another customer, run a phishing site, or attempt to use our infrastructure against third parties in a way that generates abuse reports, we will terminate service. We will respond to law enforcement requests in our jurisdiction with whatever operational data exists, which is minimal but not zero.