What document editing costs when you self-host it
The license is often the smallest line in a self-hosted document editing budget. What you pay depends on how many people edit, how many edit at the same moment, who carries support when an editor misbehaves, and who runs the servers day to day. A team comparing a Microsoft 365 or Google Workspace renewal with a self-hosted editor should cost all four before comparing the per-seat figures. There are three ways to fund the work. An in-house build means your own staff install, patch, scale and troubleshoot the document server. An implementation partner such as DeployOpen plans, deploys and hardens the stack in your infrastructure under a fixed scope, and ongoing support is usually a separate retainer. SaaS moves hosting to a vendor but gives up control over where documents and editing sessions run.
The free download is real value for testing and small teams, but it is not a production support plan. Collabora describes its free CODE edition as suited to testing, home use or small teams and not recommended for production, and it is released as a rolling build. ONLYOFFICE Docs Community Edition is AGPL-3.0 licensed and supported through GitHub and the forum, with configuration done through config files. For regulated workloads, ask whether a paid edition carries long term support, signed security updates, a service level agreement and a named escalation path. Collabora's published Business plan price of 3 euros per user per month applies to up to 99 users, and its Enterprise plan is quoted for 100 or more users, so confirm the current terms directly with the vendor.
Recurring costs sit in the servers and the people. Concurrent editing drives server sizing, and Collabora's Helm chart recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with scaling set by hand because autoscaling breaks collaborative sessions. Plan for staging, backups, upgrades, font management and monitoring as ongoing work. Before requesting a quote, ask the partner for a written scope that lists the editor edition and support tier, the number of named users and expected peak concurrency, the file platform integration, the server count and sizing assumptions, the backup and upgrade schedule, and what is excluded. DeployOpen issues quotes only after that written scope is agreed.
Which cost components sit with you, a partner or a SaaS vendor
This table shows who typically pays for each cost component of self-hosted document editing when you build in-house, hire a partner, or buy a hosted editing service. Read each row for the owner, then check whether the cost is one-time or recurring, since recurring items drive the total over the life of the platform. Most of the recurring cost sits in subscriptions, patching and support rather than in the initial setup.
| Cost component | In-house | Partner or SaaS |
|---|---|---|
| Software license or subscription | Community builds are free to use under AGPL-3.0 or MPL-2.0. Collabora Business is 3 euros per user per month for up to 99 users (Collabora pricing page). Nextcloud Enterprise Standard starts at 71.29 euros per user per year for 100 or more users (Nextcloud pricing page). Recurring. | Subscriptions are billed per user or per year and recur. Confirm in writing whether the vendor or a reseller invoices you, and what the quote covers. |
| Servers and storage | You buy and run compute, memory and storage for editor pods and the file platform. Recurring as infrastructure. Sizing depends on concurrent editors. | A SaaS vendor provides hosting in its own cloud, usually billed recurring. Confirm where documents and editing sessions are stored and processed. |
| Container platform and load balancing | You operate Docker or Kubernetes, ingress, and sticky routing by WOPISrc so all editors of one document reach the same pod. One-time design, then recurring operation. | A partner can configure and document the platform for you. Ongoing operation is recurring and should be scoped separately from setup. |
| File platform integration (Nextcloud or other WOPI host) | Your team configures the WOPI connection and tests each file platform version. One-time build with recurring retesting after upgrades. | A partner can build and test the integration. Confirm whether it covers future file platform major releases. |
| Installation and customization | Staff time for deployment, branding, and any custom functions. Largely one-time, with change requests recurring. | Fixed-scope project fees are typically one-time, agreed in writing before work starts. Customization is priced separately. |
| Fonts and format testing | Your team builds a test set of your own templates and fonts and checks fidelity for .docx, .xlsx and .pptx files. Repeated at each major upgrade. | A partner can run the fidelity test on your templates. Ask who owns the test set after the project ends. |
| Upgrades and security patching | Your staff apply monthly maintenance and major releases, back up first, and handle third-party app compatibility. Recurring. | Retainer-based upgrades and patching are recurring. Vendor-managed SaaS includes patching in the subscription, but confirm the terms. |
| Monitoring and backups | You own alerting, capacity tracking, and backup and restore testing. Recurring operating cost. | Partners can set up monitoring and backups as a one-time task and run them under a retainer. SaaS vendors handle this, but confirm restore terms. |
| Support | Community support comes through forums and GitHub. Commercial support is an additional subscription tier. Recurring. | Support is included in some paid tiers. Collabora Business includes long term support and a service level agreement. Confirm response times in writing. |
When a free community build is enough and where it stops
A free community build carries no license fee, and that is the reason it is often the first option a small team tests. CODE, the free edition of Collabora Online, is released roughly once a month as a rolling release, and Collabora describes it as suited to testing, home use or small teams but not recommended for production. ONLYOFFICE Docs Community Edition is licensed under AGPL-3.0 and is also free to run. Neither license fee is the real cost. What changes is who carries the operational work: someone on your staff applies each update, watches the server, diagnoses editing failures and changes settings in configuration files, because the community route offers no admin panel and no vendor-backed support tier.
ONLYOFFICE 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, according to the ONLYOFFICE blog. That change makes the community build more credible for teams with larger concurrent editing loads, but it does not remove the other gaps. The Enterprise Edition adds an admin panel, white labeling, scaling for thousands of users and Basic, Plus or Premium support, according to ONLYOFFICE's edition comparison. Ask whether your security team accepts a rolling release without a written patch commitment, and whether the staff who will run it can apply a security fix within your own change window.
The community route stops being cheaper once you need a contractual support path, signed security updates or a version you can stay on for a defined period. Collabora's paid Business plan, listed at 3 euros per user per month for up to 99 users, includes long term support, a service level agreement, signed security updates and customer portal access, according to Collabora's pricing page. Before you decide, count the staff hours that would absorb incident response and upgrades, then compare that figure with the subscription and with an implementation partner's fixed-scope quote. Confirm the current terms directly with each vendor, since editions and limits change between releases.
What moves the cost up or down
Document editing costs follow a small set of decisions: how many people edit at once, how many users hold a license, how much support the business requires, and how much integration and testing the file platform demands. Each card below names one of these levers and what to confirm before accepting a quote.
Concurrent editors and peak load
Server capacity is driven by how many people edit at the same time, not by the total user count. The Collabora Online Helm chart recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB. Ask the partner how many pods the peak needs, how many documents each pod is expected to hold open, and whether the figure covers term start, month end or other known spikes. Each extra pod adds infrastructure cost and operating effort.
User count and license tiers
Per-user subscriptions scale with the number of named users, so the cost curve changes at tier boundaries. Collabora's Business plan is priced per user for up to 99 users, and its Enterprise plan for 100 or more users is quoted with volume discounts. Count the people who will edit, not everyone with a mailbox, and ask whether view-only users need a license. Confirm the edition that matches your count before comparing totals.
Support and lifecycle commitments
Free community builds carry no vendor response obligation, so the cost of fixing a broken upgrade falls on your team or your partner. Paid tiers buy a defined maintenance window, security updates and response times. Nextcloud's list prices, for example, rise from Standard to Premium and Ultimate, and Ultimate adds support up to 24/7 with response times down to 1 hour. Decide which support level your incident process needs, then price it into the three-year total.
File platform integration effort
The editor is only one part of the job. Connecting Collabora or ONLYOFFICE to Nextcloud, Seafile or another WOPI host requires configuration, certificate handling, user mapping and access testing. Nextcloud upgrades cannot skip major releases, and each upgrade needs a backup and a check of third-party apps, which adds recurring work. Ask the partner to state the integration scope in writing, including who maintains the connector after each platform upgrade.
Format and fidelity testing
Costs rise when documents must render exactly as they do in desktop Office. Testing your own templates, fonts and legacy files takes time before go-live, and it repeats when editor versions change. ONLYOFFICE treats .docx, .xlsx and .pptx as native formats, while Collabora builds on LibreOffice technology, so the test plan may differ. Budget for a sample of real documents, a font inventory and a sign-off by the business owners who use them.
AI assistant hosting choices
Collabora Online 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 runs externally or on their own infrastructure. An externally hosted provider adds usage fees and data review work, while a self-hosted model adds GPU or compute capacity and model operations. Leave the assistant off in the initial quote, and price it separately once the hosting decision is made.
How concurrent editing sizes the server bill
Concurrency, not headcount, sets the server footprint. A company with 2,000 licensed users may only have a few dozen documents open at the same moment, while a team of 40 running a live budget review in one spreadsheet can load the editor just as hard. What the document server must handle is simultaneous editing sessions, so your server bill follows the peak number of open editors, not the size of the directory. Before comparing quotes, ask each vendor and partner how they count concurrent sessions and whether the licensing or sizing model uses the same definition you do.
The sizing decision has a constraint that changes the architecture. The official Collabora Online Helm chart disables horizontal pod autoscaling because scaling breaks collaborative editing and copy and paste, so replicas are set manually. Load balancers must route by the WOPISrc parameter so every user editing one document reaches the same pod. In practice, this means you pay for peak capacity in every hour of the year, and adding pods for a quarter-end close or a term start is an operational change, not an automatic response. Ask whether the partner's runbook covers scheduled scale-up, scale-down and what happens to open sessions during a change. The chart's README lists production resource figures per pod, which is a useful starting reference, but treat it as a baseline to test, not as capacity you can promise your users.
Your job is to measure your own peak before you buy. Pull session or connection logs from your file platform for several representative weeks, including your heaviest month, and record the maximum number of documents open in the editor at once, by hour. Then ask a partner for a sizing test on a staging environment that replays that pattern against your real templates and largest spreadsheets, with the load balancer and WOPI routing in place. Ask for the measured results, the number of pods used, the memory and CPU per pod, and the recovery behavior when a pod restarts mid-session. Those results, not a generic capacity claim, should drive both the infrastructure quote and the subscription tier.
How to build your own estimate
This sequence turns a vague budget question into a written comparison you can take to vendors, partners and your SaaS renewal, with each cost traced to a named owner. It produces an estimate built from your own user counts, sizing and staff time rather than from figures on this page.
Count named users and peak concurrent editors
Start by listing who will hold an editing right, not just who will open a file. Separate named users from people who only view, and from external guests if any. Then estimate the peak number of people editing at the same time, using your own usage data from the current file share or Microsoft 365 tenant where available. Done means you have one table with named users, a peak concurrency figure and the date you measured it, signed off by the business owner of the editing service.
Choose the edition and support tier
Match your user count to the commercial model each vendor publishes. Collabora's community build (CODE) is described by Collabora as suited to testing, home use or small teams and not recommended for production, while its paid Business and Enterprise plans add support, signed security updates and integration services. ONLYOFFICE's Enterprise Edition adds an admin panel, white labeling and paid support tiers that the Community Edition lacks. Ask each vendor in writing which tier covers your user count, what support hours apply and whether security fixes are included. Done means you have a short list of editions with the price basis confirmed in writing for your count.
Size servers and the container platform
List the hosting you need for the document server, the file platform and the database, with separate lines for test and production. For Collabora on Kubernetes, the official Helm chart disables autoscaling, so you must plan replica counts manually and route by WOPISrc, and its README recommends production limits of 8 CPU cores and 8000 MiB of memory per pod with requests of 4 cores and 6000 MiB. Confirm the equivalent limits for ONLYOFFICE with its vendor and note any load balancer, ingress and backup storage your platform team must supply. Done means a sizing sheet that your infrastructure team has reviewed and that maps each component to a cost owner.
Price internal staff hours
Estimate the hours your own engineers and administrators will spend on installation, integration with your file platform, fidelity testing on your templates, patching, upgrades and backup restoration tests. These hours are often the largest recurring cost of a self-hosted build, even when software is free. Record who performs each task, how often it recurs and what skills it needs. Done means each recurring activity has an owner, a frequency and an hourly cost basis from your finance team, so the total is visible rather than assumed.
Write partner scope as a quote request
Turn the gaps in your own capacity into a written scope for an implementation partner. DeployOpen works to fixed scope agreed in writing before work begins, and does not publish a price list, so the quote follows from the document you send. Include the platform choice, the file platform and identity integration, the environments, the testing you require, the backup and upgrade expectations, and whether you want ongoing support. Ask each bidder to separate one-time implementation from recurring support and to state what is excluded. Done means every bidder has received the same written scope and returned a quote in the same format.
Compare against the SaaS renewal and AI add-ons
Collect your current office suite renewal, including every add-on that touches editing, such as AI features, storage tiers and premium support, and convert it to the same per-user, per-year basis as your self-hosted estimate. Note that Nextcloud Enterprise, for example, has a published 100-user minimum and per-user list prices, which you should verify against its pricing page for your count. Add any AI assistant cost separately, because Collabora 26.04 lists an optional assistant that is off by default and whose provider choice affects the cost. Done means one side-by-side table of one-time and recurring costs for the options, with each figure tied to a written source.
Confirm figures and document assumptions
Before you rely on any number, request written pricing from every vendor and confirm the price basis, currency, tax treatment, minimum commitment and renewal terms. The figures on this page are only the ones cited in their sources and should not be carried into a budget unchanged. Record each assumption next to the number it supports, and set a review date when vendor price lists or edition terms change. Done means a signed estimate that finance, security and the platform owner have each reviewed, with every line linked to a vendor quote or internal timesheet.
Build, partner or SaaS: which costs fit which team
An in-house build means your own engineers install, configure, patch and operate the editor and its document server, usually from the community container images or system packages. Your costs are mostly staff time: someone must learn the WOPI integration, size the servers, set up load balancing and keep the stack current with each release. The community editions carry no license fee, but the ONLYOFFICE Docs Community Edition is AGPL-3.0 and the Collabora CODE image is described by Collabora as not recommended for production, so a production build means you own every test and every security fix.
- Staff time: setup, upgrades, font and format testing, and on-call work fall on your team and recur for as long as the service runs.
- Sizing and routing: you must set replica counts and sticky routing yourself, because the Collabora Helm chart disables autoscaling for editing sessions.
- Support: community forums and GitHub are the support path, so incidents are answered by your own staff.
- Edition limits: some features, such as the admin panel and white labeling, sit in ONLYOFFICE's Enterprise Edition, so check which ones you need before you start.
- Upgrades: you own version testing for the file platform and the editor, including the one-major-version-at-a-time rule for Nextcloud.
Before committing, check whether your team can staff an on-call rotation for a stateful, browser-facing service and whether your audit scope accepts an unsupported edition.
An implementation partner plans, installs, integrates, hardens and documents the editor inside your own infrastructure, under a written scope. The partner's fee is one-time for the build and any agreed testing, while the license relationship stays with you: you buy the paid edition or subscription from the vendor and hold the contract. DeployOpen works this way, and most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. Ongoing support, upgrades and continuous testing are separate retainers, so ask whether they are included or priced apart.
- Fixed scope: the quote lists the editions, file platform integrations, load testing, font and format checks and documentation the partner will deliver.
- License ownership: you hold the vendor subscription, so support terms, signed updates and renewal stay under your control.
- Recurring costs: the vendor fee and any retainer recur; the build fee does not.
- Incident ownership: the contract should name who responds to the editor, the document server and the WOPI link, and within what hours.
- Handover: runbooks, configuration records and evidence for your compliance assessment should be part of the deliverables.
Request a written quote that separates one-time build work from recurring retainers and vendor fees, and confirm who is paid for each item.
An office suite subscription means the vendor hosts the editing service, applies updates and runs the servers, and you pay a per-seat fee. Your recurring cost is the seat count multiplied by the subscription rate, and your internal effort falls to identity setup, license administration and user change control. The vendor answers for platform availability under its own terms, but documents, edit history and any AI processing leave your infrastructure, so the data processing terms, storage region, subprocessor list and AI processing options become central to the decision.
- Per-seat fees: cost grows with every user, including guests and occasional editors, and recurs for the life of the contract.
- Data location: check where documents and editing sessions are processed and stored, and whether that fits your transfer and sovereignty rules.
- AI processing: confirm whether any assistant sends content to third parties and whether you can disable it.
- Incident ownership: the vendor answers for its service, but you still answer to your regulator and customers for data exposure.
- Exit terms: confirm export formats, retention after cancellation and the cost of moving documents out.
Before signing, ask the vendor to show its data processing terms, subprocessor list and incident notification commitments in writing, and compare them with your own retention and audit obligations.
Questions buyers ask about document editing cost
How much effort does a self-hosted document editor take to run?
Effort depends mostly on how many people edit at once, which edition you run, and how much of the platform you operate yourself. A free community build can run on a single small server for testing or a small team, but Collabora describes its free CODE edition as not recommended for production, so production use usually means a paid edition with tested updates and security fixes. Ongoing work includes applying updates, watching the editor's version against your file platform's version, monitoring server load and keeping backups of documents and configuration. Ask any partner to split their quote into one-time setup and recurring operations so you can compare the two cost types directly.
Can our team run a self-hosted editor without outside help?
A team with container and reverse proxy experience can deploy a community build, but production operation needs more than installation. Collabora's Helm chart README says horizontal autoscaling is disabled because scaling breaks collaborative editing, so replicas are set manually and the load balancer must route by the WOPISrc parameter so every editor of one document reaches the same pod. ONLYOFFICE's Community Edition is configured through config files only, while its Enterprise Edition adds an admin panel and paid support tiers. Decide early which of these tasks you will own and which you will buy as a retainer or a fixed-scope project.
How long does setup take, and what drives the timeline?
Setup time is driven by scope, not by the installer. The main variables are the number of file platforms to connect through WOPI, the file formats your staff exchange and need to test, the number of concurrent editors you expect, and how many rounds of fidelity testing your templates need. Connecting an editor to Nextcloud is documented in the Nextcloud admin manual, but your identity integration, network rules and backup design can add more work than the connection itself. Ask for a written timeline that lists each milestone and the acceptance test attached to it.
What does the work need from our side?
You will need named owners for infrastructure, identity, storage and the business users who test documents. On the infrastructure side, Nextcloud 35 recommends MariaDB 11.8 or PostgreSQL 18 and PHP 8.5, and Nextcloud does not allow skipping major releases, so upgrades must proceed one major version at a time with a backup before each step. Your team must also provide test documents from real templates, a decision on who may edit versus view, and a window for change control. Lack of these inputs is the most common reason fixed-scope work runs past its planned dates.
How do self-hosted editors compare with office suite subscriptions?
Compare total cost over the period you plan to run the service, not the per-user line on each price list. Collabora's Business plan is listed at 3 euros per user per month for up to 99 users, including long term support and a service level agreement, and its Enterprise plan for 100 or more users is quoted with volume discounts. Nextcloud Enterprise list prices start at 71.29 euros per user per year for Standard at 100 or more users, with tiers for longer maintenance and 24/7 support. Add your own infrastructure, operations and partner costs, then compare the total with your current office suite and its admin tooling.
Which costs recur every year, and which are one-time?
Setup, integration, fidelity testing and initial hardening are usually one-time costs. Recurring costs include the editor subscription or support plan, server capacity, backups, monitoring, staff time for updates and the retainer for upgrades if you buy one. Subscription prices are published per user, so the recurring line grows with headcount, while server cost grows with peak concurrent editing. Ask any quote to state which items recur, the billing unit for each, and what changes when your user count crosses a published tier.
What should we ask for in a quote for document editing?
Ask for a written scope that names the editor, the edition, the file platform connections, the formats and templates to be tested, the number of environments and the backup and monitoring approach. Request the editor edition and support plan that matches your user count, the server sizing assumption for peak concurrent editors, and the exact acceptance criteria. DeployOpen plans, implements, integrates, hardens, backs up, upgrades, documents and supports self-hosted platforms in your own infrastructure, and most engagements are fixed-scope with scope and timelines agreed in writing before work starts. Ask also which items are one-time and which are retainers.
How DeployOpen scopes and supports a fixed-scope editing implementation
DeployOpen plans, implements, customizes, integrates, hardens, documents and supports self-hosted open-source platforms inside the client's own infrastructure. For document editing cost, that means agreeing in writing which editor, editions, servers, file platform integration and support terms are in scope before any work starts, so the cost comparison is based on a defined deployment.
How we scope
- Written scope lists the editor, edition, user count and file platform the quote is based on.
- Concurrent editing peaks, server count and hosting location are agreed before any sizing begins.
- Recurring subscription, support and retainer items are separated from one-time implementation work.
How we build
- Deployment runs in your cloud accounts, data centers or air-gapped networks, not a DeployOpen-hosted service.
- Integration with your file platform through WOPI or the vendor connector is configured and tested.
- Fidelity checks use your own templates and sample files so cost assumptions match real document work.
How we hand over
- Handover includes configuration documentation, sizing notes, update and backup procedures and a cost register.
- Evidence for access control, audit logging and update records is prepared for your assessors.
- Your team receives a record of which subscriptions are held directly with the vendor and which sit with DeployOpen.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- Support terms are defined in the written scope so renewal costs are visible in advance.
- Security testing of the editing deployment can be scoped alongside the implementation if your risk review requires it.
