Questions about upgrading from free Collabora CODE to paid and supported integrations

Hi Collabora Support,

I had a couple of questions regarding moving from the free version (Collabora CODE) to the paid version:

  1. If we already have the free version running via Docker, what does the upgrade process to the paid version look like? Is it a straightforward switch (e.g., license/config change), or does it require a fresh setup?

  2. Can the paid version integrate with services other than Nextcloud? In your demos, it often appears bundled—so I wanted to confirm whether Collabora can be integrated independently with custom platforms (via WOPI or other methods), or if it typically comes as part of a package.

Would appreciate any guidance or documentation you can share.

Thanks!

The switch is mostly straightforward, your configuration and deployment can stay the same.

Collabora Online supports many integrations (Integrations - Collabora Online and Collabora Office), and you can create your own https://sdk.collaboraonline.com/docs/introduction.html or reuse existing opensource ones: Making sure you're not a bot!

Thank you for the above answers!
Also, wanted to understand -
1)Does Collabora provide a trial/evaluation Docker image for the paid Collabora Online version separately (without Nextcloud)?
2)If a trial is available, what would be the recommended way to obtain and deploy it for evaluation purposes?

We do provide a different build available (CODE) that is tracking our supported version (COOL).

That is essential the same version as provided by Nextcloud Office with a different theme though.

Thank you for this!
Just to reconfirm my understanding, CODE and COOL are largely the same underlying product, and the primary differences are around enterprise support,scalability/commercial support rather than a fundamentally different architecture or implementation.

Is that understanding correct?

hi Kartika

Yes, that’s broadly correct. CODE (Collabora Online Development Edition) and the Collabora Online are built from the same codebase. The core architecture and implementation are the same. it’s not a fundamentally different product under the hood.