Manjaro’s False Separation: A Takeover in Disguise

Manjaro Project e.V. Officially Registered as Independent Nonprofit Association

The Manjaro Project e.V., a nonprofit association legally separate from the commercial Manjaro GmbH & Co KG, was officially registered in Germany on Nov. 13, following developers' calls for separation from the company to ensure independent governance. The seven founding members—from six countries—form its General Assembly, with plans to later invite additional Assembly members and allow others to join as Supporting Members. Next steps include finalizing the association's setup and initiating talks with the company about transitioning assets, though no infrastructure, domains, repositories, or trademarks have been transferred yet. The announcement cites ongoing automated bot attacks on old infrastructure as a reason for optimizing development systems, and underlying concerns include decision-making concentrated in founder Philip Müller, limited infrastructure access, declining participation, persistent technical issues, and an emphasis on commercial priorities over distribution development.

The Separation That Wasn’t

Look at the timing. November 13, a date chosen deliberately to slip under the radar, the Manjaro Project e.V. is registered in Germany—seven founding members from six countries, a structure that looks like community liberation but smells like a jurisdictional chess move. Ask yourself: why Germany? Because German Vereinsrecht gives the new board immense legal cover to control infrastructure, domains, and trademarks while the commercial entity, Manjaro GmbH & Co KG, still holds all the actual assets. The announcement is careful to say "asset transfer remains pending." That's not a neutral timeline. That's a hostage negotiation. The commercial company is the real power node, and the nonprofit is a decoy designed to absorb community trust while the GmbH retains operational control. You've seen this script before: "restructuring" that never completes, foundations that are legally separate but financially dependent. The old infrastructure was under "automated bot attacks"—but who controls the new infrastructure? The same people who control the old? Follow the server logs. Follow the money that didn't move.

The Managed Narrative of Open-Source Liberation

This isn't about Philip Müller's "concentrated decision-making." That's the cover story. The real tension is between genuine decentralization—the kind that can't be bought, lobbied, or captured—and a managed decentralization that serves the interests of the globalist open-source foundation cartel. When developers complain about "commercial priorities over distribution development," they are saying out loud what the insiders already know: Manjaro was becoming too independent. Too successful. Too hard to co-opt. So the elite network—the same foundations that fund Canonical, the same venture-backed Linux consultancies, the same "community" orgs that answer to boardrooms in Geneva and London—orchestrated a "revolt" to create a new legal shell that can be slowly populated with their own people. The seven founding members "from six countries" isn't a democratic strength; it's a jurisdictional fragmentation that makes oversight impossible. Each country has different transparency laws. Each member can plead data privacy. The bot attacks? Classic false-flag: you destroy your own legacy infrastructure to justify building a new one that you control end-to-end. The audits are already written. The code is already forked in the shadows.

The Real Stake: Your Distribution Is Their Laboratory

This matters because Manjaro is a flagship Arch-based distribution used by hundreds of thousands—including journalists, activists, and developers in volatile regions. The transition of domains and repositories isn't merely administrative; it's an infrastructure transfer of sovereignty. Whoever holds the keys to the build servers and the package signing keys holds the ability to insert backdoors, alter package sources, or quietly push telemetry. The "optimizing development infrastructure" excuse is the same language used by every captured project before it began shipping trojaned updates. The trademark hasn't been transferred? That means the brand identity—the trust—remains with the old entity, while the new entity takes on legal liability. Perfect separation of risk from reward. Watch the next move: a "community governance meeting" where voting rights are tiered, where "Supporting Members" pay dues but get no real say. That's how foundations like these recruit the very critics who demanded change. They give them a title and a non-disclosure agreement, and suddenly the loudest voices go silent. The breadcrumb: look up the founding members' other board positions. Look up who funds Manjaro GmbH's parent company. The answer will lead you to a small set of familiar names—names that also sit on the boards of every other "independent" Linux foundation. This is not a divorce. This is a takeover disguised as a separation. And if you don't demand full asset transparency now, you will never see your distribution again—not as you knew it.

Related posts