Collabora Online vs ONLYOFFICE: which to choose

Collabora Online vs ONLYOFFICE: when each one fits

Choose Collabora Online when your team already runs Nextcloud, ownCloud, Seafile or another WOPI-capable file platform and wants an online editor built on LibreOffice technology under the Mozilla Public License 2.0. Collabora is integrated through the WOPI protocol, and its paid Business plan is listed at 3 euros per user per month for up to 99 users, with long term support, a service level agreement, signed security updates and customer portal access. That paid tier is the point of the decision: the free CODE edition is described by Collabora as not recommended for production, so a production budget must cover the supported build from the start. Confirm the Business plan terms and any volume discount for 100 or more users directly with Collabora before you rely on them in a budget.

Choose ONLYOFFICE when your documents are mostly Office Open XML files and fidelity to .docx, .xlsx and .pptx is the first requirement, since those are the editor's native formats. The Community Edition is AGPL-3.0 licensed, and with ONLYOFFICE Docs 9.4, released on May 19, 2026, the 20 simultaneous connection limit was removed from it. Choose the paid Enterprise Edition when you need an admin panel, white labeling, scaling for thousands of users or Basic, Plus or Premium support, since the edition comparison lists these as Enterprise features. Check each feature you need against the ONLYOFFICE edition comparison rather than assuming it carries over from the Community build.

The decision turns on three checks. First, run a fidelity test on your own documents, including complex tables, tracked changes, embedded objects and the templates your legal and finance teams actually use, in both editors. Second, compare support models: Collabora sells support as a per-user subscription, while ONLYOFFICE Community support runs through GitHub and the forum and paid support sits in Enterprise. Third, list the edition features you need, such as administration, branding or support hours, and price them against the written scope. Ask each vendor to confirm these items in writing, because the features that matter most to your team are the ones most likely to sit in a paid tier.

Which editor fits which scenario

This table maps common situations to the editor that fits them better and the condition that tips the decision. Read each row as a starting point, then confirm the condition against your own documents, user counts and support requirements before committing.

Scenario	Better fit	Condition that makes it so
Nextcloud or ownCloud site with mostly OpenDocument files	Collabora Online	Your documents are .odt, .ods and .odp, and LibreOffice-based rendering matches what your users expect. Test a sample set before deciding.
Site where Microsoft Office files dominate	ONLYOFFICE Docs	Your daily work centers on .docx, .xlsx and .pptx files, which ONLYOFFICE handles as native formats. Confirm fidelity with your own templates and macros.
Team that needs white labeling or an admin panel	ONLYOFFICE Docs (Enterprise Edition)	Both features are listed as Enterprise Edition items in ONLYOFFICE's comparison, so budget for that edition. Confirm the exact features your brand policy requires.
Software vendor embedding editors in a service for its customers	ONLYOFFICE Docs (Developer Edition)	ONLYOFFICE sells a Developer Edition under a commercial license for vendors that embed the editors. Confirm the license terms with ONLYOFFICE before shipping.
Large Kubernetes deployment with many concurrent editors	Collabora Online (paid build, with the Controller)	Collabora's Helm chart disables autoscaling, so replicas are set manually and the load balancer must route by WOPISrc. Plan capacity and session affinity with your platform team.
Small team evaluating before purchase	Collabora Online CODE or ONLYOFFICE Docs Community Edition	CODE is described as suited to testing and small teams but not recommended for production. Use it to evaluate, then move to a supported build before go-live.
Production with contractual support and security update commitments	Depends on the paid support you buy	Compare Collabora's Business plan terms with ONLYOFFICE's Basic, Plus or Premium support tiers. Ask each vendor for written support scope, response windows and SLA terms.

How each editor is built and what that means for operations

Both editors plug into the file platform through WOPI-style integration, but they differ in how they scale, what they depend on and how often they ship. The cards below tie each design point to the work your team will own after go-live.

WOPI connects each editor to the file platform

Both Collabora Online and ONLYOFFICE Docs are reached by the file platform rather than serving users directly, so the file server hands documents to the editor and the browser opens them there. Collabora integrates through the WOPI protocol and lists Nextcloud and ownCloud among its supported platforms. ONLYOFFICE Docs also lists Nextcloud, ownCloud and Seafile as integrations. Operationally, your team must confirm the editor URL, the callback addresses and the TLS trust between the two services in your own environment before any user testing.

Collabora Kubernetes routing constraints

The official Helm chart disables horizontal pod autoscaling because scaling breaks collaborative editing and copy and paste, so replica counts are set by hand. Load balancers must route by the WOPISrc parameter so every user editing one document reaches the same pod. Your platform team owns the ingress choice (Nginx, HAProxy or OpenShift Router are supported) and the capacity planning that replaces autoscaling. Ask the vendor how a pod restart affects open sessions before you commit to this layout.

Collabora production pod sizing

The chart recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB. Those figures are the baseline for capacity reviews and for the node pools you reserve. Because replicas are fixed, every additional pod you add to absorb peak load consumes that full reservation. Budget the node capacity and the cloud or hardware cost of that footprint up front, since it recurs for as long as the cluster runs.

ONLYOFFICE 9.4 single process design

ONLYOFFICE Docs 9.4, released May 19, 2026, removed the 20 simultaneous connection limit from the Community Edition and consolidated the service into a single process with no RabbitMQ or database dependencies. That shrinks the set of components your team must back up, patch and monitor. It also means fewer moving parts to troubleshoot during an incident. Confirm the concurrency you need in load tests, because removing the limit does not replace the sizing work for your own user count.

Deployment methods each editor supports

Collabora Online installs from Docker images, system packages or Kubernetes, and offers the Collabora Online Controller for large deployments. ONLYOFFICE Docs recommends Docker as its installation method. Choose the method your platform team already operates, because the upgrade path, rollback and certificate handling follow it. Confirm which method your file platform's documentation supports for the editor version you plan to run.

Native formats and conversion paths

ONLYOFFICE treats .docx, .xlsx and .pptx as its native Office Open XML formats, and converts DOC, ODT, RTF, ODS, CSV and ODP. Collabora is built on LibreOffice technology, so its document handling follows the LibreOffice engine. For your operation, the practical question is which conversions run on the server and which files users open in the browser. Test your own document set in both editors before you standardize, because conversion errors surface as user complaints, not as server alerts.

Release cadence each vendor publishes

ONLYOFFICE publishes DocumentServer releases on GitHub, with v10.0.0 dated October 12, 2026 after v9.4.0 on May 19, 2026. Collabora's free CODE edition is a rolling release, typically about one build a month, while the paid Collabora Online branch receives point releases such as 25.04.13 on September 21, 2026. Plan a patch window for whichever cadence you adopt, and confirm with each vendor which branch receives security fixes and for how long.

Feature by feature: Collabora Online and ONLYOFFICE

This table compares the two online office editors on license, editions, support, file formats, integrations and deployment guidance. Read each row as a question to put to both vendors, since the facts supplied cover some capabilities in depth and others only by name.

Capability	Collabora Online	ONLYOFFICE Docs
Server license	MPL-2.0 for the Collabora Online server code, per its COPYING file	AGPL-3.0 for ONLYOFFICE Docs Community Edition
Free edition and production use	CODE is free and rolling, but Collabora describes it as not recommended for production	Community Edition is free under AGPL-3.0; confirm with ONLYOFFICE whether its production terms fit your deployment
Connection limit history	No connection limit is named in the supplied facts; confirm current limits with Collabora	Removed the 20 simultaneous connection limit from Community Edition in version 9.4, released May 19, 2026
Paid edition contents	Business plan at 3 euros per user per month for up to 99 users, with long term support, SLA, signed security updates and portal access	Enterprise Edition adds admin panel, white labeling and scaling for thousands of users; Developer Edition is a commercial license for embedding
Support tiers	Business and Enterprise plans; Enterprise for 100 or more users is quoted, with integration support and customization services	Community support through GitHub and forum; Enterprise offers Basic, Plus or Premium support
Native file formats	Built on LibreOffice, with OpenDocument and Microsoft format support; test your own Office files before choosing	Native .docx, .xlsx and .pptx; converts DOC, ODT, RTF, ODS, CSV and ODP
PDF editing	Not covered in the supplied facts; confirm with Collabora	Includes text editing, page manipulation, annotations and form filling
AI assistant	Version 26.04, announced July 23, 2026, adds an optional AI assistant that is off by default and can use an external or self-hosted provider	Not covered in the supplied facts; confirm with ONLYOFFICE
WOPI and named integrations	WOPI-based; lists Nextcloud, ownCloud, Seafile, WordPress, Alfresco, Mattermost and others	Integrates with Nextcloud, ownCloud, Seafile, Moodle, Odoo and WOPI-compatible platforms
Kubernetes guidance	Official Helm chart; autoscaling disabled, replicas set manually, load balancer must route by WOPISrc	Docker is the recommended installation method; confirm Kubernetes guidance with ONLYOFFICE

What the license and paid editions include for each platform

Collabora Online's server code is licensed under the Mozilla Public License 2.0, and the source repository is public. The free edition, CODE (Collabora Online Development Edition), is a rolling release published on average once a month. Collabora describes CODE as suited to testing, home use or small teams, and states that it is not recommended for production. The paid Collabora Online build adds tested updates, security fixes and support. Its Business plan is listed at 3 euros per user per month for up to 99 users, according to Collabora's pricing page, and includes long term support, a service level agreement, signed security updates and customer portal access. The Enterprise plan covers 100 or more users, is quoted with volume discounts, and adds integration support, customization services and roadmap input.

Free route: CODE suits a lab, a pilot or a small team that accepts monthly changes and handles its own patch testing.
Business plan: Buy this when you need signed security updates, long term support and an SLA for a production office suite.
Enterprise plan: Buy this when you need integration support, customization services or input into the roadmap, and confirm the volume quote with Collabora.
Per-user cost: The Business price is per user, so ask whether service accounts, guests and shared mailboxes count toward the total.
Support boundary: DeployOpen can plan, install and test the deployment, but the vendor's SLA applies to the Collabora product itself.

Before you buy, confirm the current plan terms, the SLA wording and which edition your file platform's integration documents support.

What drives the running cost of each editor

The running cost of a self-hosted online office is not only a license line. For Collabora Online, the only subscription figure supplied is the Business plan at 3 euros per user per month for up to 99 users, which includes long term support, a service level agreement, signed security updates and customer portal access. Enterprise, for 100 or more users, is quoted with volume discounts and adds integration support, customization services and roadmap input, so ask Collabora for a written figure at your user count. The per-user fee recurs for as long as you keep the paid build. The free CODE edition carries no subscription, but Collabora describes it as not recommended for production, so a production team should price the Business plan rather than assume CODE is free to run at scale. For ONLYOFFICE, no pricing was supplied for this comparison. Ask for the Enterprise Edition and Developer Edition quotes, the support tier (Basic, Plus or Premium) and whether they are priced per server, per user or per connection, since the Community Edition no longer has its connection limit after version 9.4.

Infrastructure is the second recurring cost, and both vendors publish sizing you can use as a baseline. The Collabora Online Helm chart README recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB, and the chart disables horizontal autoscaling, so you pay for the replicas you set by hand. Multiply those figures by the number of pods your load balancer and session affinity need, plus a standby for maintenance. ONLYOFFICE's sizing depends on the deployment; confirm its documented minimum and recommended resources for your user count in its installation guide before you budget. Staff time is the cost most often missed. Count the hours for upgrades, testing your document formats after each release, monitoring the document server and the file platform's connector, and handling incidents. Ask each vendor how often it ships security fixes to the release you run, because that sets your patch cadence.

Separate one-time costs from recurring ones in the quote. One-time items include the initial deployment, integration with your file platform, the migration of test documents and any customization. Recurring items include subscriptions, support contracts, infrastructure, and staff time for upgrades and monitoring. Ask for a written quote that lists each line, names the edition and support tier, states the term and renewal terms, and says whether price changes apply at renewal. Also ask what happens to your subscription if you later move to the other editor, because a switch repeats the integration and testing work. If a vendor will not state a price in writing for your user count, treat that as a gap to close before procurement, not a detail to assume away.

Moving from one editor to the other without losing documents

This sequence lets you switch between Collabora Online and ONLYOFFICE Docs while proving, on your own files, that documents open, edit and save with the fidelity your teams need. Each step ends with a check you can record before the next one starts.

Inventory document types and editing habits
Start by listing every file type in use across the file platform, grouped by how people edit them: native Office Open XML (.docx, .xlsx, .pptx), legacy Office formats, OpenDocument files, PDFs that need form filling or annotation, and any macros or embedded objects. Ask the business owners of each team which documents are critical, which templates are shared and which contain tracked changes or comments. Record the counts and owners in a single inventory sheet. The step is done when every active file type has an owner and a named test document set.
Reconfigure the file platform connector
Point the file platform's office connector at the new editor's server address and confirm the integration path the platform documents for that editor. For Nextcloud, this means updating the Office settings in the admin interface, and the Nextcloud admin manual describes the options. The WOPI endpoint, allowed hosts, certificates and any secret used between the two services must be rebuilt, and the reverse proxy or ingress rules must route the editor's traffic correctly. Keep the old connector configuration in version control so you can restore it. Confirm with the vendor how their server handles WOPI-based session handling and whether any file-type handlers differ. The step is done when a test file opens, edits and saves through the new connector on a staging instance.
Run a fidelity test on your own files
Open a representative sample from the inventory in the new editor and in the current one, then compare layout, fonts, tables, charts, footnotes, comments, tracked changes, headers, footers and form fields. Save each file in the new editor, reopen it in the original application and repeat the check in the other direction. Log each difference with a severity, such as blocking, cosmetic or acceptable with a template fix. Share the results with the document owners. Ask the vendor which formats they consider native and which they convert, because conversion steps can change content. The step is done when every blocking difference has either a fix or a documented decision to accept it.
Pilot with a small user group
Move a small group of users, chosen to cover the main document types and roles, onto the new editor for a defined period agreed by the project team. Give them written guidance on what is different, such as toolbar locations, keyboard shortcuts, collaboration behavior and how to report a problem. Watch support tickets, save errors and any documents that reopen with changed formatting. Ask the vendor which support options cover your pilot, because the support model differs between the two products. The step is done when the pilot group has no unresolved blocking issues and the support log has been reviewed by the project owner.
Migrate the remaining users in waves
Move the rest of the users in batches, starting with the teams whose documents passed the fidelity test with the fewest changes. Before each wave, confirm the editor server has capacity for the expected concurrent sessions, and note any document types that still need a manual check. Keep the previous editor available for read access so people can reopen older files while they adjust. Communicate each wave's date and rollback contact in advance. The step is done when all user groups in the inventory are on the new editor and the last wave has passed its checks.
Retire the old editor safely
Before removing the previous editor, confirm that no integrations, scheduled jobs, templates or external partners still call it. Export the configuration, certificates and logs you need for records, and store them under your retention rules. Then disable the old connector, remove the editor from the file platform's allowed services, and decommission its servers or containers. Ask the vendor what their license terms require when you stop using a product and whether any support or subscription must be cancelled in writing. The step is done when the old endpoint returns no traffic for a period your operations team has agreed and the decommissioning record is signed by the document owner.

Where implementation projects with each editor usually run long

For Collabora Online, the work that most often runs long is session affinity and ingress design when it is deployed on Kubernetes. The project's Helm chart README states that horizontal pod autoscaling is disabled because scaling breaks collaborative editing and copy and paste, so replicas are set by hand, and the load balancer must route by the WOPISrc parameter so every user editing one document reaches the same pod. That rule applies only when you run several pods. A single server or container next to the file platform avoids most of this design work, but it also means capacity is planned by hand. Before work starts, the scope should name the ingress controller (the chart supports Nginx, HAProxy and OpenShift Router), the replica count, the per-pod resource settings the chart recommends for production, and who owns the routing test that proves two users on one document land on the same pod.

For ONLYOFFICE Docs, the work that most often runs long is sizing for concurrent editing and document fidelity testing. Version 9.4 removed the 20 simultaneous connection limit from the Community Edition and consolidated the service into a single process without RabbitMQ or database dependencies, so the limit is no longer a licensing blocker. Capacity still has to be measured against your own user count and document mix, and the scope should say which load test defines acceptable response times. Fidelity testing is the other long task. Native .docx, .xlsx and .pptx handling is the strength of this editor, but your own templates, macros, tracked changes and PDF forms should be opened, edited and saved in the editor before sign-off. Support scope is also a decision: Community support runs through GitHub and the forum, while admin panel, white labeling and Basic, Plus or Premium support are Enterprise Edition features, so procurement should be settled before the project plan is fixed.

Questions buyers ask before hiring help with an online office rollout

What drives the cost of an online office implementation?

Scope drives most of the cost, because the work is priced by what the engagement covers, not by the license of the editor. The main components are planning the architecture, installing and integrating the editor with your file platform, configuring identity and storage, hardening, testing with your own documents, backup and upgrade procedures, and documentation. Collabora Online's Business plan is priced per user, at 3 euros per user per month for up to 99 users, according to Collabora's pricing page, so its license cost scales with headcount. ONLYOFFICE's paid Enterprise Edition is a separate commercial product, and its pricing is not in the facts we have, so ask ONLYOFFICE for a quote. DeployOpen does not publish a price list. A quote follows from a written scope, and you should ask for each component as a separate line item.

How long does a typical online office rollout take?

The duration depends on the number of users, the number of file platforms and identity systems involved, the document types you must support, and whether you run one server or a cluster. Collabora's Helm chart documentation shows that a Kubernetes deployment requires manual replica management and session-aware load balancing, which adds design and test time compared with a single container. Most engagements are fixed-scope, so the timeline is agreed in writing before work starts. We do not publish a typical duration. Ask for a timeline tied to named milestones, such as a test environment, a pilot group and a production cutover, and ask what testing is included with your own documents.

What does the work need from our own staff?

Your staff must supply decisions and access, which determine how quickly the work moves. Expect to name a business owner for document formats and templates, provide a test group that uses your real documents, and assign someone who can approve network changes, DNS records, certificates and identity configuration. Your platform team should own the production environment after handover, so they need the runbooks for upgrades, backups and monitoring. If you plan to run CODE or any other non-production build, confirm with the vendor first, because Collabora describes CODE as not recommended for production.

Can a small team run either editor without outside help?

A small team can run either editor alone if it has container and reverse proxy skills, a patching routine and someone who can read the vendor's upgrade notes. ONLYOFFICE Docs 9.4 removed the 20 simultaneous connection limit from its Community Edition and consolidated it into a single process without RabbitMQ or database dependencies, per the ONLYOFFICE blog, which lowers the number of moving parts. Collabora Online has a free CODE build, but production use needs the paid edition for tested updates and security fixes. Teams without security or platform staff often need help with hardening, backup testing and upgrade planning, and that is where a fixed-scope engagement or a retainer fits.

Can we switch between Collabora and ONLYOFFICE later?

Switching is possible because both editors connect to file platforms through established integration paths, but the cost is in the documents and the users, not the server. Collabora integrates through the WOPI protocol, and ONLYOFFICE also supports WOPI-compatible platforms, per the DocumentServer README. The main migration risks are formatting differences in complex Microsoft Office files, changes to user workflows, and any custom templates or macros. Test a representative set of documents in both editors before you commit, and keep the migration plan in your scope so the switch cost is known in advance.

Does DeployOpen issue certifications for the rollout?

No. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports, attestations or certifications. Independent auditors and certification bodies perform those assessments. In practice, we can document how the online office is configured, how access is controlled, how backups are tested and how changes are logged, so your assessor has the evidence it needs. Ask the assessor which evidence format they accept before the work starts, so the scope includes it.

Which security checks should we ask for before go-live?

Ask for hardening of the editor servers, the reverse proxy and the file platform integration, plus a security test of the exposed endpoints. DeployOpen runs application and API security testing and cloud and infrastructure testing, and it can scope those tests into an implementation. Confirm the exact test types, the environments covered and the reporting format in the written scope. For the editor itself, verify how your chosen edition receives security fixes: Collabora's paid edition includes signed security updates, and ONLYOFFICE's support tiers are listed on its edition comparison page.

How DeployOpen helps choose, implement and migrate an online office

DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure, so the choice between Collabora Online and ONLYOFFICE is tested against your file platform, your documents and your network. Engagements are agreed as fixed scope with written deliverables before work starts.

How we scope

Confirm which file platform the editor must pair with, and which versions of it are in use.
Inventory the Office formats your users edit, and agree a test set of your own documents.
Record the edition, support model and user count that the written scope will assume.
Engagements are fixed-scope, so scope, deliverables and timelines are agreed in writing first.

How we build

Deploy the chosen editor in your cloud account, data center or air-gapped network.
Integrate the editor with your file platform and test document opening, saving and co-editing.
Plan replica and session handling for multi-pod setups, and document the ingress configuration used.
Harden the deployment and prepare backup and upgrade procedures for the editor and its file platform.

How we hand over

Document the architecture, configuration keys, and the operating steps your team will run.
Provide a format test report covering the documents you supplied, with open issues listed.
Walk your administrators through upgrades, licence key handling and the edition in use.
Deliver compliance-readiness evidence for the editor where your assessors require it.

How we support

Ongoing support, upgrades and continuous testing are available as a retainer after handover.
Retainers can cover editor version upgrades and retesting after your file platform changes.
Ask us to confirm which support tier from the editor vendor your written scope assumes.
Security testing of the deployed editor and its integration can be scoped separately.

Collabora Online vs ONLYOFFICE