Our take
Activeregular commits and releases- Activity
- 57
- Community
- 83
- Issues
- 47
- Pull requests
- 70
+1 stars in the last 30 days
This is an actively maintained, focused integration with recent commits and releases, though teams should account for its separate on-premises server requirement and documented locking issue.
Good fit if
- You operate Nextcloud and can also deploy Office Online Server with WOPI trust configured.
- You want an integration app rather than a standalone office suite, and can use the branch matching your Nextcloud version.
- You value an active project with many contributors and recent releases under the AGPL-3.0 license.
Look elsewhere if
- You need Microsoft’s cloud-based Office 365, which this integration does not support.
- You cannot operate an on-premises Office Online Server.
- Your browser and document-locking workflow cannot tolerate the reported Chrome and Chromium-based browser issue.
All health signals
| Last commit | 2026-10-05 (8 days ago) |
|---|---|
| Commits, last 90 days | 50 |
| Releases, last 12 months | 4 (latest v3.3.0, 2026-09-28) |
| Contributors | 77 (top contributor: 23% of commits) |
| Issues closed, last 90 days | 1 |
| Pull requests merged, last 90 days | 29 (typically merged in 0 days) |
| Project age | 6 years |
Checked on 2026-10-14 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
65Forks
15Change since Nov 10, 2026: 0 stars·+1 forks
Overview
The Nextcloud Office Online integration connects a Nextcloud server to an on-premises Office Online Server, allowing users to work with documents through that server. It addresses the need to pair Nextcloud file storage with Office Online document editing.
This is an integration app, not an Office Online server. It requires Office Online Server to be deployed separately and configured to trust the Nextcloud server for WOPI.
Key Features
- Integrates Nextcloud with an on-premises Office Online Server.
- Uses WOPI for communication between the Nextcloud and Office Online servers.
- Supports a main branch for Nextcloud 24 and later, and a
stable1branch for Nextcloud 22–23. - Includes JavaScript frontend code with npm-based development commands.
- Documents a browser-related file-locking issue and possible workarounds.
Use Cases
- Nextcloud administrators who already run Office Online Server and want document editing integrated with their file service.
- Organizations that need to keep Office Online Server on premises rather than use Microsoft’s cloud-based Office 365.
- Nextcloud developers who need to build or maintain the integration’s frontend code.
- Teams upgrading Nextcloud who need to choose the integration branch compatible with their server version.
What you need
Detected in the repository
- Node.js ^24.0.0 (from package.json)
- PHP (from composer.json)
- A test suite and automated checks on GitHub Actions
License in plain words
AGPL-3.0network copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
For development, clone the repository into a Nextcloud app directory, then run:
npm ci
npm run dev
This requires a Nextcloud server checkout and Node.js. For server installation and setup details, see the README.
Alternatives
- cryptpad: CryptPad is a standalone, end-to-end encrypted collaboration suite, rather than a Nextcloud app that connects files to an on-premises Office Online Server.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| officeonline | JavaScript | AGPL-3.0 | 64 | Active |
| cryptpad | JavaScript | AGPL-3.0 | 8k | Active |
Considerations
- The app depends on an independently deployed on-premises Office Online Server configured to trust Nextcloud for WOPI. It does not support cloud-based Office 365.
- The README reports that Chrome and Chromium-based browsers may fail to trigger user removal or document unlocking. It points to file-lock timeout configuration or manual unlocking as workarounds.
- The project is active, with regular commits and releases and contributions from many people. However, only one issue was closed in the measured recent period, so teams should assess whether its issue handling meets their support needs.
- The repository is licensed under AGPL-3.0. Review the license obligations before adopting or modifying it.
Found this useful?
Share it with someone who would like officeonline.