
# Customer support on Google Cloud

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

Canonical page: https://launchinyourcloud.com/clouds/gcp/customer-support/
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.

3 listings.


## Chatwoot Self-Hosted

Self-hosted customer-support inbox combining live chat, email and messaging conversations.

- Listing: https://launchinyourcloud.com/directory/chatwoot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp, aws, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Community Edition; proprietary enterprise features and paid self-hosted plans
- Licensing model: open-source
- Installation: Production Docker Compose, Linux VM or Kubernetes deployment
- Architecture: Customer-operated application and workers with PostgreSQL, Redis and upload storage
- Operations: Customer maintains the server, database, storage, updates and channel integrations; support differs by plan.
- Product website: https://www.chatwoot.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Community Edition excludes paid features such as SSO/SAML, SLA policies and Captain AI. Captain integrations may send data to external model providers. Official Azure and Google Cloud deployment guides are marked work in progress; validate their instructions against current requirements before production.

The self-hosted offering combines an MIT Community Edition with proprietary Enterprise feature code. Paid feature entitlements are distinct from community source-code rights; premium support alone is not the basis for this classification.

The production Docker guide runs Rails application/worker services alongside PostgreSQL and Redis, or connects to separately managed equivalents. Official cloud guides use VMs and also identify Kubernetes paths.


Cloud evidence scope: Official Azure VM and Google Compute Engine guides exist and are marked work in progress; other cloud badges are not inferred.

### Category fit

- customer-support: Shared support inbox, live chat, email and messaging channels, with automation and reporting; feature entitlements depend on edition.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/azure (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/gcp (checked 2026-11-12). 

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/aws (checked 2026-11-12). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developers.chatwoot.com/self-hosted/deployment/digitalocean (checked 2026-11-12). 


### Cloud deployment evidence

- Chatwoot self-hosted deployment on AWS (aws): https://developers.chatwoot.com/self-hosted/deployment/aws
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on Azure (azure): https://developers.chatwoot.com/self-hosted/deployment/azure
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on Google Cloud (gcp): https://developers.chatwoot.com/self-hosted/deployment/gcp
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Chatwoot self-hosted deployment on digitalocean (digitalocean): https://developers.chatwoot.com/self-hosted/deployment/digitalocean
  The vendor documents creating cloud infrastructure and installing the Chatwoot application, rather than just connecting an external service. Some VM walkthroughs still reference Ubuntu 20.04; use current Chatwoot runtime requirements, supported images and the relevant upgrade instructions before production deployment.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Community support functionality: https://www.chatwoot.com/community

- Production Docker installation: https://developers.chatwoot.com/self-hosted/deployment/docker

- Edition licensing: https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition

- Self-hosted plan features: https://www.chatwoot.com/pricing/self-hosted-plans

- Azure deployment: https://developers.chatwoot.com/self-hosted/deployment/azure

- Google Cloud deployment: https://developers.chatwoot.com/self-hosted/deployment/gcp

- Chatwoot self-hosted deployment on aws: https://developers.chatwoot.com/self-hosted/deployment/aws

- Chatwoot self-hosted deployment on digitalocean: https://developers.chatwoot.com/self-hosted/deployment/digitalocean

### Licensing sources

- https://www.chatwoot.com/hc/user-guide/articles/1677776492-enterprise-edition

- https://www.chatwoot.com/pricing/self-hosted-plans

### Infrastructure sources

- https://developers.chatwoot.com/self-hosted/deployment/docker


### 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: Edition-dependent. SAML SSO is included in Enterprise, but not Community or Premium Support. Scope: Self-hosted plan comparison. Source: https://www.chatwoot.com/pricing/self-hosted-plans (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 guide links an upstream Compose stack with Rails, Sidekiq, PostgreSQL and Redis. Its application image uses latest; pin a compatible release, set secrets, and configure TLS, storage and backups. Scope: Production Docker deployment. Source: https://developers.chatwoot.com/self-hosted/deployment/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/chatwoot/chatwoot/blob/develop/docker-compose.production.yaml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Documented. The technical requirements page specifies 4 CPU cores and 4 GB RAM for its smallest example workload; the pricing FAQ separately says 2 CPU cores and 4 GB. Resolve this difference for your workload before sizing. Scope: Technical requirements; compare the pricing FAQ. Source: https://developers.chatwoot.com/self-hosted/deployment/requirements (reviewed 2026-11-14). Supporting source: Self-hosted pricing FAQ: production starting point — https://www.chatwoot.com/pricing/self-hosted-plans.

- License pricing: Documented. Community is free to self-host. The current page lists Premium Support at $19 and Enterprise at $99 per agent/month; SAML is Enterprise-only. These are software/support plan units, excluding your infrastructure, taxes and connected AI usage. Confirm currency and billing terms at checkout. Scope: Current self-hosted edition comparison; not a hosted subscription or a total operating-cost estimate. Source: https://www.chatwoot.com/pricing/self-hosted-plans (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.



### Vendor alternative positioning

Positioning is not a finding of feature parity.

- zendesk: The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows. Source: https://www.chatwoot.com/pricing/self-hosted-plans; reviewed 2026-11-16.

- intercom: The self-hosted plan page positions Chatwoot as an alternative for customer-support workflows. Source: https://www.chatwoot.com/pricing/self-hosted-plans; reviewed 2026-11-16.





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







## Jira Service Management Data Center

Commercial self-managed IT service management platform deployed on customer-operated infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/jira-service-management-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 Jira Data Center installation
- Architecture: Single-node or clustered Jira Service Management application nodes with an external database, load balancer, shared home, indexes and optional dedicated nodes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, email, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/jira/service-management/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 Jira Service Management Data Center, not Atlassian 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). All Jira Service Management Data Center versions before the fixed 5.12.40, 10.3.26, or 11.3.12 releases are affected by unauthenticated access to specifically named files under the web application root. Upgrade immediately to a fixed or later version; if patching is delayed, restrict internet access and apply Atlassian's documented WAF or Tomcat rewrite mitigation. 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.

Jira Service Management Data Center runs persistent Jira application services with durable database, shared-home and local-index storage.


### Category fit

- customer-support: Provides self-managed service desks, request portals, queues, knowledge integration and service-management workflows.

- devops: Supports IT service management, incident response, change coordination and development-to-operations workflows.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Jira Service Management Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html
  Atlassian documents Jira Service Management Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Install Jira Data Center: https://confluence.atlassian.com/security/installing-jira-data-center-1409092898.html

- Run Jira Service Management Data Center on Kubernetes: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html

- Jira Service Management Data Center architecture: https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.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 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/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.html

- https://confluence.atlassian.com/security/jira-service-management-data-center-architecture-and-infrastructure-options-1409093042.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. The Data Center SSO guide explicitly covers Jira Service Management 5.15+. SAML login can include customer-portal logins when enabled; application access remains separately configured. Scope: Jira Service Management Data Center 5.15+; not Atlassian Guard cloud customer provisioning. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16).

- 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: Jira Service Management Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-jira-service-management-data-center-on-a-kubernetes-cluster-1409093034.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 vendor’s 11.3.x extra-large benchmark uses three r5.8xlarge application nodes, 30 GB Java heap per node and a separate db.m6i.4xlarge PostgreSQL 16.9 database in AWS ap-southeast-2. Its dataset includes about 3.1 million issues and 6,471 agents. This is a test configuration, not a universal minimum or a performance/cost guarantee. Scope: JSM 11.3.x extra-large benchmark; representative workload sizing remains necessary. Source: https://confluence.atlassian.com/servicemanagement/jira-service-management-11-3-x-long-term-support-release-performance-report-1689289059.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: Jira Service Management 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.3.13, released 2026-11-05. 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/jira-servicedesk.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/SERVICEDESK/JIRA+Service+Management+11.3.x+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.

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



