Open Source Economics, LibreOffice, and Swiss Digital Sovereignty

Robert Jacobi:

Good day. And welcome to OCN, the Open Channels News Broadcast. Today is September 17th, 2026, and I am your host, Robert Jacobi. Today, 3 stories about open source economics. A WordPress developer conference loses half its budget 6 weeks before the event and has to move an entire year. LibreOffice breaks download records by very deliberately not adding AI. And the Swiss federal government is putting thousands of machines on an open source path because digital sovereignty is becoming a purchasing requirement. Different stories, same pressure. Open source is no longer competing only on features. It’s competing on resilience, independence, trust, and the basic question of who pays to keep the ecosystem running.

We’ll start with LoopConf. The Repository reports that LoopConf, the developer-focused WordPress conference, has postponed its 2026 event to June 16th and 17th of 2027 after its lead sponsor pulled out just 6 weeks before the conference. This was not a small sponsorship. LoopConf says that one sponsor represented about 50% of the event’s operating budget. Lose half the budget 6 weeks out, and there’s really no clever spreadsheet trick that fixes that.

The organizers made the decision to postpone rather than cut the experience down to something they did not want to deliver. Attendees were refunded in full, and LoopConf says it also covered non-refundable travel expenses. Amazing but painful.

It is also useful to look at how much of the open source event economy still depends on sponsorship. Conferences love to talk about community, but venues cost money. AV, food, travel, recording, Wi-Fi that everyone complains about — all that costs money. Community does not magically make invoices disappear.

LoopConf’s response is interesting because the 2027 version is being rebuilt as what organizers described as a 100% attendee-funded event. No lead sponsor carrying half the financial risk. The trade-off is obvious. Tickets now have to carry much more of the cost, but the benefit is also obvious. If attendees fund the event, the event can optimize for attendees instead of sponsor packages.

LoopConf says that is exactly the plan. Focus the program on technical sessions around performance, security, AI, architecture, tooling, and workflows for WordPress developers. The event is staying in Grand Rapids, Michigan, and will remain relatively small.

That matters because this is not simply a conference scheduling story, it’s a business model story. Open source communities have spent years depending on a relatively small number of companies to subsidize gatherings, contributors, infrastructure, and sometimes entire projects. That works until one sponsor changes strategy, then everybody discovers where the concentration risk was hiding. LoopConf is testing a different model. The question is whether attendees are willing to pay enough to make it sustainable.

Now to LibreOffice, where the most interesting new feature may be the feature that is not there. Manual do Usuário reports that LibreOffice 26.8 became the project’s most popular update ever, passing 1 million installer downloads in a week. And this does not include installs distributed through Linux package repositories.

The release brought improvements to writing and typography, but the Document Foundation also made a point of something else. LibreOffice does not ship generative AI features by default. In 2026, it’s almost contrarian. Every productivity suite wants an AI assistant. Every toolbar needs a sparkle icon. Every document apparently needs somebody standing by to summarize the paragraph you just wrote. LibreOffice is saying, not so fast.

The Document Foundation says AI is not rejected outright, but built-in AI has to meet some pretty strict principles. Execution should remain under user control. Content should not leave the computer without authorization. There should be no required telemetry. Users should not be locked to one vendor. File formats should not be compromised, and AI should remain optional. That is less an anti-AI position than an anti-dependency position. If you want AI inside LibreOffice, the community can provide plugins, but the core product is not going to assume that every document should automatically be sent into somebody else’s infrastructure.

That distinction matters. For years, software differentiated itself by adding features. Now privacy, simplicity, local control, and the absence of a feature can also be a differentiation. Because AI has become so universal in product strategy that choosing not to add it can suddenly make you stand out.

There’s also a commercial point hiding underneath this. AI features are expensive to run. They create cloud dependencies, they create privacy questions, and they give vendors another reason to push customers toward recurring subscriptions and proprietary infrastructure. LibreOffice does not have to play that game. Its value proposition can simply be, here is a productivity suite, your files remain yours. If you want AI, you can choose how to add it. Surprisingly, or not, there is a market for that.

And finally, Switzerland is turning open source into government infrastructure. TechRadar reports that the Swiss federal government plans to move roughly 3,000 devices toward open source productivity software by the end of 2027. That platform is openDesk, the German-developed open source workplace suite. An earlier proof of concept involved 172 federal employees. The next stage expands that to around 3,000 machines, or roughly 7% of the government’s estimated 54,000 computers.

And the goal is not to wage war against Microsoft or Google or anything like that. It’s digital sovereignty. The phrase keeps showing up for a reason. Governments increasingly want to know where their data lives, which legal jurisdictions can reach it, whether they can move away from a vendor, and what happens if a geopolitical relationship changes. Microsoft 365, and I’m just going to use that generically to also include any other proprietary office suite, is deeply embedded in government enterprise environments. But Microsoft is an American company. US cloud laws and the possibility of foreign access to sensitive information are part of the Swiss government’s assessment.

So open source becomes more than a cost question, it becomes a control question. Can the government operate essential systems without depending completely on one foreign vendor? Can it inspect the software? Can it host more of the infrastructure under its own rules? Can it switch providers without rebuilding everything? These are increasingly strategic questions, and Switzerland is not alone. Germany and France are also pursuing open source and sovereign cloud initiatives.

The Swiss project is expected to cost around $11 million. So it’s not about open source being free, it’s always about framing. It’s about migration, training, support, integration. The argument is that independence has value and governments are increasingly willing to pay for it.

So that’s the thread for today. LoopConf learned the hard way, unfortunately, that sponsor-funded community infrastructure can carry serious concentration risks. LibreOffice is showing that user control in the absence of mandatory AI can actually be a product differentiation. And Switzerland is treating open source as part of a broader strategy for technological independence.

None of these stories is really about free software. They’re about who pays, who controls the infrastructure, and who gets to make the decisions. That is where open source gets interesting. Free does not mean free as in beer or free without cost. Open does not mean without a business model, and independence does not mean you stop paying. Sometimes it means deciding what you are actually willing to pay for.

And that’s OCN for September 17th, 2026. I’m Robert Jacobi. Be open and stay secure.