When can CODE run in production, and when do you need Collabora Online?
CODE can serve testing, home use or a small team, but Collabora does not recommend it for production. If your online office will hold live business documents, sit behind a file platform that many people depend on, or have to meet patch and update obligations, plan for the supported Collabora Online build. CODE is the Collabora Online Development Edition, a rolling release that Collabora says is released on average once a month, with community forum support. Collabora positions the paid build as the official supported stable version with tested updates, security fixes and improvements.
CODE does give you something the supported build does not: earlier access to Collabora's latest feature work. That matters if you want to test a new capability against your own documents or your file platform before it reaches stable users. Use CODE in a staging copy of your stack, not as the editor for production files, and keep a record of which build you tested so you can reproduce a problem. Ask Collabora which build line the paid edition follows and how fixes reach it, so your staging results map onto what you would actually run.
Move to Collabora Online when the deployment carries production data or when someone in your organization owns patching and vulnerability response. The Business plan, listed on the pricing page at 3 euros per user per month on premises for up to 99 users, includes long-term support, a service level agreement, signed security updates and customer portal access. Confirm current terms, the SLA response commitments and the Enterprise volume quote for 100 or more users directly with Collabora before you budget, because a pricing page can change. Also confirm whether your file platform's integration is covered, since Enterprise adds integration support and customization services.
Which capabilities differ between CODE and Collabora Online
This table compares the free CODE rolling release with the paid Collabora Online build across the capabilities that matter for production decisions. Where Collabora's published material does not state a feature for CODE, the cell tells you to confirm it with Collabora before you rely on it.
| Capability | CODE (Collabora Online Development Edition) | Collabora Online (Business or Enterprise) |
|---|---|---|
| Release model | Continuously updated rolling release where Collabora tries out its latest feature work | Official supported stable version with tested updates, security fixes and improvements |
| Intended use | Testing, home use or small teams; Collabora does not recommend it for production | Production use, with the supported build as the vendor's stated target for business deployments |
| Update cadence | Builds released on average once a month | Tested updates on a supported stable line; confirm the exact cadence and branch policy with Collabora |
| Security fixes | Community forum support; confirm with Collabora how and when security fixes reach CODE | Security fixes included in the subscription |
| Support channel | Community forum support | Vendor support as part of the paid subscription; confirm the channels and hours in your contract |
| Long-term support | Not stated for CODE; confirm with Collabora | Included in Business and Enterprise subscriptions |
| Service level agreement | Not stated for CODE; confirm with Collabora | Included in Business and Enterprise subscriptions; ask for the written terms |
| Signed security updates | Not stated for CODE; confirm with Collabora | Included in Business and Enterprise subscriptions |
| Customer portal access | Not stated for CODE; confirm with Collabora | Included in Business and Enterprise subscriptions |
| Accessibility certification | Not stated for CODE; confirm with Collabora | Included in Business and Enterprise subscriptions |
| Integration support and customization | Not stated for CODE; confirm with Collabora | Integration support and customization services are included in Enterprise only |
| Roadmap input | Not stated for CODE; confirm with Collabora | Included in Enterprise, per the vendor's pricing page |
How licensing and support terms differ by edition
The server code is the same MPL-2.0 base in every edition, so the difference lies in what Collabora commits to in writing: update cadence, security fixes, support and roadmap influence. Read each card as a question to answer before you pick a build for a production office service.
Same MPL-2.0 source base
The Collabora Online server code is licensed under the Mozilla Public License 2.0, and the COPYING file in the repository is the reference for that license. Because the source base is shared, the choice between CODE and the paid build is not a licensing choice. Confirm with Collabora which of its builds your organization may run under the MPL-2.0 terms and whether any proprietary components differ between them.
What the free edition includes
CODE is a continuously updated rolling release, released on average once a month, with earlier access to Collabora's latest feature work. Collabora positions it for testing, home use or small teams, and support comes through the community forum. Treat it as a build you can evaluate and pilot, not a build that carries a support contract or a fixed update commitment.
What Business adds
The Business plan is priced per user per month on premises for up to 99 users and includes long-term support, a service level agreement, signed security updates, lifetime maintenance, customer portal access and accessibility certification. Ask Collabora for the length of the support window, the response times in the SLA, and how it notifies customers when a security fix ships.
What Enterprise adds
Enterprise is quoted for 100 or more users with volume discounts and adds integration support, customization services, mobile support and roadmap input. Its value depends on whether you need Collabora engineers to help with your WOPI integration or custom work. Ask for the scope of integration support in writing and whether roadmap input is a commitment or a channel for requests.
Terms to confirm in writing
Ask Collabora for the update windows covered by each supported branch, how long point releases continue after a new major version, and the response targets for security and production incidents. The 25.04 branch was still receiving point releases in 2026, which shows how support can extend beyond the first release. Get these answers in the contract, not from a web page, before you plan upgrades.
Which team profile fits CODE, Business or Enterprise
CODE suits personal use, evaluation and test environments where an outage costs little and the team is comfortable tracking upstream changes. Collabora describes it as a continuously updated rolling release, so you receive new feature work earlier than the supported version, and builds arrive on average about once a month. Support comes from the community forum rather than a contract.
- Update rhythm: Expect frequent builds. You apply them yourself and test them against your own documents.
- Security fixes: Collabora does not position CODE as the vehicle for signed security updates, so treat patching as your own job.
- Support path: Community forum support only, with no service level agreement.
- Packaging: Docker image, Linux package or virtual appliance, depending on your lab setup.
Before you rely on a test instance for anything more, confirm with Collabora which build you would deploy, how long each build is maintained, and whether the lab setup matches how you would run production.
A small team that wants editing to work for real business documents has to decide whether a free build is enough. Collabora describes CODE as suited to small teams for testing and home use, but not recommended for production. Once documents carry commercial or client obligations, the supported build matters more than the license price, because it adds tested updates and security fixes.
- Pricing entry point: Collabora's pricing page lists a free edition for home, testing and start-ups, and Business at 3 euros per user per month on premises for up to 99 users.
- Business inclusions: Long-term support, a service level agreement, signed security updates, lifetime maintenance and customer portal access.
- Patch ownership: With Business, you apply the supported updates, but the vendor's tested stream reduces the risk of breaking your editing workflow.
- Cost driver: Per-user pricing scales with headcount, so count the people who will open documents, not the people with accounts.
Before committing, ask Collabora to confirm the current Business terms in writing, including what counts as a user and how renewals are priced.
For production use with fewer than 100 users, Business is the published fit. It is priced per user on premises and includes the support, signed security updates and long-term support that a production document workflow needs. Your job is to match the release line to a support window you can actually plan around, and to test upgrades before they reach users.
- Release line: Choose the supported stable version and keep your update schedule aligned with its tested releases, not with the rolling CODE builds.
- Support model: Business includes a service level agreement; read its response terms and who you contact in the customer portal.
- Upgrade testing: Stage each update against a copy of your document set, including templates and macros your staff depend on.
- Integration check: Confirm the WOPI connection with your file platform, such as Nextcloud or ownCloud, works after each update.
Before go-live, confirm the exact Business terms, the support windows for the release you plan to run, and how security notices reach your team.
At 100 or more users, Collabora's published pricing moves to Enterprise, which is quoted with personalized volume discounts rather than a listed per-user rate. Enterprise keeps the Business support, update and long-term support terms and adds integration support, customization services and roadmap input. Those extras matter most when your deployment has to fit a larger architecture, such as multiple servers or Kubernetes.
- Quote basis: Ask for a written quote built on your user count, deployment model and required services.
- Added services: Integration support, customization and roadmap input are Enterprise items, so decide which of them you need before you negotiate.
- Architecture effort: Multi-pod deployments need session affinity, and the Helm chart disables autoscaling, so plan capacity by hand.
- Ownership: Name who receives security notices, who approves upgrades and who responds to incidents.
Before go-live, confirm the Enterprise scope in writing, test failover and upgrades on a staging cluster, and verify that your load balancer routes all users editing one document to the same pod.
What each edition costs and what drives the total
This table separates the one-time and recurring costs of running the free CODE build, the paid Business plan and the quoted Enterprise plan. Read the rows as a checklist: the subscription line is only one part of the total, and internal testing, patching and upgrade effort applies to every option.
| Cost component | CODE (free) | Business (paid, on premises) | Enterprise (quoted) |
|---|---|---|---|
| Subscription fee | None. Collabora describes CODE as free. | 3 euros per user per month on premises for up to 99 users, per the Collabora pricing page. | Quoted for 100 or more users with personalised volume discounts, per the Collabora pricing page. No published figure. |
| Who is paid | Nobody to Collabora. Your staff or partner carries testing, patching and upgrades. | Collabora, through the subscription. | Collabora, through a negotiated contract tied to your user count and requested services. |
| One-time deployment and integration work | Installation, WOPI connection to your file platform, and testing in your own environment. | Same technical setup work, plus onboarding into the supported release line. | Same setup work, plus any integration support or customization you contract for. |
| Recurring subscription | None. | Per-user fee, recurring for as long as you hold the subscription. | Recurring contract fee, with terms set in your written agreement. |
| Recurring internal operations effort | High relative to the license cost: you own rolling-release testing, regression checks and rollback. | Lower: tested updates, security fixes and long-term support reduce your validation burden. | Lower again if you use the requested support and roadmap input, but still requires your internal ownership. |
| Main cost drivers | Size of your test program, release frequency and your patch windows. | Number of named users, up to the 99-user Business tier. | Negotiated user count, support scope and customization work. |
| What to ask for in a quote | Not applicable. Ask your partner to scope testing and upgrade effort in writing. | Confirm the user count, on-premises terms and what support is included. | Request a written quote covering users, SLA terms, integration support, customization and mobile support. |
Moving from CODE to Collabora Online, and back
This sequence moves a file platform's office connector from the free CODE build to the supported Collabora Online build, with validation before CODE is removed. It also explains why the reverse move is rarely a good production choice.
Inventory the current CODE deployment
Your platform or infrastructure team records how CODE is running today: the image tag or Linux package version, the deployment method (virtual appliance, Docker image or Linux package), the host or pod it runs on, the WOPI URL that your file platform calls, and any custom configuration such as TLS certificates, allowed hosts and resource limits. Store this record with your change ticket. The step is done when someone other than the original installer could rebuild the current setup from the record alone.
Confirm the target version and deployment method
Decide which supported Collabora Online release and which deployment method you will use, based on your existing platform and team skills. Collabora describes the paid edition as the official supported stable version with tested updates and security fixes, and it can be deployed from Docker images, system packages or Kubernetes. Check the Collabora Online pricing and product pages for the edition that matches your user count and support needs, and confirm the exact release and supported platforms with Collabora before you commit. The step is done when the version, method and licence edition are written into the change plan and approved.
Build a test instance with the same WOPI setup
Install the supported Collabora Online build on a separate host or cluster that is not serving users. Configure it to accept the same WOPI integration your file platform uses, including the allowed host and the URL pattern, so that the only difference from production is the build. Your platform team checks that the test instance loads the office editors for a test account. The step is done when a test document opens for editing from the file platform against the new instance.
Point the file platform at the supported endpoint
Change the office connector setting in your file platform so that it calls the supported Collabora Online endpoint instead of the CODE endpoint. For Nextcloud, this is set through the Nextcloud Office configuration in the admin manual. Schedule the change in a maintenance window agreed with the users who edit documents, because open sessions will reconnect. The step is done when the connector setting shows the new endpoint and a new editing session is served by the supported build.
Validate documents and collaborative editing
Test with a representative set of your own documents in the formats your organisation uses, including Microsoft Office and OpenDocument files. Have at least two test users edit the same document at the same time, check that changes merge correctly, and check copy, paste, comments, saving and export. If you run several Collabora Online instances behind a load balancer, confirm that all users editing one document reach the same instance. The step is done when the test plan has a recorded pass for each case, and any failure has a documented fix or a decision to hold the cutover.
Cut over and monitor the supported instance
Move production users to the supported instance and keep the CODE instance running but idle for a rollback window agreed in advance. Watch error logs, session failures and user reports during the first working days, and record any issues against the test results. Rollback means pointing the connector back at CODE, so keep the previous configuration saved. The step is done when the agreed monitoring period passes without open editing failures.
Decommission CODE and update records
Once the rollback window closes, stop the CODE service, remove its image or package, delete any DNS entries, certificates and firewall rules that only it used, and update your configuration inventory and patching schedule so the supported build is tracked. Keep the inventory record from the first step as the audit trail of the change. The step is done when no production traffic reaches CODE and the inventory lists only the supported build.
Treat any move back to CODE as an exception
Moving from the supported build back to CODE reverses the protections the paid edition provides, because CODE is described by Collabora as not recommended for production and is a rolling release. If you still need it, for example for a test or home instance, run it outside production, confirm the current guidance with Collabora, and document who accepts the risk. Expect the reverse change to follow the same configuration and image replacement steps as the forward move, with the same validation. The step is done when the decision is recorded and the production environment is confirmed to run only the supported build.
How deployment size changes the operating burden
The operating burden of Collabora Online depends on how you deploy it, not on which edition you license. CODE and the paid Collabora Online build run the same server code, so the sizing, replica and session decisions below apply whichever edition you choose. A team running one server or container beside its file platform carries a light load. A team running several pods on Kubernetes carries a heavier one, and that work does not shrink because the free build is in use. Budget for it before you compare license costs.
The official Helm chart makes the central constraint explicit. Horizontal pod autoscaling is disabled because scaling breaks collaborative editing and copy and paste, so you set the replica count by hand in your values file and change it through a planned change window. Your ingress or load balancer must also route by the WOPISrc parameter so that every user editing the same document reaches the same pod. Test this with two browsers on one document before go-live, and confirm that your chosen ingress (the chart supports Nginx, HAProxy and the OpenShift Router) keeps that affinity under failover and during rolling updates.
For capacity planning, the chart recommends production limits of 8 CPU cores and 8000 MiB of memory per pod, with requests of 4 cores and 6000 MiB. Those figures come from the chart's README, so ask your own platform team to confirm they fit your node sizes and your concurrent editing load. Sizing work, affinity testing and ongoing replica management recur with every upgrade and every change in user numbers, so ask any implementation partner to price them as ongoing operations, not as a one-time install.
Questions buyers ask before choosing CODE or a paid build
Can we run CODE in production?
Collabora describes CODE as the development edition, suited to testing, home use or small teams, and not recommended for production. It is a continuously updated rolling release with builds released on average once a month, so each update carries new feature work that has not been positioned as a stable line. If your users depend on the editor for daily document work, plan for the supported Collabora Online build. Before you decide, confirm with Collabora how CODE updates would be tested against your file platform and whether your internal change process can absorb a monthly rolling change.
What does Business cost per user, and when does Enterprise apply?
The Collabora Online pricing page lists Business at 3 euros per user per month on premises for up to 99 users. Enterprise applies to deployments of 100 or more users and is quoted with personalised volume discounts, so there is no published list price at that tier. Business is a recurring subscription, so the cost grows with the user count and continues for as long as you run the service. Ask for the subscription term, how users are counted, and whether a quote covers the server footprint or only the seats.
Does the paid build include signed security updates and an SLA?
Yes, according to the Collabora Online pricing page, both Business and Enterprise subscriptions include a service level agreement and signed security updates, along with long-term support, lifetime maintenance and customer portal access. Enterprise adds integration support, customization services and mobile support. The page does not publish the SLA terms, response times or support hours in the material available to us, so request the written SLA, the severity definitions and the support window before signing. Confirm also which versions receive security fixes and for how long.
How much internal effort does each option need?
Effort depends on how many people run the editor and how often you update it. With CODE, your team owns testing each monthly build against your file platform, because the project does not position it as a tested production release. With the paid build, updates are tested by Collabora before release, but you still plan rollouts, maintain the host and monitor the service. For larger installations, the Collabora Online Helm chart says horizontal autoscaling is disabled, replicas are set manually, and the load balancer must route by the WOPISrc parameter, which adds operational work regardless of edition.
Can we switch from CODE later without rebuilding our file platform integration?
The integration is built on the WOPI protocol, which Collabora says connects Collabora Online to file sync and share platforms, so the integration point is the same across the free and paid builds. The practical question is whether your deployment configuration, hostnames, certificates and load balancer rules carry over unchanged. Test the switch in a staging environment with your own file platform, including the WOPI discovery and session routing behavior, before you move users. Ask Collabora whether the paid build can be installed over the same configuration, and what changes if you move from Docker images to system packages or Kubernetes.
What should we ask Collabora or a partner in a quote?
Ask for a written scope that lists the edition, the user count and whether it is Business or Enterprise, along with the subscription term and renewal conditions. Request the SLA document, the security update policy and the support window. Ask which deployment method is included, such as Docker, system packages or Kubernetes, and what the hosting footprint is for your expected load. If you use a partner for installation, testing, upgrades or integration with your file platform, ask for the deliverables, acceptance criteria, what is one-time and what recurs, and who is responsible for upgrades after go-live. DeployOpen issues quotes only from a written scope.
What scoping a CODE or Collabora Online deployment involves
Scope and deliverables are agreed in writing before any work starts, whichever edition you choose. For a CODE or Collabora Online deployment, that scope usually names the file platform the editor will serve (Nextcloud, ownCloud, Seafile or another WOPI host), the deployment method (Docker image, Linux package or Kubernetes), the users and document volumes expected, and the ingress layer that will route requests. DeployOpen plans and implements inside your own cloud accounts, data centers or air-gapped networks, so the scope also records where the editor runs, who holds the administrative credentials and how the editor is reached from the file platform. Ask for these items to appear in the written scope so that the two editions can be compared on the same footing.
Integration and hardening are where the edition choice shows up in practice. Under either edition, the WOPI connection between the file platform and the editor needs its URLs, certificates and allowed hosts set correctly, and the scope should list the test cases that prove documents open, save and co-edit as expected. Hardening covers the host, container or cluster configuration and the network paths between components. Backup and upgrade planning should state how the editor is versioned and patched. If you select the CODE rolling release, the scope needs a written plan for how frequent builds are tested before they reach users, because Collabora describes CODE as not recommended for production. Confirm with Collabora which update channel and support terms apply to your chosen edition before you sign.
DeployOpen does not publish a price list, and a quote follows from the written scope. The cost drivers are the number of components to deploy and integrate, the number of file platform and identity integrations, the hardening and test effort, the backup and upgrade plan, and the documentation handed over. Ongoing support, upgrades and continuous testing are offered as retainers. Ask any provider for a quote that separates one-time implementation work from recurring items, and that states which vendor licenses or subscriptions the client pays for directly. Collabora's per-user subscription terms are set by Collabora, not by DeployOpen.
How DeployOpen scopes and supports either edition
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure, so the choice between CODE and a supported Collabora Online build is handled as part of the written scope. We work with the edition you pick, whether that is a development build for testing or a supported stable release for production.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope states which Collabora Online edition is in use and why it fits the intended production use.
- We confirm the file platform it integrates with, such as Nextcloud or another WOPI-capable host, and the users and documents involved.
- Quotes follow from the written scope, so ask for each cost component to be itemized in the proposal.
How we build
- We deploy Collabora Online in your own cloud account, data center or air-gapped network, using the packaging method your team chooses.
- Where several replicas are needed, we configure load balancing so all sessions for one document reach the same pod.
- We test document editing, copy and paste and failover against your own sample files before go-live.
- Hardening and configuration are documented so your team can review the settings and reproduce them.
How we hand over
- You receive documentation of the deployed architecture, configuration, integration points and upgrade steps.
- Runbooks cover how to apply point releases and how to move between CODE and a supported build if requirements change.
- Evidence and controls are prepared for your compliance assessment, which independent auditors or certification bodies then review.
- Knowledge transfer sessions are scheduled as part of the agreed scope so operating staff can run the platform.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- Retainer scope, response expectations and upgrade cadence are written down and confirmed before the retainer starts.
- Your support terms from Collabora, such as any service level agreement, are confirmed separately with the vendor, since DeployOpen is not a Collabora partner.
- Upgrades to new Collabora Online releases are tested in a non-production environment before they reach your users.
