Technology for people who refuse to be governed by surveillance.

Activists, journalists, organisers and dissidents whose communications are, or may be, watched.

People in countries that block websites, fingerprint VPNs or switch the internet off.

Anyone who wants to hold and move value without asking permission, and without broadcasting their finances.

Operators who want to add capacity and independence to free networks.

Developers and engineers designing systems that should not need to be trusted.

People who want to own their identity, audience and reputation instead of renting them from platforms.

Publishers, maintainers and archivists planning for the loss of a host or a name.

Release a test secret only after the workload, hardware evidence and communication channel satisfy your policy.

Confirm who signed the bytes you will run, then ask whether those bytes can be rebuilt from the published source.

Before choosing a single tool, write down what you are protecting, who you are protecting it from, and what failure would cost you.

When a single mistake or a single exploit would be catastrophic, the operating system has to enforce the discipline for you.

Metadata cleanup, safe rendering and redaction solve different problems. Use the right step for each, then inspect the actual file you will send.

Every one of these networks is only as strong as the number of independent people running it. Here is how to become one of them.