Who runs Cabal and how is it governed?

Updated

Cabal is run by volunteers, not a company, and it has no owners. The project describes itself as "private and peer-to-peer, by volunteers and without owners," so there is no central operator, no corporate parent, and no single person who decides what happens next. Governance is informal and community-driven: people contribute when they can, and the project moves at the pace that volunteer life allows.

What "no owners" means in practice

The phrase "without owners" is the clearest statement of Cabal's governance model. There is no entity that holds the platform, sells access to it, or sets policy from the top down. Instead:

  • The software is built and maintained by regular people who volunteer their time.
  • The project has no owner in the sense of a proprietor who can shut it down, change its terms, or monetize it unilaterally.
  • Because it is peer-to-peer, there is no central server operator whose business model depends on the chat traffic.

This is a structural choice, not just a slogan. A peer-to-peer chat platform that works offline does not need a company in the middle, so the project does not have one.

How the project is actually governed

There is no published charter, board, or voting process in the available material. What the project does describe is a volunteer rhythm:

"We are regular people volunteering behind the project and so life has a way of making itself known in various ways, causing periods of downtime and rest in the project."

That sentence is the most concrete governance signal available. It tells you two things:

  1. Decision-making is distributed among whoever is actively contributing. There is no full-time staff whose job is to keep a roadmap on schedule.
  2. Progress is uneven by design. Periods of quiet or downtime are expected, not a sign that the project is abandoned.

The 2025 retrospective notes that the year was "quiet as a project" for exactly this reason. If you are evaluating Cabal for a community that needs predictable release cadence or formal support, that volunteer pace is the main trade-off to weigh.

Who contributes, and how outsiders fit in

Contributions come from volunteers and from people adjacent to the project. The retrospective credits specific named contributors for design and implementation work, including A. V. Bridgwood, Freya Morgan, and Eileen Wagner for website design and illustrations, and a contributor known as Cryptix for a standalone implementation of the Cable protocol in Erlang.

That pattern is the practical answer to "how is it governed": work happens when someone volunteers to do it, and the project publicly thanks them. If you want to contribute, the model is open in the sense that there is no gatekeeping company — but there is also no onboarding department. You would be joining a volunteer effort, not applying to a vendor.

What this means if you are deciding whether to use Cabal

If you need... Cabal's volunteer model gives you...
A vendor with an SLA and support contract No — there is no company to contract with
A platform that cannot be shut down by an owner Yes — no owner exists to shut it down
Predictable release dates No — pace depends on volunteer availability
A project you can contribute to directly Yes — contributions come from volunteers and outsiders
Formal governance documents Not in the available material — governance is informal

The short version: Cabal is governed by the people who show up to work on it, and nobody owns it. That makes it resilient against commercial shutdown but dependent on volunteer energy, which is why the project itself frames quiet periods as normal rather than alarming.