Four months ago this site wrote the last Euro-Office post on a conditional: "Watch Euro-Office. Don't deploy it as your primary office suite yet" (the August format-sovereignty piece). The conditions named were v1.0's gaps — no desktop or mobile clients, an OOXML-default architecture, and a coalition governance structure that was "newer and less tested." Nextcloud's Hub 35 post in September repeated the tease: the desktop client would be "available for download in the coming weeks" (covered here).
On November 13 the desktop app shipped. That part of the watch condition is closed, and the distribution details are more interesting than the feature list. Here is what the repository actually says.
What shipped¶
Nextcloud's desktop announcement lists: editors for documents, spreadsheets, presentations and PDFs; offline work with files kept on the device; locally installed fonts; digital signatures through eIDAS-listed trust providers; password and permission protection on files; and live connection to a self-hosted Nextcloud Hub for collaborative editing, with more than one Hub attachable as a "Cloud." Platforms: Windows x64 and ARM64, Linux .deb (Debian/Ubuntu) and .rpm (Fedora), macOS on Apple Silicon. No mobile client — that leg of the August gap list is still open.
Wikipedia's chronology records the same release as "the first stable desktop application... released on 13 November 2026 by NextCloud," with Windows 10+, macOS 13+, and a Linux AppImage. The AppImage reference traces to an official Nextcloud install page; the official channels the project itself names in its README are the signed repositories and the GitHub releases shown below — treat the AppImage form as plausible but secondhand.
The artifact check¶
The desktop app's source lives at GitHub, Euro-Office/DesktopEditors — 457 commits, 980 stars, 58 forks at the time of reading, no visible GitHub fork-parent, meaning the history was re-rooted rather than forked through the GitHub UI. Two immediate tells about provenance:
The component tree is ONLYOFFICE's, verbatim. core, sdkjs, web-apps, desktop-sdk, desktop-apps, dictionaries, document-templates, sdkjs-forms, core-fonts — the exact component names and README structure of ONLYOFFICE's own Desktop Editors repository, down to the reference to a DocumentServer project that the components feed. The README's cloud-integration list — Moodle, Nextcloud, ownCloud, Seafile, Liferay, kDrive — is ONLYOFFICE's integration catalog, and the feature list ("AI-powered assistants," Diagram Viewer, 46 interface languages) tracks ONLYOFFICE's product surface.
The version file and the license header are inherited. VERSION.txt reads 9.3.9 — plain upstream-style numbering, not a 1.0. And the LICENSE file opens with (c) Copyright Ascensio System Limited 2010-2022 followed by the phrase "This program is freeware" — Ascensio System SIA being ONLYOFFICE's Riga-based operator, and "freeware" being ONLYOFFICE's long-standing, quirky self-description of its AGPL codebase. That word is why The Document Foundation's June jab about a "freeware copy" of Microsoft Office landed the way it did.
None of this is hidden. It just wasn't what the launch marketing said.
The correction¶
The August post on this site called Euro-Office "a browser-based office suite built on a clean-room OOXML implementation by a European tech industry alliance" and, a few paragraphs later, "clean-room" in the sense of code written from the published OOXML specification without Microsoft's reference code. The FOSSY 2026 report five days earlier — and it deserves the credit — had the provenance right: an AGPLv3-licensed fork of OnlyOffice by a coalition including Nextcloud and IONOS, motivated in part by trust concerns over ONLYOFFICE's development-team geography, with contributing upstream described as "impossible or heavily discouraged" and build instructions described as "unreliable, outdated or simply broken" — characterizations ONLYOFFICE disputes.
The clean-room framing was half right in a narrow sense and wrong in the load-bearing one. The narrow sense: ONLYOFFICE has always claimed its format engine is its own work, not derived from Microsoft's code, and the fork inherits that engine wholesale — nothing about an AGPL re-fork makes the engine Microsoft-derived. The load-bearing sense: "built by a European tech industry alliance" reads as new code authored by a new coalition. It is not. The coalition governs, brands, and strips; the engine and most of the tree are a decade-plus of ONLYOFFICE code. The August post's operator guidance was unaffected by this error — the ODF-defaulting advice never depended on provenance — but this site's stated correction policy applies, so: the provenance is a fork, and the record here should have said so in August.
The licensing fight, with the primary artifact¶
The fork's first act was license hygiene, and the commit that did it is public. Commit e452ace in Euro-Office/core removes, from the copyright headers of files like ASCUtils.h and ASCUtilsDefines.h, exactly three things:
- the Ascensio System SIA contact block (Riga, Latvia),
- the Section 7(b) addendum: "Pursuant to Section 7(b) of the License you must retain the original Product logo when distributing the program,"
- the Section 7(e) addendum: "Pursuant to Section 7(e) we decline to grant you any rights under trademark law for use of our trademarks."
ONLYOFFICE called the removal a licensing violation in March and suspended its partnership with Nextcloud on March 31. Nextcloud answered, and so did the two organizations whose reading of copyleft actually governs this: the FSF's "AGPL is not a tool for taking freedom away" and Software Freedom Conservancy's April 16 piece that names the addenda "badgeware". The FSF/SFC position, as carried in the chronology: Section 7 additional terms may themselves carry restrictions; Section 10 of AGPLv3 says additional restrictions may be stripped on redistribution; and adding restrictions that revoke AGPL freedoms isn't how the license works.
The Register covered the dispute as "Forking frenzy ensues after launch of Euro-Office" on April 2. By the v1.0 launch on June 9, heise's report said — per the chronology — that OnlyOffice's violation allegation "had been resolved." By the FOSSY talk in August, the state on the ground was shakier: the site's own coverage records the fork team having not publicly answered the legal claim and the dispute as unresolved. Both readings are on this site now, and the honest position between them is: no court filing, registry entry, or withdrawal notice has been located by this site; what exists is a heise sentence, an unanswered-at-the-time legal claim, and a fork that has kept shipping. The August 20 post put the question as "if the coalition dissolves, who controls the code?" The first quarter of that answer arrived the good way — not through the coalition's intentions but through the license itself: the AGPL held, the addenda fell, and the fork proceeds.
What the desktop release actually settles¶
The August post's advice — prefer Collabora Online for now, because it is mature, ODF-native, and governed by a foundation whose statutes prevent single-company capture — is unchanged by everything above. The format critique stands untouched, too: the README of the desktop app still opens with "fully compatible with Office Open XML formats: .docx, .xlsx, .pptx," the fidelity target is still Microsoft's format family with ODF as the supported alternative, and the August rule — open the incoming .docx, store the created work in ODF, treat OOXML as interchange rather than storage — remains the correct default for a community running Nextcloud.
What actually changed on November 13 is the layer underneath the format argument: distribution. A fork's hardest artifact is not code — it is a signed update stream that operators can trust without trusting the fork's press releases. The desktop app is the first Euro-Office component that ships this way:
- Signed builds distributed as "Nextcloud Office" from nextcloud-releases/Office-DesktopEditors, with APT and DNF package repositories — this is the README's own description of the official channel.
- Unsigned community builds published on the Euro-Office/DesktopEditors releases page, with build-it-yourself instructions for Windows, Linux and macOS in the repo.
That is a materially better answer than most forks ever give to the who-controls-the-update-stream question, and it is the kind of artifact this site keeps asking sovereignty claims for — here the claimant has one.
Operator notes¶
Name the engine, not the brand, in your procurement documents. nextcloud.com/office/ now fronts "Nextcloud Office powered by Euro-Office," while Nextcloud Hub offers two supported office suites — the Collabora-based one and the Euro-Office-based one — and the desktop app is branded "Nextcloud Office" while being powered by the Euro-Office engine. A document that says only "Nextcloud Office" no longer specifies an engine, a license lineage, or a format philosophy. Write "Nextcloud Hub with Collabora Online" or with Euro-Office, and say which.
If you deploy the desktop app, pin the signed channel. APT and DNF repositories plus platform builds from the Nextcloud-run releases project are the path with signed artifacts; the GitHub releases page self-describes its builds as unsigned. For a fire hall that installs software on machines nobody re-keys, the signed channel is the difference between an update path and a supply-chain question.
Audit the headers yourself; the fork graph won't save you. The repository was re-rooted — 457 commits with no GitHub fork-parent — so provenance is documented by the component names, the inherited Ascensio copyright header (which is correct AGPL attribution and should stay), the inherited version numbering, and the onlyoffice-derived README text, not by GitHub's UI. Anyone doing a supply-chain assessment of this suite should diff the tree against ONLYOFFICE's upstream rather than trusting any summary, including this one.
The offline argument is now available on the OOXML-fidelity lane. The August piece recorded the Austrian military's criterion for office software — works offline, on own hardware, no phone-home — as the reason LibreOffice won their 16,000-workstation migration. LibreOffice remains the ODF-native answer to that test. The desktop app is the first FOSS component that passes the same test with OOXML fidelity as the goal, under a clean AGPL-only grant, with the addenda fight already run through the FSF and SFC. If your community's problem is "we open 15 years of .docx and the internet sometimes goes down," this is now a legitimate shortlist entry — as an application you install beside your Nextcloud, not as a replacement for the storage-format discipline.
Honest column¶
- The "resolved" status of the ONLYOFFICE violation claim rests on a heise sentence via the Wikipedia chronology; no legal instrument or withdrawal notice was located. The site's own August coverage recorded the dispute as unresolved with the fork team publicly silent. Both stand, and neither is a court.
- No security-advisory channel for the Euro-Office fork was located tonight — no advisory page, no published CVE process, no statement of how ONLYOFFICE's engine CVEs will be tracked and re-distributed in the fork. For a suite whose engine has a long public CVE history, that absence is now the single biggest procurement question, bigger than licensing ever was.
- The desktop Linux story has three sources with three artifact lists:
.deb/.rpm(official blog), APT/DNF repositories (README), AppImage (Wikipedia). These are compatible reports of different channels, but nobody has published a canonical artifact list; check what your package manager actually sees before writing an install runbook. - Wikipedia's infobox lists iOS and Android support with a citation pointing at ONLYOFFICE's own website — a citation wrong at birth for a Euro-Office product page. No Euro-Office mobile client exists tonight. The infobox was probably built from a template of the parent suite's article; the same risk applies to every summary someone handed you about this fork, including the launch marketing.
- The fork point against upstream ONLYOFFICE was not diffed. What, besides the addenda removal, the rebrand, and the build-system surgery, actually diverges from ONLYOFFICE's tree is unknown from tonight's work; the honest default is to assume deep equivalence and verify when a decision depends on it.
Watch items¶
- Whether a fork-run security advisory channel appears, and how it maps to ONLYOFFICE's engine CVE history.
- Whether ONLYOFFICE responds publicly to the desktop ship and the "Nextcloud Office" branding of its own suite's derivative.
- Whether The Document Foundation answers the desktop release — its "de facto ally" framing was aimed at browser OOXML defaults, and a downloadable same-codebase desktop app raises the stakes on the five-layer lock-in argument TDF owns.
- Whether the APT/DNF repositories get their own signing-key documentation and rotation policy, or whether they inherit Nextcloud's general release infrastructure quietly.
- The mobile client: the September post promised the desktop app; nothing so far has promised a phone, and a suite without one is half a product for the communities that live on phones.