  ____  _     ____  _     ____  _      _     _  __ _____
 /   _\/ \   /  _ \/ \ /\/  _ \/ \  /|/ \ /\/ |/ //  __/
 |  /  | |   | / \|| | ||| | \|| |\ ||| | |||   /|  \  
 |  \__| |_/\| \_/|| \_/|| |_/|| | \||| \_/||   \ |  /_ 
 \____/\____/\____/\____/\____/\_/  \|\____/\_|\_\\____\

CloudNuke Software Collective

RealFCC
CloudNuke.org, 2026

What we are

The CloudNuke Software Collective is a small, independent body dedicated to one purpose: keeping software small, auditable, and free, and keeping the services people depend on out of corporate hands.

We are not a foundation with a board and a mailing address. We are a collective, held together by a shared conviction that the user must remain sovereign over the machine. Where larger organizations have grown cautious, bureaucratic, or compromised, we intend to stay small enough to say exactly what we mean.

Our principles

Freedom is not negotiable

Software must respect the four freedoms: to run it, to study it, to redistribute it, and to improve it and share those improvements. Anything less is a leash, no matter how convenient the leash is made to feel.

Auditable over convenient

A tool you cannot read is a tool you cannot trust. We favor small, legible codebases over sprawling ones, even when the sprawling ones ship more features. A feature you cannot verify is not a feature; it is a liability you have agreed to carry.

Federated over centralized

No single server, and no single company, should hold a monopoly on how people communicate. We build and host on protocols anyone can run for themselves: XMPP, Mumble, and whatever comes next that keeps this promise.

No telemetry, no accounts, no compromises

We do not collect what we do not need, and we do not need almost anything. Every account we do not require is a person we cannot be pressured to hand over.

What we do

The Collective maintains community infrastructure and writes the software that keeps it running. This includes:

Hosting free, federated communication services under CloudNuke.org, including XMPP and Mumble, open to anyone who wants to use them.
Writing and maintaining small, auditable C software: allocators, package managers, media tools, and the utilities that keep a minimal system livable.
Documenting how to run the same services yourself, so that no one has to depend on us either.
Speaking plainly about which software respects you and which software does not, without softening the message to protect anyone's feelings, including our own.

Why "collective" and not "foundation"

A foundation implies permanence, staff, and process. We do not promise any of that. What we promise is a standard: every piece of infrastructure we run and every line of code we publish will meet the same bar of freedom, simplicity, and auditability, for as long as the Collective exists.

If that standard ever slips, the Collective has failed at the only thing it exists to do.

How to join

The Collective is not a membership you apply for. It is a practice you take up.

Run something free, and run it for others where you can.
Audit what you depend on, and stop depending on what you cannot audit.
Contribute code, documentation, or infrastructure back to the projects that make this possible.
Tell someone else, plainly, why it matters.

If you are already doing this, you are already part of it.

RealFCC
CloudNuke.org, 2026

Back to CloudNuke