A Fork Too Far: How a European Office Software Clone Blew Up One of Open Source’s Most Prominent Partnerships

ONLYOFFICE has suspended its partnership with Nextcloud after discovering the German cloud company forked its document editors into an unauthorized product called Euro Office, igniting a dispute over open-source ethics, European sovereignty branding, and the limits of collaborative trust.
A Fork Too Far: How a European Office Software Clone Blew Up One of Open Source’s Most Prominent Partnerships
Written by Eric Hastings

For nearly a decade, ONLYOFFICE and Nextcloud operated as one of the more visible alliances in open-source enterprise software. The Latvian document editor maker and the German cloud platform company had built a joint product used by governments, universities, and businesses across Europe. That partnership is now suspended β€” and the fallout is exposing deep tensions over intellectual property, sovereignty branding, and the unwritten rules of open-source collaboration.

The rupture centers on a product called Euro Office, a fork of the ONLYOFFICE document editors that Nextcloud began distributing without authorization. ONLYOFFICE announced the suspension of its partnership on June 19, 2025, in a pointed blog post that accused Nextcloud of creating and promoting a modified version of its software under a different name β€” one designed to appeal to European digital sovereignty buyers β€” without ever seeking permission or even informing ONLYOFFICE in advance.

The details matter. And they’re messier than a typical open-source licensing spat.

According to ONLYOFFICE, Nextcloud took the open-source ONLYOFFICE Docs codebase, modified it, rebranded it as “Euro Office,” and began marketing it as an independent product. Nextcloud reportedly stripped out ONLYOFFICE branding, replaced logos and names with its own, and presented the software to prospective customers β€” including major European public-sector organizations β€” as a Nextcloud-native offering. ONLYOFFICE says it learned about the fork not through any partner communication channel, but through public marketing materials and customer inquiries.

That last point stung. ONLYOFFICE’s blog post made clear the company felt blindsided: “We were not consulted, informed, or asked for permission.”

As reported by Neowin, the situation raises questions that go beyond a simple branding dispute. ONLYOFFICE Docs is released under the GNU Affero General Public License version 3 (AGPLv3), which does permit forking and redistribution. In pure licensing terms, Nextcloud may have been within its legal rights to create a derivative work. But ONLYOFFICE argues that legal permission and partnership ethics are not the same thing. The company contends that Nextcloud’s actions violated the spirit β€” if not the letter β€” of their commercial partnership agreement, which included specific terms about how ONLYOFFICE technology could be used and presented.

There’s a broader commercial dimension here too. ONLYOFFICE and Nextcloud had a revenue-sharing arrangement. Enterprise customers who purchased the integrated ONLYOFFICE-Nextcloud product generated income for both companies. By forking the editor and rebranding it, Nextcloud could potentially capture the full revenue stream from document editing without sharing proceeds with ONLYOFFICE. Whether that was the intent or merely a side effect, the economic incentive is obvious.

Nextcloud has not remained silent. Frank Karlitschek, Nextcloud’s founder and CEO, responded publicly, framing Euro Office as a natural evolution in European digital sovereignty efforts. In posts on social media and in statements to the press, Karlitschek argued that European organizations need software stacks free from dependencies on any single vendor β€” including ONLYOFFICE, which is headquartered in Riga, Latvia, but has development operations that have historically included staff in Russia. Karlitschek suggested that some European government customers had expressed concern about the supply chain, and that Euro Office was a response to those concerns.

That argument didn’t land well with ONLYOFFICE. The company’s blog post directly addressed the sovereignty framing, calling it a “misleading narrative” and noting that ONLYOFFICE is an EU-based company subject to EU law. ONLYOFFICE also pointed out that its source code is fully open and auditable, making supply-chain concerns a matter of due diligence rather than a justification for an unauthorized rebrand.

The sovereignty angle is not incidental. It’s the commercial engine driving much of this conflict.

European governments have spent the last several years actively seeking alternatives to American and Chinese technology platforms. The European Commission’s push for digital sovereignty has created a lucrative market for software that can be credibly marketed as European, open-source, and free from foreign dependencies. Nextcloud has positioned itself aggressively in this space, winning contracts with the German federal government and other major public-sector buyers. A fully branded “Euro Office” product β€” with no visible connection to a Latvian-Russian development history β€” would be an easier sell in procurement processes where sovereignty credentials are evaluated.

ONLYOFFICE clearly sees this as an attempt to appropriate its technology for competitive advantage. The company’s statement described the situation as a partner “using our own product against us.”

Open-source licensing experts have weighed in with mixed assessments. The AGPLv3 does grant broad rights to fork, modify, and redistribute. That’s foundational to how open-source software works. But the license also requires that derivative works carry proper attribution and that the source code of modifications be made available. Whether Nextcloud’s Euro Office fork meets all attribution requirements is a factual question that hasn’t been fully resolved in public. ONLYOFFICE has implied there may be compliance issues, though it hasn’t filed a formal legal complaint as of this writing.

The situation also highlights a persistent tension in open-source business models. Companies that release their core product under permissive or copyleft licenses always face the risk that a partner, competitor, or even a customer will fork the code and compete directly against them. It’s the bargain you make for the distribution advantages and community goodwill that open source provides. But when the entity doing the forking is your most prominent integration partner β€” one with whom you share customers, marketing efforts, and revenue β€” the sense of betrayal runs deeper than a typical competitive fork.

Industry observers have drawn comparisons to other high-profile open-source disputes. The 2018 conflict between Redis Labs and cloud providers over the use of Redis modules. Elastic’s 2021 decision to change its license after Amazon launched a competing Elasticsearch service. The ongoing friction between WordPress creator Automattic and hosting provider WP Engine. In each case, the core tension is the same: one party feels another is extracting disproportionate value from shared technology without adequate contribution or compensation.

But the ONLYOFFICE-Nextcloud split has a distinctly European flavor. The sovereignty market creates incentives that don’t exist in the same way in the United States or Asia. When government procurement officers are explicitly scoring bids on “European-ness,” the branding and provenance of software components become strategic assets β€” not just marketing details. Stripping ONLYOFFICE’s name from its own code and replacing it with “Euro Office” isn’t just a rebrand. It’s a repositioning designed to capture sovereignty premium pricing.

For Nextcloud, the risk is reputational. The company has built its brand on openness, transparency, and community trust. Being seen as a partner that forks an ally’s code without discussion β€” regardless of legal rights β€” could damage relationships with other technology partners and open-source contributors. Several commentators on Hacker News and the Fediverse have already expressed discomfort with Nextcloud’s approach, even among those who are generally sympathetic to the company’s sovereignty mission.

For ONLYOFFICE, the risk is existential in a narrower sense. Nextcloud was its primary channel into the European public-sector market. Losing that distribution pathway β€” or worse, competing against a fork of its own software in that market β€” could significantly impact revenue. The company will need to build direct sales capabilities in European government procurement or find alternative partners quickly.

So what happens next? ONLYOFFICE has suspended the partnership but hasn’t terminated it outright, leaving the door open for negotiation. The company has called on Nextcloud to cease distribution of Euro Office, restore proper branding, and return to the terms of their original partnership agreement. Nextcloud has shown no public indication it intends to comply with those demands.

A legal battle is possible but not certain. Litigation over open-source license compliance is expensive, slow, and unpredictable. ONLYOFFICE might instead pursue a strategy of competitive differentiation β€” emphasizing its direct relationship with customers, its EU headquarters, and its transparent development process. The company could also tighten its licensing terms for future releases, following the path Elastic, MongoDB, and others have taken by adopting source-available licenses that restrict competitive forking.

The broader lesson here isn’t really about licensing. It’s about trust.

Open-source partnerships work because of norms that extend well beyond what any license file specifies. Don’t fork your partner’s code without talking to them first. Don’t strip their branding to gain a competitive edge. Don’t use sovereignty rhetoric to obscure what is fundamentally a business maneuver. These aren’t legal obligations. They’re the social contract that makes collaboration possible in a world where the code itself is free.

When that contract breaks down, the consequences ripple outward. Other open-source companies are watching this dispute closely, recalculating the risks of deep integration partnerships. Some will conclude that permissive licensing is too dangerous when your partner has the technical capability and market incentive to fork. Others will add more restrictive clauses to their partnership agreements. A few will abandon open-source licensing for their core products entirely.

None of those outcomes serve the broader open-source community well. But they’re the predictable result when a partnership built on mutual benefit becomes a zero-sum competition β€” and when the code that was supposed to bind two companies together becomes the weapon one uses against the other.

The ONLYOFFICE-Nextcloud breakup is, at its core, a story about what happens when commercial incentives overwhelm collaborative norms. The European sovereignty market is real, growing, and enormously valuable. The temptation to capture more of it β€” even at the expense of a long-standing partner β€” proved too strong to resist. Whether Nextcloud’s bet pays off or backfires will depend on how the market, the community, and possibly the courts respond in the months ahead.

Subscribe for Updates

DevNews Newsletter

The DevNews Email Newsletter is essential for software developers, web developers, programmers, and tech decision-makers. Perfect for professionals driving innovation and building the future of tech.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us