
# Customer support on AWS

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

Canonical page: https://launchinyourcloud.com/clouds/aws/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: AWS account
- 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.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

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

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





## Deskpro Private — Self-Hosted

Commercial helpdesk installed on customer servers or in customer-controlled private infrastructure.

- Listing: https://launchinyourcloud.com/directory/deskpro-private/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Deskpro Private subscription; chosen plan and order terms apply
- Licensing model: commercial-only
- Installation: Deskpro Private implementation with vendor deployment guidance
- Architecture: Persistent Windows or Linux server installation, with single-server and multi-server options documented by the vendor.
- Operations: Customer controls update timing, backups, network exposure and self-hosted infrastructure, with vendor support and implementation arrangements.
- Product website: https://www.deskpro.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The current product is named Deskpro Private and includes customer-server deployment. Scope excludes Deskpro Cloud. Optional AI models and external integrations require deployment and data-flow choices; customer operation does not automatically mean every integration runs locally.

Commercial Deskpro Private subscription software. Confirm chosen plan, agent entitlements and deployment services in the order; this entry does not classify the separate hosted Cloud product.

Persistent Windows or Linux server installation, with single-server and multi-server options documented by the vendor.


### Category fit

- customer-support: Agent ticketing, shared inboxes, knowledge base and support automation in a customer-operated private deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.deskpro.com/blog/deskpro-cloud-and-deskpro-private-are-now-available-in-aws-marketplace (checked 2026-11-12). 


### Cloud deployment evidence

- Deskpro Private AWS VPC deployment (aws): https://www.deskpro.com/blog/deskpro-cloud-and-deskpro-private-are-now-available-in-aws-marketplace
  The vendor explicitly offers Deskpro Private deployment inside a customer Amazon VPC, including optional Bedrock access through PrivateLink. Review the installation package and license; support-site instructions for other providers were not publicly readable during this check.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated environments and operations: https://www.deskpro.com/cloud-vs-on-premise

- Private helpdesk capabilities: https://www.deskpro.com/private

- Private product plans and commercial scope: https://www.deskpro.com/pricing/private

### Licensing sources

- https://www.deskpro.com/pricing/private

### Infrastructure sources

- https://www.deskpro.com/cloud-vs-on-premise


### 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. Deskpro publishes a distinct Private AMI offer, separate from Deskpro Cloud. The reviewed image is 2.26.5; the offer says the software license is purchased externally and AWS infrastructure is billed separately. Scope: Deskpro Private vendor AMI; not the SaaS offer. Source: https://aws.amazon.com/marketplace/pp/prodview-kmtvuyl6ztfyw (reviewed 2026-11-14). Offer prodview-kmtvuyl6ztfyw: Deskpro; AMI; external software license; package 2.26.5; https://aws.amazon.com/marketplace/pp/prodview-kmtvuyl6ztfyw.

- Cloud commitment eligibility: Sources checked — unresolved. The vendor announcement mentions AWS commitments, while the reviewed Private AMI offer says software licensing is externally billed. Neither establishes credit for those external license charges under a particular buyer agreement. Scope: Private AMI software charges versus AWS infrastructure; contractual eligibility unresolved. Source: https://aws.amazon.com/marketplace/pp/prodview-kmtvuyl6ztfyw (reviewed 2026-11-14). Supporting source: Vendor marketplace announcement — https://www.deskpro.com/blog/deskpro-cloud-and-deskpro-private-are-now-available-in-aws-marketplace.

- Single sign-on: Documented. Deskpro documents SAML 2.0 authentication for agents and customers, configured separately in their Auth & SSO settings. Register the correct ACS/metadata URLs and signing certificate, and configure account matching/sync policy. The vendor advertises SAML without an additional integration fee; confirm the selected Private plan and deployment version. Scope: Deskpro application SAML integration; selected self-hosted plan/version still governs contractual entitlements. Source: https://www.deskpro.com/apps/saml (reviewed 2026-11-20). Supporting source: Vendor SAML setup guide — https://support.deskpro.com/en-US/guides/admin-guide/apps-integrations/authentication-and-sso-1/saml-setup-1. Supporting source: Current self-hosted Private plans — https://www.deskpro.com/pricing/private.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. The vendor explicitly documents an on-premises, fully air-gapped option for Deskpro Private. Agree package, licensing, updates and any selected AI dependencies in the implementation scope. Scope: Deskpro Private air-gapped option; vendor statement rather than a deployed test. Source: https://www.deskpro.com/private (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The Deskpro-published AWS Marketplace AMI deploys its Private Controller; the reviewed offer lists DPC 2.26.5. Its usage instructions require setting the controller master password and completing appliance setup. The controller manages the application stack; an AMI boot is not a configured HA deployment or an entitlement to every optional component. Scope: Vendor-published DPC appliance delivery; not an interchangeable generic Linux image. Source: https://aws.amazon.com/marketplace/pp/prodview-kmtvuyl6ztfyw (reviewed 2026-11-20). Deployment artifact: https://aws.amazon.com/marketplace/pp/prodview-kmtvuyl6ztfyw. Artifact reference: Deskpro Private Controller 2.26.5 offer; choose the matching regional AMI/version.

- Minimum footprint / sizing: Documented. The Deskpro-published AWS image instructions specify at least 2 CPUs and 4 GB RAM, recommending 4 CPUs and 8 GB. This is the DPC appliance starting point, not a sized cluster or a 100-user, 1 TB HA design; storage, attachments, search and optional private AI need separate sizing. Scope: Vendor AWS Marketplace AMI usage instructions; DPC release and workload boundaries apply. Source: https://aws.amazon.com/marketplace/pp/prodview-kmtvuyl6ztfyw (reviewed 2026-11-20).

- License pricing: Documented. Deskpro Private is quote-based commercial software. The listed Team, Professional and Enterprise packages start with 10, 20 and 35 agent licences respectively; staging, clustering, non-DPC deployment and private-AI entitlements vary. Obtain the applicable self-hosted agreement and quote; the vendor-managed VPC plan is a separate operating model. Scope: Current Private plans; no public numeric software price established. Source: https://www.deskpro.com/pricing/private (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Discourse

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

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


### Community and maintenance

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

Reviewed 2026-11-14.

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

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

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

### Sources

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

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

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

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

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

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

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

### Licensing sources

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

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

### Infrastructure sources

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

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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




## ManageEngine ServiceDesk Plus On-Premises

Customer-operated IT service management and asset management software with a vendor-published Enterprise AMI for AWS.

- Listing: https://launchinyourcloud.com/directory/manageengine-servicedesk-plus-on-premises/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary editions; the reviewed AWS Enterprise AMI is usage-priced, while direct purchases have separate licensing terms.
- Licensing model: commercial-only
- Installation: Vendor-published AWS Enterprise AMI (10 technicians/500 nodes); other on-premises packages require separate deployment and entitlement review
- Architecture: Customer-operated application VM and database/storage in AWS; the reviewed AMI is an Enterprise Windows Server package.
- Operations: Customer manages VM and OS security, database, storage, backups, email and identity integrations, upgrades, scaling and the BYOL license.
- Product website: https://www.manageengine.com/products/service-desk/on-premises/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers ServiceDesk Plus On-Premises, not Cloud or MSP. The AWS AMI packages build 15340 while current on-premises notes identify 16030. The vendor Azure collection links ServiceDesk Plus On-Demand and does not establish this edition’s customer-VM deployment. Absence of an Azure badge is an evidence gap, not incompatibility.

The selected AWS Enterprise AMI is paid usage software, not a verified BYOL image. Direct Standard, Professional and Enterprise terms differ.

The reviewed vendor AMI runs the application on provisioned customer EC2 with persistent application/database state.


### Category fit

- customer-support: Provides an IT service desk for incidents, service requests, problems, changes, assets and a knowledge base.

- workflow-automation: Automates service-management routing, approvals, SLAs and change/request workflows.

### Deployment boundaries


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


### Cloud deployment evidence

- ServiceDesk Plus Enterprise in customer EC2 (aws): https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32
  ZOHO Corporation publishes the paid Enterprise 10 Tech/500 Nodes AMI, package 15340 on Windows Server 2025. This is not the generic BYOL claim; application build and package version must be checked separately.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Edition: ServiceDesk Plus Enterprise Edition (10 Tech 500 Nodes). Versions: 15340.


### Sources

- ManageEngine solutions in the customer's AWS infrastructure: https://www.manageengine.com/aws-marketplace-listing.html?cat=MECloudsolutions&loc=ProdMenu&pos=SDP

- ServiceDesk Plus On-Premises: https://www.manageengine.com/products/service-desk/on-premises/

- ServiceDesk Plus pricing and editions: https://www.manageengine.com/ca/products/service-desk/pricing.html

- ServiceDesk Plus Enterprise in customer EC2: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32

### Licensing sources

- https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32

- https://www.manageengine.com/ca/products/service-desk/pricing.html

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32


### Buyer diligence


Research coverage: 12/12 fields (100%); 8 documented, 4 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: Edition-dependent. ZOHO Corporation’s AWS offer is ServiceDesk Plus Enterprise Edition (10 Tech 500 Nodes), AMI package 15340 on Windows Server 2025. This is a paid usage offer, not the generic BYOL deployment described elsewhere on the vendor site. The reviewed Azure link resolves to ServiceDesk Plus On-Demand, not proof of this on-premises edition. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32 (reviewed 2026-11-18). Supporting source: Vendor Azure collection and On-Demand link — https://www.manageengine.com/uk/microsoft-azure-marketplace-listing.html?cat=MECloudsolutions&loc=ProdMenu&pos=OpMgr_MSP. Offer prodview-2bykbzgjbsq32: ZOHO Corporation; Amazon Machine Image (AMI); package 15340; https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32.

- Cloud commitment eligibility: Sources checked — unresolved. The paid AMI offer does not state whether its charges count toward the buyer’s AWS commitment. Confirm the exact offer, region and contract with procurement; do not transfer generic BYOL or SaaS terms. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32 (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Documented. ManageEngine documents SAML SSO for ServiceDesk Plus On-Premises using ADSelfService Plus as IdP, HTTPS, login/logout URLs and an X.509 certificate. The ServiceDesk administrator configures the SAML service-provider settings. Check the purchased build and IdP entitlement. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://www.manageengine.com/products/self-service-password/help/admin-guide/Application/sso/servicedesk-plus.html (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The on-premises release history documents Microsoft Entra user import and synchronization, including delta imports and deleted users. That is not evidence of a SCIM endpoint, its supported operations or deprovisioning semantics. Obtain a build/edition-specific SCIM guide before asserting support. Cisco Duo’s current ServiceDesk Plus SAML integration explicitly has no SCIM 2.0 user/group provisioning. That settles the reviewed Duo connector, not whether another supported on-premises integration exists. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://www.manageengine.com/products/service-desk/on-premises/readme.html (reviewed 2026-11-18). Supporting source: Cloud-only provisioning app, now deprecated; not on-premises SCIM — https://www.manageengine.com/products/service-desk/customizations/cloud-provisioning-tool.html. Supporting source: Duo’s explicit connector provisioning limitation — https://duo.com/docs/sso-manageengine-servicedesk-plus.

- Compliance attestations: Documented. BSI’s issuer register confirms Zoho’s ISO/IEC 27001:2022 ISMS, IS 642819, includes development/provision of on-premises software; its site scope explicitly names ManageEngine. The November 13, 2026 revision expires August 21, 2028. BSI also confirms associated ISO/IEC 27701:2019 PIMS PM 732705 through that date. These are supplier management-system assurances, not certification of a buyer’s ServiceDesk Plus installation. The private SOC report and customer controls need separate review. Scope: Issuer-verified Zoho/ManageEngine organisational ISMS/PIMS scope, including on-premises software development/provision; not a customer-deployment attestation. Source: https://www.bsigroup.com/en-ID/products-and-services/assessment-and-certification/validation-and-verification/client-directory-certificate/IS%20642819/ (reviewed 2026-11-18). Supporting source: On-premises product security-development practices — https://www.manageengine.com/products/service-desk/sdp-security-policy.html. Supporting source: Issuer register: related privacy management system — https://www.bsigroup.com/en-ID/products-and-services/assessment-and-certification/validation-and-verification/client-directory-certificate/PM%20732705/. Supporting source: Issuer site scope explicitly names ManageEngine — https://www.bsigroup.com/en-ID/products-and-services/assessment-and-certification/validation-and-verification/client-directory-profile/ZOHO_C-0047575501-000/. Supporting source: Product division and cloud-only assurance boundaries — https://www.manageengine.com/compliance.html.

- Security controls: Documented. The on-premises SAML guide requires HTTPS and explicit identity-provider certificate configuration. AWS image setup also instructs changing the initial administrator credentials. Current release notes document security fixes, so the older Marketplace package needs its own patch review. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://www.manageengine.com/products/self-service-password/help/admin-guide/Application/sso/servicedesk-plus.html (reviewed 2026-11-18). Supporting source: AMI setup and version — https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32. Supporting source: Current on-premises security maintenance — https://www.manageengine.com/products/service-desk/on-premises/readme.html.

- Air-gapped operation: Sources checked — unresolved. On-premises installation does not establish disconnected activation, updates, asset discovery or external integration behavior. Confirm the offline licence/update procedure and required outbound connections for the selected Enterprise build and modules. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://www.manageengine.com/products/service-desk/on-premises/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The vendor’s Enterprise AMI installs ServiceDesk Plus in customer EC2; its usage instructions cover instance launch, administrator login and password changes. Record AMI/package 15340 and the Windows/database configuration. A separate, current source-controlled IaC template was not established. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32 (reviewed 2026-11-18).

- Minimum footprint / sizing: Documented. The AWS offer recommends m4.xlarge for its 10-technician/500-node Enterprise package. This is a provider-image reference, not a current HA sizing guarantee. One hundred internal requesters do not specify technician licences, managed asset count, ticket volume or database capacity. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32 (reviewed 2026-11-18).

- License pricing: Documented. The reviewed Enterprise 10 Tech/500 Nodes AMI publishes a software usage rate of USD 1.034/hour, with AWS infrastructure additional. This scoped image price does not price other editions, extra technicians/assets, HA licensing or a direct BYOL purchase. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32 (reviewed 2026-11-18). Supporting source: Direct edition/pricing comparison — https://www.manageengine.com/ca/products/service-desk/pricing.html.

- Operating cost estimate: Sources checked — unresolved. The AMI publishes a software rate, but a complete estimate still needs technician/asset counts, ticket and attachment growth, database choice, HA/failover licensing, Windows and instance costs, backup retention and upgrade design. Do not treat the 10-technician package as a 100-user HA quote. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32 (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. ServiceDesk Plus On-Premises build 16030 was released November 4, 2026. Its notes include framework and security fixes. The reviewed AWS AMI is package 15340; it must not be represented as already containing build 16030. Scope: ManageEngine ServiceDesk Plus On-Premises: selected customer-operated edition. Source: https://www.manageengine.com/products/service-desk/on-premises/readme.html (reviewed 2026-11-18). Supporting source: Older Marketplace package — https://aws.amazon.com/marketplace/pp/prodview-2bykbzgjbsq32.




### Security and lifecycle reviews

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

- ServiceDesk Plus build 16030 security fixes (security-advisory): The on-premises release fixes stored XSS in asset-name barcode list views and request API scope issues, alongside framework updates. Scope: Build 16030 release entries SD-144708 and SD-144375; the notes do not establish a complete affected-version range or confirm the older AMI has these patches. Conditions: The named asset view and request API operations determine exposure. MSP and Cloud are separate products and are not covered by this record. Action: Review the vendor’s supported upgrade path, patch the selected on-premises build and verify the AWS image’s actual installed version. Source: https://www.manageengine.com/products/service-desk/on-premises/readme.html; reviewed 2026-11-18.




## Request Tracker (RT)

Self-hosted ticketing, request tracking and service workflows.

- Listing: https://launchinyourcloud.com/directory/request-tracker/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Request Tracker application and persistent database in the Best Practical AWS AMI.
- 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://bestpractical.com/rt
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor image is RT 6.0.3, while upstream 6.0.4 is a separate release. Check application updates after launching the AMI. Upgrade the RT 6.0.3 AWS image’s application through the supported 6.0.4-or-later process and check database/plugin compatibility.

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

Request Tracker application and persistent database in the Best Practical AWS AMI. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted ticketing, request tracking and service workflows.

### Deployment boundaries


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


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-j7nw37pratobq
  Request Tracker application and persistent database in the Best Practical AWS AMI. The vendor image is RT 6.0.3, while upstream 6.0.4 is a separate release. Check application updates after launching the AMI.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes sunnavy, obra, alexmv, 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/bestpractical/rt/graphs/contributors

- Upstream project: https://github.com/bestpractical/rt

### Sources

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

- GitHub COPYING (GPL-2.0): https://raw.githubusercontent.com/bestpractical/rt/stable/COPYING

- GitHub Releases: https://github.com/bestpractical/rt/releases

- Request Tracker 6.0.4 security release: https://github.com/bestpractical/rt/releases/tag/rt-6.0.4

### Licensing sources

- https://raw.githubusercontent.com/bestpractical/rt/stable/COPYING

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-j7nw37pratobq


### Buyer diligence


Research coverage: 6/12 fields (50%); 5 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 reviewed AWS offer delivers Amazon Machine Image (AMI) from Best Practical Solutions. Its package version is RT 6.0.3 (August 2026); verify the contained application and required entitlements separately. Scope: Request Tracker (RT) selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-j7nw37pratobq (reviewed 2026-11-19). Offer prodview-j7nw37pratobq: Best Practical Solutions; Amazon Machine Image (AMI); package RT 6.0.3 (August 2026); https://aws.amazon.com/marketplace/pp/prodview-j7nw37pratobq.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. RT 6.0.4 documents web-server SSO using REMOTE_USER, including Kerberos through Apache modules. Configure WebRemoteUserAuth, user matching/autocreation, fallback and continuous-session policy; the external system handles its own MFA. LDAP/password lookup and REST tokens are separate authentication paths. Scope: Versioned RT external user authentication through a configured web-server trust boundary. Source: https://docs.bestpractical.com/rt/6.0.4/authentication.html (reviewed 2026-11-20). Supporting source: Versioned RT authentication configuration — https://docs.bestpractical.com/rt/6.0.4/RT_Config.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The RT 6.0.4 distribution documents configure, dependency checks, installation, database initialization and web-server setup. Set the database driver, service permissions, mail gateway, HTTPS and secrets for your topology. The upstream source distribution and third-party marketplace image are separately versioned artifacts. Scope: Published RT 6.0.4 source installation. Source: https://docs.bestpractical.com/rt/6.0.4/README.html (reviewed 2026-11-20). Deployment artifact: https://github.com/bestpractical/rt/releases/tag/rt-6.0.4. Artifact reference: rt-6.0.4.

- Minimum footprint / sizing: Sources checked — unresolved. The versioned manual identifies the Perl/web-server and supported relational database dependencies but does not establish a workload-specific whole-system CPU/RAM/storage minimum. Ticket volume, attachments, indexing and mail processing drive sizing; marketplace instance options are not a 100-user, 1 TB HA capacity plan. Scope: RT 6.0.4 dependency guidance; numeric production and HA sizing remains unconfirmed. Source: https://docs.bestpractical.com/rt/6.0.4/README.html (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Request Tracker (RT); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/bestpractical/rt/stable/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Request Tracker 6.0.4 security release (security-advisory): Best Practical recommends upgrading for the multiple security issues listed in RT 6.0.4. Scope: RT 6.0.4 security corrections; individual issues have separate conditions and ranges. The reviewed AWS AMI is RT 6.0.3. Conditions: Launching the older vendor AMI does not apply the newer application security fixes. Action: Upgrade the RT 6.0.3 AWS image’s application through the supported 6.0.4-or-later process and check database/plugin compatibility. Source: https://github.com/bestpractical/rt/releases/tag/rt-6.0.4; reviewed 2026-11-19.




## Znuny

Open-source service desk and ticketing system from the Znuny project.

- Listing: https://launchinyourcloud.com/directory/znuny/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: TurnKey Debian appliance with Znuny application, database and mail processing.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://www.znuny.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

TurnKey 19.0.3 is the appliance version and packages the Znuny 6.5 LTS line; it is not the upstream application version. Review both appliance and application updates.

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

TurnKey Debian appliance with Znuny application, database and mail processing. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Open-source service desk and ticketing system from the Znuny project.

### Deployment boundaries


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


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-ebokmjetfz4wg
  TurnKey Debian appliance with Znuny application, database and mail processing. TurnKey 19.0.3 is the appliance version and packages the Znuny 6.5 LTS line; it is not the upstream application version. Review both appliance and application updates.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes martini, mgruner, carlosfrodriguez, 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/znuny/Znuny/graphs/contributors

- Upstream project: https://github.com/znuny/Znuny

### Sources

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

- GitHub COPYING (GPL-3.0): https://raw.githubusercontent.com/znuny/Znuny/dev/COPYING

- GitHub Releases: https://github.com/znuny/Znuny/releases

### Licensing sources

- https://raw.githubusercontent.com/znuny/Znuny/dev/COPYING

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-ebokmjetfz4wg


### Buyer diligence


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

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


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

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The current guide documents native SAML 2.0 for agents and customers, with separate provider/application settings; native SAML was added in 7.3.1. It also documents web-server SSO through REMOTE_USER with Kerberos, OIDC or SAML modules. Match the selected package version, account attributes, group sync and trust boundary. Scope: Current Znuny 7.3 authentication; older/LTS packages need version-specific verification. Source: https://doc.znuny.org/znuny/admin/usermanagement/saml_configuration/ (reviewed 2026-11-20). Supporting source: Native SAML introduction in Znuny 7.3.1 — https://doc.znuny.org/znuny/releases/7_3_1/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The current guide installs Znuny 7.3.8 from the vendor RPM or source archive, with checksum/signature verification, Perl dependencies, database and Apache setup, web installation and cron jobs. Confirm the supported OS/database and configure TLS, secrets and backups; a marketplace image has its own release and terms. Scope: Vendor-native installation instructions; not a certification of a separately published cloud image. Source: https://doc.znuny.org/znuny/installation/index.html (reviewed 2026-11-20). Deployment artifact: https://download.znuny.org/releases/znuny-7.3.8.tar.gz. Artifact reference: 7.3.8 vendor source distribution; verify its published signature and checksum.

- Minimum footprint / sizing: Sources checked — unresolved. The current native-installation guide establishes the web/database/Perl stack but does not specify a current whole-system CPU/RAM/storage minimum for this workload. Database packet/buffer settings are not host capacity. Size agents, tickets, attachments, search and redundancy; older OTRS/LTS sizing is not automatically a Znuny 7.3 guarantee. Scope: Current upstream installation topology; numeric workload and HA sizing remains unconfirmed. Source: https://doc.znuny.org/znuny/installation/index.html (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Znuny; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/znuny/Znuny/dev/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






