When is the free ONLYOFFICE Docs Community Edition enough?
If your team runs its own file platform and the editor only needs to work, the free Community Edition may be enough. ONLYOFFICE Docs Community Edition is AGPL-3.0 licensed, and since ONLYOFFICE Docs 9.4 removed the 20 simultaneous connection limit, it no longer caps concurrent co-editing on that basis. That matters most for teams connecting ONLYOFFICE to Nextcloud, ownCloud, Seafile or another WOPI-compatible host, where the editor server sits behind the file platform and users never see its administration interface. Before you commit, confirm the current connection and scaling behavior for your expected concurrency in the ONLYOFFICE Docs 9.4 release post and in your own load test.
The Community Edition suits a team that is comfortable administering everything through configuration files, since ONLYOFFICE's edition comparison lists configuration through config files only and community support through GitHub and the forum. Someone on your team must own the local.json settings, JWT secret handling, certificate renewal, upgrades and log review, and that effort recurs with every release. Enterprise becomes the better fit when you need the admin panel, white labeling of the editor interface, scaling for thousands of users, or a contracted Basic, Plus or Premium support tier with a response commitment your procurement or risk team can hold a vendor to. Ask ONLYOFFICE for the written support terms and any scaling guidance for your user count before you decide.
The Developer Edition answers a different question: whether you are allowed to use the editors at all. ONLYOFFICE sells it under a commercial license for software vendors that embed the editors in services they provide to customers, so a SaaS product or a hosting provider that delivers document editing to its own customers should review its license position with ONLYOFFICE rather than assume AGPL terms cover it. An internal deployment for your own staff does not usually need that license, but confirm the distinction against your actual service model with counsel. Price and terms for any of these editions come only from ONLYOFFICE's quote against a written scope.
Which features sit in Community and which need Enterprise?
This table compares the capabilities ONLYOFFICE documents for its free AGPL Community Edition and its paid Enterprise Edition, row by row. Read the Community column as the baseline in the vendor's edition comparison, and confirm any entry marked as unconfirmed in writing with ONLYOFFICE before you commit. The main takeaway is that the 9.4 release removed the 20-connection limit from Community, so the paid split centers on administration, branding, scale and support.
| Capability | Community Edition (AGPL-3.0) | Enterprise Edition |
|---|---|---|
| File formats, conversion and PDF editing | Native .docx, .xlsx and .pptx; converts DOC, ODT, RTF, ODS, CSV and ODP; PDF text, page, annotation and form editing per the README | Not listed as an Enterprise difference; confirm the current format and PDF list with ONLYOFFICE |
| Integrations with Nextcloud, ownCloud, Seafile and WOPI hosts | Listed in the DocumentServer README as supported integrations | Not listed as an Enterprise difference; confirm connector versions for your platform release |
| Installation method | Docker is the recommended method; configure through files | Same packaging is not separately documented; confirm supported install paths and scope |
| Admin panel | No | Yes |
| White labeling | No | Yes |
| Scaling for thousands of users | Not listed as a Community capability | Listed for thousands of users; ask for sizing guidance and architecture for your user count |
| Configuration method | Config files only | Admin panel added on top of configuration; confirm which settings the panel controls |
| Simultaneous connections | No 20-connection limit since 9.4 (May 19, 2026) | Confirm whether any connection terms differ from Community |
| Support channels | Community support through GitHub and the forum | Basic, Plus or Premium support tiers; compare response terms in the written quote |
What changed when 9.4 removed the 20-connection limit
The main change in ONLYOFFICE Docs 9.4, released on May 19, 2026, is that the 20 simultaneous connection limit no longer applies to the Community Edition. ONLYOFFICE also consolidated the Docs server into a single process that does not depend on RabbitMQ or a separate database. For a platform team, this changes the shape of the deployment more than the license. Earlier designs that assumed a message queue and database alongside the document server can be simplified, and the number of components to patch, monitor and back up goes down. Confirm the exact service layout for your target version against the ONLYOFFICE blog post on 9.4 and the release notes before you change an existing cluster.
Operationally, the question shifts from how to stay under the connection cap to how to size and load test the single process for your concurrency. Run a pilot with your real integration (Nextcloud, ownCloud, Seafile or a WOPI host), measure memory, CPU and document conversion latency at peak editing sessions, and record the results before you sign off on an architecture. If your existing deployment used the queue or database for scaling, plan a migration step and a rollback path, and test both in a non-production environment.
What did not change is the commercial boundary. The admin panel, white labeling and Basic, Plus or Premium support remain Enterprise Edition features, and the comparison page lists Community support as GitHub and the forum with configuration through config files only. If your team needs a graphical admin console, branding for end users, or a support contract with response commitments, those requirements still point to the Enterprise edition. Ask ONLYOFFICE to confirm in writing which features are included in each tier and which support terms apply.
How licensing and support differ between editions
ONLYOFFICE Docs is sold under three different sets of terms, and each one changes who you can turn to when something breaks and what you owe when you ship the editors to others. The cards below cover the free AGPL Community Edition, the paid Enterprise Edition, the commercial Developer Edition and the AGPL-3.0 obligations that apply to modified, network-facing deployments. Confirm current terms in writing with ONLYOFFICE before you decide.
Community Edition under AGPL-3.0
The Community Edition of ONLYOFFICE Docs is licensed under AGPL-3.0, so you can run it without a license fee and inspect the source. Support comes from GitHub issues and the community forum rather than a contracted vendor, so response times depend on volunteers and cannot be guaranteed. Since 9.4 removed the 20 simultaneous connection limit, the main question is no longer connection count but whether your team can absorb its own troubleshooting, patching and upgrades. Ask ONLYOFFICE to confirm in writing what the Community terms cover.
Enterprise Edition with support tiers
The Enterprise Edition is a paid tier that adds an admin panel, white labeling and scaling for thousands of users, with Basic, Plus or Premium support. Community configuration relies on config files only, so the admin panel is the main operational difference for teams managing many users. Compare the support tiers against your own on-call and severity requirements, and ask what response targets each tier commits to. Pricing and terms are set in your written quote, not assumed from this page.
Developer Edition for embedding vendors
The Developer Edition is sold under a commercial license for software vendors that embed the editors in services they provide to customers. If your product or managed service delivers document editing to third parties, the AGPL-only Community path may not match how you distribute the software. Map each customer-facing delivery model against the license text before choosing. Confirm with ONLYOFFICE whether your model counts as embedding under its terms.
AGPL-3.0 network use obligations
AGPL-3.0 extends source obligations to software users interact with over a network, so if you modify ONLYOFFICE Docs and offer it to users through a web service, you may need to make your modified source available to those users. Internal use without modification carries lighter duties, and the answer changes with how you customize the editors, integrate them or host them for others. Involve legal counsel early and keep a record of every change. Verify the obligations against the license text and ONLYOFFICE's terms before deploying.
Support path for internal deployments
A company that runs Community internally must plan its own escalation path, since GitHub and the forum are not a contracted service. Document who monitors upstream releases, such as DocumentServer v10.0.0 published on October 12, 2026, and who tests them before rollout. Decide whether a retainer or paid tier is needed to meet your recovery expectations. Ask any support provider to define severity levels and hours in writing.
What to confirm before deciding
Before buying a tier, get written answers on which features each edition includes, how support is delivered, whether your delivery model needs the Developer license, and how AGPL obligations apply to your modifications. Ask for the scope of white labeling in Enterprise, the support tier terms, and any change in terms between releases. Keep the answers with your architecture and compliance records, because they will shape your licensing position for years.
Which edition fits your deployment?
If you run ONLYOFFICE Docs behind Nextcloud, ownCloud or Seafile for one organization's staff, the Community Edition is usually the starting point. The AGPL-3.0 license covers running the document server for your own users, and the 9.4 release removed the 20 simultaneous connection limit that used to shape small deployments. The integration itself is documented in the DocumentServer README, which names these platforms among its supported integrations.
- Editing scope: Native Office Open XML editing, format conversion and PDF editing are part of the free edition, so most internal document work needs no paid license.
- Admin panel: The admin panel and white labeling are listed as Enterprise features, so branding and central administration stay on the paid side.
- Configuration: Community configuration is done through config files only, which is workable for a small platform team.
- Support: Community support runs through GitHub and the forum, with no contractual response times.
Confirm with your file platform's vendor which ONLYOFFICE connector version it supports, and confirm that your staff count does not trigger a need for the admin features before you commit to Community.
A multi-thousand-user enterprise usually needs more than the editors themselves. ONLYOFFICE's edition comparison lists scaling for thousands of users, an admin panel and white labeling as Enterprise Edition features, so this tab is where the paid edition most clearly changes what you operate. The Community Edition still performs document editing without the 20 connection cap, but the management layer is not part of it.
- Central administration: The admin panel is the Enterprise feature most teams will ask to be budgeted first.
- Scaling: The comparison page ties thousands-of-users scaling to the Enterprise Edition, so do not assume the Community setup scales the same way.
- Branding: White labeling is an Enterprise feature, relevant if editors must match internal branding.
- Support tier: Enterprise support is offered in Basic, Plus or Premium levels, each with different terms.
Ask ONLYOFFICE for the current written feature list for the version you plan to deploy, and request load-test results for your own user profile before you rely on any scaling claim.
If you embed the editors inside a product or service you sell to customers, the license question changes. ONLYOFFICE sells a Developer Edition under a commercial license for software vendors that embed the editors in services they provide to customers. The Community AGPL-3.0 license is not the same as a commercial embedding right, so the license decision comes before any architecture decision for this tab.
- License trigger: Providing editing to your customers inside your own service is the case the Developer Edition is designed for.
- Community limits: AGPL-3.0 obligations can apply when you distribute or offer modified network services, so legal review is needed.
- Feature set: Confirm whether the Developer Edition includes the features your product needs, since the public comparison is the starting point.
- Ownership of support: Clarify who supports your customers when an editing issue reaches ONLYOFFICE, you, or an implementation partner.
Have counsel read the ONLYOFFICE license terms against your exact delivery model, and get the Developer Edition terms in writing before you build.
Regulated organizations often need a named support tier, contractual response commitments and documented patch processes. The Community Edition has support through GitHub and the forum, which is not a contract. Enterprise Edition support is sold in Basic, Plus or Premium tiers, and the public comparison does not give response times, so you must read the terms directly. Compliance assessors will want evidence of who patches the document server and how quickly.
- Support tiers: Basic, Plus and Premium differ in scope, and the levels should be mapped to your incident and patch requirements.
- Evidence: Request a written description of update delivery, security fix notification and supported versions.
- Change control: Document how Community or Enterprise versions are tested before production, since v10.0.0 is a new major release.
- Auditor readiness: DeployOpen prepares systems, controls and evidence for assessments, but independent auditors issue the findings.
Ask ONLYOFFICE for the response targets, supported version policy and escalation path for each tier in writing, and check them against your own compliance obligations.
What does each edition cost to run?
This table breaks down what each ONLYOFFICE Docs edition costs beyond the license line, including who is paid, what recurs and what moves the total. Read it as a checklist for a quote request, because ONLYOFFICE does not publish Enterprise prices here and no figures are given for either edition.
| Cost component | Community Edition | Enterprise Edition |
|---|---|---|
| License or subscription fee | No license fee under AGPL-3.0. Confirm with your counsel how your use, modifications and distribution are covered. | Paid subscription. Request a quote for the tier, support level and user or connection scope, since prices are not published. |
| Infrastructure and Docker hosting | Recurring compute, storage and bandwidth in your own cloud or data center. Docker is the recommended install method, so plan for container hosting and image updates. | Same recurring hosting footprint, plus any scaling components you add for larger user counts. Ask the vendor which topology it expects for your load. |
| Staff time for setup and upgrades | Recurring internal effort for configuration through config files, certificate handling, version upgrades and testing against your file platform. | Similar internal effort, with some admin panel tasks moved into the UI. Ask what remains file-based and what upgrade testing the vendor expects. |
| Integration work | One-time work to connect to Nextcloud, ownCloud, Seafile or a WOPI host, plus recurring retesting after each platform upgrade. | Same integration work. Confirm whether white labeling and branding changes are included in the quote or billed separately. |
| Support | Community support through GitHub and the forum, so response depends on community activity. Your team carries incident response. | Paid Basic, Plus or Premium support tiers. Ask for the response windows, severity definitions and what each tier covers before you compare. |
| What drives cost up | More document load, more hosts for high availability, staff turnover and frequent upgrades across several integrated platforms. | Higher user counts, stricter support tiers, added scaling components and extra white labeling or customization scope. |
| What keeps cost down | Standard Docker deployment, a single well-documented integration, and a tested upgrade runbook kept current. | Clear written scope, one support tier matched to real incident risk, and a quote that lists every optional feature separately. |
How to move from Community to Enterprise, or back
The sequence confirms the feature gap, secures a written quote and support tier, rolls out the license and admin panel, validates the host integration, and sets a documented fallback if the subscription lapses. The result is a move that can be reversed without losing documents or breaking the connector.
Confirm the feature gap against your requirements
List what the Community Edition does not give you that your team needs, such as the admin panel, white labeling, scaling for larger user counts, or Basic, Plus or Premium support. Compare that list against the edition comparison published by ONLYOFFICE. Community Edition already removed the 20 simultaneous connection limit in 9.4, so that limit should no longer be the reason to upgrade. Done means a signed-off gap list that names each missing feature and the person who needs it.
Request a written quote and support tier
Send the gap list and your deployment details to ONLYOFFICE or an authorized channel and ask for a written quote tied to a stated scope. Ask which support tier (Basic, Plus or Premium) is included, what response coverage applies, how license keys are issued and renewed, and whether the price recurs annually. DeployOpen does not publish a price list, so the quote is the only reliable cost figure. Done means a quote that lists the edition, support tier, term and renewal terms in writing.
Plan the license key and admin panel rollout
Decide where the Enterprise license key will be stored, who can replace it, and which environment receives it first. Install the Enterprise build in a staging copy of the document server, then enable the admin panel and any white labeling settings there before production. Record every setting you change, because the Community Edition is configured through config files only and the admin panel adds a second place to manage settings. Done means a tested staging instance with the key applied and a change log of settings.
Test integrations with the host platform
Connect the staging document server to a non-production copy of your host platform, such as Nextcloud, ownCloud, Seafile or a WOPI-compatible system, and open, edit, save and co-edit representative .docx, .xlsx and .pptx files. Test PDF editing and conversion paths your users depend on. Confirm the JWT secret, the server address and the host connector all still match after the change. Done means a written test result for each host integration and each file type in your inventory.
Cut over production and verify users
Schedule the production change in a maintenance window agreed with the host platform owners, then repeat the integration checks against production with a small pilot group. Confirm that existing documents open, that co-editing sessions behave as before, and that the admin panel reflects the expected license state. Keep the Community configuration files and a backup of the data before the switch. Done means a pilot sign-off and a stored backup labeled with the pre-change version.
Document the reverse path if the subscription lapses
Write down what happens if the subscription ends: which edition runs afterward, whether the Community Edition can be reinstalled on the same version line, and which Enterprise-only settings must be removed or disabled first. Confirm with ONLYOFFICE in writing how a lapsed key is handled and whether any feature stops working without warning. Test the fallback in staging at least once so the team knows the steps. Done means a runbook that a second engineer can follow without the original author.
Confirm what stays the same and what changes
Record the items that should not change, such as document formats, file storage, the document server URL and the host connector, and the items that do change, such as the admin panel, license key handling and the support contact. Ask ONLYOFFICE to confirm any change to updates, backups or upgrade procedures before you rely on them. Done means a short summary that the platform owner and the compliance lead have both reviewed and signed.
What do buyers ask before choosing an edition?
Can ONLYOFFICE Docs Community serve many concurrent editors now?
Yes, the 20 simultaneous connection limit was removed from the Community Edition with version 9.4, released on May 19, 2026. ONLYOFFICE also consolidated the Community Edition into a single process without RabbitMQ or database dependencies, which simplifies the stack. Concurrency is still a capacity question, not a licensing one. Your practical limit depends on the server's CPU and memory, document sizes, the number of concurrent co-authoring sessions, and how your storage and file sync platform calls the editors. Load test with your own document mix before you size production, and confirm current limits and tuning guidance with ONLYOFFICE before you commit to a design.
What does ONLYOFFICE Enterprise Edition cost and how is it quoted?
ONLYOFFICE publishes an edition comparison, but the supplied material does not include Enterprise pricing, so confirm the current figures directly with ONLYOFFICE. Enterprise adds an admin panel, white labeling, scaling for thousands of users, and Basic, Plus or Premium support tiers. Ask for a quote that states the user or connection basis, the support tier, the license term, whether renewals are annual, and whether upgrades to later major versions are included. Costs that recur are the subscription and support renewals. One-time costs are usually the integration, testing and cutover work, which you pay separately to whoever performs it. DeployOpen does not publish a price list, and its quotes follow from a written scope.
How long does a move from Community to Enterprise take?
The duration depends on what you have built around the Community Edition. The supplied facts do not give a migration timeline, so treat any figure from a vendor or partner as something to verify. The main drivers are the number of integrated platforms (for example Nextcloud, ownCloud, Seafile or WOPI hosts), custom configuration kept in config files, the need for white labeling or admin panel changes, and your change-control rules. Plan for a staging environment, a test of document conversion and co-authoring, and a rollback path. Ask the vendor and any implementation partner for a written plan with named tasks before agreeing a date.
Can a platform team run ONLYOFFICE Docs Community without vendor support?
A capable platform team can run the Community Edition on its own, since it is AGPL-3.0 and Docker is the recommended installation method. Support for Community comes through GitHub and the community forum, and configuration is done through config files only. The work that recurs is patching, watching release notes such as the DocumentServer v10.0.0 release on October 12, 2026, testing upgrades against your integrations, certificate and JWT configuration, backups, and monitoring. Decide whether your team has the time and the on-call coverage for those tasks. If it does not, a paid support tier or a fixed-scope implementation and retainer with a services provider may be cheaper than the staff time you would otherwise spend.
When is the 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. If you only run ONLYOFFICE Docs inside your own organization, or connect it to a file platform you operate for your own staff, the AGPL Community Edition may cover you, but you should have counsel confirm that against your actual service model. If you build a product or hosted service that gives editing to your customers as part of what you sell, check the Developer Edition terms before launch. Ask ONLYOFFICE in writing which licence fits your deployment and what conditions apply.
What do ONLYOFFICE support tiers actually differ on?
The supplied comparison lists Basic, Plus and Premium support as Enterprise Edition features, but it does not give the response times, hours or escalation paths for each tier in the material available here. Compare the tiers on the points that matter to your operation: coverage hours, severity definitions, response and resolution commitments as written in the contract, access to named engineers, help with upgrades and incident analysis, and whether support covers your integrations with Nextcloud, ownCloud, Seafile or other WOPI platforms. Get those terms in writing and check them against your own incident process.
What does a DeployOpen engagement scope cover for ONLYOFFICE?
DeployOpen plans, implements, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure, which can include ONLYOFFICE Docs. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. A typical scope for this decision could include a sizing review, installation in your cloud account or data center, integration with your file platform, hardening, backup and restore tests, and documentation. Ongoing support, upgrades and continuous testing are available as retainers. DeployOpen does not publish prices, and the quote follows from the written scope. DeployOpen is not an official partner or reseller of ONLYOFFICE, and it does not issue audit reports or certifications.
What should I confirm about security and data handling before choosing?
Confirm where the document conversion and editing services run, which network paths they need, and how they authenticate to your file platform. Check the JWT secret handling, TLS configuration, and which logs record document access. Because the Community Edition is configured through files, confirm the change process for those settings. Ask the vendor which Enterprise features touch access control or branding, and whether any of them change your audit evidence. DeployOpen can prepare systems, controls and evidence for a compliance assessment, but independent auditors and certification bodies issue the reports, so confirm your framework's requirements with them.
How DeployOpen scopes and supports either edition
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For ONLYOFFICE Docs, that work starts with deciding which edition fits your users, integrations and licensing position, then turning that decision into a written scope.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope records which ONLYOFFICE Docs edition applies, which file platforms connect to it and who the users are.
- Quotes follow from the written scope, so ask us to list each licensing, hosting and integration item separately.
How we build
- We deploy ONLYOFFICE Docs in your cloud account, data center or air-gapped network, not on infrastructure we operate for you.
- We wire the editors into your file sync and share platform and document the connection settings and their owners.
- We run security testing against the deployment and harden the configuration before users are onboarded.
How we hand over
- Handover documents the installed edition, configuration files, backup routine and upgrade steps in your environment.
- Compliance evidence covers configuration and access records that your independent auditor can review, not an audit result.
- Your team receives a runbook that states what changes if you later move from Community to an Enterprise or Developer license.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped separately from the build.
- Ask us to confirm which upgrade path applies to your edition before each DocumentServer version change.
- Vendor support tiers, such as Basic, Plus or Premium, are bought from ONLYOFFICE and are not included in DeployOpen services.
