
# Project management

Project planning, delivery tracking and team work management.

Canonical page: https://launchinyourcloud.com/categories/project-management/
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.


Project planning, delivery tracking and team work management.

14 listings.


## Azure DevOps Server

Source control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.

- Listing: https://launchinyourcloud.com/directory/azure-devops-server/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary; Express is free for up to five active users, while paid Server use requires server and user entitlements plus Windows licensing.
- Licensing model: commercial-only
- Installation: Windows installer on an Azure VM with SQL Server, Azure SQL Database or Azure SQL Managed Instance
- Architecture: Customer-operated Windows application tier and SQL data tier.
- Operations: Customer operates the Azure VMs, Windows, SQL data tier, backups, patches, upgrades and Azure DevOps Server configuration.
- Product website: https://azure.microsoft.com/en-us/products/devops/
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Azure DevOps Server, not Microsoft-hosted Azure DevOps Services. Microsoft's Azure configuration installs the server on an Azure VM and can use Azure SQL Database or Azure SQL Managed Instance. Advanced configuration is unavailable on Azure VMs; use Basic or Azure configuration. SQL Server on Linux is unsupported. Only Azure receives a badge because current first-party documentation does not establish equivalent AWS or Google Cloud server deployments. Azure DevOps Server 2022.2 Patch 9, published October 13, 2026, includes security fixes and is recommended by Microsoft. Confirm the exact server generation and prerequisite patch sequence before applying it.

Azure DevOps Server is proprietary Microsoft software. Express is a no-cost license limited to five active users, not an open-source edition; broader use requires paid server/CAL or eligible Visual Studio and Azure DevOps entitlements.

Azure DevOps Server runs on customer-operated Windows application-tier VMs and requires a supported SQL Server or Azure SQL data tier.


### Category fit

- devops: Self-hosted repositories, pipelines, test plans and artifact management.

- project-management: Azure Boards provides work-item tracking, backlogs and planning within the same server.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server (checked 2026-11-17). 


### Cloud deployment evidence

- Azure DevOps Server on an Azure VM with Azure SQL (azure): https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server
  Microsoft requires Azure DevOps Server on an Azure VM for the documented Azure SQL topology and supplies Azure VM identity, networking, firewall and database steps. Application and data tiers remain in the customer's Azure environment.
  Source type: provider-guide; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Install and configure Azure DevOps Server: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- Use Azure SQL with Azure DevOps Server: https://learn.microsoft.com/en-us/azure/devops/server/install/install-azure-sql?view=azure-devops-server

- Azure DevOps Server requirements: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server

- Azure DevOps Server pricing and licensing: https://azure.microsoft.com/en-us/pricing/details/devops/server/

- Azure DevOps Server release notes: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server

### Licensing sources

- https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- https://azure.microsoft.com/en-us/pricing/details/devops/server/

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server

- https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. Server installation media and server/CAL licensing are documented. A current first-party Marketplace offer delivering this self-hosted Server edition was not established. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Azure DevOps Services billing and Azure VM charges do not establish Marketplace commitment treatment for Server licences/CALs. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Single sign-on: Documented. Microsoft distinguishes Server Windows authentication from Services Microsoft Entra authentication. Use Windows integrated authentication for the self-hosted server; Services service-principal and managed-identity patterns do not establish Server support. Scope: Azure DevOps Server identity boundary. Source: https://learn.microsoft.com/en-us/azure/devops/organizations/security/authentication-guidance?view=azure-devops (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The Server authentication guidance establishes Windows authentication and supported PAT/client-library paths, not a SCIM lifecycle endpoint. Microsoft Entra provisioning for Azure DevOps Services cannot be transferred to Server. Scope: Azure DevOps Server; SCIM unconfirmed. Source: https://learn.microsoft.com/en-us/azure/devops/organizations/security/authentication-guidance?view=azure-devops (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Azure DevOps Server material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://learn.microsoft.com/en-us/azure/devops/server/architecture/key-concepts?view=azure-devops (reviewed 2026-11-17).

- Security controls: Documented. Use the documented Windows/domain identity and permission boundaries and restrict service accounts and database access. Server security requirements are distinct from the Microsoft-hosted Services security posture. Current advisory review: Microsoft's Patch 9 for Azure DevOps Server 2022.2 includes security fixes and is recommended for affected installations. Apply Patch 9 or a later applicable supported update after checking prerequisites. Scope: Self-managed Server identity and authorization Azure DevOps Server 2022.2; other server generations require their own patch guidance.. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://learn.microsoft.com/en-us/azure/devops/server/architecture/key-concepts?view=azure-devops.

- Air-gapped operation: Sources checked — unresolved. The self-hosted installer and Windows/SQL dependencies are documented, but a complete disconnected activation, extension/feed and security-update workflow was not established. Scope: Reviewed public evidence for Azure DevOps Server; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Microsoft documents installing Server on a supported Windows host and configuring the application/database tiers. The Azure SQL topology requires Azure VMs; this is an installer/configuration workflow, not a pinned IaC artifact. Scope: Self-managed Windows Server installation. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Microsoft recommends an eight-core machine, 16 GB RAM and SSD for a single-server deployment. HA application tiers and SQL availability add servers; repository size, builds and usage can require more. Scope: Server hardware recommendation; not an HA minimum. Source: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server (reviewed 2026-11-17).

- License pricing: Documented. Azure DevOps Server is proprietary Microsoft software. Express is a no-cost license limited to five active users, not an open-source edition; broader use requires paid server/CAL or eligible Visual Studio and Azure DevOps entitlements. Scope: Azure DevOps Server: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://learn.microsoft.com/en-us/azure/devops/server/install/get-started?view=azure-devops-server (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Only Azure deployment is confirmed here. An AWS estimate would assume an unevidenced cloud path; obtain an Azure topology and Server/CAL/Windows/SQL licensing quote. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. Azure DevOps Server 2022.2 Patch 9 was published October 13, 2026 and includes security fixes. Match the patch to the exact installed server generation and prerequisites. Scope: Azure DevOps Server 2022.2. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Azure DevOps Server 2022.2 Patch 9 security update (security-advisory): Microsoft's Patch 9 for Azure DevOps Server 2022.2 includes security fixes and is recommended for affected installations. Scope: Azure DevOps Server 2022.2; other server generations require their own patch guidance. Conditions: Installed server generation and prerequisite patch level determine applicability. Action: Apply Patch 9 or a later applicable supported update after checking prerequisites. Source: https://learn.microsoft.com/en-us/azure/devops/server/release-notes/azuredevopsserver?view=azure-devops-server; reviewed 2026-11-18.




## Ever Gauzy

Open-source business operations platform for people, projects, time and financial records.

- Listing: https://launchinyourcloud.com/directory/ever-gauzy/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean, heroku, fly, railway, render
- 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: Application platform deployment
- Architecture: Ever Gauzy application/API, database and required workers using provider-specific deployment recipes.
- 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://gauzy.co
- 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 supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.

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

Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Open-source business operations platform for people, projects, time and financial records.

- hr-employee-records-management: Open-source business operations platform for people, projects, time and financial records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/azure-deployment/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/gcp-deployment/ (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/ (checked 2026-11-19). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/heroku-deployment/ (checked 2026-11-19). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/flyio-deployment/ (checked 2026-11-19). 

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

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.gauzy.co/deployment/cloud/render-deployment/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guide (aws): https://docs.gauzy.co/deployment/cloud/aws-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.gauzy.co/deployment/cloud/azure-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Guide (gcp): https://docs.gauzy.co/deployment/cloud/gcp-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Guide (digitalocean): https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Heroku Guide (heroku): https://docs.gauzy.co/deployment/cloud/heroku-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Fly.io Guide (fly): https://docs.gauzy.co/deployment/cloud/flyio-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/ever-gauzy
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Render Guide (render): https://docs.gauzy.co/deployment/cloud/render-deployment/
  Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes evereq, rahul-rocket, adkif, 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/ever-co/ever-gauzy/graphs/contributors

- Upstream project: https://github.com/ever-co/ever-gauzy

### Sources

- AWS Guide: https://docs.gauzy.co/deployment/cloud/aws-deployment/

- Azure Guide: https://docs.gauzy.co/deployment/cloud/azure-deployment/

- GCP Guide: https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- DO Guide: https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- Heroku Guide: https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- Fly.io Guide: https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- Railway: https://railway.com/deploy/ever-gauzy

- Render Guide: https://docs.gauzy.co/deployment/cloud/render-deployment/

- AGPL-3.0 LICENSE: https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

- Releases v111.250.0: https://github.com/ever-co/ever-gauzy/releases

### Licensing sources

- https://github.com/ever-co/ever-gauzy/blob/develop/LICENSE

### Infrastructure sources

- https://docs.gauzy.co/deployment/cloud/aws-deployment/

- https://docs.gauzy.co/deployment/cloud/azure-deployment/

- https://docs.gauzy.co/deployment/cloud/gcp-deployment/

- https://docs.gauzy.co/deployment/cloud/digitalocean-deployment/

- https://docs.gauzy.co/deployment/cloud/heroku-deployment/

- https://docs.gauzy.co/deployment/cloud/flyio-deployment/

- https://railway.com/deploy/ever-gauzy

- https://docs.gauzy.co/deployment/cloud/render-deployment/


### 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. The vendor documents application-user OAuth login with Google, GitHub, Facebook, Twitter, LinkedIn and Microsoft, including registered clients and instance callback settings. Provider login and the application JWT session/API mechanism are distinct configuration layers. Scope: Upstream application-user social OAuth configuration; not proof of arbitrary enterprise SAML or SCIM support. Source: https://docs.gauzy.co/authentication/social-auth/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official AWS guide provides service architecture, CLI provisioning and ECS task configuration for the application, PostgreSQL, Redis and S3. Configure images, task resources, secrets, networking and persistence for production; the illustrative commands are not a supplied complete CloudFormation stack. Scope: Vendor-documented customer AWS deployment recipe; complete production configuration and version alignment require review. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The AWS guide illustrates two Fargate tasks at 1 vCPU/2 GB each, a db.t3.medium database with a 50-GB provisioning example and cache.t3.micro Redis. These are example service sizes from the guide, with file storage and load balancing additional; its advertised cost table is not a reference-workload quote. Scope: Published AWS example allocations, not a 100-user/1-TB HA minimum or current operating-cost estimate. Source: https://docs.gauzy.co/deployment/cloud/aws-deployment/ (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## JetBrains YouTrack Server

Customer-hosted project and issue management application from JetBrains.

- Listing: https://launchinyourcloud.com/directory/youtrack-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary YouTrack Server subscription; a limited free-user tier is available
- Licensing model: commercial-only
- Installation: Official YouTrack Docker image and Server installation documentation
- Architecture: Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.
- Operations: Customer manages Docker/server resources, persistent data, backups, TLS/network configuration and upgrades.
- Product website: https://www.jetbrains.com/youtrack/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry selects YouTrack Server. Free user allowances do not make the application open source, and each installation requires its own license. Review optional integrations and AI services separately from the self-hosted project-tracking deployment.

YouTrack Server is proprietary subscription software, including when used within its free-user allowance. The Server agreement and selected plan determine install rights, updates and user/agent entitlements.

Persistent Docker server deployment with mounted application data, configuration, logs and backup directories.


### Category fit

- project-management: Task and issue tracking with Scrum/Kanban boards, planning and progress reporting for project teams.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html (checked 2026-11-12). 


### Cloud deployment evidence

- YouTrack Server Kubernetes deployment on named cloud services (aws, azure, gcp, oci): https://www.jetbrains.com/help/youtrack/server/deploy-youtrack-kubernetes.html
  JetBrains names Amazon EKS, Azure Kubernetes Service, Oracle Container Engine for Kubernetes and Google Kubernetes Engine for YouTrack Server, with a worked GKE deployment. The instructions deploy a single YouTrack node with persistent volumes; multi-node application installations are not supported. Check the current image, license, storage and backup requirements rather than treating Kubernetes as application clustering.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official server installation and updates: https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html

- Docker deployment and persistent directories: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html

- Project-management functionality: https://www.jetbrains.com/youtrack/features/agile_project_management.html

- Server software subscription agreement: https://www.jetbrains.com/legal/docs/youtrack/subscription/

- Server/free-tier license scope: https://www.jetbrains.com/youtrack/buy/?section=server&with-helpdesk=true

### Licensing sources

- https://www.jetbrains.com/legal/docs/youtrack/subscription/

- https://www.jetbrains.com/youtrack/buy/?section=server&with-helpdesk=true

### Infrastructure sources

- https://www.jetbrains.com/help/youtrack/server/installation-and-upgrade.html

- https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html


### 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. The Server SAML 2.0 module configures YouTrack as a service provider for an external identity provider. Configure metadata, certificate trust and callback URLs; login-time user/group updates differ from separately configured SCIM provisioning. Scope: YouTrack Server 2026.2 user authentication, not a Cloud-only claim. Source: https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html (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. JetBrains distributes YouTrack Server as an official Docker image for evaluation and production. Configure persistent data/conf/log/backup directories and use a selected versioned image. Scope: YouTrack Server 2026.2 installation guide. Source: https://www.jetbrains.com/help/youtrack/server/youtrack-docker-installation.html (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/jetbrains/youtrack. Artifact reference: versioned image tag must be selected.

- Minimum footprint / sizing: Documented. The Server 2026.2 guide states 1.5 GB minimum RAM with JVM minimums of 1,024 MB heap and 250 MB Metaspace. Storage guidance is roughly 1 GB per 5,000 issues before attachment variation. Database growth and transactions drive sizing; this is not a 1-TB HA topology. Scope: Upstream Server sizing guidelines; issue and attachment workload are material. Source: https://www.jetbrains.com/help/youtrack/server/youtrack-supported-environments.html (reviewed 2026-11-20).

- License pricing: Documented. The current Server license guide grants free use for up to ten users and three helpdesk agents. New commercial purchases from June 23, 2026 use annual user-pack subscriptions; earlier perpetual licenses have different terms. Each installation needs its own license; confirm the current pack price and renewal terms. Scope: Current Server licensing; historical perpetual-license and Cloud pricing are separate. Source: https://www.jetbrains.com/help/youtrack/server/manage-youtrack-server-license.html (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Jira Software Data Center

Commercial self-managed Jira Software edition deployed on customer-operated cloud or Kubernetes infrastructure. New Data Center subscriptions are restricted to eligible existing Atlassian customers.

- Listing: https://launchinyourcloud.com/directory/jira-software-data-center/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Atlassian Data Center term license for eligible existing customers; new-customer sales ended March 30, 2026. Affected subscriptions expire March 28, 2029.
- Licensing model: commercial-only
- Installation: Official Atlassian Helm chart on Amazon EKS, Azure AKS or Google GKE, or package-based single-node and clustered installation
- Architecture: Single-node or clustered Jira application nodes with an external database, load balancer, shared home, local indexes and optional dedicated nodes
- Operations: Customer manages Kubernetes or hosts, the database, shared and local storage, load balancing, networking, TLS, identity, Marketplace apps, backups, monitoring and upgrades.
- Product website: https://www.atlassian.com/software/jira/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 Software Data Center, not Jira 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, so they are not listed as current install methods. 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 Software Data Center versions before the fixed 9.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 Data Center runs persistent application nodes with durable database, shared-home and index storage; managed Kubernetes supplies the cluster control plane but not a serverless application runtime.


### Category fit

- project-management: Provides self-managed issue, project, planning and work-tracking capabilities for enterprise teams.

- devops: Supports software-delivery planning, issue tracking, release coordination and integrations with development toolchains.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Jira Data Center on EKS, AKS or GKE (aws, azure, gcp): https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html
  Atlassian documents Jira Data Center deployment with its Helm charts and explicitly lists Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine as managed cluster environments. Atlassian supports the product and Helm chart, but not the underlying Kubernetes platform.
  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 Data Center on Kubernetes: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.html

- Jira Data Center architecture and infrastructure: https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.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-data-center-on-a-kubernetes-cluster-1409092879.html

- https://confluence.atlassian.com/security/jira-data-center-architecture-and-infrastructure-options-1409092890.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Atlassian documents SAML 2.0 and OIDC through its Data Center SSO app. Match app compatibility to Jira Software 8.15+; authentication does not assign application access or permissions. Scope: Jira Software 8.15+ Data Center SSO feature baseline; existing-customer lifecycle restrictions remain. Source: https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html (reviewed 2026-11-16). Supporting source: OIDC product/version scope — https://confluence.atlassian.com/enterprise/openid-connect-for-atlassian-data-center-applications-987142159.html.

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

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

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

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Atlassian publishes product-specific Data Center Helm charts. Select a chart and application version supported for this product and configure its database, persistent storage, ingress and license; one product’s chart does not establish compatibility for another. Scope: Jira Software Data Center; existing-customer eligibility and lifecycle conditions apply. Source: https://confluence.atlassian.com/security/running-jira-data-center-on-a-kubernetes-cluster-1409092879.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 installation guide, last modified in 2021, gives a multicore server with 8 GB available RAM for 100 projects, 1,000–5,000 issues and 100–200 users. This is a legacy small-installation example, not a current Data Center cluster minimum; size production nodes, supported database and storage separately. Scope: Legacy small-installation example; not a current Data Center production sizing recommendation. Source: https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.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 Software 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-software.json (reviewed 2026-11-16). Supporting source: Vendor release notes — https://confluence.atlassian.com/display/JIRASOFTWARE/JIRA+Software+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.




## Kan

Self-hosted kanban boards for projects and team tasks.

- Listing: https://launchinyourcloud.com/directory/kan-bn/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Kan application, PostgreSQL and persistent data on Railway.
- 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://kan.bn
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The reviewed v0.7.0 tag is a prerelease. Treat it as an early project and validate migrations and recovery before relying on it for production work.

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

Kan application, PostgreSQL and persistent data on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted kanban boards for projects and team tasks.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/kan
  Kan application, PostgreSQL and persistent data on Railway. The reviewed v0.7.0 tag is a prerelease. Treat it as an early project and validate migrations and recovery before relying on it for production work.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes hjball, ovran, LovelessCodes, 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/kanbn/kan/graphs/contributors

- Upstream project: https://github.com/kanbn/kan

### Sources

- Railway Template: https://railway.com/deploy/kan

- AGPL-3.0 LICENSE: https://github.com/kanbn/kan/blob/main/LICENSE

- Releases v0.7.0: https://github.com/kanbn/kan/releases

### Licensing sources

- https://github.com/kanbn/kan/blob/main/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The v0.7.0 source reads configured social-provider client credentials and passes those providers into the application authentication server. This establishes the configured provider-login path, with instance URL/origin and provider callback settings required; a Better Auth dependency alone is not the evidence. Scope: Versioned upstream configured social login; generic enterprise SAML or arbitrary OIDC-provider compatibility is not established by this finding. Source: https://github.com/kanbn/kan/blob/v0.7.0/packages/auth/src/auth.ts (reviewed 2026-11-21). Supporting source: Provider configuration and enabled-provider endpoint — https://github.com/kanbn/kan/blob/v0.7.0/packages/auth/src/providers.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v0.7.0 Compose file separates PostgreSQL, migrations and the web application with persistence and service ordering. The README also identifies an official Railway template. The versioned file still references moving application/migration images, so choose compatible releases, secrets and public URL settings. Scope: Versioned upstream Compose example; a file snapshot does not pin its latest images. Source: https://github.com/kanbn/kan/blob/v0.7.0/docker-compose.yml (reviewed 2026-11-21). Deployment artifact: https://github.com/kanbn/kan/blob/v0.7.0/docker-compose.yml. Artifact reference: v0.7.0; application and migration image references move. Supporting source: Official installation paths — https://github.com/kanbn/kan/blob/v0.7.0/README.md.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed v0.7.0 installation documentation and Compose topology identify application, migrations and PostgreSQL, with optional Redis/storage services, but do not establish a quantitative production CPU/RAM/storage baseline. Instance sizing and HA capacity remain workload-specific. Scope: Deployment topology confirmed; production hardware minimum remains unconfirmed. Source: https://github.com/kanbn/kan/blob/v0.7.0/docker-compose.yml (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Kaneo

Self-hosted project, board and issue management application.

- Listing: https://launchinyourcloud.com/directory/kaneo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Kaneo frontend and API, PostgreSQL and persistent application data.
- 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://kaneo.app/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Railway recipe installs the application and database; local SQLite development examples are a different topology.

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

Kaneo frontend and API, PostgreSQL and persistent application data. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted project, board and issue management application.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/kaneo
  Kaneo frontend and API, PostgreSQL and persistent application data. The Railway recipe installs the application and database; local SQLite development examples are a different topology.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes andrejsshell, tinsever, randoneering, 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/usekaneo/kaneo/graphs/contributors

- Upstream project: https://github.com/usekaneo/kaneo

### Sources

- Railway Template: https://railway.com/deploy/kaneo

- Kaneo Docs: https://kaneo.app/docs

- MIT LICENSE: https://github.com/usekaneo/kaneo/blob/main/LICENSE

- Releases v2.49.0: https://github.com/usekaneo/kaneo/releases

### Licensing sources

- https://github.com/usekaneo/kaneo/blob/main/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The v2.50.0 guide documents custom OAuth/OIDC login with client credentials, discovery or explicit endpoints, callback URL, PKCE and optional account/profile/logout policies. Configure provider access and local account policy deliberately rather than treating the MCP OAuth server as employee SSO. Scope: Versioned self-hosted application-user OAuth/OIDC configuration. Source: https://github.com/usekaneo/kaneo/blob/v2.50.0/apps/docs/core/social-providers/custom-oauth.mdx (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v2.50.0 documentation supplies a Compose example for Kaneo and PostgreSQL, with required secrets, persistent database storage and health checks; it also publishes an OCI Helm chart. The Compose example names an older application image tag, so deliberately select the intended compatible release and production ingress/TLS configuration. Scope: Versioned local-start example and separate Helm deployment; source tag and example image tag differ. Source: https://github.com/usekaneo/kaneo/blob/v2.50.0/apps/docs/core/installation/docker-compose.mdx (reviewed 2026-11-21). Deployment artifact: https://github.com/usekaneo/kaneo/tree/v2.50.0/charts/kaneo. Artifact reference: v2.50.0 source snapshot; select compatible published chart and image versions. Supporting source: Helm deployment and configuration — https://github.com/usekaneo/kaneo/blob/v2.50.0/charts/kaneo/README.md.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed chart documents configurable application/database resources and autoscaling but does not establish a complete production CPU/RAM/storage baseline. Empty/default resource configuration and ingress examples are not a workload-sized hardware recommendation. Scope: Published deployment configuration; quantitative production/HA sizing remains unconfirmed. Source: https://github.com/usekaneo/kaneo/blob/v2.50.0/charts/kaneo/README.md (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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







## Leantime Self-Hosted

Customer-hosted project and task management application for cross-functional teams.

- Listing: https://launchinyourcloud.com/directory/leantime/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 downloadable application; marketplace plugins have separate terms
- Licensing model: open-source
- Installation: Official release package or documented Docker setup
- Architecture: Persistent PHP web application and MySQL/MariaDB database, with customer-controlled data storage and optional Docker packaging.
- Operations: Customer maintains the PHP/database or container stack, configuration, file storage, backups and application/plugin upgrades.
- Product website: https://leantime.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the downloadable application. The vendor distinguishes its open-source project section and work dashboard from other offerings; do not assume all website or marketplace features are included. Verify each plugin license and compatibility separately. Releases v3.15.1 and v3.15.2 fix calendar-event exposure, continued use of deactivated-user sessions and tokens, draft-document leakage, cross-project comment leakage, and inactive-account LDAP/OIDC behavior. v3.15.3 fixes users being unable to resume or complete onboarding. All three releases state that no database changes are required; use v3.15.3 or later rather than stopping on an earlier 3.15.x patch. Plugin developers upgrading from before v3.15.0 must still replace the removed legacy HTMX ticket event aliases with the documented lt:tickets:* events or event classes.

The downloadable application is GNU AGPL version 3. This entry covers that application; separately purchased marketplace plugins and hosted services are not represented as AGPL features.

Persistent PHP web application and MySQL/MariaDB database, with customer-controlled data storage and optional Docker packaging.


### Category fit

- project-management: Open-source project and task planning, task boards, milestones and timesheets; selected marketplace capabilities have separate scope.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/leantime (checked 2026-11-12). Source: https://github.com/Shinyduo/docker-leantime/blob/master/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Leantime community deployment on Railway (railway): https://railway.com/deploy/leantime
  The community recipe builds upstream Leantime with PHP, Nginx and database configuration in a customer Railway project. Review and set the actual Leantime release/build argument, compatible PHP version, persistent uploads and database backups. This is not the vendor-managed Leantime cloud service or a vendor support commitment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the community Leantime Railway image (railway): https://github.com/Shinyduo/docker-leantime/blob/master/Dockerfile
  The inspected Dockerfile downloads a selected release from Leantime/leantime and requires LEAN_VERSION to be set. It uses PHP 8.3 and supervises the application services; the recipe needs version and configuration review rather than treating all template defaults as production-ready.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release feed lists v3.15.3. Releases v3.15.1 and v3.15.2 contain security and privacy fixes for calendars, deactivated sessions and tokens, draft documents, comment polling, and inactive SSO accounts; recent releases credit multiple contributors. The vendor identifies Fraunhofer, Linksys and Techstars teams or users on its homepage; these logos do not establish organization-wide adoption or a hosting model.

Reviewed 2026-11-16.

- Maintained releases and named contributors: https://github.com/Leantime/leantime/releases

- Vendor-listed teams and users: https://leantime.io/

### Sources

- Core features, system requirements and installation: https://github.com/Leantime/leantime

- Self-hosted download: https://leantime.io/download-leantime/

- Application license: https://raw.githubusercontent.com/Leantime/leantime/master/LICENSE

- Vendor explanation of open-source scope: https://support.leantime.io/en/article/how-is-leantime-the-open-source-system-licensed-29l3j/

- Maintained releases and contribution credits: https://github.com/Leantime/leantime/releases

- Vendor-listed teams and users: https://leantime.io/

- Leantime v3.15.0 release and upgrade notes: https://github.com/Leantime/leantime/releases/tag/v3.15.0

- Leantime v3.15.1 security and upgrade notes: https://github.com/Leantime/leantime/releases/tag/v3.15.1

- Leantime v3.15.2 security and upgrade notes: https://github.com/Leantime/leantime/releases/tag/v3.15.2

- Leantime v3.15.3 release and upgrade notes: https://github.com/Leantime/leantime/releases/tag/v3.15.3

### Licensing sources

- https://raw.githubusercontent.com/Leantime/leantime/master/LICENSE

- https://support.leantime.io/en/article/how-is-leantime-the-open-source-system-licensed-29l3j/

### Infrastructure sources

- https://github.com/Leantime/leantime

- https://leantime.io/download-leantime/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The configuration guide documents OIDC sign-in and LDAP/Active Directory integration. Configure the provider, callback, claim mapping and application roles; this is not evidence of SCIM provisioning. Scope: Self-hosted Leantime OIDC and LDAP configuration. Source: https://docs.leantime.io/installation/configuration (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 upstream Docker repository supplies Compose with an environment template and MySQL. Replace demonstration passwords, configure persistent storage and select a compatible image before production. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/Leantime/docker-leantime (reviewed 2026-11-14). Deployment artifact: https://github.com/Leantime/docker-leantime. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The v3.15.3 README establishes PHP 8.2+, MySQL 8.0+/MariaDB 10.6+, web-server/extensions and supported standard/Docker installation paths, but no CPU, RAM or data-volume baseline was confirmed. Size the application, database, attachments, backups and HA arrangement for the intended load. Scope: Reviewed runtime/deployment prerequisites; production hardware sizing remains unconfirmed. Source: https://github.com/Leantime/leantime/blob/v3.15.3/README.md (reviewed 2026-11-20).

- License pricing: Documented. The v3.15.3 core is AGPL-3.0. Its README explicitly excepts plugins under /app/Plugins, which may use other terms including the enterprise licence. Assess plugin, support and hosting entitlements separately from core self-hosting rights. Scope: Versioned core licence; commercial plugin and service entitlements are separate. Source: https://github.com/Leantime/leantime/blob/v3.15.3/LICENSE (reviewed 2026-11-20). Supporting source: Versioned project licensing notes — https://github.com/Leantime/leantime/blob/v3.15.3/README.md.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v3.15.3, published 2026-11-16. Includes the 3.15.1–3.15.2 privacy/session fixes and 3.15.3 onboarding fixes. No database changes are required; the earlier 3.15.0 plugin event migration still applies. This is a dated release snapshot, not a support or future-cadence promise. Scope: Upstream Leantime/leantime release record; commercial editions and deployment packages may differ. Source: https://github.com/Leantime/leantime/releases/tag/v3.15.3 (reviewed 2026-11-16).







## MantisBT

Self-hosted issue and bug tracking application.

- Listing: https://launchinyourcloud.com/directory/mantisbt/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL licence for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: TurnKey Debian appliance with MantisBT application and database.
- 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://mantisbt.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Appliance 19.0.3 is distinct from MantisBT application releases; plugins and mail settings add their own maintenance requirements.

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

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


### Category fit

- project-management: Self-hosted issue and bug tracking application.

### Deployment boundaries


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


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-4jhsm3lntgxlg
  TurnKey Debian appliance with MantisBT application and database. Appliance 19.0.3 is distinct from MantisBT application releases; plugins and mail settings add their own maintenance requirements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes dregad, vboctor, mantis, 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/mantisbt/mantisbt/graphs/contributors

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

### Sources

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

- GPL-2.0 LICENSE: https://github.com/mantisbt/mantisbt/blob/master/doc/LICENSE

- Releases v2.28.4: https://github.com/mantisbt/mantisbt/releases

### Licensing sources

- https://github.com/mantisbt/mantisbt/blob/master/doc/LICENSE

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-4jhsm3lntgxlg


### Buyer diligence


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

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


- Marketplace delivery: 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: MantisBT selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-4jhsm3lntgxlg (reviewed 2026-11-19). Offer prodview-4jhsm3lntgxlg: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-4jhsm3lntgxlg.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The 2.28.4 core guide documents database-password, LDAP and web-server authentication modes. Those entries alone do not establish a current maintained SAML/OIDC deployment or the IdP-to-session mapping of an external plugin; federation support for the selected package remains unconfirmed. Scope: Core authentication documented; no negative SSO claim and no LDAP/password mode treated as federation. Source: https://github.com/mantisbt/mantisbt/blob/release-2.28.4/docbook/Admin_Guide/en-US/config/auth.xml (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream installation guide documents release-package installation on a configured PHP web server, database creation and the browser-based admin installer. This is a manual installation path; it does not establish an upstream maintained cloud-specific IaC stack or endorsement of a marketplace packager. Scope: MantisBT 2.28.4 manual installer instructions. Source: https://github.com/mantisbt/mantisbt/blob/release-2.28.4/docbook/Admin_Guide/en-US/Installation.xml (reviewed 2026-11-20). Deployment artifact: https://github.com/mantisbt/mantisbt/blob/release-2.28.4/docbook/Admin_Guide/en-US/Installation.xml. Artifact reference: release-2.28.4.

- Minimum footprint / sizing: Sources checked — unresolved. The 2.28.4 guide says CPU and memory must be sized for site traffic and application code is under 50 MiB; database and attachments need additional storage. No quantitative production CPU/RAM baseline or complete HA footprint was established by that guidance. Scope: Application-code size is not a complete installation requirement; workload sizing remains unconfirmed. Source: https://github.com/mantisbt/mantisbt/blob/release-2.28.4/docbook/Admin_Guide/en-US/Installation.xml (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## OpenProject On-Premises

Self-hosted project management with work packages, schedules, agile boards and collaboration.

- Listing: https://launchinyourcloud.com/directory/openproject/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 across Community and Enterprise software; paid Enterprise plans provide support, services and add-on enablement
- Licensing model: open-source
- Installation: Linux packages, Docker Compose or Helm deployment
- Architecture: Customer-operated application services with PostgreSQL and persistent file storage
- Operations: Customer manages infrastructure, backups and updates; support scope depends on the selected plan.
- Product website: https://www.openproject.org/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

OpenProject explicitly states that Enterprise add-ons remain open-source GPLv3 software, not proprietary extensions. The recommended production Docker path separates processes with Compose; the all-in-one quick-start container is not the recommended production setup. Feature availability and support depend on the plan. OpenProject 17.9.7 fixes a critical CVSS 9.4 flaw that allowed users, and anonymous visitors on public instances, to invoke unintended project operations including deletion or restricted-data reads. It also fixes a second-factor bypass and multiple authorization and disclosure issues. Installations on 17.2–17.4 must move to a patched supported release; patched 17.5–17.8 branches are also available. OpenProject 17.9.8 adds eight security fixes covering meeting authorization, cached activity and work-package disclosure, invitation-mail disclosure, repository-URL SSRF, external-storage virus-scan enforcement and unauthorized meeting-outcome movement. Upgrade the 17.9 line and review the linked advisories for other affected branches.

OpenProject states that Community, Enterprise and Enterprise add-ons are GPLv3 software. Paid Enterprise plans provide support, services and add-on enablement; they do not establish proprietary feature-code licensing.

Docker Compose deploys persistent application, database and supporting processes; packages run on a customer server. Persistent storage and external HTTPS termination must be configured.


### Category fit

- project-management: Project planning and delivery through work packages, Gantt charts, agile boards, time tracking and collaborative project records.

### Deployment boundaries


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


### Cloud deployment evidence

- OpenProject Community deployment on Railway (railway): https://railway.com/deploy/openproject-server
  The community template uses upstream OpenProject 17 application images with web, worker and scheduler roles, PostgreSQL, Redis, Hocuspocus and an edge proxy. This is a customer Railway project with platform-managed infrastructure. Confirm matching image versions, attachment storage, credentials, backups and Community versus licensed features.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker installation and production caveats: https://www.openproject.org/docs/installation-and-operations/installation/docker/

- Docker Compose deployment: https://www.openproject.org/docs/installation-and-operations/installation/docker-compose/

- Enterprise on-premises guide: https://www.openproject.org/docs/enterprise-guide/enterprise-on-premises-guide/

- Editions and GPLv3 clarification: https://www.openproject.org/blog/enterprise-edition-upgrade-test-free/

- Licensing FAQ: https://www.openproject.org/docs/faq/

- Licensing and edition terms: https://raw.githubusercontent.com/opf/openproject/dev/COPYRIGHT

- OpenProject 17.9.7 critical security release: https://www.openproject.org/docs/release-notes/17-9-7/

- OpenProject 17.9.8 security release: https://github.com/opf/openproject/releases/tag/v17.9.8

### Licensing sources

- https://www.openproject.org/blog/enterprise-edition-upgrade-test-free/

- https://www.openproject.org/docs/faq/

- https://raw.githubusercontent.com/opf/openproject/dev/COPYRIGHT

### Infrastructure sources

- https://www.openproject.org/docs/installation-and-operations/installation/docker/

- https://www.openproject.org/docs/installation-and-operations/installation/docker-compose/


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 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. The SAML administrator guide documents federated authentication as an Enterprise add-on. Configure the identity provider and claim mappings for the selected self-managed instance. Scope: OpenProject Enterprise SAML integration. Source: https://www.openproject.org/docs/system-admin-guide/authentication/saml/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. SCIM user/group synchronization is an Enterprise add-on. Configure an authentication provider and privileged SCIM client; token lifecycle and deletion settings need explicit administration. Scope: Self-managed Enterprise add-on; not Community. Source: https://www.openproject.org/docs/system-admin-guide/authentication/scim/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Documented. The Docker guide documents signed release provenance, SBOM and VEX attestations and verification commands. These software supply-chain artifacts are distinct from an organizational SOC/ISO attestation. Current review: v17.9.8 contains eight fixes for meeting authorization, cached activity and work-package disclosure, invitation-mail disclosure, repository-URL SSRF, external-storage virus-scan enforcement and meeting-outcome authorization. Upgrade and validate branch-specific guidance in the linked GHSAs. Scope: OpenProject 17.9 line; individual GHSAs define exact affected ranges. Source: https://github.com/opf/openproject/releases/tag/v17.9.8 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://www.openproject.org/docs/installation-and-operations/installation/docker/.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. OpenProject distinguishes slim application images for production Compose/Helm installations from the all-in-one quickstart. Choose a versioned image tag and run the required migration/seeder jobs during upgrades. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.openproject.org/docs/installation-and-operations/installation/docker/ (reviewed 2026-11-14). Deployment artifact: https://hub.docker.com/r/openproject/openproject. Artifact reference: select X.Y.Z or X.Y.Z-slim image tag.

- Minimum footprint / sizing: Documented. The minimum single-server guidance is a quad-core CPU at 2 GHz or above, 4,096 MB RAM and 20 GB free disk for up to 200 total users. Separate scaling examples allocate additional database and worker resources; concurrency changes requirements. Scope: Minimum single-server guidance, distinct from distributed scaling examples. Source: https://www.openproject.org/docs/installation-and-operations/system-requirements/ (reviewed 2026-11-14).

- License pricing: Documented. The v17.9.8 project is GPLv3. The vendor distinguishes free Community from Enterprise on-premises with additional features and professional support. Confirm the chosen subscription tier, user requirements and current commercial quote rather than transferring hosted-plan charges. Scope: Open-source project versus paid Enterprise on-premises subscription; excludes infrastructure. Source: https://github.com/opf/openproject/blob/v17.9.8/COPYRIGHT (reviewed 2026-11-20). Supporting source: Enterprise on-premises guide — https://www.openproject.org/docs/enterprise-guide/enterprise-on-premises-guide/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenProject v17.9.8 was published November 19, 2026. It fixes eight authorization, disclosure, SSRF, virus-scan enforcement and meeting-operation vulnerabilities. Review each linked advisory for branch-specific affected and fixed versions. Scope: OpenProject 17.9 release snapshot; linked advisories define other affected and fixed branches. Source: https://github.com/opf/openproject/releases/tag/v17.9.8 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/opf/openproject/releases/tag/v17.9.7.




### Security and lifecycle reviews

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

- OpenProject project-operation and authentication fixes (security-advisory): A critical project-editing flaw can expose restricted information or permit unintended operations, including deletion. Scope: The critical issue affects 17.2.0 onward before the applicable fixes: 17.5.2, 17.6.1, 17.7.3, 17.8.2 or 17.9.7. The release also fixes other issues. Conditions: Project visibility is required; anonymous visitors can be affected on public instances. The release separately addresses second-factor and other authorization flaws. Action: Apply a fixed supported release. Instances on 17.2–17.4 must move to a patched line. Source: https://www.openproject.org/docs/release-notes/17-9-7/; reviewed 2026-11-17.

- OpenProject 17.9.8 security update (security-advisory): OpenProject 17.9.8 fixes eight authorization, disclosure, SSRF, virus-scan enforcement and meeting-operation vulnerabilities. Scope: OpenProject 17.9 line; the GHSAs linked from the release define exact affected ranges on other branches. Conditions: Meeting access, cached activity or work-package responses, invitations, repository URLs and external-storage attachments determine applicability. Action: Upgrade to the fixed release for the installed supported branch and review every linked GHSA. Source: https://github.com/opf/openproject/releases/tag/v17.9.8; reviewed 2026-11-19.




## Plane Self-Hosted

Self-hosted project and work management with work items, cycles, modules, pages and collaborative planning.

- Listing: https://launchinyourcloud.com/directory/plane-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 Community Edition; closed-source Commercial and Airgapped editions use separate license terms.
- Licensing model: open-source
- Installation: First-party AWS Marketplace AMI or CloudFormation delivery; Docker and Kubernetes methods are also documented.
- Architecture: Customer-operated application services with PostgreSQL, cache/queue services and object storage
- Operations: Customer manages compute, database, object storage, network access, backups and upgrades; license activation and support depend on the selected edition.
- Product website: https://plane.so/
- Source review: 2026-11-17; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-17

### Scope and qualifications

Plane's AWS Marketplace delivery runs in the customer's AWS account. Community, Commercial and Airgapped editions have different codebases, feature sets, update paths and license behavior. Standard Commercial deployments use online license activation; choose the Airgapped edition when outbound activation is prohibited. Plane v1.5.0 fixes broad cross-workspace and cross-project access-control flaws across the application, external REST API, and published boards, and hardens OAuth state, redirects, cookie-authenticated writes, sessions, rate limits, and asset handling. Self-hosted operators should upgrade. Before rollout, account for Redis TLS certificate verification, randomized MinIO credentials, Caddy replacing nginx in the admin and web images, the requirement to run matching API and live-collaboration images, and three database migrations.

Plane Community Edition is AGPLv3. Commercial and Airgapped editions are closed-source and separately licensed; this platform-family classification does not imply that commercial governance features are open source.

Plane runs persistent application, collaboration and worker services backed by PostgreSQL, cache/queue components and object storage. The AWS AMI or CloudFormation package remains a server/container deployment. In v1.5.0 the admin and web images use Caddy instead of nginx, so custom nginx configuration for those images no longer applies. Redis TLS connections now verify the certificate and hostname; private-CA deployments must provide REDIS_SSL_CA_CERTS or explicitly disable verification.


### Category fit

- project-management: Manages projects, work items, cycles, modules, pages and team delivery records in a customer-operated workspace.

### Deployment boundaries


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


### Cloud deployment evidence

- First-party Plane AMI and CloudFormation delivery in AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-2aq5qeciy25pw
  The Plane-published Marketplace offer deploys an AMI or CloudFormation package into the buyer's AWS account. The image starts with a free self-hosted tier and supports separately purchased licenses. Review instance sizing, security groups, load balancing, persistent storage, backups and edition-specific update procedures.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Self-hosting architecture and responsibilities: https://developers.plane.so/self-hosting/self-hosting-101

- Self-hosted edition and license comparison: https://developers.plane.so/self-hosting/editions-and-versions

- First-party Plane AWS Marketplace deployment: https://aws.amazon.com/marketplace/pp/prodview-2aq5qeciy25pw

- Plane v1.5.0 security and upgrade notes: https://github.com/makeplane/plane/releases/tag/v1.5.0

### Licensing sources

- https://developers.plane.so/self-hosting/editions-and-versions

- https://developers.plane.so/self-hosting/self-hosting-101

### Infrastructure sources

- https://developers.plane.so/self-hosting/self-hosting-101

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

- https://github.com/makeplane/plane/releases/tag/v1.5.0


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 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: Edition-dependent. Plane publishes an AWS AMI/CloudFormation Free-tier offer and links a separate paid-plan offer. Free-tier delivery does not grant paid features or Enterprise Grid air-gapped rights; verify the selected offer and license. Scope: Plane AWS Free-tier marketplace offer and separate paid-plan procurement. Source: https://aws.amazon.com/marketplace/pp/prodview-2aq5qeciy25pw (reviewed 2026-11-14). Offer prodview-2aq5qeciy25pw: Plane; Free-tier AMI / CloudFormation; package v3.0.0; https://aws.amazon.com/marketplace/pp/prodview-2aq5qeciy25pw.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The current self-hosting guide labels generic OIDC SSO for Pro and Business. SAML is also separately documented; confirm the purchased Commercial entitlement and selected instance version rather than transfer these features to Community. Scope: Plane Commercial self-hosted Pro/Business authentication; not Community. Source: https://developers.plane.so/self-hosting/govern/oidc-sso (reviewed 2026-11-20). Supporting source: Self-hosted SAML configuration — https://developers.plane.so/self-hosting/govern/saml-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. Commercial self-hosted Plane ordinarily validates licenses through the Prime portal. A separately sold Airgapped Edition uses offline activation and a customer image registry, and is offered with Enterprise Grid. Scope: Enterprise Grid Airgapped Edition; not ordinary Community/Commercial deployment. Source: https://developers.plane.so/self-hosting/self-hosting-101 (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The official self-hosting documentation supplies a Docker Compose deployment and Prime CLI configuration, with bundled or external PostgreSQL, Redis and S3-compatible storage. Match Community/Commercial images, configuration and licence requirements; the single-server route is not the Kubernetes HA topology. Scope: Current official self-hosted Compose deployment; selected edition/version matters. Source: https://developers.plane.so/self-hosting/methods/docker-compose (reviewed 2026-11-20). Deployment artifact: https://developers.plane.so/self-hosting/methods/docker-compose. Artifact reference: Current Compose/Prime configuration instructions; pin compatible application/stack releases.

- Minimum footprint / sizing: Documented. The self-hosted Commercial page lists a minimum of 4 CPU cores, 8 GB RAM and 50 GB storage. This is an installation baseline, not a 100-user/1-TB HA benchmark; backing-service storage, replicas, AI dependencies and concurrent usage need a separate design. Scope: Published Commercial self-hosted installation minimum; Community/provider packages may differ. Source: https://plane.so/self-hosted (reviewed 2026-11-20).

- License pricing: Documented. Plane distinguishes its AGPL Community core from Commercial self-hosted Pro/Business/Enterprise licensing. Commercial instances can start on a free tier and unlock paid features with a Prime-issued licence. Confirm the self-hosted plan/seat quote and separate Airgapped Edition terms; Cloud tab prices are not assumed to be self-hosted prices. Scope: Published self-hosted licensing workflow; no unsupported numeric self-hosted quote inferred. Source: https://plane.so/self-hosted (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v1.5.0, published 2026-11-16. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package. Scope: Upstream makeplane/plane release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/makeplane/plane/releases/tag/v1.5.0 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- Plane access-control and session fixes (security-advisory): The 1.5.0 release fixes cross-workspace/project access and hardens authentication, API writes, sessions and asset handling. Scope: Upstream Plane v1.5.0 self-hosted release; marketplace and commercial package versions remain separate. Conditions: Affected app, API and published-board paths have different conditions. The upstream release does not provide one complete affected-version range. Action: Upgrade using matching API/live images; review the three migrations, Redis TLS trust, MinIO credentials and Caddy transition. Source: https://github.com/makeplane/plane/releases/tag/v1.5.0; reviewed 2026-11-17.




## Solidtime

Self-hosted project time tracking and billing records.

- Listing: https://launchinyourcloud.com/directory/solidtime/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- 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: Docker / Compose
- Architecture: Solidtime application, database, workers and persistent files.
- 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.solidtime.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Time tracking and billing are its core scope; it is not a full project planning or payroll system. Update and recreate the Solidtime image/runtime with the corrections supplied in v0.22.1 or a later compatible build.

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

Solidtime application, database, workers and persistent files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted project time tracking and billing records.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/solidtime (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/solidtime
  Solidtime application, database, workers and persistent files. Time tracking and billing are its core scope; it is not a full project planning or payroll system.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes Onatcer, korridor, TheSpyder, 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/solidtime-io/solidtime/graphs/contributors

- Upstream project: https://github.com/solidtime-io/solidtime

### Sources

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

- AGPL-3.0 LICENSE.md: https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md

- GitHub Releases: https://github.com/solidtime-io/solidtime/releases

- Solidtime PHP runtime security release: https://github.com/solidtime-io/solidtime/releases/tag/v0.22.1

### Licensing sources

- https://raw.githubusercontent.com/solidtime-io/solidtime/main/LICENSE.md

### Infrastructure sources

- https://www.hostinger.com/applications/solidtime


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The self-hosting guide supports company OIDC identity providers and explicitly requires On-Premise Business. Configure the public URL, proxy/HTTPS settings, IdP callback and access rules, with a working super-admin account for recovery. Scope: Current commercial self-hosted SSO feature; not established for the AGPL core v0.22.1 package alone. Source: https://docs.solidtime.io/self-hosting/single-sign-on (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting repository supplies separate application, scheduler and queue-worker services plus PostgreSQL, persistent storage and health checks. Generate keys and configure environment, email, URL/proxy and backup settings; choose matching application images instead of relying on latest. Scope: Upstream self-hosted Compose topology; Business SSO entitlement is separate. Source: https://docs.solidtime.io/self-hosting/guides/docker (reviewed 2026-11-21). Deployment artifact: https://github.com/solidtime-io/self-hosting-examples/blob/main/1-docker-with-database/docker-compose.yml. Artifact reference: main (moving branch); SOLIDTIME_IMAGE_TAG defaults to latest.

- Minimum footprint / sizing: Sources checked — unresolved. The official Compose example identifies application, scheduler, queue worker and database roles with persistent storage, but no production CPU/RAM or concurrency baseline was established. Their combined capacity, retention, database size and HA arrangement need workload-specific sizing. Scope: Service topology confirmed; quantitative production hardware sizing remains unconfirmed. Source: https://github.com/solidtime-io/self-hosting-examples/blob/main/1-docker-with-database/docker-compose.yml (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Solidtime PHP runtime security release (security-advisory): Solidtime 0.22.1 updates PHP to 8.3.36 for two critical runtime issues. Scope: CVE-2026-109618 and CVE-2026-109619 in the PHP runtime; the release updates FrankenPHP as well. Conditions: Custom installations must inspect their own PHP/runtime build; no application-wide vulnerable range is invented. Action: Update and recreate the Solidtime image/runtime with the corrections supplied in v0.22.1 or a later compatible build. Source: https://github.com/solidtime-io/solidtime/releases/tag/v0.22.1; reviewed 2026-11-19.




## Taiga

Open-source agile project, issue and team planning application.

- Listing: https://launchinyourcloud.com/directory/taiga/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Mozilla Public License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: Taiga frontend, backend, database, task workers and persistent media.
- 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/taigaio/taiga-back
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials.

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

Taiga frontend, backend, database, task workers and persistent media. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Open-source agile project, issue and team planning application.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/taiga.html
  The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.
  Source type: package-platform-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/taiga
  Taiga frontend, backend, database, task workers and persistent media. Cloudron packages Taiga 6.10.2 separately from its own package version; the Railway recipe is a separate deployment. OAuth and external integrations require their own credentials. This source is distinct from the Cloudron package.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes bameda, superalex, jespino, 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/taigaio/taiga-back/graphs/contributors

- Upstream project: https://github.com/taigaio/taiga-back

### Sources

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

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

- MPL-2.0 LICENSE: https://github.com/taigaio/taiga-back/blob/main/LICENSE

- Releases v6.10.2: https://github.com/taigaio/taiga-back/releases

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

### Licensing sources

- https://github.com/taigaio/taiga-back/blob/main/LICENSE

### Infrastructure sources

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

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


### 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. The upstream self-hosting guide documents GitHub and GitLab OAuth user login, disabled by default. Both backend and frontend settings, registered OAuth clients and public-registration settings must align. This establishes those social/provider login paths, not general SAML/OIDC or Cloudron-package SSO support. Scope: Upstream Taiga user login configuration; packaged distributions may differ. Source: https://docs.taiga.io/setup-production.html (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 taiga-docker repository supplies Compose, initialization configuration and environment settings for application, async worker, database, events and supporting services. Configure secrets, TLS, email and persistent volumes, and align all component image versions before use. Scope: Official self-hosted Compose stack; not the source-development quickstart. Source: https://docs.taiga.io/setup-production.html (reviewed 2026-11-20). Deployment artifact: https://github.com/taigaio/taiga-docker/blob/main/docker-compose.yml. Artifact reference: main (moving branch); choose compatible component release tags.

- Minimum footprint / sizing: Documented. The Cloudron package declares 300MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing. Scope: Selected Cloudron application package; add database, files, backups and concurrent workload requirements. Source: https://www.cloudron.io/store/taiga.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Tududi

Self-hosted task, project and personal productivity application.

- Listing: https://launchinyourcloud.com/directory/tududi/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: Tududi application and persistent database and files.
- 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://tududi.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.

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

Tududi application and persistent database and files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- project-management: Self-hosted task, project and personal productivity application.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/tududi (checked 2026-11-19). 

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/tududi
  Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/tududi
  Tududi application and persistent database and files. CalDAV, Telegram, email and OIDC integrations are optional external services; the server does not host those services automatically.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes chrisvel, antanst, rome-xi, 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/chrisvel/tududi/graphs/contributors

- Upstream project: https://github.com/chrisvel/tududi

### Sources

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

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

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/chrisvel/tududi/main/LICENSE

- GitHub Releases (v2.1.1): https://github.com/chrisvel/tududi/releases

### Licensing sources

- https://raw.githubusercontent.com/chrisvel/tududi/main/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/tududi

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The v2.1.1 OIDC guide documents one or multiple identity providers, installation callbacks, account linking and optional just-in-time provisioning. Automatic provisioning and admin-domain rules require deliberate IdP access restrictions; personal API tokens and CalDAV Basic authentication are separate paths. Scope: Versioned self-hosted application-user OIDC login. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docs/10-oidc-sso.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v2.1.1 Compose example runs Tududi with PostgreSQL 16, database health checks and persistent database/uploads/backups storage. Supply environment secrets and replace the moving latest application image with the intended released version; optional local dumps still need off-host backup. Scope: Versioned Compose example; PostgreSQL-backed v2.x is different from older SQLite installations. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml (reviewed 2026-11-20). Deployment artifact: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml. Artifact reference: v2.1.1 (file snapshot; example application image still uses latest).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed v2.1.1 README and Compose stack establish a PostgreSQL-backed application with persistent uploads and backups, but no production CPU/RAM or concurrency baseline was confirmed. The sample has no resource requests/limits that could substantiate a host minimum. Scope: Deployment topology confirmed; production/HA sizing for the reference workload remains unconfirmed. Source: https://github.com/chrisvel/tududi/blob/v2.1.1/docker-compose.yml (reviewed 2026-11-20). Supporting source: Versioned installation prerequisites — https://github.com/chrisvel/tududi/blob/v2.1.1/README.md.

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

- Operating cost estimate: Not researched.

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







## ZenTao Project Management (Open Source)

Self-hosted project, development, testing and issue management application.

- Listing: https://launchinyourcloud.com/directory/zentao/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Dual-licensed under ZPL 1.2 or GNU AGPL-3.0, at the user’s choice.
- Licensing model: open-source
- Installation: VM image
- Architecture: ZenTao application and database 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://aws.amazon.com/marketplace/pp/prodview-5jziwpvx4puq4
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The AWS route pairs Websoft9 platform installation with its explicit ZenTao application installer. The Azure route is cloudimg's separate VM. Package/platform versions do not establish an upstream ZenTao version; AGPL-3.0 and ZPL are alternative upstream licences.

Dual-licensed under ZPL 1.2 or GNU AGPL-3.0, at the user’s choice.

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


### Category fit

- project-management: Self-hosted project, development, testing and issue management application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.websoft9.com/en/docs/zentao/ (checked 2026-11-19). 

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


### Cloud deployment evidence

- Zentao | Websoft9 (aws): https://support.websoft9.com/en/docs/zentao/
  ZenTao application and database in a cloudimg Azure VM. The AWS route pairs Websoft9 platform installation with its explicit ZenTao application installer. The Azure route is cloudimg's separate VM. Package/platform versions do not establish an upstream ZenTao version; AGPL-3.0 and ZPL are alternative upstream licences.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.zentao-ubuntu-24-04
  ZenTao application and database in a cloudimg Azure VM. The AWS route pairs Websoft9 platform installation with its explicit ZenTao application installer. The Azure route is cloudimg's separate VM. Package/platform versions do not establish an upstream ZenTao version; AGPL-3.0 and ZPL are alternative upstream licences.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes catouse, liumengyi-luna, liyangLyon, 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/easysoft/zentaopms/graphs/contributors

- Upstream project: https://github.com/easysoft/zentaopms

### Sources

- Zentao | Websoft9: https://support.websoft9.com/en/docs/zentao/

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

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

- ZPL-1.2/AGPL-3.0 COPYING: https://github.com/easysoft/zentaopms/blob/main/COPYING

- Releases v22.7: https://github.com/easysoft/zentaopms/releases

- AWS | Websoft9: https://support.websoft9.com/en/docs/install-aws/

### Licensing sources

- https://github.com/easysoft/zentaopms/blob/main/COPYING

### Infrastructure sources

- https://support.websoft9.com/en/docs/zentao/

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.zentao-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: Sources checked — unresolved. The linked AWS offer delivers the Websoft9 platform. Its separate installer can deploy ZenTao, but a distinct transactable ZenTao software offer was not established. Scope: Websoft9 platform AMI versus the ZenTao application. Source: https://aws.amazon.com/marketplace/pp/prodview-5jziwpvx4puq4 (reviewed 2026-11-19).

- 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.zentao-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.zentao-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. The reviewed 22.6 source implements a ZDOO/Ranzhi SSO callback, validates the configured shared-key response, maps or binds the external account and creates the ZenTao user session. The settings explicitly target ZDOO. This confirms that specific integration, not general SAML/OIDC or current support for third-party federation plugins. Scope: Versioned source-code evidence for built-in ZDOO/Ranzhi user SSO only; broader IdP compatibility and vendor support are not established. Source: https://github.com/easysoft/zentaopms/blob/zentaopms_22.6_20260917/module/sso/zen.php (reviewed 2026-11-20). Supporting source: SSO route and configured callback — https://github.com/easysoft/zentaopms/blob/zentaopms_22.6_20260917/module/sso/control.php. Supporting source: ZDOO endpoint and shared-key settings — https://github.com/easysoft/zentaopms/blob/zentaopms_22.6_20260917/module/sso/lang/en.php.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes the easysoft/zentao container repository with installation, external-database and Compose instructions. Its description warns of the post-18.6 image-layout change to /data. Many examples still name older app/database versions; choose a verified compatible release, persistence layout and secrets before deploying. Websoft9 has separate packaged-install instructions. Scope: Vendor container artifact and third-party packaging are distinct; old samples do not establish current component support. Source: https://hub.docker.com/r/easysoft/zentao (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/easysoft/zentao/tags. Artifact reference: moving image repository; select a verified release tag, not latest or an old documentation example. Supporting source: Packager-specific console installation — https://support.websoft9.com/en/docs/zentao/.

- Minimum footprint / sizing: Sources checked — unresolved. The official container description documents persistent storage and a configurable per-PHP-process memory limit, but no complete production CPU/RAM/storage baseline was confirmed. That process limit and older single-container examples do not size current ZenTao, database, attachments, backups and HA replicas. Scope: Deployment configuration established; quantitative production and HA workload sizing remains unconfirmed. Source: https://hub.docker.com/r/easysoft/zentao (reviewed 2026-11-20).

- License pricing: Documented. Dual-licensed under ZPL 1.2 or GNU AGPL-3.0, at the user’s choice. Scope: ZenTao Project Management (Open Source); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/easysoft/zentaopms/blob/main/COPYING (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream zentaopms_22.6_20260917 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: ZenTao Project Management (Open Source) upstream application; verify compatibility with the selected package. Source: https://github.com/easysoft/zentaopms/releases/tag/zentaopms_22.6_20260917 (reviewed 2026-11-19).






