
# Customer support on Azure

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

Canonical page: https://launchinyourcloud.com/clouds/azure/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: Subscription and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal (checked 2026-11-20).
- Network: Virtual Network (VNet)
- Identity and access: Microsoft Entra identities and Azure RBAC
- Installation guidance: Bicep/ARM templates or Terraform; review deployment scope and role assignments.
- Guidance source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview
- Guidance reviewed: 2026-11-10


### Private offers

Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment.
Source: https://learn.microsoft.com/en-us/marketplace/private-offers-overview (reviewed 2026-11-14).

### Private connectivity

Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability.
Source: https://learn.microsoft.com/en-us/azure/private-link/private-link-overview (reviewed 2026-11-14).

### Cross-tenant operations

Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor.
Source: https://learn.microsoft.com/en-us/azure/lighthouse/overview (reviewed 2026-11-14).

### Government environments

Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government.
Source: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome (reviewed 2026-11-14).

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

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





## django-helpdesk

Django-based helpdesk for tickets, queues and support communication.

- Listing: https://launchinyourcloud.com/directory/django-helpdesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Django application, database and persistent files in a cloudimg Azure VM.
- 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://github.com/django-helpdesk/django-helpdesk
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The third-party VM is distinct from an upstream-supported appliance; confirm installed package versions and apply security updates. Use django-helpdesk 2.6.1 or a later compatible fixed build and review the public ticket and non-staff permission settings.

BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Django application, database and persistent files in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Django-based helpdesk for tickets, queues and support communication.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.django-helpdesk-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.django-helpdesk-ubuntu-24-04
  Django application, database and persistent files in a cloudimg Azure VM. The third-party VM is distinct from an upstream-supported appliance; confirm installed package versions and apply security updates.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes gwasser, rossp, uhurusurfa, 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/django-helpdesk/django-helpdesk/graphs/contributors

- Upstream project: https://github.com/django-helpdesk/django-helpdesk

### Sources

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.django-helpdesk-ubuntu-24-04

- GitHub LICENSE (BSD-3-Clause): https://raw.githubusercontent.com/django-helpdesk/django-helpdesk/main/LICENSE

- GitHub Releases (v2.6.1): https://github.com/django-helpdesk/django-helpdesk/releases

- GitHub Commits: https://github.com/django-helpdesk/django-helpdesk/commits/main

- django-helpdesk public ticket access checks: https://github.com/django-helpdesk/django-helpdesk/security/advisories/GHSA-9g24-qf73-cjxh

### Licensing sources

- https://raw.githubusercontent.com/django-helpdesk/django-helpdesk/main/LICENSE

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.django-helpdesk-ubuntu-24-04


### Buyer diligence


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

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


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: django-helpdesk selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.django-helpdesk-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.django-helpdesk-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.django-helpdesk-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.django-helpdesk-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.django-helpdesk-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The published v2.6.1 package integrates Django users and login views, but its installation/settings material does not establish a specific SAML/OIDC identity-provider integration. Using Django authentication backends is a customization path, not confirmation that a marketplace image includes configured SSO. Verify the backend, callback and user/permission mapping. Scope: Published Django application authentication hooks; external federation remains unconfirmed. Source: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/settings.rst (reviewed 2026-11-20). Supporting source: Published application login routes — https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/src/helpdesk/urls.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v2.6.1 standalone guide supplies a setup script and Compose stack; it separately documents installation as a package in an existing Django application. Configure database, secrets, mail, site URL, reverse proxy and production settings. The demo server and default demo credentials are not a production deployment. Scope: Published standalone versus embedded Django installation. Source: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/standalone.rst (reviewed 2026-11-20). Deployment artifact: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/standalone/docker-compose.yml. Artifact reference: v2.6.1. Supporting source: Integration into an existing Django application — https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/install.rst.

- Minimum footprint / sizing: Sources checked — unresolved. The published installation material identifies the Python/Django application, database and production services but gives no complete CPU/RAM/storage minimum. Development/demo allocations do not establish capacity for ticket mail, attachments, concurrency or HA; obtain a workload-specific sizing plan for the selected image/version. Scope: Published application topology; numeric production sizing remains unconfirmed. Source: https://github.com/django-helpdesk/django-helpdesk/blob/v2.6.1/docs/standalone.rst (reviewed 2026-11-20).

- License pricing: Documented. BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: django-helpdesk; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/django-helpdesk/django-helpdesk/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- django-helpdesk public ticket access checks (security-advisory): The advisory describes a public ticket lookup that did not validate its secret key. Scope: Versions 0.3.0–2.6.0; patched in 2.6.1 (GHSA-9g24-qf73-cjxh). Conditions: Affected public-ticket configuration can disclose a ticket to a visitor who knows the ID and submitter email; see the full advisory for conditions. Action: Use django-helpdesk 2.6.1 or a later compatible fixed build and review the public ticket and non-staff permission settings. Source: https://github.com/django-helpdesk/django-helpdesk/security/advisories/GHSA-9g24-qf73-cjxh; reviewed 2026-11-19.




## Frappe Helpdesk

Self-hosted support desk for tickets, knowledge content and service operations.

- Listing: https://launchinyourcloud.com/directory/frappe-helpdesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Frappe Helpdesk and Frappe framework services, database, queues and files on an Azure VM.
- 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://frappe.io/helpdesk
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cloudimg image is a third-party package. Helpdesk application releases and Frappe framework versions are separate.

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

Frappe Helpdesk and Frappe framework services, database, queues and files on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted support desk for tickets, knowledge content and service operations.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04
  Frappe Helpdesk and Frappe framework services, database, queues and files on an Azure VM. The cloudimg image is a third-party package. Helpdesk application releases and Frappe framework versions are separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes RitvikSardana, kamaljohnson, aerodeval, 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/frappe/helpdesk/graphs/contributors

- Upstream project: https://github.com/frappe/helpdesk

### Sources

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/frappe/helpdesk/main/LICENSE

- GitHub Releases: https://github.com/frappe/helpdesk/releases

### Licensing sources

- https://raw.githubusercontent.com/frappe/helpdesk/main/LICENSE

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04


### Buyer diligence


Research coverage: 7/12 fields (58%); 6 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: Frappe Helpdesk selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.frappe-helpdesk-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. Helpdesk v16.2.0 redirects unauthenticated agents to the Frappe site /login page and uses the resulting Frappe session and Helpdesk roles. The framework documents Social Login Key providers including Google, Microsoft and custom providers. Configure the provider/callback and existing user/Agent records; this source-based integration finding is not a SCIM or universal SAML claim. Scope: Published Helpdesk login routing plus official framework identity configuration. Source: https://github.com/frappe/helpdesk/blob/v16.2.0/desk/src/router/index.ts (reviewed 2026-11-20). Supporting source: Framework Social Login Key configuration — https://docs.frappe.io/framework/user/en/guides/integration/social_login_key. Supporting source: Helpdesk application user and role mapping — https://github.com/frappe/helpdesk/blob/v16.2.0/helpdesk/api/auth.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v16.2.0 README documents self-hosting through the Frappe easy-install script and Helpdesk container. Its example selects the moving stable image; pin a compatible application/framework image, review the downloaded script, and configure the site, TLS, secrets, database, workers and backups. Its development Compose recipe is a different path. Scope: Published production instructions; unversioned installer URL and stable image require separate pinning. Source: https://github.com/frappe/helpdesk/blob/v16.2.0/README.md (reviewed 2026-11-20). Deployment artifact: https://frappe.io/easy-install.py. Artifact reference: easy-install.py (moving URL), referenced by Helpdesk v16.2.0 production instructions. Supporting source: Official Helpdesk installation guide — https://docs.frappe.io/helpdesk/installation.

- Minimum footprint / sizing: Sources checked — unresolved. The Helpdesk production recipe establishes the application/framework deployment but does not specify a complete CPU/RAM/storage minimum for agents, workers, database and attachments. Hosting plan allocations and development containers do not establish 100-user, 1 TB HA sizing; confirm ticket load, concurrency, mail processing and redundancy. Scope: Helpdesk-specific self-hosting guidance; whole-system production sizing remains unconfirmed. Source: https://docs.frappe.io/helpdesk/installation (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







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



