A new contender has entered the arena of cloud-based productivity, promising a homegrown European alternative to industry giants Microsoft 365 and Google Workspace. Named Euro-Office, this open-source browser-based office suite has officially reached its first stable release. Positioned as a cornerstone of European digital sovereignty, its arrival has, however, ignited a fiery debate within the open-source community, particularly concerning its reliance on Microsoft document formats.
Backed by a powerful coalition of EU-based companies, including Nextcloud and Ionos, Euro-Office aims to offer organizations the ability to host their office suite on EU infrastructure under EU law. Yet, The Document Foundation (TDF), the stewards of LibreOffice, has lambasted the project, accusing it of inadvertently reinforcing Microsoft’s document lock-in. This friction highlights the complex balance between practicality and principle in the world of open-source software.
Introducing Euro-Office: A Sovereign Solution
Euro-Office 1.0, which went live on June 9, 2026, isn’t a standalone application in the traditional sense. Its developers describe it as an “integration component,” primarily handling document editing. This means it relies on existing platforms like Nextcloud Hub, Proton Docs, or OpenProject for crucial functions such as storage, navigation, permissions, and sharing logic.
While tech-savvy users can install Euro-Office on their own Linux servers, seamless integration requires a certain level of expertise. Fortunately, several companies have already stepped up to offer packaged, ready-to-install Euro-Office stacks. These include Nextcloud Hub 26 Spring, Ionos’ Nextcloud Workspace, and Office.eu, making the suite accessible to a broader audience who might not be Linux experts. The project’s overarching goal is to deliver an experience familiar to Microsoft Office users, all while maintaining European control over data and development.
Our initial impressions suggest that while the ribbon UI will feel instantly familiar to Microsoft Office users, the frontend still carries some OnlyOffice branding, and certain menus and dialogs appear a bit dated. Nevertheless, the software is usable, and core functions like real-time collaboration work well within a Nextcloud instance. It’s important to note, however, that the configuration can be quite “fiddly,” making ready-to-go packages the recommended choice for most users, as this initial release feels more like a tech preview than a fully polished product ready for widespread production deployment.
The Open-Source Tug-of-War
The launch of Euro-Office has brought to light two significant internal disputes within the open-source ecosystem. First, Euro-Office is built as a fork of OnlyOffice’s open-source core, a move that initially sparked a licensing disagreement with OnlyOffice’s vendor, Ascensio System SIA. This dispute, centered on attribution and branding, was reportedly resolved just in time for Euro-Office’s launch.
Supporters of Euro-Office justify the fork by citing concerns over OnlyOffice’s strategic decisions, transparency, and geopolitical ties with Russia. They argue that shifting control over development, hosting, and legal jurisdiction to European entities is crucial for governments and public institutions to trust an office suite as part of a truly sovereign cloud stack.
The second, and perhaps more vocal, criticism comes from The Document Foundation (TDF), the organization behind LibreOffice. TDF disputes Euro-Office’s marketing claim of being “the first European open-source office suite,” pointing to its own deep European roots through LibreOffice and its predecessors like StarOffice. TDF believes such claims risk diminishing the historical contributions of existing European office suites in advancing digital sovereignty.
Compatibility vs. Sovereignty: The Format Debate
Beyond branding and historical claims, TDF’s primary objection revolves around Euro-Office’s default document format. Unlike LibreOffice, which champions the Open Document Format (ODF), Euro-Office defaults to Microsoft’s OOXML formats. TDF argues that while compatibility with Microsoft formats is a pragmatic necessity, making OOXML the native default undermines any true claim to independence from Redmond.
TDF’s stark warning, “Compatibility is not sovereignty,” underscores their belief that a European-branded suite defaulting to OOXML inadvertently supports Microsoft’s content lock-in strategy. However, Euro-Office supporters counter that seamless compatibility with existing Microsoft Office documents is non-negotiable for public-sector migrations. They emphasize that ODF support is on the roadmap and that the project’s European governance, licensing, and hosting genuinely shift control away from US hyperscalers.
This debate echoes similar format wars from years past. While ODF offers an open standard, the reality is that Microsoft Office formats remain dominant in everyday use. The pragmatic need for high-fidelity support for these prevalent documents is a legitimate concern for any new office suite aiming for widespread adoption.
Ultimately, the current landscape of open-source office suites seems fraught with internal friction, which appears counterproductive. With Microsoft 365 and Google Workspace holding the vast majority of the online office market, the open-source community could benefit from greater collaboration rather than infighting. There’s ample room for competition and innovation in the marketplace, and focusing efforts on common goals could lead to more robust, user-friendly, and truly sovereign alternatives for everyone.
Source: ZDNet – AI
