A European coalition of cloud and collaboration vendors has released Euro-Office 1.0, a browser-based, AGPL-licensed office suite forked from OnlyOffice, announcing it on June 9, 2026, as a direct sovereign alternative to Microsoft 365. The launch lands squarely at the intersection of escalating digital sovereignty demands, the long-running OOXML versus ODF format wars, and a continent-wide push to decouple critical productivity tools from non-European vendors. Euro-Office 1.0 arrives with no desktop client—only a self-hosted or vendor-operated web interface—and positions itself as the first mature open-source office platform built entirely under a strong copyleft license and European governance.
Backers include several mid-tier European cloud providers, a German IT service conglomerate, and a French public-sector digital agency, though the governance structure remains community-driven through a newly formed Euro-Office Foundation based in Brussels. The codebase starts from OnlyOffice 8.3, with the fork stripping out proprietary elements and adding European-specific authentication, auditing, and data-residency modules. All contributions are required under the AGPLv3, ensuring that any cloud deployment must release source modifications to end users—a deliberate counter to the “open core” model that has drawn fire in previous European open-source projects.
Microsoft 365 controls roughly 85 percent of the European enterprise productivity market, a figure that regulators in Berlin, Paris, and The Hague have repeatedly flagged as a systemic risk. Euro-Office’s backers argue that the suite’s instant familiarity—its UI mimics the ribbon-and-panel layout of desktop OnlyOffice, which itself copies Microsoft’s design language—will ease adoption in public administrations and SMEs that have hesitated to migrate to LibreOffice or Collabora Online. The project’s technical lead, Dr. Anke Vogelsang, said in a launch statement that “document fidelity with the OOXML formats used by every ministry and business is non-negotiable,” explaining why the fork chose OnlyOffice over LibreOffice as a starting point.
That choice reignites a decades-old debate. The Open Document Format (ODF) is the ISO-approved open standard long championed by LibreOffice, Apache OpenOffice, and the European Commission’s own interoperability guidelines. OOXML, an ECMA and ISO standard maintained by Microsoft, is the default format for .docx, .xlsx, and .pptx files. Critics of OOXML point to its monolithic specification and legacy compatibility quirks, while supporters insist it reflects real-world document complexity. Euro-Office 1.0 settles the argument pragmatically: it uses OOXML as its native save format and renders them with near-perfect fidelity, but can also open and export ODF files. The suite’s import engine handles ODF 1.4, and an experimental converter pipeline aims to batch-migrate libraries from ODF to OOXML without manual touch-up.
This dual-format strategy places Euro-Office in a unique market niche. OnlyOffice has long been favored by enterprises that need bulletproof .docx rendering, while Collabora Online and LibreOffice lean toward ODF purity. Euro-Office doubles down on OOXML to court the 90 percent of European public-sector documents that arrive in Microsoft formats, then layers compliance and sovereignty features on top. Users can enforce eIDAS-compliant electronic signatures, store documents in Gaia-X certified clouds, and log access requests to a European chain-of-trust audit trail that meets GDPR Article 30 requirements.
The immediate use case is browser-only: organizations run Euro-Office on their own infrastructure via Docker Compose or Kubernetes Helm charts, or purchase a managed instance from a partner in the Euro-Office Marketplace. The full editing suite includes word processor, spreadsheet, and presentation modules that load in any modern browser without plugins. Real-time co-authoring uses the OnlyOffice document server’s WebSocket-based collaboration engine, with Raft consensus ensuring edits converge even during network partitions. Performance benchmarks released alongside the launch show that a 500-user instance on a 16-core server sustains sub-200-millisecond edit propagation, comparable to Microsoft 365’s same-region latency.
Mobile access remains a weak spot. Euro-Office 1.0 has no native Android or iOS app; mobile users must open the browser interface, which can pinch-zoom and edit but is not touch-optimized. The foundation says mobile apps are on the six-month roadmap, likely based on OnlyOffice’s existing mobile shell. Offline editing is also absent: the suite requires a persistent server connection, though an Electron-based desktop wrapper with local caching is slated for version 1.2 in early 2027.
European governments have been scrambling for a sovereign office stack ever since the European Court of Justice’s 2025 ruling that data transfers under the EU-U.S. Data Privacy Framework still expose citizens to bulk surveillance. France’s DINUM and Germany’s ZenDiS both published catalog requirements earlier this year demanding that office suites support OOXML, real-time collaboration, and self-hosting. Euro-Office 1.0 was demonstrably written to those procurement checklists. The project’s launch press kit includes a compliance matrix showing it meets 42 of 47 mandatory items in the DINUM specification; of the remaining five, three are mobile-client requirements the team promises in version 1.1.
An ICT procurement officer from the Netherlands, speaking on background, described the launch as “the most complete open-source attempt yet to mirror the Microsoft 365 stack without depending on a US-headquartered company.” She noted, however, that the absence of an integrated mail and calendar server is a problem. Euro-Office 1.0 ships only with a document-connection plugin for Nextcloud, ownCloud, and the open-source mail server Kopano. Full Outlook-style groupware requires additional components, which the Euro-Office Foundation does not yet package in a unified installer.
That fragmentation is deliberate. The foundation’s governance charter prohibits bundling “non-document collaborative services” into the core distribution, reasoning that specializing on editing and letting ecosystem partners handle mail, calendar, and video conferencing will accelerate adoption. Critics call it a repeat of the legacy open-source fragmentation that allowed Microsoft to sweep the market in the 2000s. Proponents argue that a modular approach, with well-defined APIs between components, better matches the European Commission’s digital strategy of “interoperable building blocks” rather than vertically integrated silos.
Security researchers have given the initial codebase a cautious welcome. Euro-Office inherits OnlyOffice’s C++ base for the server-side editing engine and client-side JavaScript editors, but the fork’s first public commit shows the removal of a telemetry module that phoned home to Ascensio System, OnlyOffice’s original developer. The Euro-Office team also replaced the default font set with open-licensed alternatives—Carlito for Calibri, DejaVu for Arial—so that default templates render identically without proprietary fonts. A static analysis by the German BSI, commissioned by the foundation, found no critical vulnerabilities in the 1.0 release, though it flagged 14 medium-severity issues related to stale NPM dependencies that will be patched in a point release this week.
Community reaction at launch has been mixed. On the Hacker News thread announcing the release, several European sysadmins praised the AGPL choice as “finally a real open-source office that can’t be swallowed by a proprietary fork,” while others worried that the OOXML-first approach would cement the very monopoly the project claims to fight. A French contributor on the Euro-Office GitHub repository opened an issue titled “Make ODF default, not just an export option,” which has drawn over 200 comments in 48 hours. The maintainers responded by reaffirming that OOXML remains the default for interoperability but said they would ship a “sovereign mode” toggle in version 1.1 that switches the default save format to ODF for those who want it.
The project’s alignment with the “Euro Stack” movement is unmistakable. Euro-Office runs on European cloud providers like Scaleway, Hetzner, and OVHcloud, and the foundation’s marketplace lists hosted plans that guarantee data stays within Schengen-area data centers. It integrates with the European Blockchain Services Infrastructure (EBSI) for document notarization, and the next release promises support for the EUDI Wallet’s verifiable credentials for document signing. If these integrations materialize, Euro-Office could become a reference implementation for the European Commission’s “Internet of Humans” pledge to make all official document workflows sovereign by 2030.
Microsoft has not commented publicly on the Euro-Office launch, though a source inside the company’s legal department acknowledged that it is watching the project’s ability to pass procurement gateways. Microsoft’s own push toward “EU Data Boundary” compliance for Microsoft 365, completed in early 2026, was partly intended to undercut these sovereign alternatives. Yet Euro-Office’s AGPL license and non-profit governance are structural defenses that no amount of data-boundary marketing can replicate.
Pricing is absent: Euro-Office 1.0 is free software. Organizations can download the source and binaries at no cost. The foundation operates on voluntary ecosystem contributions and a paid marketplace that takes a 10 percent commission on hosted plans sold by partners. Those plans start at €3 per user per month for a shared-tenant instance, scaling to dedicated bare-metal clusters running in German or French federal data centers. A foundation executive noted that the bulk of early interest is coming not from cash-strapped municipalities but from EU agencies that already run Nextcloud or ownCloud for file sync and see a document editor as the missing piece.
The technical architecture leans heavily on the OnlyOffice Document Server, which spawns headless LibreOffice instances for additional format conversions. Euro-Office keeps this backend but adds an abstraction layer that allows swapping the format converter—opening the possibility of a pure ODF pipeline in the future if that converter gets replaced by a Rust-based engine now being prototyped at the University of Luxembourg. The editing client itself is a JavaScript single-page application, built with the Quasar framework and Vue.js, that communicates with the server via WebSocket and REST APIs. The stack’s performance on low-powered hardware is untested, but initial reports from a pilot in a Czech regional government show that a 2018-era i5 desktop runs the web client smoothly in Firefox while editing a 200-page .docx with track changes.
Euro-Office 1.0’s long-term fate depends on whether it can build a sustainable developer community outside the initial consortium. OnlyOffice once enjoyed a vibrant open-source community before Ascensio shifted focus to its commercial Enterprise Edition, a cautionary tale that Euro-Office’s foundation bylaws try to prevent by mandating that the full release—with all features—always ships under AGPL. The project also needs to deliver on its mobile and offline promises; without them, field workers and executives who rely on tablets will remain locked into Microsoft 365.
For now, the release has injected genuine momentum into Europe’s drive for digital sovereignty. Euro-Office 1.0 is not a speculative whitepaper or a limited pilot: it is live, feature-complete, open-source, and already passing procurement checklists that had no plausible non-Microsoft answer a year ago. Whether that translates into mass deployment in the public sector—or merely adds another option to the graveyard of open-source office suites that never unseated the incumbent—will depend as much on political will as on engineering execution.