ownCloud + Collabora Online
Two open source projects. One integration that’s been in production for over a decade. Collabora Online and ownCloud by Kiteworks have been shipping together since before « digital sovereignty » became a procurement checkbox.
The partnership covers oCIS (ownCloud Infinite Scale) and the classic ownCloud 10 stack. Both embed Collabora Online directly into the file interface, so users open, edit, and co-author documents without ever leaving their file manager. No redirects, no separate login, no awkward handoffs.
What that looks like in practice:
- Collaborative real-time editing of Writer documents, Calc spreadsheets, and Impress presentations
- Secure View mode for sensitive files where guests can read but not copy or download.
- Change tracking, comments, revision history.
- Full-screen presentation mode.
- Works in any modern browser, no plugins required.
The data never leaves your infrastructure. That’s not a marketing claim, it’s the architecture. ownCloud runs on-premises or in your own cloud. Collabora Online runs alongside it. Everything stays inside your perimeter.
- Germany
- File Sync and Sharing, Groupware and Productivity Tool, Hosting Provider
ownCloud & Collabora Online Success Stories
We decided to rely on Collabora at a very early stage. The fact that the solution was supported by ownCloud right from the start was a key factor in this decision, as it ensured smooth operation right from the start – and if there were any problems, we could always turn directly to the joint support team.
William van Santen - Product Manager, SURFnet
Seamlessly Integrated into ownCloud
The ecosystem context
ownCloud is now developed under the Kiteworks umbrella, with oCIS as the modern, Go-based, cloud-native successor to ownCloud 10. The Collabora integration carries forward into oCIS, so operators upgrading from OC10 aren’t starting from scratch on document editing.
For public sector deployments specifically (education, healthcare, federal agencies) the combination of ownCloud EFSS and Collabora Online covers the full collaborative content lifecycle under EU-jurisdiction infrastructure. That matters increasingly where sovereign cloud mandates.
Try the Collabora Online Demo
How to Install and Test CODE
Install Docker and Docker Compose Plugin
1. Install Docker
sudo apt update
sudo apt install docker.io
sudo apt install docker-compose-plugin
sudo systemctl enable docker
2. Allow User to edit docker without sudo
sudo usermod -aG docker $USER
3. Log out and back in
Quick-Setup using provided compose files
1. Extract the download to a directory
2. Edit the .env file
Set your local IP address.
Set your login credentials.
3. Run docker compose up -d
Make sure you are running compose from the created directory (where the compose file is saved)
4. Open ownCloud in your browser
http://<ipadress>:8080
Login with your credentials, set in step 2.
5. Install Collabora Online Integration App
Top left (Menu) > Market > Integration > Collabora Online > Install
6. Configure Collabora Online Integration
Top right (admin) > Settings > Additional > Set Collabora Online server to http://<ipaddress>:9980 > Save
7. Create a document and try CODE
You are now all setup and can try editing documents using CODE!
Setting up and configuring native CODE packages on Linux
Collabora provide native Linux packages in deb and rpm formats. For the deb format 3 platforms are supported: amd64, ppc64, and arm64. For the rpm format only amd64 is supported.
1. Import the signing key:
CODE packages are digitally signed by Collabora Productivity Ltd. First step is to import the signing key.
On deb based distributions use the following command:
mkdir -p /etc/apt/keyrings && cd /etc/apt/keyrings sudo wget -O collaboraonline-release-keyring.gpg https://collaboraoffice.com/downloads/gpg/collaboraonline-release-keyring.gpg
On rpm based distributions use the following command:
wget https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-rpm/repodata/repomd.xml.key && sudo rpm --import repomd.xml.key
2. Add CODE package repositories:
On deb based distributions create /etc/apt/sources.list.d/collaboraonline.sources with the following contents:
Types: deb URIs: https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-deb Suites: ./ Signed-By: /etc/apt/keyrings/collaboraonline-release-keyring.gpg
On rpm based distributions use the following commands:
RHEL, CentOS, Fedora, etc.:
sudo yum-config-manager --add-repo https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-rpm
SUSE:
sudo zypper ar 'https://www.collaboraoffice.com/repos/CollaboraOnline/CODE-rpm' 'CODE' sudo zypper mr -r 'CODE' # enable auto refresh
3. Install packages:
On deb based distributions use the following command:
sudo apt update && sudo apt install coolwsd code-brand
On RHEL, CentOS, Fedora, etc. use the following command:
sudo yum install coolwsd CODE-brand
On SUSE, use the following command:
sudo zypper ref && sudo zypper in coolwsd CODE-brand
This is the minimal installation, without localizations. For full installation install ‘collaboraoffice*’ packages.
4. Configuration:
Edit /etc/coolwsd/coolwsd.xml. Collabora Online (coolwsd) service runs via systemd. After editing the configuration file, you have to restart the service:
sudo systemctl restart coolwsd
Collabora Online logs into systemd journal by default. You can check the log with:
sudo journalctl -u coolwsd
The default configuration is looking for an SSL certificate and key, which are not present, so probably it’s the best to disable SSL, and optionally enable SSL termination, then set up the reverse proxy.
It is highly recommended to set up a reverse proxy in front of CODE, either you run CODE from Docker, or you use native packages. It is easy, and this way CODE can be reached on standard HTTP or HTTPS ports. We provide sample configuration files for Apache2 and Nginx. If you want SSL, we recommend certificates from Let’s Encrypt.
Now you can give https://collabora.example.com as the WOPI URL in your preferred File Sync and Share solution. See below for specific examples.
For more detailed and pretty instructions on integrating with various partner solutions please see (in alphabetical order):
- Nextcloud Setup Instructions (Apache & Nginx)
- ownCloud