A new office software suite marketed as a European alternative to Microsoft Office has come under technical scrutiny following reports that its source code is almost entirely derived from existing projects. Security analysts and software developers have identified that the platform, which claims to reduce dependence on U.S.-based technology, mirrors the codebase of OnlyOffice to a significant degree, with some reports suggesting upwards of 99 percent overlap.
The project, which has been positioned as a sovereign digital tool for European enterprises and public institutions, is a fork of the open-source software OnlyOffice. While forking—the process of taking existing source code to create a separate, independent development path—is a standard practice in the open-source community, the lack of substantial new development in this specific iteration has raised questions regarding its claims of independence and innovation. According to analysis from industry observers, the software maintains the underlying architecture and functionality of its predecessor, challenging the narrative that it serves as a distinct, domestically engineered solution.
The Mechanics of Software Forking and Transparency
In the world of open-source software, forking is protected by licenses like the AGPL, which allow developers to modify and redistribute code. However, the controversy surrounding this European suite centers on the distinction between legitimate project evolution and “rebranding.” When a developer forks a project, the expectation is typically that they will add unique features, security patches, or localized improvements that address specific user needs. If the resulting product remains functionally identical to the original, it raises concerns about the longevity of the project and the intent behind its creation.
Industry experts note that relying on a fork without a robust team to maintain the underlying codebase can be risky. If a security vulnerability is discovered in the original software, the fork must also be updated. If the developers behind the fork lack the resources or expertise to keep pace with the parent project, they risk leaving their users exposed to cyber threats. This is a critical consideration for government and enterprise users who prioritize data sovereignty and long-term security support over cost or political branding.
Data Sovereignty and the Quest for Independence
The push for a “European-made” office suite is part of a broader trend among EU policymakers to reduce reliance on dominant American technology firms, often referred to as “digital sovereignty.” The goal is to ensure that European organizations retain control over their data and are not subject to the legal or operational constraints of non-EU jurisdictions. However, the technical reality of software development often complicates these political goals.
Most modern office suites rely on complex global ecosystems. Building a truly independent suite from the ground up would require significant investment and a long development cycle. By choosing to fork an existing, highly functional open-source project, developers can quickly provide a viable product. Yet, as this case demonstrates, the efficiency of this approach can clash with the requirement for genuine, verifiable domestic innovation. Organizations looking to adopt such tools are now being advised to conduct thorough due diligence, including code audits, to understand exactly what they are deploying within their infrastructure.
What Lies Ahead for European Open-Source Initiatives
The situation serves as a case study for the challenges of building a sovereign European technology stack. As organizations continue to migrate away from proprietary giants like Microsoft, the market for open-source alternatives is expected to grow. The European Commission has previously highlighted the importance of open-source software in its Open Source Software Strategy, which emphasizes the need for transparency and community-driven development to ensure security and interoperability.
Moving forward, the success of such projects will likely depend on their ability to move beyond simple rebranding and demonstrate tangible contributions to the software ecosystem. Users, particularly those in regulated sectors, are increasingly looking for transparency regarding development roadmaps, security governance, and the composition of the development team. The next phase for these initiatives will involve demonstrating that they are not merely mirrors of existing software, but active participants in the global open-source community that can provide long-term, stable, and secure alternatives to the status quo.
The community is awaiting further technical disclosures from the project developers regarding their long-term maintenance plans and how they intend to distinguish their offering from the parent project. Developers and security auditors are encouraged to review official project repositories for ongoing updates and commit histories to track the evolution of the codebase. For those interested in the broader impact of these developments, public documentation on digital sovereignty initiatives remains available through official EU digital policy portals.