
# Project management on Railway

Compare documented Project management deployments on Railway, including operating responsibility, licensing and deployment evidence.

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


## Provider guidance

- Account boundary: Railway workspace, project and environment; platform-managed infrastructure
- Provider group: application-platform
- Provider classification: Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Source: https://docs.railway.com/projects (checked 2026-11-20).
- Network: Project/environment private networking with separately exposed public services
- Identity and access: Workspace/project access and scoped deployment tokens
- Installation guidance: Deploy application containers and data services into your project. Community templates require review of source images, credentials, volumes and release compatibility; they do not imply upstream vendor support.
- Guidance source: https://docs.railway.com/projects
- Guidance reviewed: 2026-11-12


### Project networking

Private networking connects services inside a project environment using encrypted tunnels and internal DNS. This project boundary does not give the customer ownership of the underlying infrastructure account.
Source: https://docs.railway.com/networking/private-networking (reviewed 2026-11-14).

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

7 listings.


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







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







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




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






