
# Collaboration on Google Cloud

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

Canonical page: https://launchinyourcloud.com/clouds/gcp/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: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

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

5 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.




## 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).







## Confluence Data Center

Commercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/confluence-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Confluence and optional Synchrony services with an external database, load balancer, shared home and local indexes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, Synchrony, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/confluence/enterprise
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers Confluence Data Center, not Confluence Cloud. Atlassian supports its Kubernetes Helm chart and documents EKS, AKS and GKE as managed cluster options. The older AWS Quick Start and Azure Resource Manager templates are no longer supported or maintained. Atlassian states that affected Data Center subscriptions and associated Marketplace apps expire on March 28, 2029, after which the applications become read-only; evaluate the migration timeline before a new deployment. New customers cannot purchase this Data Center subscription after March 30, 2026. The remaining purchase/expansion window through March 30, 2028 is for existing Data Center customers; do not treat this listing as an unrestricted new-customer offering. Atlassian rates CVE-2026-21589 critical (9.3). Upgrade to Confluence 9.2.26, 10.2.19, or a later fixed release to prevent unauthenticated access to specifically named files under the web application root. Separately, CVE-2026-90436 is a critical unauthenticated remote-code-execution issue in Confluence 1.x–9.x when Remote API (XML-RPC and SOAP) is enabled. Upgrade to 9.2.28 or a later fixed release, or disable the remote API and verify that the Axis endpoint returns HTTP 403; Confluence 10.x and later are unaffected by the RCE. Atlassian's November 17, 2026 bulletin aggregates 266 high- and 52 critical-severity third-party CVEs, while assessing the bulletin items as non-critical in product context. Use a fixed supported target for this product and branch, and validate app compatibility before upgrading.

New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies.

Confluence Data Center runs persistent application and collaborative-editing services with durable database, shared-home and local-index storage.


### Category fit

- collaboration: Provides self-managed team workspaces, collaborative authoring and enterprise knowledge sharing.

- content-management: Manages structured spaces, pages, attachments, templates and governed enterprise knowledge content.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html (checked 2026-11-16). 


### Cloud deployment evidence

- Confluence Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html
  Atlassian documents Confluence Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. The linked page applies to Confluence Data Center 11.0; select a Helm chart compatible with the installed product release.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed. Versions: 11.0; use the current compatibility matrix for other releases.


### Sources

- Install Confluence Data Center 11.0: https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html

- Run Confluence Data Center on Kubernetes: https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html

- Confluence Data Center supported platforms: https://confluence.atlassian.com/doc/supported-platforms-207488198.html

- Atlassian Data Center licensing and end of life: https://www.atlassian.com/licensing/data-center

- Atlassian product-specific end-of-life and purchase eligibility: https://www.atlassian.com/licensing/data-center-end-of-life

- Atlassian CVE-2026-21589 critical file-access advisory: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html

- Atlassian CVE-2026-90436 Confluence RCE advisory: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html

- Atlassian security bulletin — November 17, 2026: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html

### Licensing sources

- https://www.atlassian.com/licensing/data-center

- https://www.atlassian.com/licensing/data-center-end-of-life

### Infrastructure sources

- https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html

- https://confluence.atlassian.com/doc/running-confluence-data-center-on-a-kubernetes-cluster-1085179764.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 7 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: Documented. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Confluence 7.12+; authentication does not assign application access or permissions. Scope: Confluence 7.12+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

- SCIM provisioning: Documented. Atlassian’s native cloud-IdP scenario uses login-time JIT provisioning for Data Center, without regular synchronization or de-provisioning. Its cloud SCIM path is different; third-party Data Center provisioning apps require separate review. Scope: Native Data Center cloud-IdP integration described by Atlassian; not an assessment of every Marketplace add-on. Source: https://confluence.atlassian.com/enterprise/manage-users-between-cloud-and-data-center-products-1085188069.html (reviewed 2026-11-16).

- Compliance attestations: Sources checked — unresolved. Atlassian’s public SOC 2 page points to product reports, but does not establish the customer-operated Data Center boundary or report validity. Review the actual report before claiming coverage. Scope: Vendor reports versus this self-managed Data Center installation. Source: https://www.atlassian.com/trust/compliance/resources/soc2 (reviewed 2026-11-16).

- Security controls: Documented. Current advisory review: Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS.. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Confluence Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/doc/installing-confluence-data-center-203603.html (reviewed 2026-11-16). Deployment artifact: https://github.com/atlassian/data-center-helm-charts. Artifact reference: main (moving branch; select product-compatible chart and application release).

- Minimum footprint / sizing: Documented. The Data Center technical overview recommends at least 10 GB RAM per Confluence node, including operating-system, JVM, external-process and Synchrony allocations. Database, shared storage, node count and any separate Synchrony cluster require additional planning. Scope: Clustered Confluence Data Center node guideline; not an installation-wide total. Source: https://confluence.atlassian.com/enterprise/confluence-data-center-technical-overview-612959401.html (reviewed 2026-11-16).

- License pricing: Documented. New customers can no longer purchase affected Data Center subscriptions after March 30, 2026. Existing Data Center customers may purchase new subscriptions and expansions until March 30, 2028. Affected subscriptions and associated Marketplace apps expire and become read-only on March 28, 2029; review the vendor migration and exception policies. Scope: Confluence Data Center: software license terms; infrastructure and operating costs are separate. Source: https://www.atlassian.com/licensing/data-center (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.atlassian.com/licensing/data-center-end-of-life.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Atlassian’s current-download feed lists 11.0.1, released 2026-11-03. This is the reviewed download snapshot, not a guarantee that every other release branch, Helm chart, app or upgrade path is compatible. Existing-customer and lifecycle restrictions still apply. Scope: Vendor current-download feed; publication day only, with no invented release time. Source: https://my.atlassian.com/download/feeds/current/confluence.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/DOC/Confluence+11.0+Release+Notes.




### Security and lifecycle reviews

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

- Data Center purchase restrictions and 2029 retirement (lifecycle): Affected subscriptions become read-only on March 28, 2029. New customers lost purchase eligibility on March 30, 2026; existing customers have a different expansion window. Scope: Jira Software, Jira Service Management and Confluence Data Center. Bitbucket is excluded from this retirement; exceptional extensions require Atlassian agreement. Conditions: Existing-customer status and the purchased product determine eligibility. Action: Confirm purchase eligibility, migration timing and any written exception before evaluation. Source: https://www.atlassian.com/licensing/data-center-end-of-life; reviewed 2026-11-16.

- Atlassian Data Center unauthenticated file access (security-advisory): CVE-2026-21589 allows access to specifically named files under the web application root; Atlassian assigns critical severity. Scope: Jira Software: 9.12.40/10.3.26/11.3.12; JSM: 5.12.40/10.3.26/11.3.12; Confluence: 9.2.26/10.2.19; Bitbucket: 9.4.26/10.2.8/10.5.1. Versions before the appropriate branch fix are affected. Conditions: An attacker needs the exact file name and path; directory enumeration is not provided. Sensitive files in the application root change the risk. Action: Patch every affected installation to its fixed supported branch. If delayed, restrict internet access and apply the vendor WAF or product-specific rewrite mitigation to all relevant nodes. Source: https://confluence.atlassian.com/security/cve-2026-21589-arbitrary-file-access-vulnerability-impacts-multiple-products-1870495748.html; reviewed 2026-11-17.

- Confluence Remote API code-execution advisory (security-advisory): CVE-2026-90436 is an unauthenticated code-execution issue when the affected Remote API is enabled. Scope: Confluence Data Center 1.x–9.x before the applicable fix; 9.2.28 is the listed fixed LTS release. Confluence 10.x and later are unaffected. Conditions: Requires Remote API (XML-RPC and SOAP). Disabling it can break scripts, automation and add-ons. Action: Install a fixed supported release, or disable Remote API and verify HTTP 403 from the documented SOAP Axis endpoint. Source: https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html; reviewed 2026-11-17.

- Atlassian Data Center November 17, 2026 bulletin (security-advisory): Atlassian aggregates 266 high- and 52 critical-severity third-party CVEs fixed during the month, while assessing the bulletin items as non-critical in product context. Scope: Fixed targets include Bitbucket 10.5.2, 10.2.9 LTS or 9.4.27 LTS; Confluence 11.0.1, 10.2.20 LTS, or 9.2.27/9.2.28 LTS; and Jira/JSM 11.3.13 LTS or 10.3.27 LTS. Conditions: Installed product, branch, bundled dependency, and Marketplace app compatibility determine applicability. Action: Upgrade each Data Center product to a fixed supported target, preferring the vendor-recommended LTS where appropriate, and validate app compatibility. Source: https://confluence.atlassian.com/security/security-bulletin-november-17-2026-1874690748.html; reviewed 2026-11-18.




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







## Mattermost Self-Hosted

Self-hosted team messaging and collaborative operational workflows on customer infrastructure.

- Listing: https://launchinyourcloud.com/directory/mattermost/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, oci, aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Team Edition; commercial Enterprise offerings and separately licensed components; inspect the selected edition
- Licensing model: open-source
- Installation: Linux binary/packages or Mattermost Kubernetes Operator; provider architectures and Azure/OCI Marketplace guides
- Architecture: Customer-operated application with PostgreSQL and file/object storage
- Operations: Customer maintains the deployment, database, storage, upgrades and availability; subscriptions govern supported enterprise capabilities.
- Product website: https://mattermost.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

Team Edition is intended for small teams and lacks the commercial governance and enterprise identity capabilities. Enterprise Entry has limits; paid features require the applicable subscription. The current Docker Compose guide is for evaluation/testing and is not recommended for production/HA. The vendor provides AWS and Google Cloud self-hosted architectures alongside Azure VM and OCI OKE deployment guides. Mattermost 12.0.2 and the November 5 patches for maintained 11.x branches contain medium-to-high severity security fixes. For v12 upgrades, verify community and custom plugin compatibility.

The listed self-hosted family includes MIT Team Edition and commercial Enterprise offerings with proprietary capabilities and feature entitlements. The license of a public core, community build or plugin must not be applied to the complete Enterprise distribution.

Production documentation uses persistent Linux application hosts or Kubernetes, PostgreSQL and file storage. Azure provisions a VM scale set; the OCI option provisions OKE and managed database/storage components. Mattermost 12 drops RHEL 7 and 8, requires glibc 2.34 or later, PostgreSQL 15 or later, and OpenSearch 2.x or later.


Cloud evidence scope: Official customer-subscription Azure VM and customer-tenancy Oracle OKE guides establish these paths; unreviewed provider badges are omitted.

### Category fit

- collaboration: Team channels, messaging, file sharing and collaborative operational workflows; production scale, identity and governance capabilities depend on edition.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/deployment-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mattermost.com/deployment-guide/deployment-architecture (checked 2026-11-12). 


### Cloud deployment evidence

- Mattermost customer cloud deployment on Azure (azure): https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm
  The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Mattermost customer cloud deployment on Oracle Cloud (oci): https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke
  The vendor documents the full Mattermost application in the customer Azure subscription or OCI tenancy. The OKE Marketplace option uses Enterprise Edition; Kubernetes/Operator and enterprise features require their applicable plan, separate from Team Edition and the evaluation-only Compose example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Mattermost self-hosted provider architecture and sizing (aws, gcp): https://docs.mattermost.com/deployment-guide/deployment-architecture
  The vendor architecture builder explicitly includes AWS and Google Cloud hosting for the self-hosted application, with separate VM and Kubernetes deployment options and linked installation instructions. These are application hosting architectures, not Mattermost Cloud residency or storage adapters. Provider SKU suggestions are illustrative; size and validate the selected deployment and edition.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Editions and feature restrictions: https://docs.mattermost.com/product-overview/editions-and-offerings

- Business and licensing: https://docs.mattermost.com/product-overview/faq-license

- Linux deployment: https://docs.mattermost.com/deployment-guide/server/deploy-linux

- Kubernetes deployment: https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes

- Container deployment caveats: https://docs.mattermost.com/deployment-guide/server/deploy-containers

- Azure Native VM deployment: https://docs.mattermost.com/deployment-guide/server/linux/deploy-azure-native-vm

- Oracle OKE deployment: https://docs.mattermost.com/deployment-guide/server/kubernetes/deploy-k8s-oke

- Licensing and edition terms: https://docs.mattermost.com/developers/integrate/plugins/source-available-license

- Mattermost self-hosted provider architecture and sizing: https://docs.mattermost.com/deployment-guide/deployment-architecture

- Mattermost v12 security and upgrade changelog: https://docs.mattermost.com/product-overview/mattermost-v12-changelog

### Licensing sources

- https://docs.mattermost.com/product-overview/editions-and-offerings

- https://docs.mattermost.com/product-overview/faq-license

- https://docs.mattermost.com/developers/integrate/plugins/source-available-license

### Infrastructure sources

- https://docs.mattermost.com/deployment-guide/server/deploy-linux

- https://docs.mattermost.com/deployment-guide/server/deploy-kubernetes

- https://docs.mattermost.com/product-overview/mattermost-v12-changelog


### 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 current SAML documentation lists Entry, Professional, Enterprise and Enterprise Advanced. It distinguishes tested Okta, OneLogin and ADFS integrations from custom identity providers that require validation. Scope: Current Mattermost commercial distribution plan names; not a blanket Team Edition entitlement. Source: https://docs.mattermost.com/onboard/sso-saml (reviewed 2026-11-14).

- SCIM provisioning: Explicitly unsupported. The SAML provisioning FAQ explicitly states SCIM is not supported and refers administrators to AD/LDAP for provisioning/deactivation. This is a documented limitation, rather than an unanswered field. Scope: Current SAML user-lifecycle documentation; recheck for the selected release. Source: https://docs.mattermost.com/administration-guide/onboard/sso-saml-entraid (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official container guide uses the mattermost/docker Compose repository with application and PostgreSQL containers and an optional NGINX proxy. Configure secrets, persistent paths, domain and TLS; the quick-start Compose stack is not automatically a clustered production deployment. Scope: Self-managed Docker deployment; HA architecture is a separate design. Source: https://docs.mattermost.com/deployment-guide/server/deploy-containers.html (reviewed 2026-11-20). Deployment artifact: https://github.com/mattermost/docker. Artifact reference: Moving deployment repository; pin supported server and PostgreSQL versions.

- Minimum footprint / sizing: Documented. The upstream traditional-deployment guide gives a small-team baseline of 1 vCPU and 2 GB RAM for 1–1,000 registered users. Activity, peak file sharing, database/storage and multi-server HA alter sizing; this is not a complete 1-TB HA design. Scope: Upstream small/medium single-server baseline; enterprise multi-server sizing is separate. Source: https://docs.mattermost.com/deployment-guide/software-hardware-requirements.html (reviewed 2026-11-20).

- License pricing: Documented. The current offerings guide distinguishes commercial self-hosted Enterprise Edition from its free Entry mode and paid subscriptions. Entry has server-wide feature/usage limits; advanced entitlements require a trial or subscription. Exact paid-plan pricing and infrastructure costs remain separate. Scope: Current self-hosted Entry/Enterprise offerings; do not reuse historical Team Edition or SaaS pricing. Source: https://docs.mattermost.com/product-overview/editions-and-offerings.html (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Mattermost maintained-line security review (security-advisory): The v12 changelog records medium/high security fixes and important runtime and plugin compatibility changes. Scope: Mattermost 12.0.2 and the maintained 11.x patches identified in the November 5 security notice. Conditions: Individual vulnerability details follow the vendor disclosure schedule; plugins, PostgreSQL and optional search integrations have separate compatibility requirements. Action: Use the appropriate maintained-line patch. For v12, review plugin compatibility, glibc 2.34+, PostgreSQL 15+ and OpenSearch 2.x+ where used. Source: https://docs.mattermost.com/product-overview/mattermost-v12-changelog; reviewed 2026-11-17.



