
# Collaboration on DigitalOcean

Compare documented Collaboration deployments on DigitalOcean, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/digitalocean/collaboration/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: DigitalOcean team/account and project
- Provider group: cloud-infrastructure
- Provider classification: Droplets and managed Kubernetes use the customer infrastructure account. App Platform is a separate platform-workspace path and is identified per listing. Source: https://docs.digitalocean.com/products/droplets/how-to/create/ (checked 2026-11-20).
- Network: VPC and Cloud Firewalls; review public endpoints
- Identity and access: Team roles, scoped API tokens and SSH keys
- Installation guidance: Provision Droplets or Kubernetes in your account; review the application image, storage, updates and firewall rules.
- Guidance source: https://docs.digitalocean.com/products/droplets/how-to/create/
- Guidance reviewed: 2026-11-12


### Private networking

DigitalOcean VPCs isolate resource traffic from the public internet; VPC peering can connect VPCs. Confirm the selected service can join the intended VPC and configure application access controls.
Source: https://docs.digitalocean.com/products/networking/vpc/ (reviewed 2026-11-14).

The listings below have evidence for DigitalOcean. Read each cloud evidence note for the applicable package, edition and support qualifications.

14 listings.


## 3CX Self-Hosted

Commercial business communications and PBX platform installed into the customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/3cx-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary annual 3CX system license; edition and simultaneous-call entitlements vary.
- Licensing model: commercial-only
- Installation: 3CX deployment wizard or provider Marketplace path for AWS, Azure, Google Cloud or DigitalOcean
- Architecture: Customer-operated PBX/application VM with web client, SIP/RTP media, certificates, firewall rules and external trunk or carrier dependencies.
- Operations: Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.
- Product website: https://www.3cx.com/
- Source review: 2026-11-19; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry excludes the Hosted by 3CX service. External SIP trunks, carriers, calling charges and endpoint hardware remain separate. Review provider sizing and media-network requirements before deployment. The AWS AMI is vendor-published package 20.0.10.1785 on Debian 12, with its 3CX licence billed outside AWS Marketplace. 3CX's November 2026 security-hotfix log updates V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest update through the Admin Console, restart as directed and verify the deployed package set; do not treat the application build number alone as proof that OS hotfixes are current.

3CX is proprietary commercial software licensed by edition and capacity; cloud hosting and telecom services are separate.

3CX runs as a persistent PBX and communications application on a customer-managed cloud VM.


### Category fit

- collaboration: Provides business voice, video, chat, web meetings and PBX collaboration in a customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-aws/ (checked 2026-11-18). Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-google-cloud/ (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/manual/install/ (checked 2026-11-18). 


### Cloud deployment evidence

- 3CX in the customer's AWS account (aws): https://www.3cx.com/docs/hosted-pbx-aws/
  3CX documents provisioning the PBX in a customer AWS account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's Azure account (azure): https://www.3cx.com/docs/hosted-pbx-azure/
  3CX documents provisioning the PBX in a customer Azure account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's Google Cloud account (gcp): https://www.3cx.com/docs/hosted-pbx-google-cloud/
  3CX documents provisioning the PBX in a customer Google Cloud account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's DigitalOcean account (digitalocean): https://www.3cx.com/docs/manual/install/
  The current private-cloud install guide identifies DigitalOcean as a supported customer-account deployment target.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX-published AWS self-hosted AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm
  The vendor publishes the full PBX as a Debian 12 x86 AMI in the customer AWS account. Software licensing is external to AWS Marketplace; telecom and infrastructure charges are separate.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Versions: 20.0.10.1785.


### Sources

- Install 3CX in a private cloud: https://www.3cx.com/docs/manual/install/

- Deploy 3CX on AWS: https://www.3cx.com/docs/hosted-pbx-aws/

- Deploy 3CX on Azure: https://www.3cx.com/docs/hosted-pbx-azure/

- Deploy 3CX on Google Cloud: https://www.3cx.com/docs/hosted-pbx-google-cloud/

- 3CX pricing: https://www.3cx.com/ordering/pricing/

- Exact vendor AWS AMI and external licence billing: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm

- 3CX PBX security updates change log: https://www.3cx.com/blog/change-log/pbx-security-updates/

### Licensing sources

- https://www.3cx.com/ordering/pricing/

### Infrastructure sources

- https://www.3cx.com/docs/manual/install/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. 3CX publishes prodview-f5qwwdeeq4uvm as an x86 AWS AMI, package 20.0.10.1785 on Debian 12. Its pricing explicitly requires an external 3CX billing/licence relationship; the software licence is purchased outside AWS Marketplace. AWS infrastructure charges remain separate. This is the customer-operated PBX, not Hosted by 3CX. Scope: 3CX AWS self-hosted AMI 20.0.10.1785, externally licensed. Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (reviewed 2026-11-18). Supporting source: Vendor AWS Marketplace installation guide — https://www.3cx.com/docs/pbx-amazon-aws-marketplace/. Offer prodview-f5qwwdeeq4uvm: 3CX; Amazon Machine Image (AMI), x86; package 20.0.10.1785; https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed 3CX AMI offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms. Scope: Externally billed software licence for the exact reviewed public 3CX AMI offer; not all provider spend or future private offers. Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (reviewed 2026-11-18). Supporting source: AWS BYOL pricing boundary — https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html. Supporting source: Commitment qualification remains product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Edition-dependent. The Microsoft 365 integration documents SSO to the 3CX web client and one-way scheduled user synchronization. It requires a supported Microsoft 365 Exchange plan and configured application permissions. This does not establish SCIM or every client’s login behavior. Deleted/disabled M365 users remain in 3CX until manually removed; SSO is not a substitute for offboarding. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/microsoft-365/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The M365 guide documents nightly one-way sync, not a SCIM endpoint. A user deleted or disabled in M365 remains in 3CX and must be removed manually; deleting only in 3CX causes recreation at the next sync while the M365 account remains. This confirms a manual offboarding requirement, but does not establish SCIM operations or active-session/extension revocation through a SCIM integration. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/microsoft-365/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. 3CX describes security reviews with Mandiant, ReversingLabs, Coverity and HackerOne. This establishes a vendor security-testing statement, not a current independent attestation whose scope covers the buyer’s PBX, recordings, carrier/transcription services and operations. Obtain the relevant report, audit period, findings/remediation and deployment boundary. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/pbx/security/ (reviewed 2026-11-18).

- Security controls: Documented. The firewall guide specifies SIP/RTP, tunnel and HTTPS connectivity and requires uninspected outbound HTTPS for activation. Configure the required ports and TLS/FQDN correctly; external SIP trunks, push and meeting services create separate dependencies. M365 sync does not remove users deleted/disabled at the IdP; explicitly remove them in 3CX and review sessions, SIP/extension credentials and retained data. Current review: The November 2026 V20 SP9/SP10 security-hotfix log refreshes Linux packages including nginx, kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest Admin Console update and verify the installed package set. Scope: Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing. Source: https://www.3cx.com/blog/change-log/pbx-security-updates/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://www.3cx.com/docs/manual/firewall-router-configuration/. Supporting source: Microsoft 365 SSO configuration — https://www.3cx.com/docs/manual/microsoft-365/.

- Air-gapped operation: Explicitly unsupported. The standard documented self-hosted configuration requires outbound HTTPS to activate.3cx.com for licence activation and other external services for updates and selected functions. It is not a fully disconnected deployment path; a separate offline exception was not established. Scope: 3CX standard documented self-hosted activation and operation. Source: https://www.3cx.com/docs/manual/firewall-router-configuration/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The current installation guide provisions a private-cloud PBX in the customer’s chosen AWS, Azure, Google Cloud or DigitalOcean account. This is a vendor deployment workflow, not a reviewed source-controlled Terraform or CloudFormation artifact. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/install/ (reviewed 2026-11-18).

- Minimum footprint / sizing: Documented. The current small PBX table lists 2 vCPU/4 GB RAM and 80 GB SSD, with larger tiers and extra recording/log capacity. Its cloud table places up to 250 extensions in the large tier, with AWS t3.xlarge as an example. These are extension/call-capacity guidelines; HA, simultaneous calls and a 1 TB recording policy still need a design. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/ (reviewed 2026-11-18).

- License pricing: Documented. 3CX publishes annual system licences by edition and simultaneous-call capacity, with extension limits and feature differences. Obtain the selected self-hosted tier; a count of internal users alone does not price licences, trunks or calling charges. The reviewed AWS offer bills its software licence outside AWS Marketplace. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/ordering/pricing/ (reviewed 2026-11-18). Supporting source: External licence billing in the exact AWS offer — https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.

- Operating cost estimate: Sources checked — unresolved. Specify concurrent calls, extensions, edition, SIP trunks/minutes, recording/transcription volume, retention and HA/failover requirements. The t3.xlarge sizing example does not include carrier service, a second server, recording backup or external AI services. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. 3CX announced V20 Update 10 on November 11, 2026; the V20 change log identifies production build 20.0.10.1785. Exclude release candidates and separately versioned mobile clients from this PBX snapshot. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/blog/releases/ai-agents-mcp-local-ai/ (reviewed 2026-11-18). Supporting source: Production PBX build number — https://www.3cx.com/blog/change-log/phone-system-change-log-v20/. Supporting source: AWS AMI package 20.0.10.1785 — https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- 3CX V20 November 2026 Linux security hotfix (security-advisory): 3CX refreshed V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Scope: Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing. Conditions: The exact installed application and operating-system package set determines exposure. Action: Apply the latest Admin Console update, restart as directed and verify installed package versions. Source: https://www.3cx.com/blog/change-log/pbx-security-updates/; reviewed 2026-11-19.




## Apache Answer

Self-hosted community questions, answers and knowledge content.

- Listing: https://launchinyourcloud.com/directory/apache-answer/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Apache Answer application and persistent database/storage.
- Operations: 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.
- Product website: https://answer.apache.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Apache Answer application and persistent database/storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted community questions, answers and knowledge content.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/apache-answer.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/apache-answer (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/apache-answer.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/apache-answer
  Apache Answer application and persistent database/storage. The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes LinkinStars, aichy126, kumfo, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/apache/answer/graphs/contributors

- Upstream project: https://github.com/apache/answer

### Sources

- Cloudron Store: https://www.cloudron.io/store/apache-answer.html

- Railway: https://railway.com/deploy/apache-answer

- Apache-2.0 LICENSE: https://github.com/apache/answer/blob/main/LICENSE

- Releases v2.0.3: https://github.com/apache/answer/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/apache/answer/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/apache-answer.html

- https://railway.com/deploy/apache-answer


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The official plugin guide demonstrates building Answer with GitHub and Google OAuth connector plugins. Include and configure compatible plugins in the deployed binary/image; this is not a claim that the default image includes enterprise SAML/OIDC. Scope: Official plugin-based application-user OAuth authentication. Source: https://answer.apache.org/docs/plugins (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide supplies Docker/Compose and binary installation options. Persist the data directory, configure the selected database and include required authentication plugins in the built image; default standalone examples do not supply production HA. Scope: Apache Answer application installation; plugin/custom-image build may be required. Source: https://answer.apache.org/docs/installation (reviewed 2026-11-20). Deployment artifact: https://answer.apache.org/docs/installation. Artifact reference: Current official deployment examples; pin binary/container and plugin versions.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/apache-answer.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Apache Answer; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/apache/answer/blob/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.0.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Apache Answer upstream application; verify compatibility with the selected package. Source: https://github.com/apache/answer/releases/tag/v2.0.3 (reviewed 2026-11-19).







## BigBlueButton

Self-hosted conferencing and virtual classroom platform.

- Listing: https://launchinyourcloud.com/directory/bigbluebutton/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, hetzner, scaleway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Official bbb-install.sh from the maintained 4.0 installer branch on supported Ubuntu
- Architecture: BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure.
- Operations: 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.
- Product website: https://bigbluebutton.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee. The maintained 4.0 installer also explicitly documents Scaleway and Azure behind-NAT deployments.

GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted conferencing and virtual classroom platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 

- scaleway: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md (checked 2026-11-19). 


### Cloud deployment evidence

- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9 (aws, azure, gcp, digitalocean, hetzner, scaleway): https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md
  BigBlueButton media, web, conferencing and recording services on dedicated Linux infrastructure. Use supported installer/Ubuntu combinations, public-address and UDP/media firewall requirements. A small development VM is not a production capacity or HA guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes antobinary, ritzalam, ramonlsouza, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/bigbluebutton/bigbluebutton/graphs/contributors

- Upstream project: https://github.com/bigbluebutton/bigbluebutton

### Sources

- <img width="1012" alt="bbb-install-banner" src="https://user-images.githubusercontent.com/1273169/141152865-f497c883-6c9: https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md

- Official Install Docs: https://docs.bigbluebutton.org/administration/install/

- bbb-install README: https://raw.githubusercontent.com/bigbluebutton/bbb-install/master/README.md

- LGPL-3.0 LICENSE: https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE

- Releases v4.0.2: https://github.com/bigbluebutton/bigbluebutton/releases

### Licensing sources

- https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE

### Infrastructure sources

- https://raw.githubusercontent.com/bigbluebutton/bbb-install/v4.0.x-release/README.md


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The optional Greenlight v3 front end supports external authentication through OpenID Connect and can connect to an external identity server. This is a Greenlight user-login capability, not the conferencing engine shared-secret API or an assurance about every LMS/front-end integration. Scope: BigBlueButton with the separately configured Greenlight v3 front end. Source: https://docs.bigbluebutton.org/greenlight/v3/install/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official 4.0 installation instructions link the maintained bbb-install.sh branch for Ubuntu 24.04. The older master README describes 2.6 and must not be used as the 4.0 installer reference. Scope: BigBlueButton 4.0 installer; verify the selected release line, dedicated CPU, public address and media firewall rules. Source: https://docs.bigbluebutton.org/administration/install/ (reviewed 2026-11-19). Deployment artifact: https://github.com/bigbluebutton/bbb-install/blob/v4.0.x-release/bbb-install.sh. Artifact reference: v4.0.x-release (moving maintained 4.0 installer branch).

- Minimum footprint / sizing: Documented. The production guide recommends Ubuntu 24.04, 8 CPU cores, 16 GB RAM, symmetric 250 Mbit/s networking and 500 GB free recording space, or 50 GB without recording. Smaller 4-core/8-GB development settings are separate. Concurrent media usage and HA need additional design. Scope: Current upstream production conferencing-node requirements; not meeting capacity for every workload. Source: https://docs.bigbluebutton.org/administration/install/ (reviewed 2026-11-20).

- License pricing: Documented. GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: BigBlueButton; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/bigbluebutton/bigbluebutton/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v4.0.2 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: BigBlueButton upstream application; verify compatibility with the selected package. Source: https://github.com/bigbluebutton/bigbluebutton/releases/tag/v4.0.2 (reviewed 2026-11-19).







## BookStack Self-Hosted

Self-hosted wiki and documentation organized into books, chapters and pages.

- Listing: https://launchinyourcloud.com/directory/bookstack/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT application; third-party components retain their licenses.
- Licensing model: open-source
- Installation: Cloudron package on a customer VM; upstream also documents native PHP/MySQL installation.
- Architecture: Persistent PHP web application with MySQL, uploaded media, attachments, configuration and themes
- Operations: Customer manages administrators, registration roles, identity, content permissions, mail, database and file backups, recovery and upgrades. Cloudron manages package services on the customer server.
- Product website: https://www.bookstackapp.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed Cloudron 2.3.1 contains upstream 26.09.3 and its access-control fixes. Change the initial local administrator credentials. With Cloudron SSO, change the default registration role before admitting users: the package initially grants administrator status. Back up the database, configuration, uploads, storage and custom themes. Only the latest upstream release is supported. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations.

MIT application; third-party components retain their licenses. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Persistent PHP web application with MySQL, uploaded media, attachments, configuration and themes. Cloudron provides a persistent server application, not event-driven application functions.


### Category fit

- collaboration: Collaborative wiki documentation with books, chapters, pages, revisions, attachments and role-based access.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (checked 2026-11-13). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudron.io/installation/ (checked 2026-11-13). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  BookStack Self-Hosted 26.09.3 is available as Cloudron package 2.3.1. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

BookStack has been maintained since 2015 with sustained development, translations and substantive code contributions from multiple participants. The project FAQ and contributor history establish participation beyond popularity counts; the reviewed release addresses access-control defects.

Reviewed 2026-11-13.

- Project maintenance and participation: https://www.bookstackapp.com/about/project-faq/

- Contributor history: https://github.com/BookStackApp/BookStack/graphs/contributors

- Maintained release: https://github.com/BookStackApp/BookStack/releases/tag/v26.09.3

### Sources

- Upstream installation: https://www.bookstackapp.com/docs/admin/installation/

- Database, configuration and file recovery: https://www.bookstackapp.com/docs/admin/backup-restore/

- Upstream upgrades: https://www.bookstackapp.com/docs/admin/updates/

- Project maintenance, edition and support policy: https://www.bookstackapp.com/about/project-faq/

- Cloudron BookStack configuration and administrator roles: https://docs.cloudron.io/packages/bookstack/

- Reviewed access-control fixes: https://github.com/BookStackApp/BookStack/releases/tag/v26.09.3

- MIT application license: https://github.com/BookStackApp/BookStack/blob/v26.09.3/LICENSE

- Contributor history: https://github.com/BookStackApp/BookStack/graphs/contributors

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

### Licensing sources

- https://github.com/BookStackApp/BookStack/blob/v26.09.3/LICENSE

- https://www.bookstackapp.com/about/project-faq/

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/bookstack/

- https://docs.cloudron.io/installation/


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/bookstack/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. BookStack documents SAML 2.0 and OpenID Connect as primary authentication alternatives to its email/password login. Reconcile these settings with any packaged distribution and its identity integration. Scope: Upstream BookStack; packaged Cloudron configuration may differ. Source: https://www.bookstackapp.com/docs/admin/saml2-auth/ (reviewed 2026-11-14). Supporting source: BookStack OpenID Connect authentication — https://www.bookstackapp.com/docs/admin/oidc-auth/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation page links Ubuntu installation scripts that provision the application and supporting PHP/web-server/database stack. Review the script before execution and use a supported matching OS; this is a single-server installer, not provider IaC or HA automation. Scope: Official Ubuntu 24.04 installer option; other distributions/packages have separate instructions. Source: https://www.bookstackapp.com/docs/admin/installation/ (reviewed 2026-11-20). Deployment artifact: https://codeberg.org/bookstack/devops/raw/branch/main/scripts/installation-ubuntu-24.04.sh. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The reviewed Cloudron BookStack package declares a 256 MB application-memory minimum. Cloudron itself additionally needs at least 2 GB RAM and 20 GB disk. These package limits do not size database, attachments, backups, concurrency or HA, and are not a whole-system VM requirement. Scope: Cloudron BookStack 26.09.3 package, not a universal upstream host floor. Source: https://www.cloudron.io/store/bookstack.html (reviewed 2026-11-20). Supporting source: Cloudron platform installation requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. The upstream BookStack software is MIT-licensed. This license does not include a hosting platform subscription, managed operation, implementation or a commercial support service. Packaged distributions and their supporting services can charge separately. Scope: Upstream BookStack core software terms. Source: https://raw.githubusercontent.com/BookStackApp/BookStack/development/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v26.09.3, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream BookStackApp/BookStack release record; commercial editions and deployment packages may differ. Source: https://github.com/BookStackApp/BookStack/releases/tag/v26.09.3 (reviewed 2026-11-14).







## Campfire (ONCE)

Self-hosted group chat and team conversation application.

- Listing: https://launchinyourcloud.com/directory/once-campfire/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: ONCE Campfire application and persistent message and upload storage on DigitalOcean.
- Operations: 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.
- Product website: https://once.com/campfire
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The current project is MIT-licensed; historical one-time commercial purchase descriptions are not the current source-code licence.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

ONCE Campfire application and persistent message and upload storage on DigitalOcean. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted group chat and team conversation application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/campfire (checked 2026-11-19). 


### Cloud deployment evidence

- DigitalOcean Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/campfire
  ONCE Campfire application and persistent message and upload storage on DigitalOcean. The current project is MIT-licensed; historical one-time commercial purchase descriptions are not the current source-code licence.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes monorkin, dhh, jeremy, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/basecamp/once-campfire/graphs/contributors

- Upstream project: https://github.com/basecamp/once-campfire

### Sources

- DigitalOcean Marketplace: https://marketplace.digitalocean.com/apps/campfire

- MIT LICENSE: https://github.com/basecamp/once-campfire/blob/main/MIT-LICENSE

- Releases v1.5.10: https://github.com/basecamp/once-campfire/releases

### Licensing sources

- https://github.com/basecamp/once-campfire/blob/main/MIT-LICENSE

### Infrastructure sources

- https://marketplace.digitalocean.com/apps/campfire


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed application README and self-hosting guide do not establish a supported corporate SAML/OIDC user-login integration. API access and installation through ONCE do not establish SSO. Confirm a maintained integration and supported version rather than infer federation from self-hosting. Scope: Campfire application user identity; current public evidence remains insufficient. Source: https://github.com/basecamp/once-campfire (reviewed 2026-11-20). Supporting source: Official self-hosting configuration — https://raw.githubusercontent.com/basecamp/once-campfire/main/docs/self-hosting.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting guide supplies a single-machine image with application, jobs, cache, file serving and TLS. Persist /rails/storage and set instance secrets and domain configuration. ONCE can manage installation/updates/backups; this is not a multi-node HA artifact. Scope: Upstream Campfire Docker deployment and optional ONCE lifecycle tooling. Source: https://raw.githubusercontent.com/basecamp/once-campfire/main/docs/self-hosting.md (reviewed 2026-11-20). Deployment artifact: https://github.com/basecamp/once-campfire. Artifact reference: main (moving repository); use a version-tagged application image.

- Minimum footprint / sizing: Sources checked — unresolved. The official guide establishes a self-contained single-machine deployment with database/uploads in persistent storage, but publishes no quantitative production CPU/RAM/storage floor in the reviewed instructions. Confirm attachment growth, active usage, backup and availability requirements. Scope: Single-machine deployment topology; quantitative production sizing remains open. Source: https://raw.githubusercontent.com/basecamp/once-campfire/main/docs/self-hosting.md (reviewed 2026-11-20).

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Campfire (ONCE); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/basecamp/once-campfire/blob/main/MIT-LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v1.5.12 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Campfire (ONCE) upstream application; verify compatibility with the selected package. Source: https://github.com/basecamp/once-campfire/releases/tag/v1.5.12 (reviewed 2026-11-19).







## Collabora Online (CODE)

Community office editing server for integration with a document platform.

- Listing: https://launchinyourcloud.com/directory/collabora-online/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hetzner, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package
- Architecture: Collabora Online Development Edition server and a separate WOPI-compatible file platform.
- Operations: 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.
- Product website: https://collaboraonline.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

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.


### Category fit

- collaboration: Community office editing server for integration with a document platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/ (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/collabora-online.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/collabora-online.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner Tutorial (hetzner): https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/
  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.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and 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.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/CollaboraOnline/online/graphs/contributors

- Upstream project: https://github.com/CollaboraOnline/online

### Sources

- Cloudron Store: https://www.cloudron.io/store/collabora-online.html

- Hetzner Tutorial: https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/

- MPL-2.0 COPYING: https://github.com/CollaboraOnline/online/blob/master/COPYING

- Releases 2026: https://github.com/CollaboraOnline/online/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/CollaboraOnline/online/blob/master/COPYING

### Infrastructure sources

- https://www.cloudron.io/store/collabora-online.html

- https://community.hetzner.com/tutorials/install-and-configure-nextcloud-collabora-online/


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. 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. Scope: CODE engine identity versus external document-platform authentication. Source: https://www.collaboraonline.com/code/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Listed CODE development edition; not Collabora Online commercial production support. Source: https://www.collaboraonline.com/code/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/collabora/code. Artifact reference: Select a supported version-tagged CODE image; distinguish nightly and commercial builds. Supporting source: Upstream source/build repository locations — https://raw.githubusercontent.com/CollaboraOnline/online/master/README.md.

- Minimum footprint / sizing: Documented. 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/collabora-online.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Collabora Online (CODE); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/CollaboraOnline/online/blob/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Discourse

Self-hosted discussion and community platform for workplace collaboration and customer support communities.

- Listing: https://launchinyourcloud.com/directory/discourse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, linode, vultr, hetzner
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-2.0 core; review extensions separately
- Licensing model: open-source
- Installation: Official Docker installer on a Linux cloud or local server
- Architecture: Persistent Docker server; the standalone template includes web, PostgreSQL and Redis services with host-mounted data volumes.
- Operations: Customer maintains the Linux host, Docker deployment, backups, updates and configured messaging services; choose an actively supported release channel.
- Product website: https://www.discourse.org/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers self-hosted Discourse. The official cloud installation guide explicitly lists AWS EC2 and Google Cloud as supported Docker hosts; customers provision the Linux server, rather than using a bundled cloud-specific infrastructure template. The installer offers an external Discourse ID login option when SMTP is skipped. Review authentication, email and other integrations for outbound data flows. Supported-series updates published November 10, 2026 include 2026.10.1 and 2026.7.5 ESR; the 2026.10.1 changelog records 38 security fixes. Self-hosted operators should upgrade on their selected supported release channel.

The listed self-hosted core has a GNU GPL version 2 license. Official paid hosting is a separate service; review the licenses of selected extensions separately.

The official installer requires a Linux server and Docker. Its standalone configuration mounts persistent host storage and includes PostgreSQL and Redis; this is a server workload.


### Category fit

- collaboration: Public or private discussion communities with searchable topics, chat and shared knowledge.

- customer-support: Customer and peer-support communities; this is a discussion platform rather than an agent-ticket helpdesk.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (checked 2026-11-12). 


### Cloud deployment evidence

- Discourse supported cloud server installation (aws, gcp, digitalocean, linode, vultr, hetzner): https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md
  The official cloud installation guide explicitly names DigitalOcean, AWS EC2, Google Cloud, Linode/Akamai, Vultr and Hetzner as supported hosts, then provides a complete server installation workflow. This is provider compatibility for the customer-operated Discourse application, not its separate hosted SaaS; configure the supported OS, DNS, email, HTTPS and recovery.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official customer directory identifies Docker, Elastic and GitLab support communities as Discourse users, without establishing their hosting model. The official release service records security-maintenance updates on November 10, 2026 for the latest, monthly and ESR channels; the supported 2026.10.1 release includes 38 security fixes.

Reviewed 2026-11-14.

- Named support-community adopters: https://www.discourse.org/customers

- Current releases and support timelines: https://releases.discourse.org/

- 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Sources

- Official self-hosting installation guide: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- Official standalone Docker service and storage template: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml

- Discussion, chat and administration features: https://www.discourse.org/features

- Discourse core license: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- Official releases and support timelines: https://releases.discourse.org/

- Official customer community directory: https://www.discourse.org/customers

- Discourse 2026.10.1 security-maintenance changelog: https://releases.discourse.org/changelog/v2026.10.1/

### Licensing sources

- https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

### Infrastructure sources

- https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md

- https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. DiscourseConnect is the official SSO protocol for connecting Discourse to an external identity provider through a signed shared-secret exchange. It is distinct from a generic SAML entitlement; configure account/email mapping and callback security for the actual identity service. Scope: Official DiscourseConnect self-hosted forum authentication. Source: https://meta.discourse.org/t/setup-discourseconnect-official-single-sign-on-for-discourse-sso/13045 (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official discourse_docker repository supplies launcher scripts and a standalone configuration example with application, PostgreSQL and Redis templates. Configure mail, TLS, secrets, volumes and backups, and pin compatible releases; a standalone container is not a clustered HA topology. Scope: Official self-hosted launcher and standalone container installation. Source: https://raw.githubusercontent.com/discourse/discourse_docker/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/discourse/discourse_docker/blob/main/samples/standalone.yml. Artifact reference: main (moving branch). Supporting source: Standalone configuration template — https://raw.githubusercontent.com/discourse/discourse_docker/main/samples/standalone.yml.

- Minimum footprint / sizing: Documented. The upstream cloud guide lists 1 CPU core, 1 GB RAM with swap and 10 GB disk as minima; 2+ cores, 2 GB+ RAM and 20 GB+ disk are recommended. Plugins, traffic and data growth change sizing. Scope: Upstream standalone cloud install baseline. Source: https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md (reviewed 2026-11-14).

- License pricing: Documented. The upstream Discourse software is GPL version 2. Hosted subscription prices on discourse.org are for separately operated hosting/services and should not be presented as the license cost of the self-hosted core. Infrastructure, implementation and optional services are separate. Scope: Upstream self-hosted core license; hosted plan pricing is a different offering. Source: https://raw.githubusercontent.com/discourse/discourse/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## DokuWiki

File-based wiki for documentation and shared knowledge.

- Listing: https://launchinyourcloud.com/directory/dokuwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: DokuWiki web application with persistent wiki pages, configuration and attachments.
- Operations: 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.
- Product website: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version.

GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

DokuWiki web application with persistent wiki pages, configuration and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: File-based wiki for documentation and shared knowledge.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/dokuwiki.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/dokuwiki (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/dokuwiki.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/dokuwiki
  DokuWiki web application with persistent wiki pages, configuration and attachments. Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes splitbrain, selfthinker, Klap-in, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/dokuwiki/dokuwiki/graphs/contributors

- Upstream project: https://github.com/dokuwiki/dokuwiki

### Sources

- Cloudron Store: https://www.cloudron.io/store/dokuwiki.html

- Railway: https://railway.com/deploy/dokuwiki

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg

- GPL-2.0 COPYING: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

- Releases 2026-07-14c: https://github.com/dokuwiki/dokuwiki/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

### Infrastructure sources

- https://www.cloudron.io/store/dokuwiki.html

- https://railway.com/deploy/dokuwiki


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from TurnKey GNU/Linux. Its package version is 19.0.3; verify the contained application and required entitlements separately. Scope: DokuWiki selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg (reviewed 2026-11-19). Offer prodview-h7wozgfyl3vfg: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The maintainer-provided oauth plugin implements login through OAuth services. It is a separately installed authentication plugin, not a guarantee that the default wiki has corporate SAML/OIDC configured; validate provider-plugin and DokuWiki release compatibility. Scope: CosmoCode DokuWiki OAuth plugin integration. Source: https://raw.githubusercontent.com/cosmocode/dokuwiki-plugin-oauth/master/README (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream DokuWiki container repository documents a non-root image, persistent /storage volume and a Compose example. Configure the initial wiki securely, set writable storage ownership and pin a supported release rather than a moving tag. Scope: Official DokuWiki application container packaging; not cloud-account HA IaC. Source: https://raw.githubusercontent.com/dokuwiki/docker/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dokuwiki/docker. Artifact reference: master (moving repository); choose a supported version-tagged image.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/dokuwiki.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: DokuWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream release-2026-07-14c release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: DokuWiki upstream application; verify compatibility with the selected package. Source: https://github.com/dokuwiki/dokuwiki/releases/tag/release-2026-07-14c (reviewed 2026-11-19).







## Etherpad

Self-hosted real-time collaborative text editor.

- Listing: https://launchinyourcloud.com/directory/etherpad/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Etherpad application, database and persistent plugins and settings.
- Operations: 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.
- Product website: https://etherpad.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Etherpad application, database and persistent plugins and settings. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted real-time collaborative text editor.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/etherpad.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/etherpad (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/etherpad.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/etherpad
  Etherpad application, database and persistent plugins and settings. Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes JohnMcLear, rhansen, Pita, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/ether/etherpad/graphs/contributors

- Upstream project: https://github.com/ether/etherpad

### Sources

- Cloudron Store: https://www.cloudron.io/store/etherpad.html

- Railway: https://railway.com/deploy/etherpad

- Apache-2.0 LICENSE: https://github.com/ether/etherpad-lite/blob/develop/LICENSE

- Releases v3.3.19: https://github.com/ether/etherpad-lite/releases

- Etherpad | Cloudron Docs: https://docs.cloudron.io/packages/etherpad/

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

- Etherpad authentication and author-token advisories: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh

### Licensing sources

- https://github.com/ether/etherpad-lite/blob/develop/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/etherpad.html

- https://railway.com/deploy/etherpad


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed configuration includes an embedded OIDC issuer with admin/user clients, and the API supports mapping a host application’s users and permissions. This does not establish login federation to an existing corporate SAML/OIDC IdP for the selected pad/admin deployment. Confirm the supported external-auth plugin or portal integration. Scope: Embedded identity issuer and host API integration are distinct from external-IdP federation. Source: https://raw.githubusercontent.com/ether/etherpad/develop/settings.json.template (reviewed 2026-11-20). Supporting source: Official host-user/API integration design — https://docs.etherpad.org/api/http_api.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker documentation provides container/environment configuration and persistent data/plugin handling. Pin compatible application/plugins, supply a production database and secrets, and configure the reverse proxy. A standalone container does not by itself supply durable clustered operation or external-user SSO. Scope: Upstream Etherpad container deployment and configuration. Source: https://docs.etherpad.org/docker.html (reviewed 2026-11-20). Deployment artifact: https://github.com/ether/etherpad/blob/develop/doc/docker.md. Artifact reference: develop (moving branch); pin application and compatible plugins.

- Minimum footprint / sizing: Documented. The Cloudron package declares 768MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/etherpad.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Etherpad; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ether/etherpad-lite/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v3.3.19 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Etherpad upstream application; verify compatibility with the selected package. Source: https://github.com/ether/etherpad/releases/tag/v3.3.19 (reviewed 2026-11-19).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Etherpad authentication and author-token advisories (security-advisory): Upstream documents an OIDC login bypass and an author-token isolation correction in separate advisories. Scope: GHSA-62cj-9j72-mfrh and GHSA-746x-9w89-7xv6; consult each notice for its own affected and fixed versions. Conditions: OIDC/password configuration and clients without author tokens change exposure; plugin/package versions must be checked separately. Action: Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version. Source: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh; reviewed 2026-11-19. Supporting source: Author-token isolation advisory — https://github.com/ether/etherpad/security/advisories/GHSA-746x-9w89-7xv6.




## ONLYOFFICE Docs (Community Edition)

Community browser-based office document editing and co-authoring server.

- Listing: https://launchinyourcloud.com/directory/onlyoffice-docs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hetzner, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package
- Architecture: ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform.
- Operations: 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.
- Product website: https://www.onlyoffice.com/see-it-in-action
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. The supplied Vultr article installs DocSpace rather than Docs; the Vultr badge here comes from the reviewed Cloudron Docs package instead.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Community browser-based office document editing and co-authoring server.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- hetzner: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/ (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/onlyoffice-docs.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, vultr, hostinger, lumadock): https://www.cloudron.io/store/onlyoffice-docs.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Akamai Quick Deploy (linode): https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice
  ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. This source is distinct from the Cloudron package.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Hetzner Tutorial (hetzner): https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/
  ONLYOFFICE Document Server and its persistent dependencies, normally integrated with a separate file platform. Community is AGPL-3.0 and distinct from Docs Enterprise in PR #28 and the DocSpace room-based application. Check Community concurrency and branding limits; an editor is not a complete repository. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes agolybev, ShockwaveNN, trofim24, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/ONLYOFFICE/DocumentServer/graphs/contributors

- Upstream project: https://github.com/ONLYOFFICE/DocumentServer

### Sources

- Cloudron Store: https://www.cloudron.io/store/onlyoffice-docs.html

- Akamai Quick Deploy: https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice

- Hetzner Tutorial: https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/

- AGPL-3.0 LICENSE: https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE

- Releases v10.0.0: https://github.com/ONLYOFFICE/DocumentServer/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/onlyoffice-docs.html

- https://techdocs.akamai.com/quick-deploy-apps/docs/onlyoffice

- https://community.hetzner.com/tutorials/install-and-configure-onlyoffice-docs-for-nextcloud/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed Docs integration uses a host platform and signed JWT requests to the editor service. This does not establish standalone SAML/OIDC user login in the listed Docs Community engine. Confirm the identity-providing host and connector instead of transferring DocSpace SSO claims. Scope: Docs Community editor engine; host-platform identity is a separate layer. Source: https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Community guide installs the DocumentServer container with persistent data and configuration, including the JWT secret used by host integrations. The editor service still needs a document-management host/connector; deploying it alone does not supply a complete authenticated collaboration portal. Scope: ONLYOFFICE Docs Community editor-engine container, not DocSpace/Workspace. Source: https://helpcenter.onlyoffice.com/docs/installation/docs-community-install-docker.aspx (reviewed 2026-11-20). Deployment artifact: https://github.com/ONLYOFFICE/Docker-DocumentServer. Artifact reference: Current official Community Docker guide; pin an application-compatible image.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/onlyoffice-docs.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: ONLYOFFICE Docs (Community Edition); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ONLYOFFICE/DocumentServer/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v10.0.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: ONLYOFFICE Docs (Community Edition) upstream application; verify compatibility with the selected package. Source: https://github.com/ONLYOFFICE/DocumentServer/releases/tag/v10.0.0 (reviewed 2026-11-19).







## Rallly

Self-hosted group scheduling polls and meeting coordination.

- Listing: https://launchinyourcloud.com/directory/rallly/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Rallly application, PostgreSQL, persistent storage and outbound email.
- Operations: 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.
- Product website: https://rallly.co
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Rallly application, PostgreSQL, persistent storage and outbound email. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted group scheduling polls and meeting coordination.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/rallly.html (checked 2026-11-19). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/rallly (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/rallly.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/rallly
  Rallly application, PostgreSQL, persistent storage and outbound email. Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes lukevella, snyk-bot, jonas-hoebenreich, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/lukevella/rallly/graphs/contributors

- Upstream project: https://github.com/lukevella/rallly

### Sources

- Cloudron Store: https://www.cloudron.io/store/rallly.html

- Railway: https://railway.com/deploy/rallly

- AGPL-3.0 LICENSE: https://github.com/lukevella/rallly/blob/main/LICENSE

- Releases v4.17.1: https://github.com/lukevella/rallly/releases

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://github.com/lukevella/rallly/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/rallly.html

- https://railway.com/deploy/rallly


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosting guide documents Google, Microsoft Entra ID and generic OIDC login from v3.4 onward. Configure callback URLs, verified email claims and linking policy; multi-user licence entitlements are a separate consideration. Scope: Rallly self-hosted user identity; review the selected v4 deployment and license. Source: https://support.rallly.co/self-hosting/single-sign-on (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installer provisions a Compose stack, generates secrets and supports external database, object storage and reverse-proxy settings. Review the downloaded script before execution, pin compatible images and plan backups; this is not a production HA template. Scope: Current official self-hosting stack and installer. Source: https://support.rallly.co/self-hosting/installation/docker (reviewed 2026-11-20). Deployment artifact: https://get.rallly.co. Artifact reference: Moving official installer; inspect and pin the selected application/stack release.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/rallly.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. The current self-hosting guide states free personal use and asks multi-user installations to purchase a licence key. It lists Plus at $49, Organization at $499 and Enterprise from $999; keys cover Rallly v4.x with tier/user/space limits. Activation requires the licensing service. These runtime-plan terms add detail beyond the repository’s AGPL notice. Scope: Published Rallly v4 self-hosting licence-key tiers; confirm applicable user/space allocation and quote. Source: https://support.rallly.co/self-hosting/licensing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v4.17.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Rallly upstream application; verify compatibility with the selected package. Source: https://github.com/lukevella/rallly/releases/tag/v4.17.1 (reviewed 2026-11-19).







## Rocket.Chat Self-Managed

Self-managed team messaging and collaboration platform deployed on customer cloud infrastructure.

- Listing: https://launchinyourcloud.com/directory/rocket-chat-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition core; Enterprise Edition code and non-community plans use separate proprietary licensing.
- Licensing model: open-source
- Installation: Docker or Docker Compose, Kubernetes with the official Helm chart, or the Launchpad CLI
- Architecture: Customer-operated Rocket.Chat application and MongoDB deployment on virtual machines or Kubernetes.
- Operations: Customer operates MongoDB, application instances, storage, TLS, monitoring, backups, scaling and upgrades; plan entitlements govern enterprise capabilities.
- Product website: https://www.rocket.chat/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-18; infrastructure review: 2026-11-17

### Scope and qualifications

New self-managed deployments receive the Starter plan, intended for evaluation or small non-critical teams and limited to 50 users. Commercial, Government, Defense and air-gapped capabilities require the applicable plan. Push notifications normally require Rocket.Chat Cloud registration and outbound access unless an alternative gateway is configured. Launchpad excludes Omnichannel and federation workloads and includes a closed-source operator. The documented DigitalOcean Marketplace one-click path is unsupported. Rocket.Chat 9.0.0 moves LDAP, SAML, and Custom OAuth to premium editions and removes several login integrations. It also fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure; verify at least one administrator login path before upgrading.

Community Edition code outside designated Enterprise Edition paths is MIT-licensed. Enterprise Edition code and paid self-managed plans have separate proprietary terms and feature entitlements. Since 9.0.0, LDAP, SAML, and Custom OAuth are premium features; several legacy login integrations were removed. Confirm the purchased plan and an administrator recovery path before upgrade.

Production paths run persistent application and MongoDB workloads on customer virtual machines or Kubernetes.


### Category fit

- collaboration: Team channels, messaging, file sharing and collaborative workflows; governance, scale and isolated-network capabilities depend on plan.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.rocket.chat/partners/aws (checked 2026-11-17). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://rocket.chat/install (checked 2026-11-17). 


### Cloud deployment evidence

- Rocket.Chat in the customer's AWS environment (aws): https://www.rocket.chat/partners/aws
  Rocket.Chat states that the self-managed deployment runs in the customer's own AWS environment and can be launched from AWS Marketplace. The EKS Launchpad guide is a separate current implementation path.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.

- Rocket.Chat self-managed deployment on DigitalOcean (digitalocean): https://rocket.chat/install
  The current publisher installation page explicitly names DigitalOcean for self-managed deployment. The older Marketplace one-click guide is unsupported and is not presented as a supported one-click method.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Self-managed installation options and named clouds: https://rocket.chat/install

- AWS customer-account deployment: https://www.rocket.chat/partners/aws

- Launchpad deployment on Amazon EKS: https://docs.rocket.chat/docs/deploy-with-launchpad

- Kubernetes and Helm deployment: https://docs.rocket.chat/docs/deploy-with-kubernetes

- Deployment guide: https://docs.rocket.chat/docs/deployment-guide

- Community Edition license: https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE

- Enterprise Edition license: https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/ee/LICENSE

- Current self-managed plans: https://docs.rocket.chat/our-plans

- Release support lifecycle: https://docs.rocket.chat/docs/releaselifecycle

- Unsupported DigitalOcean one-click path: https://docs.rocket.chat/docs/deploy-with-digital-ocean

- Rocket.Chat 9.0.0 release notes: https://docs.rocket.chat/docs/rocketchat-release-notes/

### Licensing sources

- https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE

- https://github.com/RocketChat/Rocket.Chat/blob/develop/apps/meteor/ee/LICENSE

- https://docs.rocket.chat/our-plans

- https://docs.rocket.chat/docs/rocketchat-release-notes/

### Infrastructure sources

- https://docs.rocket.chat/docs/deployment-guide

- https://docs.rocket.chat/docs/deploy-with-kubernetes


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The installation page names customer AWS/DigitalOcean deployment, but not a current cloud Marketplace procurement offer. The Rocket.Chat app Marketplace is a different catalogue. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://rocket.chat/install (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Named-cloud installation and paid workspace plans do not establish a qualifying Marketplace purchase or cloud-commitment eligibility. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://rocket.chat/install (reviewed 2026-11-17).

- Single sign-on: Edition-dependent. From Rocket.Chat 9.0, LDAP and SAML are included in Starter and premium plans, and excluded from Community. The reviewed identity FAQ explicitly separates these plans; older Community entitlement assumptions no longer apply. Scope: Self-managed Rocket.Chat 9.0+ identity plan boundary. Source: https://docs.rocket.chat/docs/identity-management-faq (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. Current self-managed identity guidance documents LDAP/SAML and plan boundaries. A SCIM endpoint, lifecycle operations and entitlement were not established. Scope: Reviewed public evidence for Rocket.Chat Self-Managed; unresolved within this edition/deployment. Source: https://docs.rocket.chat/docs/identity-management-faq (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Rocket.Chat Self-Managed material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.rocket.chat/docs/security-overview (reviewed 2026-11-17).

- Security controls: Documented. The security overview distinguishes plan-specific audit, custom-role and encryption capabilities. FIPS configuration requires a Government/Defense add-on; customers operate TLS, firewall rules and the compatible MongoDB deployment. Current advisory review: Rocket.Chat 9.0.0 fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure while changing authentication feature availability. Upgrade to 9.0.0 or later, verify an administrator login path, and confirm premium authentication entitlements. Scope: Self-managed controls; plan qualifications retained Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes.. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/ (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.rocket.chat/docs/security-overview.

- Air-gapped operation: Edition-dependent. The documented air-gapped model requires a paid plan and alternative handling for cloud-dependent services. Stage licensing/registration and apps through the supported workflow; ordinary mobile push and app Marketplace access require separate arrangements. Scope: Paid isolated workspace configuration. Source: https://docs.rocket.chat/v1/docs/choose-your-deployment-model (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Rocket.Chat documents Helm deployment into customer Kubernetes, with MongoDB and application configuration managed separately. Launchpad is a distinct deployment path with its own feature and operator constraints. Scope: Self-managed Kubernetes installation. Source: https://docs.rocket.chat/docs/deploy-with-kubernetes (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. For HA premium workspaces, the sizing guide lists Rocket.Chat at 4 vCPU/8–12 GiB and MongoDB at 2 vCPU/8–16 GiB per replica, recommending three MongoDB members. It is a workload-specific baseline, not proof that every 100-user workload fits. Scope: Premium HA sizing table; application replica count and data size require design. Source: https://docs.rocket.chat/docs/system-requirements (reviewed 2026-11-17).

- License pricing: Documented. Community Edition code outside designated Enterprise Edition paths is MIT-licensed. Enterprise Edition code and paid self-managed plans have separate proprietary terms and feature entitlements. Scope: Rocket.Chat Self-Managed: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://github.com/RocketChat/Rocket.Chat/blob/develop/LICENSE (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Confirm a premium HA workspace design, application replicas, MongoDB replica sizing, attachment storage and clock-speed requirements. The Starter 50-user plan does not cover the requested 100-user scenario. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.rocket.chat/docs/system-requirements (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Rocket.Chat 9.0.0 was released November 10, 2026. It changes authentication feature entitlements, removes login integrations, and includes access-scoping, SSRF, and Brotli fixes. Scope: Rocket.Chat self-managed 9.0 release. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/ (reviewed 2026-11-18). Supporting source: Release lifecycle — https://docs.rocket.chat/docs/releaselifecycle.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Rocket.Chat 9.0.0 security and authentication update (security-advisory): Rocket.Chat 9.0.0 fixes direct-message and transcript scoping, an SSRF bypass, and Brotli exposure while changing authentication feature availability. Scope: Rocket.Chat self-managed 9.0.0 release; exact component and feature applicability follows the release notes. Conditions: Exposure depends on messaging, transcript, outbound request, and affected dependency use. Authentication migration depends on edition. Action: Upgrade to 9.0.0 or later, verify an administrator login path, and confirm premium authentication entitlements. Source: https://docs.rocket.chat/docs/rocketchat-release-notes/; reviewed 2026-11-18.




## WBO (Whitebophir)

Self-hosted multi-user collaborative whiteboard.

- Listing: https://launchinyourcloud.com/directory/wbo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Docker / Compose
- Architecture: WBO application with persistent board storage.
- Operations: 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.
- Product website: https://wbo.ophir.dev
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Review board visibility and authentication before exposing it. A private VPS does not automatically make every board private or give the app enterprise SSO.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

WBO application with persistent board storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted multi-user collaborative whiteboard.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/wbo.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/wbo.html (checked 2026-11-19). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/wbo.html (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/wbo.html (checked 2026-11-19). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/wbo.html (checked 2026-11-19). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.cloudron.io/store/wbo.html (checked 2026-11-19). 


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/wbo.html
  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.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes lovasoa, finnboeger, h2Entwicklung, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/lovasoa/whitebophir/graphs/contributors

- Upstream project: https://github.com/lovasoa/whitebophir

### Sources

- Cloudron Store: https://www.cloudron.io/store/wbo.html

- Hostinger: https://www.hostinger.com/applications/wbo

- AGPL-3.0 LICENSE: https://raw.githubusercontent.com/lovasoa/whitebophir/master/LICENSE

- GitHub Releases (v2.18.44): https://github.com/lovasoa/whitebophir/releases

- Commits: https://github.com/lovasoa/whitebophir/commits/master.atom

- Cloudron customer-server and named-provider installation: https://docs.cloudron.io/installation/

### Licensing sources

- https://raw.githubusercontent.com/lovasoa/whitebophir/master/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/wbo.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed application supports signed JWT board access when AUTH_SECRET_KEY is configured; otherwise a board URL permits access. This establishes token authorization, not an integrated SAML/OIDC login flow. Confirm the external identity service and token-issuance integration separately. Scope: WBO board authorization; no turnkey federated user-login path established. Source: https://raw.githubusercontent.com/lovasoa/whitebophir/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README provides an official Docker run deployment with a persistent server-data volume and an alternative Node.js installation. Its example uses latest; pin a compatible image, protect board data and configure the proxy/trusted IP source. It is a single-instance application recipe. Scope: Official Whitebophir/WBO Docker and Node installation. Source: https://raw.githubusercontent.com/lovasoa/whitebophir/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/lovasoa/whitebophir. Artifact reference: master (moving branch); pin the selected Docker image or release.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/wbo.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: WBO (Whitebophir); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/lovasoa/whitebophir/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.18.44 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: WBO (Whitebophir) upstream application; verify compatibility with the selected package. Source: https://github.com/lovasoa/whitebophir/releases/tag/v2.18.44 (reviewed 2026-11-19).







## Zulip

Topic-organized team chat with a documented self-hosted server.

- Listing: https://launchinyourcloud.com/directory/zulip/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0; hosted services and commercial support plans are separate.
- Licensing model: open-source
- Installation: Install the production server on supported Ubuntu/Debian or use the documented Docker image.
- Architecture: Persistent application and database services on your chosen server infrastructure.
- Operations: Operate server security, email delivery, backups, upgrades and any optional external notification services.
- Product website: https://zulip.com/
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This listing covers the self-hosted server; review mobile notification and support service terms for your deployment. Zulip 13.2, released November 13, 2026, fixes new installations failing when PostgreSQL cannot start because postgresql-common 294 leaves the PostgreSQL log directory owned by root; upgrades are unaffected.

The Zulip application is Apache 2.0. Paid hosting, support or notification service arrangements are separate from the server source license.

The production instructions provision an Ubuntu/Debian server or Docker services; classified as servers.


### Category fit

- collaboration: Dedicated team chat organized into channels and topics for real-time and asynchronous collaboration.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://zulip.readthedocs.io/en/stable/production/install.html (checked 2026-11-12). 


### Cloud deployment evidence

- Zulip server installation options (digitalocean): https://zulip.readthedocs.io/en/stable/production/install.html
  The current server installation documentation explicitly offers a preconfigured DigitalOcean Droplet as a self-hosting option, separately from Zulip Cloud. Operate the server, backups and upgrades yourself; mobile push notifications use a separately configured external service.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Zulip Server 13.0 and 13.1 were released November 12, 2026, and 13.2 followed on November 13. Version 13.2 fixes a PostgreSQL startup failure affecting new installations. The independent Zulip Foundation stewards the project and owns its operating company Kandra Labs.

Reviewed 2026-11-14.

- Zulip 13.0 major release: https://blog.zulip.com/2026/11/12/zulip-13-0-released/

- Zulip 13.2 maintenance release: https://github.com/zulip/zulip/releases/tag/13.2

- Current production version: https://zulip.readthedocs.io/en/latest/production/install.html

- Foundation governance: https://zulip.com/team/

### Sources

- Production server installation: https://zulip.readthedocs.io/en/latest/production/install.html

- Project capabilities and Apache license: https://github.com/zulip/zulip

- Zulip 13.0 major release announcement: https://blog.zulip.com/2026/11/12/zulip-13-0-released/

- Zulip 13.2 maintenance release: https://github.com/zulip/zulip/releases/tag/13.2

- Zulip Foundation governance: https://zulip.com/team/

- Infrastructure or licensing evidence: https://github.com/zulip/zulip/blob/main/docs/contributing/licensing.md

### Licensing sources

- https://github.com/zulip/zulip

- https://github.com/zulip/zulip/blob/main/docs/contributing/licensing.md

### Infrastructure sources

- https://zulip.readthedocs.io/en/latest/production/install.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The stable server manual documents SAML, OIDC, LDAP and other authentication backends. Configure the selected backend and provider values; Docker installations use corresponding environment settings. Scope: Zulip 13.2 stable documentation as reviewed; not development branch. Source: https://zulip.readthedocs.io/en/stable/production/authentication-methods.html (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production installation guide documents its server installer and links a Docker alternative. Select a supported release/OS and configure DNS, TLS, email and backups; development documentation may describe a newer branch. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://zulip.readthedocs.io/en/latest/production/install.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The stable guide specifies 1 CPU, 2 GB RAM and 2 GB swap for a smaller deployment, rising to 2 CPUs and 4 GB for 100+ users. Allow at least 10 GB dedicated free disk plus the operating system. Scope: Zulip 13.2 stable baseline; dedicated supported server/VM. Source: https://zulip.readthedocs.io/en/stable/production/requirements.html (reviewed 2026-11-14).

- License pricing: Documented. All Zulip self-hosted features are available in the free open-source edition. Paid self-hosted plans add services such as mobile notifications and support, with eligibility/usage limits on the free notification service. Those service plans differ from Zulip Cloud hosting and customer infrastructure costs. Scope: Published self-hosted plans and optional service entitlements; not Cloud subscription pricing. Source: https://zulip.com/plans/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 13.2, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream zulip/zulip release record; commercial editions and deployment packages may differ. Source: https://github.com/zulip/zulip/releases/tag/13.2 (reviewed 2026-11-14).






