Collabora Online vs Euro-Office: which to choose

Collabora Online or Euro-Office: when each one fits

Choose Euro-Office if you are standardizing on Nextcloud Office and most of your documents are Microsoft-format files, since it is the default editor behind Nextcloud Office and edits DOCX, PPTX and XLSX alongside OpenDocument formats. Choose Collabora Online if you want LibreOffice-based editing under MPL-2.0 and a paid support tier for production use. Four factors decide the choice: how your documents render in each editor, how comfortable your legal and procurement teams are with the licensing history, whether you want signed builds with vendor support or builds you assemble yourself, and how much server capacity you can dedicate to the editor. Write down your answers for each factor before comparing feature lists.

Licensing and support often matter more than teams expect. Collabora Online's server code is under MPL-2.0, and the Collabora Online pricing page lists its Business plan at 3 euros per user per month for up to 99 users, with long term support, an SLA, signed security updates and customer portal access. Euro-Office is built on ONLYOFFICE, which is distributed under AGPLv3, and Nextcloud states that Euro-Office removed ONLYOFFICE's Section 7 logo requirement. ONLYOFFICE suspended its partnership with Nextcloud on March 31, 2026, so have counsel review that history against your policy. Signed Nextcloud Office builds come with package repositories and support through a Nextcloud Enterprise subscription, while unsigned Euro-Office community builds are meant for testing. Confirm whether your existing Nextcloud contract already covers the editor before buying a second support agreement.

Server footprint and operations differ in shape. The Euro-Office Document Server is not a standalone application and needs a platform such as Nextcloud to store the files, so it becomes one more component inside your Nextcloud deployment. Collabora's Helm chart README recommends 8 CPU cores and 8000 MiB of memory per pod for production, with requests of 4 cores and 6000 MiB, and disables horizontal autoscaling because scaling breaks collaborative editing, so you set replicas by hand and route load balancers by the WOPISrc parameter. Before you choose, run a pilot with your heaviest Word and Excel files in both editors, and ask each vendor to confirm sizing for your expected number of concurrent editors.

Which editor fits which scenario

This table matches common deployment situations to the editor that usually fits better and the condition behind each choice. Read each row against your file platform, your document mix and your procurement rules. Format behavior should be confirmed with your own sample documents before either editor is standardized.

Scenario	Better fit	Condition that makes it so
Nextcloud-first deployment with no other file platform	Euro-Office (Nextcloud Office)	Nextcloud's admin manual names Nextcloud Office, powered by Euro-Office, as the default. Choose Collabora if you want the officially supported alternative instead.
Multi-platform file estate using WOPI	Collabora Online	Collabora lists WOPI integrations with Nextcloud, ownCloud, Seafile and several others. Confirm the exact WOPI behavior of Euro-Office with each platform you plan to connect.
Mixed Microsoft Office estate	Test both before choosing	Euro-Office lists DOCX, PPTX and XLSX editing, while Collabora is built on LibreOffice. Run your own documents, macros and layouts through both editors before deciding.
Sovereignty-driven procurement	Depends on the governance you require	Euro-Office launched with European backers under a shared governance framework and depends on signed builds via Nextcloud Enterprise. Collabora Online is MPL-2.0 with a paid Business plan. Ask both vendors for their support and governance terms in writing.
Teams that need a paid, supported build with per-user pricing	Collabora Online	Collabora's pricing page lists a Business plan at 3 euros per user per month for up to 99 users, with long-term support and signed security updates. Confirm current pricing and terms before budgeting.
Teams that need only testing or a proof of concept	Euro-Office community build or CODE	Collabora describes CODE as suited to testing and small teams, not production. Euro-Office community builds are unsigned and intended for testing. Do not move either test build into production without a supported build.

How each editor is built and what that means for operations

Euro-Office and Collabora Online both edit documents in the browser, but they reach your users through different parts of the stack. The differences in how each one is packaged, what it depends on and how it scales decide who runs it, how it is patched and what the load balancer must do. The cards below cover the decisions that follow from those differences.

Euro-Office needs a host platform

The Euro-Office Document Server is not a standalone application. It needs a platform such as Nextcloud to store the files it edits, so it is never a separate place for users to log in or keep documents. Before you commit, confirm which host platforms and versions your team will run alongside it, and who owns the connector between them. Test how a file moves from storage to the editor and back, including version history and permissions.

Collabora Online as a WOPI server

Collabora Online works as a WOPI-integrated server. The file platform hands it a document reference, and the editor reads and writes the file through the WOPI protocol. That means the integration is a contract between two systems, not a bundled app. Check which file platforms and versions your team uses with Collabora Online, and confirm how each one handles WOPI host discovery, file locking and token expiry in your own environment.

Three ways to deploy Collabora

Collabora Online can be deployed from Docker images, from system packages or on Kubernetes, and the Collabora Online Controller is offered for large deployments. Choose the path your operations team can patch and monitor on its own schedule. Ask Collabora which path it supports for your file platform version, and whether the Controller's scope matches the number of pods you expect to run.

Helm chart disables autoscaling

The official Collabora Online Helm chart disables horizontal pod autoscaling, because scaling breaks collaborative editing and copy and paste. Replicas are set manually, so capacity planning becomes an operating task you own. Build a runbook for adding and removing pods during peak hours, and test it on a staging cluster before production.

Route by WOPISrc

Load balancers must route requests by the WOPISrc parameter, so every user editing one document reaches the same pod. A generic round-robin setup will split a co-editing session across pods and break it. Confirm that your ingress controller, whether Nginx, HAProxy or OpenShift Router, can match on that parameter, and test it with two users on one file before go-live.

Per-pod sizing for production

The chart recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB. These are the only sizing figures to plan from, and your real demand depends on concurrent editors and document size. Budget node capacity for the pod count you need, and treat these values as the chart's starting point, not a guarantee for your workload.

Format fidelity, licensing and footprint compared

This table sets Euro-Office and Collabora Online side by side on license, source base, formats, builds, support, AI options, packaging and Nextcloud integration. Read each row as a question to answer for your own environment, since the table shows what is documented, not how your documents will render. The main takeaway is that the two editors share little code history, so format fidelity is a test you run, not a fact you look up.

Criterion	Euro-Office	Collabora Online
Core license	AGPL-3.0, inherited from the ONLYOFFICE Docs code it is built on	MPL-2.0 for the Collabora Online server code
Source base	Built on ONLYOFFICE, which Nextcloud states is distributed under AGPLv3	Built on LibreOffice technology
Supported formats	Edits DOCX, PPTX, XLSX, PDF, ODT, ODS and ODP with real-time co-editing	Editing of documents, spreadsheets and presentations in the browser, with OpenDocument and Microsoft formats
Format test to run	Open your own DOCX, XLSX and PPTX files with complex tables, tracked changes and macros-free templates	Open the same files, plus any legacy formats in your archive, and compare layout after a round trip
Builds	Nextcloud Office signed production builds, plus unsigned community builds for testing	Docker images, system packages and Kubernetes deployment, with the free CODE edition for testing
Paid support	Through a Nextcloud Enterprise subscription for Nextcloud Office	Collabora Online paid plans with long term support, signed security updates and a service level agreement
AI assistant	Not documented in the supplied facts; confirm with the vendor before relying on it	Optional assistant in 26.04, off by default, with the administrator choosing an external or self-hosted provider
Deployment packaging	Requires a Euro-Office Document Server paired with a platform such as Nextcloud that stores the files	Standalone online server that connects to file platforms over WOPI, with a Helm chart for Kubernetes
Nextcloud integration path	Default office solution in Nextcloud Office, powered by Euro-Office	Fully supported alternative in Nextcloud, run as a built-in app or self-hosted server

What the licenses and paid editions actually give you

Euro-Office is licensed under AGPL-3.0, and one source tree produces two builds with different support paths. Nextcloud Office is the signed build intended for production, distributed through package repositories and supported through a Nextcloud Enterprise subscription. The unsigned Euro-Office community builds are meant for testing. The license question and the build question are separate, so a team can be fully licensed under the AGPL and still have no vendor support for the build it runs.

Source license: The Euro-Office Document Server is AGPL-3.0, and DocumentServer v9.3.5 was published on October 9, 2026. Your obligations depend on how you host and distribute the software, so confirm with counsel how the AGPL applies to your deployment.
Signed production builds: Nextcloud Office is signed and ships with package repositories. Its support comes through a Nextcloud Enterprise subscription, so ask which components the subscription covers and what response commitments it includes in writing.
Community builds: Unsigned builds are intended for testing. A production team should not treat them as a supported path, even though the source is the same.
Host dependency: The Document Server is not a standalone application. It needs a platform such as Nextcloud to store the files it edits.

Confirm in writing whether your Nextcloud Enterprise subscription covers the Document Server in your environment, not only the Nextcloud core.

How the ONLYOFFICE dispute affects long-term choice

The origin of Euro-Office matters for procurement because it is built on ONLYOFFICE code, and ONLYOFFICE distributes that code under AGPLv3. Nextcloud states that Euro-Office is built on ONLYOFFICE and that it removed ONLYOFFICE's Section 7 requirement to display its logo. ONLYOFFICE, for its part, suspended its partnership with Nextcloud on March 31, 2026, and calls Euro-Office a direct reuse of its technology presented under a different identity. Both positions are stated in public, and this page does not decide between them. What matters for your decision is that the licensing position of the editor component sits in a dispute between two parties that is still open, and your architecture should be able to survive either outcome. Ask Nextcloud in writing which upstream ONLYOFFICE version each Euro-Office release tracks, how it handles upstream security fixes, and what it will do if a court or the upstream licensor changes the terms under which those fixes can be redistributed.

ONLYOFFICE has said it will keep supporting and developing the ONLYOFFICE connector for Nextcloud, so a connector-based deployment is not automatically cut off. Confirm that in writing as well, and ask ONLYOFFICE whether that commitment covers the Document Server version you would run, its security patch timing and the Nextcloud versions it certifies. If you take the Nextcloud Office route, ask Nextcloud whether signed Nextcloud Office builds will remain available for the Euro-Office line you choose, which package repositories you will depend on, and how long each release line receives fixes. For Collabora Online, ask Collabora whether its MPL-2.0 build and its support terms are independent of the ONLYOFFICE dispute, so that a switch in either direction does not require re-procurement of the whole stack. Record the answers in the contract or the vendor support file, not in a sales email.

Plan for a switch before you need one. Keep documents in open formats where possible, test your own DOCX, XLSX and PPTX files in both editors, and document the WOPI or connector configuration in your runbook so that changing the online editor is a configuration exercise rather than a re-architecture. Set a review point in your procurement calendar tied to the next Nextcloud Hub release and to any public statement from ONLYOFFICE or Nextcloud about the dispute. If you are a regulated organization, bring the written answers to your compliance and legal reviewers before you sign, because the license position of the editor affects what you can redistribute, modify and support internally. The answers may also determine whether you need a commercial agreement with a vendor or can operate the community build under your own maintenance process.

What drives running cost for each editor

Running either editor means paying for infrastructure, people, support and upgrades, and the split between them differs. Collabora Online and Euro-Office have different support routes, different scaling constraints and different release cadences, so the same server count can produce very different annual bills. Use the cards below to turn each driver into questions for your vendor and your own team.

Infrastructure footprint per editor

Collabora Online is a separate service that Nextcloud calls over WOPI, so you pay for its containers or server as an extra workload. Euro-Office Document Server is not a standalone application and needs a platform such as Nextcloud that stores the files, so its footprint sits beside your file platform. Ask each vendor for the CPU and memory it expects per concurrent editing session, and size a pilot with your own largest documents before you commit hardware.

Kubernetes and autoscaling constraints

The official Collabora Online Helm chart disables horizontal pod autoscaling because scaling breaks collaborative editing and copy and paste, so replicas are set by hand. It also requires load balancers to route by the WOPISrc parameter, which adds ingress configuration and monitoring work. Estimate the always-on capacity you must keep for peak editing hours, since extra replicas cost money even when idle.

Skills to operate the editor

Most of the recurring cost is staff time: patching, certificate rotation, ingress tuning and troubleshooting document sessions. Collabora Online sits on LibreOffice technology, while Euro-Office inherits the ONLYOFFICE document server stack, so each team needs different debugging skills. Check whether your platform team already runs Docker or Kubernetes and whether someone can follow the Nextcloud admin documentation for office integration.

Support and who you pay

Collabora Online is priced per user for its Business and Enterprise plans, while signed Euro-Office builds are supported through a Nextcloud Enterprise subscription. Collabora's Business plan costs 3 euros per user per month for up to 99 users, according to Collabora's pricing page, and includes long term support and signed security updates. Ask Nextcloud for the Enterprise subscription scope and ask Collabora whether its per-user fee covers your full user count, since that fee recurs every month.

Upgrades across release lines

Collabora Online runs point releases on the 25.04 line as well as newer lines, and the free CODE edition is a rolling release that Collabora does not recommend for production. Euro-Office ships its own DocumentServer versions alongside Nextcloud Hub releases, so you must match two moving parts. Budget test cycles for each upgrade on both sides of the connector, and confirm how long each line receives security fixes.

Edition features that add cost

Collabora's Enterprise plan adds integration support, customization services and roadmap input for 100 or more users, which are one-time or recurring services you must scope in writing. Euro-Office gets its production build and package repositories through the Nextcloud Enterprise subscription, while unsigned community builds carry no such support. Ask each vendor which features, such as AI assistant hosting, are included, optional or billed separately.

Moving documents and users between the two editors

This sequence shows how a team moves its online editing from Collabora Online to Euro-Office, or the reverse, with files staying where they are and only the editing layer being rebuilt and retired.

Inventory formats, macros and open sessions
The platform owner lists the file types in use, such as DOCX, XLSX, PPTX, ODT, ODS and ODP, along with any macros, embedded objects, tracked-change conventions and templates that users rely on. The same owner records which users are on the current editor and whether long editing sessions are common. Done means a written inventory that the editing team and the business owners have both reviewed, with each file type marked as in scope or out of scope for the move. Ask both vendors which formats they handle and which features they do not, rather than relying on a general list.
Test representative files in both editors
The editing team builds a test set from the inventory, including complex layouts, tables, charts, comments, fonts and any macro-driven spreadsheets, and opens each file in Collabora Online and in Euro-Office. Reviewers compare rendering, co-editing behavior, saved output and round-trip edits against the originals. Done means a signed-off test report that names the files that failed or changed, and a decision on whether each gap is acceptable, needs a workaround or blocks the move. Keep the test set as the regression suite for later upgrades.
Change the connector setting in the file platform
The platform administrator switches the office app or connector setting in the file platform to the target editor, following the configuration documentation for that platform. For Nextcloud, the admin manual describes Nextcloud Office as the default, powered by Euro-Office and requiring a Euro-Office Document Server, and Collabora Online as a supported alternative. Done means a test account can open, edit and save each test file through the new editor, and the change is recorded in the change log with the previous setting noted for rollback.
Migrate open sessions and plan the cutover window
Because files stay in the file platform, the move does not copy document content. The team instead decides how to handle sessions that are open during the switch, asking users to save and close documents, and schedules a window when editing traffic is lowest. The administrator confirms with the vendors how in-progress co-editing sessions behave during a change of editor. Done means a published cutover notice, a named contact for users, and a rollback plan that restores the previous connector setting if the test accounts fail.
Rebuild WOPI connections, load balancer rules and monitoring
These items do not transfer and must be rebuilt for the new editor. The team recreates the WOPI endpoint configuration, updates load balancer rules so that all users editing one document reach the same backend, and points health checks, logs and alerts at the new service. For Collabora Online on Kubernetes, the Helm chart documentation says load balancers must route by the WOPISrc parameter and that horizontal autoscaling is disabled. Done means a monitored test session stays on one backend for its full duration and alerts fire on a deliberate fault.
Retire the old Document Server
After a stable period on the new editor, the team removes the old document server, its certificates, its DNS entries and its firewall rules, and archives its configuration and logs according to the retention policy. Licenses and support contracts tied to the old editor are cancelled or confirmed as ended. Done means the old service no longer answers requests, the decommissioning record lists every removed component, and the file platform logs show no calls to the retired endpoint for the agreed observation period.

What implementing each editor involves and where projects run long

Implementing either editor means deciding where the document server runs, how the file platform reaches it, and how users are routed to it. Collabora Online can be installed from Docker images, system packages or Kubernetes, and the project's Helm chart is the route most teams take for larger deployments. Euro-Office is different: its Document Server is not a standalone application and needs a platform such as Nextcloud that stores the files, so the work starts with the Nextcloud side of the integration. Plan the TLS certificates for the public office endpoint and the internal callback path separately, confirm that the file platform can reach the editor by the hostname you publish, and check how storage paths and file permissions behave when the editor writes back. Confirm each step against the current installation guide for your chosen version rather than an older tutorial, because packaging and ingress options change between releases.

On Kubernetes, the most common source of delay with Collabora Online is load balancer affinity. The Helm chart README states that horizontal pod autoscaling is disabled because scaling breaks collaborative editing and copy and paste, and that load balancers must route by the WOPISrc parameter so every user editing one document reaches the same pod. Your ingress (the chart supports Nginx, HAProxy and OpenShift Router) has to honor that routing from the first test, and the replica count is set by hand. Test with two or more users co-editing one file during the pilot, not just a single login. Euro-Office raises a different decision: whether to use signed Nextcloud Office builds with package repositories and Nextcloud Enterprise support, or unsigned Euro-Office community builds meant for testing. Settle that choice before the pilot, because moving between the two later means re-validating the environment.

Format testing is where projects usually run long. Both editors claim DOCX, PPTX, XLSX and PDF handling, but fidelity depends on your documents, including tracked changes, embedded fonts, macros, complex tables and older files. Assemble a sample drawn from every department and file age, open and save each file in both editors, and record what breaks. Budget time for this as a recurring step, since each Nextcloud or editor upgrade can change rendering. DeployOpen plans, implements and tests these deployments inside your own infrastructure and fixes scope in writing before work starts. It does not publish a price list, so ask for a written scope that names the document sample, the ingress and certificate work, and the upgrade and support terms before you compare quotes.

Questions buyers ask before choosing an online editor

Which online editor is cheaper to run in practice?

Licensing rarely decides this on its own, because both editors are open source. Collabora Online's server code is MPL-2.0, and the Collabora pricing page lists its Business plan at 3 euros per user per month for up to 99 users, with long term support, an SLA and signed security updates. Euro-Office is AGPL-3.0 and reaches production through Nextcloud Office, where signed builds come with a Nextcloud Enterprise subscription. Model the recurring costs: any per-user subscription, the servers you run for each editor, staff time for upgrades and the support contract you need. Ask each vendor for a written quote that states user count, support tier and the number of server nodes.

How long does a Collabora Online or Euro-Office deployment take?

No supplied source gives a reliable duration, so scope sets the timeline. The main drivers are the file platform you already run, whether you need one server or several pods, the ingress you use, how many people co-edit at once and how much format testing you require. Collabora's Helm chart README sets replica counts manually and requires load balancers to route by the WOPISrc parameter, so a Kubernetes rollout involves more design work than a single container. Euro-Office needs a Document Server connected to Nextcloud. DeployOpen delivers most engagements as fixed scope, with timelines agreed in writing before work starts. Ask for the prerequisites and acceptance tests behind any estimate you receive.

Can our team run an online editor without outside help?

Yes, if your staff can operate containers, a reverse proxy, a database and a file platform, and can test document output after each change. Collabora offers Docker images, system packages and Kubernetes deployment, and the free CODE image is collabora/code. Euro-Office depends on Nextcloud, so your Nextcloud administrators carry most of the operating load. The gaps teams often miss are session affinity for co-editing, WOPI and certificate configuration, a patch cadence and format regression testing after upgrades. If those gaps are real, DeployOpen can plan, implement, harden and document the deployment, and offer ongoing support or upgrades as a retainer. Confirm internal capacity before choosing a model.

Can Collabora CODE run in production?

Collabora describes CODE as the free edition, suited to testing, home use or small teams, and not recommended for production. It is released roughly once a month as a rolling release. The paid Collabora Online build adds tested updates, security fixes and support, and the Business plan lists long term support, a service level agreement, signed security updates and customer portal access. Weigh that against your own change control and patch requirements, and confirm with Collabora whether its terms cover your intended use. Check the Collabora CODE page for the current wording before you decide.

Are Euro-Office community builds safe for production?

The supplied sources describe unsigned Euro-Office community builds as intended for testing. Signed Nextcloud Office builds, delivered through package repositories and supported under a Nextcloud Enterprise subscription, are the production path. Euro-Office is built on ONLYOFFICE under AGPL-3.0, and ONLYOFFICE has said it suspended its partnership with Nextcloud and objected to how its technology is presented. Before production, get written answers on the build you will deploy, the upgrade path, the support scope and the licensing position for your organization. Have counsel review the dispute and the logo change Nextcloud made before you rely on either build.

How do we test format fidelity before choosing an editor?

Test with your own documents. Build a corpus of real DOCX, XLSX and PPTX files that includes tracked changes, comments, embedded charts, complex tables, your corporate templates and any PDF or OpenDocument files staff use. Collabora is built on LibreOffice technology, and Euro-Office edits DOCX, PPTX, XLSX, PDF, ODT, ODS and ODP files with real-time co-editing. Open each file in both editors, compare layout, fonts, formulas and comments, and log defects with screenshots. Repeat the same test after every release. Ask both vendors which conversions they document as known limitations.

What does switching editors later require?

Switching is mainly a change to the connection between your file platform and the editor, plus the testing effort, because the documents stay in your file platform. The Nextcloud admin manual describes Collabora Online as a fully supported alternative to Nextcloud Office, run as a built-in app or a self-hosted server. Plan for re-running your format corpus, updating user expectations on layout and features, reviewing where previews and caches live, adjusting ingress and monitoring rules, and retraining staff. Ask each vendor what a rollback looks like and whether any editor-specific data sits outside the files. Keep the old editor available until acceptance tests pass.

How DeployOpen helps you choose and implement

DeployOpen plans and implements self-hosted open-source platforms inside your own infrastructure, including cloud accounts, data centers and air-gapped networks. For the Collabora Online vs Euro-Office decision, we start by testing both editors against your own document set and hosting constraints before any build begins.

How we scope

We review which file platform, document formats and hosting model your team already runs or plans to run.
Engagements are fixed-scope, with the editor choice, deliverables and timelines agreed in writing before work starts.
The written scope names the test documents, user groups and integration points covered for both editors.
Ongoing support, upgrades and continuous testing can be added as a retainer once the initial scope is complete.

How we build

We deploy the chosen editor in your environment, with the server, database and ingress set up to your standards.
Where a file platform integration is needed, we configure the connector and verify document opening, saving and co-editing.
We run security testing on the deployed editor and its integration points, and record the findings and fixes.
We prepare configuration, system and evidence documentation so compliance assessors can review the controls directly.

How we hand over

Handover covers runbooks for installation, upgrades, backups and restoration of the editor and its connected services.
We document the licensing terms and edition features that apply to the build you deployed, so your team can confirm them.
Your staff receive a walkthrough of the configuration, monitoring points and known limits for the chosen editor.
The handover package states which items are your responsibility after go-live and which are covered by a retainer.

How we support

Retainers can cover maintenance, version upgrades and re-testing after each significant release of the editor.
We can repeat document compatibility checks when a new build changes format handling or connector behavior.
Support scope, response expectations and upgrade windows are written into the retainer before work begins.
If you later move to the other editor, we can scope that migration as a separate fixed-scope engagement.

Collabora Online vs Euro-Office