BRUSSELS — Euro-Office 1.0 landed this week. A cloud-based productivity package. Backed by European firms. Marketed as the answer to digital dependence on American and Russian technology. Yet its arrival triggered immediate pushback from established open source voices. The dispute centers on file formats. On claims of sovereignty. And on what true independence looks like for governments and businesses across the continent.
The project, developed under the stewardship of Nextcloud and IONOS among others, positions itself as a sovereign replacement for Microsoft 365 and Google Workspace. It promises full compatibility with familiar document types. An intuitive interface. Code released under open licenses without trademark entanglements. Supporters see it as a practical step for European public administrations and companies wary of data risks tied to non-European providers.
But The Document Foundation wasted little time. In an open letter published days before the June 9 launch, the organization behind LibreOffice delivered a sharp critique. “Compatibility is not sovereignty,” it warned. The group argued that a European-branded suite saving files in OOXML by default functions as “a de facto ally of Microsoft in its content lock-in strategy.” Servers in Europe or European oversight of code, the letter continued, cannot change the fact that document control stays with Redmond.
The Format Fight at the Heart of Sovereignty Claims
OOXML. The format Microsoft developed and pushed through standardization years ago. Euro-Office defaults to it for maximum compatibility with the documents European users already create, edit and exchange. That choice drives adoption, its advocates insist. Yet it locks future data into a specification many view as proprietary at its core despite ISO approval. ODF, the Open Document Format long championed by LibreOffice and others, offers a truly open alternative. One free from single-vendor influence. The clash isn’t new. It echoes battles from the mid-2000s. But it carries fresh weight now amid Europe’s drive for technological autonomy.
Nextcloud’s press release from March laid out the project’s ambitions. It described the absence of any solution combining strong Microsoft format support, a familiar user experience and genuine European control. Existing options, the statement noted, force trade-offs in compatibility or carry legal and governance risks. Euro-Office, by contrast, emerged from an industry initiative. Its entire codebase sits under fully open source licensing. Transparent development. Open to contributions. Hosted on GitHub and integrated into Nextcloud Hub 26.
Yet the project’s roots complicate the narrative. It represents a hard fork of OnlyOffice, the web-based editor originally from a Russian company. Geopolitical tensions played a role. Sanctions and concerns over potential influence prompted the split. OnlyOffice later accused the Euro-Office team of violating its AGPL licensing terms. The exchange added another layer of friction to an already crowded field of office software forks and disputes.
And the open source community has seen plenty of those lately. Earlier this year tensions between The Document Foundation and Collabora escalated. The foundation removed over 30 Collabora-affiliated developers from governance roles amid disagreements over commercial interests and LibreOffice Online. Contributions dried up. Critics on both sides pointed to corporate capture. The pattern repeats. Small market share. Intense competition for limited resources. Public arguments that leave observers wondering who benefits when projects turn inward.
Steven J. Vaughan-Nichols captured the fatigue in a ZDNet article published hours after launch. He noted frustration with organizations quarreling while proprietary vendors dominate the market. The piece quoted TDF’s warning directly and highlighted how opposition from LibreOffice supporters won’t ease adoption hurdles for the newcomer.
Supporters of Euro-Office counter that practical reality must guide choices. European governments and firms exchange millions of Microsoft-format documents daily. Insisting on ODF first risks isolation. Limited interoperability. Slower uptake. They frame their approach as pragmatic sovereignty. Control the infrastructure. Host the data. Maintain the code. Influence flows back to Europe even if file formats retain Microsoft DNA.
The Document Foundation sees a different equation. Its letter, covered in detail by Foss Force, contends that defaulting to OOXML strengthens the very lock-in European initiatives claim to escape. Sovereignty, it argues, requires control over the standards that define documents for decades ahead. Not just where servers sit today. A cloud service built in Europe but emitting files tied to Microsoft’s ecosystem offers only partial freedom. Future changes to OOXML. Licensing shifts. Interpretation disputes. All remain outside European hands.
So what happens next? Early reviews suggest Euro-Office delivers on its compatibility promise. Users report smooth handling of complex DOCX, XLSX and PPTX files. The interface feels closer to Microsoft Office than LibreOffice’s ribbon-free design. For organizations prioritizing minimal training and zero conversion headaches, that matters. A lot.
Yet production readiness questions linger. ZDNet noted the suite isn’t fully mature for every high-stakes deployment. Integration into existing government workflows will take time. Training. Data migration. Policy updates. And the public quarrel risks confusing potential adopters who simply want reliable tools without entering format theology debates.
Recent commentary on X reflected the split. One post from technology journalist @sjvn echoed his ZDNet piece. Another from a cybersecurity account framed the fight as a question of whether sovereignty concerns code origins or underlying standards. Discussions in European tech forums highlighted worries about Chromium dependencies and lingering ties to original OnlyOffice architecture.
The broader context includes years of European investment in open source. Billions directed toward digital sovereignty initiatives. Gaia-X. Sovereign cloud projects. Procurement preferences for open standards. Euro-Office arrives as one piece in that mosaic. Its success or failure will signal how much weight governments place on format purity versus immediate usability.
Critics worry the project could pull resources and mindshare from LibreOffice. The latter has improved its own document fidelity over time. It maintains strong ODF support and offers desktop applications many prefer for offline work. Yet its online collaboration features have lagged. Euro-Office’s web-first design targets that gap directly. Different tools. Different priorities. Perhaps room for both. But the infighting makes coordination harder.
OnlyOffice’s response to the fork, reported in technology outlets earlier this year, underscored licensing tensions common in AGPL projects. When commercial incentives collide with community expectations, disputes follow. The Euro-Office team maintained the fork became necessary due to limited acceptance of external contributions and geopolitical factors. Both sides claim adherence to open source values. They disagree on application.
European procurement officers now face a fresh choice. Stick with Microsoft and accept the vendor relationship. Adopt Google Workspace and its cloud model. Invest in LibreOffice and push ODF across departments. Or trial Euro-Office for its compatibility edge and European branding. No option satisfies every criterion. Each carries trade-offs in cost, control, usability and long-term flexibility.
The launch coverage spread quickly. Slashdot amplified the controversy within hours. German-language reports in Der Standard detailed accusations of misleading claims by the new project. Technical communities dissected the architecture. Some questioned whether forking OnlyOffice truly escapes all external influence given its web technology stack.
One thing seems clear. The argument won’t fade soon. Document formats shape how information persists across generations of software. Governments archiving citizen data for 20 or 30 years care deeply about future readability. A default that favors short-term compatibility may create decades of technical debt. Yet forcing ODF on users accustomed to Microsoft tools risks rejection and shadow use of unauthorized software.
Developers on both sides continue their work. LibreOffice refines its engines. Euro-Office teams iterate on the cloud experience. Nextcloud integrates the suite deeper into its platform. The market will test which vision resonates. Budgets. User feedback. Security audits. All will matter more than open letters.
But the rift exposes something deeper. Open source succeeded by solving real problems. When projects prioritize ideological purity over user needs, or vice versa, fractures appear. Europe’s office software battle reveals the tension between principle and pragmatism. Between open standards and market realities. Between sovereignty as rhetoric and sovereignty as daily practice.
Watch how public sector pilots unfold. Track whether Euro-Office gains traction in Brussels institutions or Berlin ministries. See if the controversy pushes both projects to improve. Or if it simply amplifies noise while Microsoft retains the overwhelming majority of seats. The answers will shape digital infrastructure across the continent for years ahead.
WebProNews is an iEntry Publication