Which self-hosted online office fits your situation
If your file platform is Nextcloud and you want the default path, Euro-Office (delivered as Nextcloud Office) is the editor Nextcloud documents first, and it is powered by Euro-Office Document Server. If you want an editor that is not tied to the ONLYOFFICE codebase, or your documents are mostly OpenDocument and LibreOffice-native, Collabora Online is the stronger starting point, since Nextcloud also documents it as a fully supported alternative. ONLYOFFICE Docs fits teams that want the editor vendor's own roadmap, its Enterprise admin panel and white labeling, or the Developer Edition for embedding. Three factors should drive the shortlist. First, licensing lineage: Collabora is LibreOffice-based under MPL-2.0, while ONLYOFFICE Docs and Euro-Office both descend from AGPL-3.0 code, so a shared codebase is a fact to weigh, not a verdict on either project.
Second, Nextcloud alignment. Euro-Office was launched on March 27, 2026 and first shipped as stable on June 9, 2026, and ONLYOFFICE suspended its partnership with Nextcloud on March 31, 2026, while saying it will keep supporting the ONLYOFFICE connector. Confirm with the vendors which connector versions and support paths apply to your Nextcloud release. Third, support model. Collabora's paid tiers and ONLYOFFICE's Enterprise support differ in scope, and Euro-Office support runs through a Nextcloud Enterprise subscription for signed builds. Ask each vendor, in writing, who supports your exact file platform version and what the response commitments are.
If you run ownCloud or Seafile instead, the decision changes less than you might expect, because Collabora and ONLYOFFICE both list those integrations, while Euro-Office is designed around Nextcloud. Test your own documents, your co-editing load and your upgrade path in a staging environment before you commit. The cost of changing editors later is driven mostly by document conversion and user retraining, so decide early and write the choice into your scope.
Which platform fits which scenario
This table matches each common team situation to the editor that fits best and the condition that makes that choice hold. Read each row against your file platform, your document mix, your licensing tolerance and whether you need a per-user paid support contract. The main takeaway is that the file platform and the licensing position usually decide the shortlist before feature details do.
| Team situation | Best fit | Condition that makes it hold |
|---|---|---|
| Nextcloud-centred teams | Nextcloud Office (Euro-Office) or Collabora Online | Nextcloud's admin manual names Nextcloud Office as the default, powered by Euro-Office, with Collabora Online as a fully supported alternative. Confirm which option your Nextcloud release supports before you commit. |
| ownCloud or Seafile teams | Collabora Online | Collabora lists WOPI integrations with both ownCloud and Seafile. Confirm the connector version for your specific ownCloud or Seafile release with the vendor. |
| Heavy .docx and .xlsx workloads | ONLYOFFICE Docs or Euro-Office | ONLYOFFICE treats .docx, .xlsx and .pptx as native formats. Test your own complex documents in each editor, since this row depends on your files, not on the feature list. |
| Teams wanting LibreOffice-compatible open formats | Collabora Online | Collabora Online is built on LibreOffice technology, so OpenDocument work is closest to the engine that creates it. Confirm fidelity for your Microsoft Office files separately. |
| Teams needing paid support with a per-user price | Collabora Online Business or ONLYOFFICE Enterprise | Collabora's pricing page lists Business at 3 euros per user per month for up to 99 users. ONLYOFFICE publishes Basic, Plus and Premium support tiers under Enterprise Edition, so request written quotes for both. |
| Teams that must avoid the ONLYOFFICE licensing dispute | Collabora Online | ONLYOFFICE suspended its Nextcloud partnership in March 2026 and disputed Euro-Office's reuse of its code. Collabora Online is MPL-2.0, so it sits outside that dispute. Ask your counsel to review any AGPL obligations you already carry. |
| Teams embedding editors in their own product | ONLYOFFICE Developer Edition or Collabora Online with a commercial agreement | ONLYOFFICE sells a Developer Edition under a commercial license for vendors that embed editors in services. Confirm embedding terms in writing with each vendor before you build on either. |
What the ONLYOFFICE and Euro-Office dispute means for your licence review
Euro-Office and ONLYOFFICE are not the same licence position, and your review should treat them separately. Euro-Office launched on March 27, 2026, and Nextcloud states that it is built on ONLYOFFICE, which is distributed under the AGPLv3. Nextcloud also states that Euro-Office removed ONLYOFFICE's Section 7 requirement to display its logo. On March 31, 2026, ONLYOFFICE suspended its partnership with Nextcloud, describing Euro-Office as a direct reuse of its technology presented under a different identity, while saying it will keep supporting and developing the ONLYOFFICE connector for Nextcloud. Both sides have published their positions, so the dispute is about how the code is presented and branded, and your review should not assume either party's account settles the question.
Start by listing every editor build in your environment and where its code came from: ONLYOFFICE Docs Community Edition, a Nextcloud Office build, or an unsigned Euro-Office community build. For each, record the license file shipped with that build, any logo or branding requirement in the distributed interface, and whether you modify or redistribute it. Ask your counsel to confirm which obligations apply to your use, particularly if you embed the editors in a service you provide to customers, a case where ONLYOFFICE's commercial Developer Edition is also relevant. Ask the vendor or Nextcloud in writing which license terms govern the build you receive.
This page is a comparison of technical and commercial fit. It is not legal advice, and nothing here states what your organization is or is not permitted to do. Keep the connector and document server versions you deploy recorded in your change log, because a later partnership or licensing change could affect updates and support. Where your counsel needs primary text, the license files in the relevant repositories and the vendors' published statements are the starting points.
Licence and paid edition terms for each platform
Collabora Online's server code is licensed under the Mozilla Public License 2.0, which is a file-level copyleft license. The free CODE edition is a rolling release that Collabora describes as suited to testing, home use or small teams and not recommended for production. Production deployments normally move to the paid Collabora Online, which adds tested updates, signed security fixes and support.
- Server code licence: MPL-2.0 covers the Collabora Online source repository, so confirm with your legal team how modifications to covered files must be shared.
- CODE edition: the free rolling release arrives roughly once a month, which suits evaluation and small teams but is not Collabora's production build.
- Business plan: the pricing page lists 3 euros per user per month for up to 99 users, including long term support, a service level agreement, signed security updates and customer portal access.
- Enterprise plan: for 100 or more users the price is quoted with volume discounts and adds integration support, customization services and roadmap input.
- Recurring cost: the per-user fee repeats for each active user, so headcount growth and user counts across the threshold change the quote.
Confirm current terms, user thresholds and what the SLA covers on Collabora's pricing page before budgeting.
ONLYOFFICE Docs Community Edition is licensed under AGPL-3.0, so network use of a modified version can trigger source disclosure obligations. The Community Edition now has no 20 simultaneous connection limit following the 9.4 release, and support comes through GitHub and the community forum. The Enterprise and Developer editions add features and commercial terms that the Community build does not include.
- Community Edition: AGPL-3.0 with community support through GitHub and the forum, and configuration through config files only.
- Enterprise Edition features: the edition comparison lists an admin panel, white labeling, scaling for thousands of users and Basic, Plus or Premium support.
- Support tiers: Basic, Plus and Premium are separate support levels, so compare response commitments in the written terms before you choose one.
- Developer Edition: a commercial licence for software vendors that embed the editors in services they provide to customers, which matters if your product passes the editor to outside users.
- Licensing dispute: ONLYOFFICE suspended its partnership with Nextcloud on March 31, 2026, so confirm the connector and support position with ONLYOFFICE before you build on it.
Ask ONLYOFFICE in writing which edition covers your user count, whether white labeling is needed, and whether embedding requires the Developer Edition.
Euro-Office DocumentServer v9.3.5 is licensed under AGPL-3.0 and is built on ONLYOFFICE technology. Nextcloud states that Euro-Office removed ONLYOFFICE's Section 7 requirement to display its logo. The same source comes in two builds with different trust and support profiles, so the build you choose determines who supports you.
- Nextcloud Office signed builds: intended for production, delivered with package repositories and supported through a Nextcloud Enterprise subscription.
- Unsigned community builds: built from the same source for testing, without signing or the Nextcloud Enterprise support path.
- Document Server dependency: the Document Server is not a standalone application and needs a platform such as Nextcloud to store the files.
- Governance: the project launched on March 27, 2026 under a shared governance framework, so ask which entity holds the trademarks and the release process.
- Support boundary: support is tied to the Nextcloud Enterprise subscription for signed builds, so confirm what is covered for your Nextcloud version.
Confirm the build, the subscription scope and the AGPL obligations for any changes you make with Nextcloud and Euro-Office directly.
Office format handling, deployment and extensibility compared
This table compares how each editor handles Office files, PDF, integrations, Docker and Kubernetes, and the connection and AI limits that affect rollout. Read each row as a question to answer in your own test environment, since several capabilities are only partly documented in the sources we reviewed. The main takeaway is that ONLYOFFICE and Euro-Office state native Office formats directly, while Collabora's Office fidelity should be tested against your own documents.
| Capability | Collabora Online | ONLYOFFICE Docs | Euro-Office |
|---|---|---|---|
| Native formats | Built on LibreOffice, with OpenDocument and Microsoft format support. Confirm fidelity on your own DOCX, XLSX and PPTX files. | Native .docx, .xlsx and .pptx. Other formats such as DOC, ODT, RTF, ODS, CSV and ODP are converted. | Edits DOCX, PPTX, XLSX, PDF, ODT, ODS and ODP with real-time co-editing. |
| PDF editing | Confirm PDF editing scope in the current release before relying on it. | Text editing, page manipulation, annotations and form filling are listed in the DocumentServer README. | Edits PDF as a supported format. Confirm the feature set against your workflow. |
| WOPI and named integrations | WOPI-based. Lists Nextcloud, ownCloud, Seafile, WordPress, Alfresco, Mattermost, Nuxeo, OpenText and xWiki. | Integrates with Nextcloud, ownCloud, Seafile, Moodle, Odoo and WOPI-compatible platforms. | Built for Nextcloud. Needs a platform such as Nextcloud to store files, since the Document Server is not standalone. |
| Docker deployment | Docker images are available, including the free CODE image collabora/code for x86-64, ppc64 and arm64. | Docker is the recommended installation method. | Community builds are unsigned and intended for testing. Signed production builds come through Nextcloud Office packages. |
| Kubernetes and Helm | Official Helm chart. Autoscaling is disabled because scaling breaks collaborative editing, so replicas are set manually. | Confirm current Kubernetes packaging and scaling guidance with the vendor before planning a cluster. | Confirm Kubernetes packaging with the project, as no chart was reviewed for this comparison. |
| Session affinity | Load balancers must route by the WOPISrc parameter so all users editing one document reach the same pod. | Confirm how co-editing sessions are routed across multiple nodes in your load balancer design. | Confirm session routing requirements for multi-node deployments. |
| Connection limits | No simultaneous connection limit is stated in the sources reviewed. Confirm against your edition. | ONLYOFFICE Docs 9.4 removed the 20 simultaneous connection limit from Community Edition and consolidated it into a single process. | Confirm connection limits in the build you deploy. |
| AI assistant | Collabora 26.04 adds an optional AI assistant across Writer, Calc and Impress. It is off by default, and administrators choose the provider and whether it is hosted externally or on their own infrastructure. | Confirm whether any AI assistant is offered in your edition. | Confirm whether any AI assistant is included in your build. |
How each editor is deployed and scaled on Kubernetes
The first thing to settle is that the three editors do not deploy the same way. Euro-Office Document Server is not a standalone application, so it needs a platform such as Nextcloud to store the files and call it. Its deployment model is therefore set by the file platform you pair it with, not by a chart you install on its own. Collabora Online is different: it runs as its own service, and its project publishes an official Helm chart for Kubernetes that supports Nginx, HAProxy and OpenShift Router ingress. ONLYOFFICE Docs 9.4 consolidated the Community Edition into a single process without RabbitMQ or database dependencies, which simplifies the moving parts you have to run per node. Confirm with ONLYOFFICE and with your Euro-Office build which chart, manifests or images they support on your cluster, and how they handle session affinity.
The Collabora Helm chart makes a scaling decision that changes your architecture. Its README states that horizontal pod autoscaling is disabled because scaling breaks collaborative editing and copy and paste, so you set the replica count manually. Your ingress must also route by the WOPISrc parameter so that every user editing one document reaches the same pod. For production, the chart recommends limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB. Budget capacity per pod and per document, not for the whole cluster, and test the routing rule with two users editing the same file before go-live.
For ONLYOFFICE and Euro-Office, ask the same questions in writing: whether the document server supports horizontal scaling behind a load balancer, what session stickiness is required, whether autoscaling is supported, and what resource requests and limits the vendor or distributor recommends. Ask for these answers in the scope document so they are tested in your environment rather than assumed. Where the answers differ from the Collabora model, plan the ingress, replica count and test plan separately for each candidate.
What drives the running cost of each editor
Licence fees are only one line in the running cost of a self-hosted online office. The other lines come from per-user subscriptions, the server footprint, the operator hours spent on upgrades and high availability, the support tier chosen, the cost of changing editors later, and the time spent reviewing licences. Use these cards to build the quote request so the three editors are priced on the same basis.
Per-user subscription fees
Collabora Online Business is listed at 3 euros per user per month for up to 99 users, which is a recurring cost that scales with headcount. ONLYOFFICE Enterprise Edition is quoted separately, and Euro-Office support comes through a Nextcloud Enterprise subscription, also quoted. Ask each vendor whether the price counts named users, concurrent users or documents, whether it applies to every user on the file platform or only to editors, and what happens to the fee at the 100-user threshold.
Infrastructure footprint per pod or server
Collabora Online's Helm chart recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB. These resources recur every month as cloud or hardware cost. ONLYOFFICE Docs 9.4 removed the 20 simultaneous connection limit and runs as a single process, so the footprint per server depends on your concurrency and document load. Ask each vendor for sizing guidance at your expected concurrent editing volume and for the number of replicas needed for availability.
Operator time for upgrades and high availability
Collabora's chart disables horizontal pod autoscaling because scaling breaks collaborative editing, so replica counts are set by hand, and the load balancer must route by the WOPISrc parameter so co-editors reach the same pod. That routing and manual scaling is staff time that recurs with every upgrade cycle. Estimate it with your own platform team, including the ingress you run (Nginx, HAProxy or OpenShift Router), and confirm how each vendor expects rolling upgrades to behave while documents are open.
Support tier and SLA choice
Community support for ONLYOFFICE runs through GitHub and the forum, while Enterprise adds Basic, Plus or Premium support tiers. Collabora's Business plan includes long-term support, a service level agreement, signed security updates and customer portal access. Euro-Office production builds are supported through a Nextcloud Enterprise subscription. Ask each vendor for the response times, security patch windows and long-term support commitments in writing, and do not assume a community build carries any of them.
Cost of switching editors later
Each editor connects to file platforms through a different connector, and the integration that works with Nextcloud may not map one-to-one to ownCloud or Seafile. Collabora lists WOPI integrations with Nextcloud, ownCloud and Seafile, while ONLYOFFICE lists its own connectors for those platforms. A switch therefore means reconfiguring the connector, retesting every Office format your team uses, and retraining users on the editing interface. Price this as a one-time cost and ask whether the vendor offers a migration path or document export guidance.
Licence review effort
The three editors sit under different terms: Collabora Online server code is MPL-2.0, ONLYOFFICE Docs Community Edition is AGPL-3.0, and Euro-Office is built on ONLYOFFICE under AGPL-3.0 with its logo requirement removed. ONLYOFFICE has publicly disputed the Euro-Office reuse, which makes the licence position a live question rather than settled background. Budget counsel or compliance time as a one-time review, and repeat it when a vendor changes terms, branding or distribution rules.
How each editor fits Nextcloud, ownCloud and Seafile
Your file platform decides which editors you can run without rework. Nextcloud Office is the default, powered by Euro-Office and requiring a Euro-Office Document Server, while the Nextcloud admin manual describes Collabora Online, based on CODE, as a fully supported alternative that runs either as a built-in app or as a self-hosted server. ONLYOFFICE has a separate connector for Nextcloud, and ONLYOFFICE says it will keep supporting and developing that connector even though its partnership with Nextcloud was suspended on March 31, 2026. Before you pick an editor for Nextcloud, confirm in the Nextcloud admin manual which integration is currently supported on your Nextcloud release line, and confirm the connector version against the Nextcloud release you run, since the three maintained lines (35.0.2, 34.0.5 and 33.0.10) may not carry identical app support.
On ownCloud, the path depends on which product you run. ownCloud Classic 11 is deployed only with Docker, with the web server, PHP runtime and database managed inside ownCloud's images, so an editor integration has to fit that packaged stack rather than your own web tier. ownCloud Infinite Scale (oCIS) is a separate Apache-2.0 platform written in Go, not a successor configuration of Classic. It needs no external database and no external identity provider for its quickstart, and the oCIS documentation lists S3, NFS and PosixFS storage backends. Your storage backend choice therefore affects both the editor placement and your backup design. Confirm with ownCloud which WOPI or connector versions are supported on Classic 11 and on oCIS 9.0 before you commit.
Seafile organizes content into libraries that sync separately and can each be encrypted with a user-chosen password, so editor access must respect library-level encryption and permissions. The Seafile manual lists SAML 2.0 for single sign-on and advanced file search among Professional Edition features, and Professional Edition can run without a license file for up to 3 users. Collabora lists Seafile among its WOPI integrations, alongside Nextcloud and ownCloud, and the Seafile download page lists Community Edition 12.0.14 for generic Linux. Test one encrypted library and one shared library end to end with each editor, and confirm with Seafile and Collabora which editor integration versions match your Seafile release.
What implementing an online office editor involves
The sequence below takes a team from an existing file platform to a tested, hardened and maintainable online office editor, with a checkpoint at each stage so the editor choice is proven on your own documents before rollout.
Confirm the file platform and its version
Start by recording which file platform you run, its exact version and its database, since that choice narrows the editor options. Nextcloud, ownCloud and Seafile each document their own connector and version support, and the editors integrate through their connectors or through WOPI. Your team, or your implementation partner, checks the vendor's current requirements page for the version you plan to keep, and confirms that the editor connector for that version is maintained. The check is complete when you have a written compatibility note naming the platform version, the connector and the editor build you intend to test against.
Pick the editor build and its license terms
Choose among the build types each product offers: Collabora CODE or paid Collabora Online, ONLYOFFICE Docs Community or Enterprise (or the Developer Edition for embedding), and Euro-Office community builds or signed Nextcloud Office. Read the license of each build, including any logo or branding requirement, and confirm whether the support, security fix and update commitments you need exist only in a paid tier. Ask each vendor in writing which build they recommend for production. The output is a short decision record that states the build, its license and the support route, signed off by the people who own the risk.
Test your own Office files before committing
Build a test set from your real documents: Word, Excel and PowerPoint files with tracked changes, comments, complex tables, embedded charts, macros you need to keep out of scope, fonts you use and any PDFs that must be edited or annotated. Open and edit each file in each candidate editor, then compare layout, formulas, co-editing behavior and saved output against the original. Record every difference that would stop a business process. The check is complete when the team agrees, in writing, which file types are acceptable in which editor, and which need a fallback or a conversion rule.
Size the server and route the editor tier
Use the test results and your expected concurrent editing load to size the document server or Collabora instance. Collabora's Helm chart documents production resource figures and states that horizontal autoscaling is disabled because scaling breaks collaborative editing, so replica counts are set by hand. ONLYOFFICE 9.4 removed the 20 simultaneous connection limit from Community, but you should still load test your own workload. Configure the load balancer so every user editing one document reaches the same instance, using the WOPI source parameter for Collabora, and confirm the routing with two browser sessions on the same document.
Integrate the editor and configure authentication
Connect the editor to the file platform using the vendor connector, then wire authentication so editing sessions inherit the file platform's identity and permissions. Confirm that a user without read access cannot open a document through a direct editor URL, that shared links respect their permissions, and that the connector uses the TLS endpoints you intend to keep. Record the connector versions and configuration keys, since these become the baseline for upgrades. The step is done when access tests for three roles (owner, editor and read-only) pass against the same document in the same session.
Harden the stack and document the configuration
Restrict the editor's internal endpoints so only the file platform can reach them, enforce TLS between each component, and review which optional features are on, including any AI assistant that is off by default in Collabora 26.04 and must be enabled deliberately with a chosen provider. Remove or disable features your policy does not allow. Write down every setting that departs from the vendor default and the reason for it. The output is a hardening record that your security team can check against your own baseline and any control framework you are assessing against.
Back up, restore and test the recovery path
Back up the file platform's database and data store together with the editor configuration and the connector settings, since restoring files without the matching configuration breaks editing. Then perform a restore into a separate environment and open a sample of documents to confirm they load, save and co-edit. Record how long the restore took on your hardware, because that measured figure, not a vendor estimate, is what you will plan around. The check is complete when a restored environment passes the same document tests as production.
Plan upgrades and keep a supported path
Set a written upgrade procedure that covers the file platform, the editor and the connector, and check version compatibility before each change. Use a staging copy to test each upgrade with your document set, and keep the previous editor image available for rollback. Track the support window for each build you run, including any rolling release cadence, since CODE is a rolling release and not recommended for production by Collabora. The process is working when each upgrade runs through staging, your document tests pass, and a rollback has been rehearsed at least once.
Questions buyers ask before choosing an online office editor
Can Collabora CODE run in production?
Collabora describes CODE, its free development edition, as suited to testing, home use or small teams, and not recommended for production. CODE is a rolling release shipped on average once a month, so each update is a new build rather than a supported branch with tested updates. The paid Collabora Online adds tested updates, security fixes and support. The Business plan also includes long term support, a service level agreement and signed security updates. If your organization needs those assurances, price the supported build from the start and confirm the edition with Collabora against your uptime and patching requirements before rollout.
What does the Collabora Business plan cost per user?
The Collabora pricing page lists the Business plan at 3 euros per user per month for up to 99 users. This is a recurring subscription, so the annual total grows with seat count and continues for as long as you keep the plan. The plan includes long term support, a service level agreement, signed security updates and customer portal access. Organizations with 100 or more users are quoted on the Enterprise plan with volume discounts, which adds integration support, customization services and roadmap input. Ask for the quote in writing, including whether taxes apply, how seats are counted, and what changes when your count passes 99.
Is Euro-Office safe to use after the ONLYOFFICE dispute?
Nextcloud states that Euro-Office is built on ONLYOFFICE, which is distributed under the AGPLv3, and that Euro-Office removed ONLYOFFICE's Section 7 requirement to display its logo. ONLYOFFICE suspended its partnership with Nextcloud on March 31, 2026, and described Euro-Office as a direct reuse of its technology under a different identity. Whether that reuse complies with the license is a question for counsel. Before you standardize, have counsel review the license position, retain the source and notices for your records, and decide whether signed Nextcloud Office builds or unsigned community builds fit your policy. Review the Euro-Office license compliance statement as a starting point.
Is a DeployOpen engagement fixed scope, and how is it quoted?
Most DeployOpen engagements are fixed-scope, and scope, deliverables and timelines are agreed in writing before work starts. A quote follows from that written scope, and DeployOpen does not publish a price list. Ongoing support, upgrades and continuous testing are available as retainers, which recur separately from the one-time implementation. To compare quotes fairly, ask every provider to price the same written scope, covering the editor edition, document server layout, file platform integration, backups, hardening and documentation. Also ask what is excluded, who performs acceptance testing, and which costs continue after go-live.
How long does implementation take and what does it need from us?
DeployOpen does not publish fixed timelines, so the duration is set in the written scope. The main drivers are the number of document servers, the file platform and its version, the number of users and document formats you need to test, and whether you run on Kubernetes. Collabora's Helm chart documents session affinity, manual replica settings and per-pod resources, which adds design work for that path. From your side, expect to provide infrastructure access, database and identity setup, DNS and TLS certificates, a representative set of test documents and named approvers. Confirm these inputs before the quote is treated as final.
Can our team self-host the office editor without outside help?
Yes, if your staff can run containers or system packages, configure a reverse proxy, manage TLS and databases, and patch on a regular schedule. Collabora supports Docker images, system packages and Kubernetes, and ONLYOFFICE recommends Docker. The harder work is ongoing: upgrading the editor and file platform in step, retesting your own documents after each update, and acting on security advisories. Decide whether that capacity sits in-house for the long term, or whether you want an outside partner for setup, documentation and retainer-based upkeep. Confirm which of these tasks your current staff can cover before committing to a platform.
How does the ONLYOFFICE connection limit change Community sizing?
ONLYOFFICE Docs 9.4, released on May 19, 2026, removed the 20 simultaneous connection limit from the Community Edition and consolidated it into a single process without RabbitMQ or database dependencies. This lowers the operational footprint for larger Community deployments. It does not add the Enterprise features, which include an admin panel, white labeling, scaling for thousands of users and Basic, Plus or Premium support. Community support runs through GitHub and the forum, with configuration through config files. Load test version 9.4 against your expected concurrency, and confirm with ONLYOFFICE whether the Community support model meets your needs.
How DeployOpen helps you choose and implement an online office editor
DeployOpen plans, implements, integrates, hardens and documents self-hosted open-source platforms inside your own infrastructure, so the choice between Collabora Online, ONLYOFFICE and Euro-Office is tested against your file platform, your document mix and your licensing position before anything is built. Engagements are fixed-scope, with the scope agreed in writing first.
How we scope
- We confirm which file platform the editor must attach to, such as Nextcloud, ownCloud or Seafile, and which WOPI or connector path applies.
- We agree the Office formats your users edit, and the sample documents we will test against before any build starts.
- We record the license, edition and support model you need in writing, including whether an AGPL or MPL obligation affects your use.
How we build
- We deploy the chosen editor in your cloud account, data center or air-gapped network, using the install method your team approves.
- We test co-editing, conversion, PDF handling and save-back on your own documents, and record where fidelity differs between editors.
- We size and configure the server footprint, including session affinity if you run several editor instances behind a load balancer.
How we hand over
- We document the architecture, configuration keys, upgrade path and the rollback steps for each component we install.
- We deliver the test results, including the document cases that passed, failed or needed workarounds, so your team can repeat them.
- We train the administrators who will run the editor, and record the items you should confirm with the vendor after handover.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, so the editor keeps pace with vendor releases.
- We track license and edition changes, such as a move between community and paid tiers, and revise the written scope when they affect your setup.
- We help you prepare the evidence your compliance assessors may request for the editor, while independent auditors issue any formal reports.
