ONLYOFFICE or Euro-Office: which fits your Nextcloud or multi-platform estate
If your files live in Nextcloud and you want the office editor that Nextcloud ships and supports by default, Euro-Office is the closer fit. The Nextcloud admin manual describes Nextcloud Office as the default office solution, powered by Euro-Office and requiring a Euro-Office Document Server. Production builds are signed, come with package repositories, and carry support through a Nextcloud Enterprise subscription. Euro-Office also removed ONLYOFFICE's Section 7 requirement to display its logo, which matters if you white label or run a branded service. Confirm with Nextcloud exactly which build and support tier your contract covers before you commit.
If your estate spans several platforms, or you need the features that only ONLYOFFICE's paid editions provide, ONLYOFFICE is the better starting point. ONLYOFFICE Docs integrates with Nextcloud, ownCloud, Seafile, Moodle, Odoo and WOPI-compatible platforms, and its Enterprise Edition adds an admin panel, white labeling, scaling for thousands of users and Basic, Plus or Premium support. A Developer Edition under a commercial license is the route if you embed the editors in a service you sell to customers. ONLYOFFICE Docs Community Edition is AGPL-3.0 and, since 9.4 removed the 20 simultaneous connection limit, it no longer caps concurrent editing. Check which of these features your use case needs before you assume the Community Edition is enough.
The decision turns on four questions. First, which platform stores your files, since Euro-Office Document Server needs a platform such as Nextcloud and cannot run on its own. Second, your license position: whether you need the logo clause removed, and whether you embed the editor in a commercial service. Third, who supports the editor when something breaks, Nextcloud GmbH or ONLYOFFICE. Fourth, how far you will rely on ONLYOFFICE's own connector for Nextcloud, given that ONLYOFFICE suspended its partnership with Nextcloud on March 31, 2026 while saying it will keep maintaining that connector. Write these answers into your requirements before you request a quote.
Which scenario favors ONLYOFFICE and which favors Euro-Office
This table maps common team scenarios to the editor that fits better and names the condition that tips the decision. Read each row as a starting point, since the deciding factors are usually the platform you already run, the license terms for how you distribute the editors, and the support contract you need. Confirm each condition against current builds, license text and contract terms before you commit.
| Scenario | Better fit | Condition that drives it |
|---|---|---|
| Existing Nextcloud deployment | Euro-Office (Nextcloud Office) | Nextcloud's admin manual makes Nextcloud Office the default, powered by Euro-Office. Confirm the migration path from your current ONLYOFFICE connector. |
| Multi-platform estate with Seafile, ownCloud or Moodle | ONLYOFFICE Docs | ONLYOFFICE Docs lists integrations with these platforms, so one editor server can serve several. Confirm connector versions for each platform in your estate. |
| Embedding editors in a product you sell | ONLYOFFICE Developer Edition | The Developer Edition is sold under a commercial license for vendors that embed editors in services for customers. Have counsel review AGPL obligations for any Euro-Office build. |
| Need for an admin panel or white labeling | ONLYOFFICE Enterprise Edition | ONLYOFFICE lists both as Enterprise Edition features. Confirm whether the Euro-Office or Nextcloud Office build offers equivalents for your needs. |
| Preference for a Nextcloud Enterprise support contract | Euro-Office (Nextcloud Office) | Signed production builds with package repositories are supported through a Nextcloud Enterprise subscription. Confirm the support scope, response terms and build coverage in writing. |
| Strict requirements on UI branding | Euro-Office | Euro-Office removed the ONLYOFFICE Section 7 logo display requirement, according to Nextcloud. Check the license text with counsel before changing any branding. |
| Preference for upstream support from the editor maker | ONLYOFFICE Docs | ONLYOFFICE says it will keep supporting and developing its Nextcloud connector. Confirm the connector's support status for your Nextcloud version. |
| Running Nextcloud with a non-Nextcloud support path | ONLYOFFICE Docs | ONLYOFFICE Docs stays under its own release line and vendor support tiers. Confirm which support plan covers your platform and connector before choosing. |
How the Document Server connects to file platforms in each stack
The two stacks attach an editing server to a file platform in different ways. ONLYOFFICE Docs connects to several platforms as a standalone service, while Euro-Office runs only as a component that depends on a host such as Nextcloud. The cards below cover what each connection means for installation, scaling and the checks to run in your own environment.
Euro-Office needs a host platform
The Euro-Office Document Server is not a standalone application. It has no file store of its own, so the host platform owns storage, user sessions and sharing, and the editor only renders and co-edits what the host passes to it. For a team evaluating Euro-Office outside Nextcloud, this is a blocking constraint. Confirm which host platforms your organization can use with it and who maintains the connector between them before you commit to a design.
ONLYOFFICE Docs platform connectors
ONLYOFFICE Docs integrates with Nextcloud, ownCloud, Seafile, Moodle, Odoo and WOPI-compatible platforms, so one editing service can serve more than one file store. Each connector is a configuration and version pairing that you own. Check that the connector version for each host platform matches the Document Server release you deploy, and test the editing path after each upgrade of either side.
Docker as the recommended install
Docker is the recommended installation method for ONLYOFFICE Docs. Running the Document Server in containers keeps its dependencies pinned and makes upgrades a matter of changing an image tag. The trade-off is that you must still manage the TLS termination, the JWT secret shared with the host platform and the network path between the two. Ask your platform team which container runtime and orchestrator they support before you plan the rollout.
Connection limit removed in 9.4
ONLYOFFICE Docs 9.4 removed the 20 simultaneous connection limit from the Community Edition, so a single Community deployment is no longer capped at that number of concurrent sessions. Read the release notes carefully, because the limit change is about the Community build and does not by itself settle capacity planning for your user count. Load test your own workload against the version you intend to run.
Single process without RabbitMQ or database
With 9.4, ONLYOFFICE consolidated the Document Server into a single process with no RabbitMQ or database dependency. Fewer moving parts means fewer services to back up, monitor and patch, and a smaller set of failure modes during an upgrade. Confirm whether your existing monitoring and backup runbooks still reference the queue or database components, and remove those checks when you move to the 9.4 line or later.
Operational checks for each environment
Before choosing either path, confirm three things in your own environment: which host platform and version stores the files, how the editor-to-host secret and TLS are managed, and who patches each component. For Euro-Office, confirm the signed Nextcloud Office build and its support path. For ONLYOFFICE Docs, confirm the connector maintenance owner now that the partnership with Nextcloud has been suspended. These checks shape the operating effort more than the license does.
Feature and license comparison: ONLYOFFICE Docs vs Euro-Office
This table compares ONLYOFFICE Docs and Euro-Office on license, formats, editing, administration, scaling, support and builds, using each platform's current release line. Read the Euro-Office column as confirmed facts plus open questions, because several administrative and scaling capabilities are not documented in the sources used here. The main takeaway is that the editing core is shared, but paid tiers, support paths and build trust differ, so confirm each gap in writing before you commit.
| Feature | ONLYOFFICE Docs | Euro-Office |
|---|---|---|
| License | AGPL-3.0 for Community Edition; Enterprise and Developer editions are commercial | AGPL-3.0 for DocumentServer; logo display requirement removed |
| Current release line | DocumentServer v10.0.0, published October 12, 2026 | DocumentServer v9.3.5, published October 9, 2026 |
| Supported formats | Native DOCX, XLSX and PPTX; converts DOC, ODT, RTF, ODS, CSV and ODP | Edits DOCX, PPTX, XLSX, PDF, ODT, ODS and ODP |
| PDF editing | Text editing, page manipulation, annotations and form filling | PDF editing listed; confirm the depth of features with Euro-Office |
| Co-editing | Real-time co-editing; 9.4 removed the 20 simultaneous connection cap from Community | Real-time co-editing; confirm connection limits for your build |
| Admin panel and white labeling | Enterprise Edition features; Community is configured through config files only | Not covered in the sources used; confirm with Nextcloud or Euro-Office |
| Scaling | Enterprise lists scaling for thousands of users; confirm the Community model for your load | Confirm the scaling model and supported user counts before you rely on it |
| Support channels | Community support via GitHub and the forum; paid Basic, Plus or Premium tiers | Signed builds supported through a Nextcloud Enterprise subscription |
| Builds | Community edition installed via Docker, which the README recommends | Signed Nextcloud Office builds for production; unsigned community builds for testing |
What ONLYOFFICE and Euro-Office charge for and what stays free
ONLYOFFICE Docs Community Edition is licensed under AGPL-3.0, so the software itself carries no license fee. The cost of running it is the infrastructure, the people who install and patch it, and any support you buy elsewhere. Since ONLYOFFICE Docs 9.4, released on May 19, 2026, the Community Edition no longer has the 20 simultaneous connection limit, which removes a concurrency constraint that previously pushed some teams toward paid tiers.
- No license fee: The AGPL-3.0 terms apply to the software, and you pay for hosting, staff time and any third-party support.
- Support path: Community support runs through GitHub and the forum, with configuration through config files only.
- No admin panel or white labeling: Those features sit in the Enterprise Edition, so Community operators manage settings in files.
- Recurring costs: Servers, storage, upgrades such as the DocumentServer v10.0.0 release published on October 12, 2026, and testing remain your responsibility.
Before you commit, confirm with ONLYOFFICE which features and connection limits apply to your version and deployment size, and check the AGPL obligations for any modifications you distribute.
ONLYOFFICE Enterprise Edition is the paid, self-hosted tier. ONLYOFFICE's edition comparison lists an admin panel, white labeling, scaling for thousands of users and Basic, Plus or Premium support as Enterprise features. The fee is quoted by ONLYOFFICE, and the price depends on the support tier and deployment terms, so request the figures in writing rather than estimating them from the feature list.
- Admin panel: Central administration that Community operators do not get.
- White labeling: Branding changes for organizations that present the editors to their own users.
- Scaling for thousands of users: Listed as an Enterprise feature in the edition comparison.
- Support tiers: Basic, Plus or Premium, with response terms that you should compare in the quote.
What to check in a quote: which support tier is included, whether upgrades and security fixes are covered, the term length, and whether the price is one-time or annual. Ask how the license applies to your Nextcloud or other integration, since the Enterprise terms do not change the AGPL status of the Community code.
ONLYOFFICE Developer Edition is a commercial license for software vendors that embed the editors in services they provide to customers. It applies when the editors are part of a product you sell or host for others, rather than a file platform run for your own staff. The edition comparison describes it as a separate license, so the question is whether your use falls under embedding, which is a legal and commercial matter to settle before deployment.
- Who needs it: Vendors that embed ONLYOFFICE editors in a service delivered to customers.
- Who usually does not: Organizations running Nextcloud or another platform internally for their own employees, subject to confirmation of the terms.
- Commercial terms: Pricing and terms come from ONLYOFFICE, so ask for a written quote and license scope.
- Interaction with AGPL: Confirm how the commercial license relates to AGPL-3.0 obligations for any code you modify.
Ask ONLYOFFICE to confirm in writing whether your architecture requires the Developer Edition, and which obligations apply if you distribute a modified build.
Euro-Office comes in two builds from the same source. The signed Nextcloud Office build is intended for production, ships with package repositories, and carries support through a Nextcloud Enterprise subscription. Nextcloud Office is the default office solution in the Nextcloud admin manual and requires a Euro-Office Document Server. The subscription is the paid element, and its price comes from Nextcloud, so the quote should state exactly what support and package access it covers.
- Signed packages: Production-grade builds with package repositories for updates.
- Support: Delivered through a Nextcloud Enterprise subscription, which is a separate purchase from the software.
- Platform dependency: The Document Server needs a platform such as Nextcloud that stores the files.
- Recurring cost: The subscription recurs, while infrastructure and staff time are additional.
What to check: whether the subscription covers the Document Server as well as Nextcloud Server, the response commitments, and how long the signed builds are maintained for the release line you choose.
The unsigned Euro-Office community build comes from the same source as the signed build and is intended for testing. It costs nothing to obtain under the AGPL-3.0 license of the Document Server, which Euro-Office lists as version 9.3.5 published on October 9, 2026. Because the build is unsigned and not offered as a production package, the cost shifts to your team, which must handle verification, patching and any troubleshooting that a paid subscription would otherwise cover.
- No subscription: The community build carries no Nextcloud Enterprise support.
- Testing purpose: The build is positioned for evaluation rather than production.
- Self-managed updates: Your team tracks releases and applies fixes without vendor packages.
- Hidden effort: Verification of builds, testing after upgrades and incident response fall to your staff.
Before relying on the community build in a regulated setting, confirm with Nextcloud and the Euro-Office project how security fixes are delivered, and budget the internal effort that the signed build's support would otherwise cover.
Who builds, maintains and supports each editor
ONLYOFFICE is built and supported by ONLYOFFICE itself. The company maintains the DocumentServer codebase, publishes the releases (DocumentServer v10.0.0 arrived on October 12, 2026), and sells the Enterprise and Developer editions. Community Edition users get support through GitHub and the community forum, while the Enterprise tiers (Basic, Plus or Premium) carry commercial support. Before you commit, ask ONLYOFFICE in writing which support tier covers security fixes for the Docs version you run, how quickly it responds to a reported vulnerability, and whether the Developer Edition terms apply to your deployment. Do not assume that a Nextcloud integration inherits any of these commitments.
Euro-Office is a governed project, not a single vendor. It launched on March 27, 2026 at a Berlin event organized by IONOS and Nextcloud, with backers including Eurostack, XWiki, OpenProject, Soverin, Abilian and BTactic under a shared governance framework. Its first stable release arrived on June 9, 2026, bundled with Nextcloud Hub 26 Spring. Signed Nextcloud Office builds for production are supported through a Nextcloud Enterprise subscription, while unsigned community builds are intended for testing. Ask Nextcloud which Euro-Office release lines receive patches, how long each line is maintained, what the security disclosure process is, and whether the subscription covers the Document Server itself or only the Nextcloud server.
Confirm the contract terms directly with each vendor before you choose. Support windows, security response targets and liability terms are set in each vendor's own agreement, and the public materials do not give a single answer for both. Write the questions into your procurement file: who issues the patch, who certifies the build you deploy, who is accountable if a vulnerability is found in code that both projects share, and what happens to your support if the upstream relationship changes again. Those answers matter more than the license label when the editor sits in a regulated environment.
What drives the running cost of each editor
Running either editor costs more than its license line. The main drivers are the Document Server infrastructure, the skills each maintenance path needs, which support tier you buy, how often you upgrade across release lines, and whether an Enterprise or Nextcloud Enterprise contract is required. Each card names one driver and what to confirm in a written quote.
Document Server infrastructure footprint
Both editors run as a separate Document Server beside Nextcloud, so you pay for another service to host, patch and monitor. ONLYOFFICE Docs 9.4 consolidated the Community Edition into a single process without RabbitMQ or database dependencies, which lowers the number of moving parts you operate. Euro-Office is not a standalone application and needs a platform such as Nextcloud to store the files. Ask each vendor for its sizing guidance for your user count, concurrent editing load and document types, and confirm whether that guidance assumes a dedicated host or a shared one.
Skills for the build path
Euro-Office is distributed as signed Nextcloud Office builds with package repositories for production, and as unsigned community builds for testing. Running the community build means your team owns the build, signing decisions and patch intake. ONLYOFFICE Docs is installed with Docker as its recommended method, so the skill set centers on container operations and config files. Confirm which path your staff can support in-house and whether the vendor's package repositories cover your operating systems.
Support tier and what it covers
ONLYOFFICE publishes Basic, Plus and Premium support tiers under its Enterprise Edition, with Community support limited to GitHub and the forum. Nextcloud sells support through a Nextcloud Enterprise subscription, which is the route for production Nextcloud Office builds. Before you sign, confirm response windows, which product versions are covered, whether Document Server issues are in scope when Nextcloud is the front end, and who you call when the two layers disagree about a fault.
Enterprise or Nextcloud Enterprise contract
Ask whether your target state needs a paid contract at all. ONLYOFFICE Enterprise features such as the admin panel, white labeling and scaling for thousands of users sit behind a paid edition, so a team that needs them pays for that license. For Nextcloud Office in production, the signed builds come with a Nextcloud Enterprise subscription. Map each feature you need to the edition that includes it, then request a quote that prices those features separately from base support.
Upgrade cadence across release lines
Each editor ships on its own schedule, so one Nextcloud deployment can require two upgrade tracks. ONLYOFFICE DocumentServer v10.0.0 was published on October 12, 2026, after v9.4.0 on May 19, 2026, and Euro-Office DocumentServer v9.3.5 was published on October 9, 2026. Plan a recurring test cycle for each Document Server line and each Nextcloud release, and ask vendors how long they keep prior lines supported and what the upgrade path from your current version involves.
One-time versus recurring costs
Installation, integration with Nextcloud, identity and storage wiring, and initial hardening are one-time work, whether you do them in-house or through an implementation partner. Subscriptions, support renewals, the test cycle for each upgrade and the staff time to watch security advisories recur every year. Ask any quote to split these two buckets, so you can compare the recurring total of each editor over the same period rather than the first invoice alone.
How to move from ONLYOFFICE to Euro-Office, or back, without losing documents
This sequence moves editing from one ONLYOFFICE-based Document Server to the other while keeping files, sharing and co-editing intact, and it ends with a documented cutover you can roll back. Each step produces a check you can record before the next one starts.
Inventory connector versions and the file platform
Your platform administrator records the Nextcloud or other file platform version, the ONLYOFFICE or Euro-Office connector app version, the Document Server version in use, and every Enterprise setting in place, such as admin panel options, white labeling and support tier. Also list the file types in active use, including PDF and legacy formats that depend on conversion. Confirm the connector path with the vendor or the connector documentation before you assume a version will work, because Euro-Office is a fork built on ONLYOFFICE and the ONLYOFFICE connector is maintained separately. The step is done when this inventory is saved in a change record that the rest of the team can read.
Stand up the target Document Server in a test instance
Your platform or infrastructure team deploys the target Document Server, either ONLYOFFICE Docs or Euro-Office, in a non-production instance that mirrors the production file platform version and its database. Use the Euro-Office build that matches your support model: signed Nextcloud Office builds for production, or unsigned community builds for testing only. Connect the test file platform to this server and confirm that the editor opens a sample document. The step is done when the test instance loads a document from the file platform without errors in the server logs.
Confirm the connector path and configuration
Your integration owner checks which connector the target Document Server needs, installs it in the test instance, and records each configuration key that differs from production, including the Document Server address, JWT secret handling and any allowed-origin settings. Ask your vendor or your DeployOpen scope to confirm which connector version pairs with the target build, since that pairing is the most common source of breakage. The step is done when the test instance opens, saves and closes documents through the agreed connector with a written list of every changed setting.
Move the file store only if the platform requires it
If the file platform and the editor can both read the existing storage, leave the files where they are and skip this step. If a new storage location or database is required for the target setup, your storage engineer copies the data with the file platform's supported tooling, then compares file counts, checksums and share records between source and destination. Files and sharing links transfer with the file store, but internal share permissions, group membership and any editor-specific metadata must be checked by hand. The step is done when a sample set of files and shares matches the source record exactly.
Re-test co-editing and conversion
Your QA owner runs a scripted set of tests in the test instance: two users co-editing the same DOCX, XLSX and PPTX file, saving and reopening it, opening a PDF for form filling, and converting legacy formats such as DOC, ODT and RTF to the native Office Open XML types. Record the results for each file type and each user role, including users who depend on Enterprise features. The step is done when every test passes or has a written defect that is accepted, fixed or deferred by the owner of the platform.
Brand, rebuild and document what does not transfer
Your platform team rebuilds the items that move with configuration rather than with files: connector settings, logos and any branding changes, admin panel customizations and support contacts. Where your organization used ONLYOFFICE Enterprise features such as white labeling, check whether the target build offers the same option and confirm the license position before you reproduce the setting. Document each rebuilt item with its owner and the date it was verified. The step is done when the rebuild list is complete and signed off by the platform owner.
Cut over and keep the original as a fallback
Your change manager schedules the cutover with a written rollback plan, switches the production connector to the target Document Server, and keeps the original Document Server running and reachable until the team has used the new setup for normal work. Confirm with users that open documents still save and co-edit correctly, and monitor logs for conversion or save errors. The step is done when the production checklist is signed, the rollback path has been tested in the test instance, and the original server is decommissioned under a recorded decision.
Where ONLYOFFICE and Euro-Office projects usually run long
Projects that combine ONLYOFFICE or Euro-Office with Nextcloud tend to slip at the seams between components, not in the editor itself. The first seam is connector version alignment. Confirm which Nextcloud line you run (35, 34 or 33 are all maintained), which document server build you will point it at, and whether your connector is the ONLYOFFICE connector or the Nextcloud Office path, because the two sides must agree on the same API behavior. Test a version pair in a staging copy before any upgrade is scheduled, and record the pair you approve so the next upgrade starts from a known state. The second group of delays is file behavior. Legacy .doc, .xls and .ppt files, RTF and OpenDocument files all pass through conversion, and PDF workflows such as form filling, annotations and page manipulation need their own test set. Build a sample corpus from your real archive, covering macros, tracked changes, embedded fonts and large spreadsheets, and check how each format opens, saves and co-edits. Include PDF forms in the same run, since those often surface problems that document tests miss.
The third area is licensing review, which is usually paperwork rather than code. Euro-Office states that it removed the logo display requirement from ONLYOFFICE's Section 7, and ONLYOFFICE disputes that position, so your legal and procurement teams should read both license positions and decide which build and branding terms you accept before the design is frozen. Identity and reverse-proxy setup is the last common delay: check the single sign-on path, forwarded headers, WebSocket handling for co-editing and the internal URL the document server uses to reach the file platform. Scaling is where the 9.4 change matters. ONLYOFFICE Docs 9.4 removed the 20 simultaneous connection limit from the Community Edition, so load tests should be rerun against the current release rather than assumed from older runbooks. Ask any implementation partner to define in writing the test scenarios, the deliverables and the acceptance criteria before work starts. DeployOpen plans and scopes engagements this way, and fixed-scope work agrees the deliverables and timelines in writing before the first task begins.
Questions buyers ask before choosing an online office editor
Is Euro-Office a drop-in replacement for ONLYOFFICE?
Not automatically. Nextcloud states that Euro-Office is built on ONLYOFFICE code distributed under the AGPLv3, but it is a separate project with its own releases, governance and builds. Its Document Server is not a standalone application and needs a platform such as Nextcloud to store the files. If you run ONLYOFFICE Docs with Nextcloud today, confirm the connector version, the document server version, the fonts, plugins and custom settings you depend on, and how branding is handled. ONLYOFFICE has said it will keep developing its Nextcloud connector, so check which connector your stack uses. Test compatibility on a copy of your documents and workflows before you plan a switch.
Does the ONLYOFFICE logo clause affect my deployment?
It can, depending on your license position and branding plans, and this page does not give legal advice. Nextcloud says Euro-Office removed the Section 7 requirement to display ONLYOFFICE's logo. ONLYOFFICE says Euro-Office is a direct reuse of its technology presented under a different identity, and it suspended its partnership with Nextcloud on March 31, 2026. These positions conflict. If you keep the default logo, white-label the editor or redistribute it, record which build and license terms you rely on, and get written advice from your legal counsel. Ask both vendors to confirm their terms in writing for your exact use case.
What does running Euro-Office or ONLYOFFICE need from my team?
Expect the work to fall into three areas, and the load depends on how many of them your team already covers:
- Platform administration for the file server, such as Nextcloud, ownCloud or Seafile, and its connector.
- Operations for the document server, including container or package installs, updates, TLS, backups and monitoring.
- License and build management, so you know which edition or build runs in production. Signed Nextcloud Office builds come with package repositories and support through a Nextcloud Enterprise subscription, while unsigned Euro-Office community builds are intended for testing.
Skills in the file platform and the document server matter more than in the editor itself.
How long does a migration to Euro-Office take, and what drives it?
The sources do not publish a duration for this switch, so ask for a timeline in a written scope rather than relying on a general estimate. The main drivers are the number of document servers, custom connectors, plugins and integrations; the volume and format mix of stored files, such as DOCX, XLSX, PPTX, PDF and the OpenDocument formats; whether you change only the editor or also the file platform; and how much branding must be removed or kept. Euro-Office's first stable release became available on June 9, 2026, so check the release you would deploy against your current configuration. Co-editing sessions also need a maintenance window.
Can we run Euro-Office ourselves, or do we need a vendor?
Your team can run either editor itself if it has the skills, since both are self-hosted AGPL code. Doing it yourself means owning patches, upgrades, backups and any changes needed after a licensing review. Nextcloud's commercial support covers its signed Nextcloud Office builds, so check whether that subscription fits your environment. DeployOpen can plan, implement, customize, integrate, harden, back up, upgrade, document and support self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. Work is usually fixed-scope, with deliverables and timelines agreed in writing before it starts, and retainers cover ongoing support and upgrades.
When is an ONLYOFFICE Developer Edition license required?
The Developer Edition is sold under a commercial license for software vendors that embed the editors in services they provide to customers, so that is the case to check first. Your own staff using ONLYOFFICE inside your organization is a different situation, and the edition comparison does not settle it for every deployment. Confirm with ONLYOFFICE whether your internal use, your connector and any customer-facing feature need a commercial license. Enterprise Edition is a separate product that adds an admin panel, white labeling, scaling for thousands of users and Basic, Plus or Premium support, so compare it with the Developer Edition before you sign.
Does the 20-connection limit still apply to ONLYOFFICE Community?
No. 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. That change affects capacity planning, not licensing. Enterprise Edition still adds scaling for thousands of users, support tiers and admin features. Before you decide, test the document server at your expected peak concurrency on your own hardware, and confirm the current behavior of any Euro-Office build you evaluate, since the sources for Euro-Office do not describe its connection limits.
How DeployOpen helps choose, implement or migrate your office editor
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For ONLYOFFICE vs Euro-Office, that starts with a written scope that settles which editor, which file platform and which license position your organization needs before any build work begins.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- We document which file platform, editor build and connector version your team runs today, and which one you intend to run.
- We confirm license obligations with you and your counsel, including logo display terms, before any branding decision is made.
How we build
- We deploy the chosen editor server inside your cloud account, data center or air-gapped network, not on a vendor-hosted service.
- We integrate the editor with your file platform and test co-editing, PDF handling and format conversion for your document types.
- We customize and harden the deployment, and we test it against the security testing scope agreed for your environment.
How we hand over
- You receive documentation covering the architecture, configuration, upgrade steps and the license position we agreed.
- We run a migration plan for existing ONLYOFFICE or Euro-Office documents, connectors and user settings, with the test results recorded.
- We walk your administrators through backup, restore and upgrade procedures so your team can operate the deployment independently.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped in writing separately from the build.
- Retainers can cover tracking of new ONLYOFFICE and Euro-Office releases and planned upgrade windows for your file platform.
- Ask any quote to state what recurs, such as support hours, upgrade work and testing, and what is one-time, such as the initial build.
