On openness · The But Is It Open? blog

Percona CEO: Open Source Is a Social Contract, Not Just a License

· 3 minute read

Peter Farkas uses MongoDB, Redis and HashiCorp to ask a harder question: your license lets you fork the software, but could you actually keep it going?

Abstract painted gathering of overlapping ochre, burgundy and navy planes on warm ivory paper, arranged around an airy open center.

Percona CEO: Open Source Is a Social Contract, Not Just a License

Peter Farkas wants developers to ask a harder question before choosing open source software. Yes, the license lets you fork it. But could you actually keep it going?

In an All Things Open 2026 talk published on YouTube on November 13, the Percona CEO argues that “open source is a social contract and not just a legal one.” His examples—MongoDB, Redis and HashiCorp—are familiar to anyone who has watched a software dependency become a business risk. His point is that the warning signs aren't all in the license.

The conference session, billed as “What Makes Open Source Work: Licensing and Beyond,” is worth watching in full:

Farkas doesn't dismiss licensing. He tells the audience to start with an actual OSI-approved open source license. But source code and legal permission don't automatically supply the knowledge needed to use them.

“If there's no documentation, if there's no transparency, even if you see an open source license, you can't exercise the freedoms that the license provides you with,” he says at 2:40.

That's a strong claim, but it describes a recognizable frustration: being handed the right to do something without enough information to do it. Maintained packages, complete source and good documentation make that right useful. Governance tells you who can change the project's direction. An ecosystem of maintainers and competing service providers gives you somewhere else to turn.

The contrast in his talk is between a license change and what happens afterward. He revisits MongoDB's move to the Server Side Public License, then points to Valkey as evidence that the community around Redis could organize an independent continuation. HashiCorp's licensing change supplies another example of a community creating alternatives. In Farkas's telling, the difference is whether enough people outside the original vendor understand the software and care enough to sustain it.

“The license tells you that. But can you realistically fork it?”

That question, at 9:01, is the talk's most useful distinction. A large company might fund a replacement. A ten-person business probably can't. The same legal freedom can offer very different protection depending on who else is there to help exercise it.

Farkas isn't a disinterested observer: Percona sells database software and services, and a multi-vendor ecosystem is good for its business. That doesn't invalidate the argument. It makes this a vendor CEO explaining why customers should want options beyond any single vendor—including, by implication, his own.

For me, this is where the talk meets But Is It Open? I've written about the gap between a license and a community; Farkas shows what that gap means when a dependency changes direction. The book's openness index separates access and permission from deployment, transparency and reproducibility. His emphasis on documentation and complete source asks whether access is usable; his governance and ecosystem questions ask whether independence can last. Those aren't identical frameworks, but they resist the same shortcut: letting a license answer every question.

The license matters. So do the people, knowledge and institutions that let you act on it. Before building on the promise, ask: but is it open?

← More from the blogJoin the newsletter ↗