Collabora Online (CODE)
Community office editing server for integration with a document platform.
- AWS
- DigitalOcean
- Hetzner
- Linode
- Vultr
- Hostinger
- LumaDock
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Cloudron package
Runs in
Documented customer environment
Collabora Online Development Edition server and a separate WOPI-compatible file platform.
- AWS: Customer cloud account
- DigitalOcean: Customer cloud account
- Linode: Customer cloud account
- Vultr: Customer cloud account
- Hetzner: Customer cloud account
- Hostinger: Customer VPS account
- LumaDock: Customer VPS account
- AWS
- DigitalOcean
- Hetzner
- Linode
- Vultr
- Hostinger
- LumaDock
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Linode: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Cloudron Store ↗ · Source checked 2026-11-19
- Hetzner: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Hetzner Tutorial ↗ · Source checked 2026-11-19
- Hostinger: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Cloudron Store ↗ · Source checked 2026-11-19
- LumaDock: Customer VPS account · Customer-operated
An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.
Cloudron Store ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Cloudron package |
|---|---|
| Infrastructure | Servers / containers Collabora Online Development Edition server and a separate WOPI-compatible file platform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The reviewed CODE material describes an embedded editing service and integrations, but does not establish standalone corporate SAML/OIDC user login in the listed development edition. Confirm the identity-providing document host, connector and edition instead of assigning its SSO to the editing engine.
CODE engine identity versus external document-platform authentication · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Collabora publishes the collabora/code container image for the CODE development/small-team edition, which the vendor does not recommend for production. Pin a suitable image and configure a document host/connector. Active source development moved to Gerrit; the retained GitHub build/chart artifacts do not make a nightly or commercial build equivalent to CODE.
Listed CODE development edition; not Collabora Online commercial production support · Source ↗ · Deployment artifact ↗ (Select a supported version-tagged CODE image; distinguish nightly and commercial builds) · Upstream source/build repository locations ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Cloudron package declares 1024MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing.
Selected Cloudron application package; add database, files, backups and concurrent workload requirements · Source ↗ · Cloudron platform requirements ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Collabora Online (CODE); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package.
Community & maintenance
The reviewed upstream contributor history includes Ashod, eszkadev, timar, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.
Category fit
- Collaboration
- Community office editing server for integration with a document platform.
Compare within Collaboration
- 3CX Self-HostedCommercial business communications and PBX platform installed into the customer's public-cloud account.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Apache AnswerSelf-hosted community questions, answers and knowledge content.
- AWS
- DigitalOcean
- Railway
- Linode
- Vultr
- Hostinger
- LumaDock
- BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Hetzner
- Scaleway
- BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
- AWS
- DigitalOcean
- Linode
- Vultr
- Hostinger
- LumaDock
- Campfire (ONCE)Self-hosted group chat and team conversation application.
- DigitalOcean
- Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
- AWS
- Azure
- Google Cloud
- DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
- AWS
- Google Cloud
- DigitalOcean
- Hetzner
- Linode
- Vultr
- Docmost Self-HostedSelf-hosted collaborative wiki and documentation with real-time editing, spaces and page history.
- Railway
Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Cloudron Store ↗www.cloudron.io
- Hetzner Tutorial ↗community.hetzner.com
- MPL-2.0 COPYING ↗github.com
- Releases 2026 ↗github.com
- Cloudron customer-server and named-provider installation ↗docs.cloudron.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
- Hetzner Tutorial ↗ · Hetzner
Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Collabora Online Development Edition server and a separate WOPI-compatible file platform. CODE is the development/community edition, separate from commercially supported Collabora Online. Helm chart versions and CODE application versions are separate; production support must not be inferred from a working package. This source is distinct from the Cloudron package.
- Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗github.com
- Upstream project ↗github.com