
# Software on Railway

Explore software with documented Railway deployment, customer-account guidance, licensing qualifications and source evidence.

Canonical page: https://launchinyourcloud.com/clouds/railway/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde



## Related questions

- [What apps can I deploy on Railway or Render?](https://launchinyourcloud.com/questions/apps-on-platforms/)


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.

61 listings.


## Activepieces Self-Hosted

Self-hosted workflow automation platform with integrations, triggers, actions and worker execution.

- Listing: https://launchinyourcloud.com/directory/activepieces/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms.
- Licensing model: open-source
- Installation: Official AWS Pulumi stack, Google Cloud VM guide or Railway template; Docker Compose and Kubernetes/Helm are also documented.
- Architecture: Application and worker containers with deployment-specific database and queue services
- Operations: Customer manages application configuration, secrets, integrations, backups and upgrades. AWS and Google Cloud paths require customer-managed infrastructure; Railway operates the underlying platform within the customer project.
- Product website: https://www.activepieces.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

This entry covers self-hosted Activepieces, not Activepieces Cloud. The AWS template can provision RDS PostgreSQL, Redis, load balancing and Route 53 integration. The Google Cloud guide uses a VM/container example with SQLite and in-memory Redis; confirm release compatibility and use the current production database and queue requirements. Railway deploys into a customer project on platform-managed infrastructure. Enterprise features require a separate license.

Activepieces Community Edition core is MIT licensed. Enterprise and cloud feature directories use a commercial license; confirm the selected edition and entitlements.

The documented deployments run long-lived application and worker containers with persistent data services. Railway operates the underlying platform; managed databases and load balancers do not make the application runtime serverless.


### Category fit

- workflow-automation: Builds event-driven business automations from triggers and actions, with customer-operated workers and integrations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.activepieces.com/docs/install/options/aws (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.activepieces.com/docs/install/options/gcp (checked 2026-11-13). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.activepieces.com/docs/install/options/railway (checked 2026-11-13). 


### Cloud deployment evidence

- Activepieces deployment into a customer AWS account with Pulumi (aws): https://www.activepieces.com/docs/install/options/aws
  The vendor-maintained Pulumi template deploys Activepieces into the operator's AWS account and can create VPC, compute, RDS PostgreSQL, Redis, load-balancing, ECR and Route 53 resources. Review template defaults, image versions, IAM permissions, secrets and production hardening.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Google Cloud VM deployment (gcp): https://www.activepieces.com/docs/install/options/gcp
  The vendor documents running the Activepieces application container on a Google Cloud VM or instance group. Its example uses SQLite and in-memory Redis; confirm compatibility with the selected release and follow current production database, queue and security requirements.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Railway project deployment (railway): https://www.activepieces.com/docs/install/options/railway
  The vendor documents a Railway template that deploys the Activepieces application with PostgreSQL and Redis into the operator's project. Railway manages the underlying infrastructure; the operator configures secrets, application access, persistence and backups. This is separate from Activepieces Cloud and does not establish ownership of an underlying hyperscaler account.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Sources

- Self-hosting and installation options: https://www.activepieces.com/docs/install/overview

- Official AWS Pulumi deployment: https://www.activepieces.com/docs/install/options/aws

- Community and enterprise licensing: https://github.com/activepieces/activepieces/blob/main/docs/about/license.mdx

- Google Cloud VM deployment: https://www.activepieces.com/docs/install/options/gcp

- Railway project deployment: https://www.activepieces.com/docs/install/options/railway

### Licensing sources

- https://github.com/activepieces/activepieces/blob/main/LICENSE

- https://github.com/activepieces/activepieces/blob/main/docs/about/license.mdx

### Infrastructure sources

- https://www.activepieces.com/docs/install/overview

- https://www.activepieces.com/docs/install/options/aws

- https://www.activepieces.com/docs/install/options/gcp

- https://www.activepieces.com/docs/install/options/railway


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 paid SSO guide explicitly documents SAML for self-hosted Enterprise. Company-domain verification and identity-provider setup are required; Google sign-in has separate self-hosted credentials. Scope: Self-hosted Enterprise SAML; not the free hobbyist mode. Source: https://www.activepieces.com/docs/admin-guide/guides/sso (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 official Compose workflow generates secrets and runs application/worker/database/cache services. Its worker replica count needs sizing and encryption keys need backup; the hobbyist single-container mode has different limits. Scope: Compose deployment; not the embedded-database hobbyist mode. Source: https://www.activepieces.com/docs/install/options/docker-compose (reviewed 2026-11-14). Deployment artifact: https://github.com/activepieces/activepieces. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The Compose guide requires at least 2 vCPU and 4 GB RAM. Workflow concurrency and the default worker replica count require workload-specific sizing; the hobbyist embedded-database install is a different topology. Scope: Activepieces Compose baseline; not guaranteed workflow throughput. Source: https://www.activepieces.com/docs/install/options/docker-compose (reviewed 2026-11-14).

- License pricing: Documented. The 0.93.0 licensing guide identifies the core as MIT-licensed and enterprise/cloud feature code as commercially licensed. Using those enterprise features in a self-hosted installation requires an Activepieces licence obtained from sales. Scope: Self-hosted core versus commercially entitled enterprise features; no hosted-plan price used as a self-hosted quote. Source: https://github.com/activepieces/activepieces/blob/0.93.0/docs/about/license.mdx (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 0.93.0, published 2026-11-08. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream activepieces/activepieces release record; commercial editions and deployment packages may differ. Source: https://github.com/activepieces/activepieces/releases/tag/0.93.0 (reviewed 2026-11-14).







## AnythingLLM Docker

Self-hosted application for document-grounded AI chat, retrieval and agents.

- Listing: https://launchinyourcloud.com/directory/anythingllm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms.
- Licensing model: open-source
- Installation: Run the official Docker edition on a customer-operated host with persistent application storage and configured model/vector endpoints.
- Architecture: Customer-operated web application and document/retrieval storage with configurable inference providers
- Operations: Customer manages users, documents, persistent storage, model access, integration secrets, backups and upgrades.
- Product website: https://anythingllm.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The Docker edition supports multi-user operation and differs from the desktop application. Local inference is an option; configured external LLMs, embeddings, vector stores and agent tools can send data outside the account. AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Optional MCP identity forwarding creates a new outbound identity path; keep the server and extension on compatible 1.20+ versions.

MIT License for upstream AnythingLLM; model weights, connectors and provider services have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web application and document/retrieval storage with configurable inference providers. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-applications-rag: Multi-user application for document-grounded chat, RAG and agents with configurable model and vector-database integrations.

- ai-tools: Self-hosted AI application interface and retrieval/agent integrations; model inference is separately configured.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.anythingllm.com/installation-docker/overview (checked 2026-11-12). 


### Cloud deployment evidence

- AnythingLLM Docker installation overview (aws, gcp, railway): https://docs.anythingllm.com/installation-docker/overview
  The project explicitly names AWS, Google Cloud and Railway for self-hosting the Docker edition, paired with its Docker installation workflow. This is an upstream hosting compatibility statement. Model endpoints, embeddings and external vector stores are separately configured and can have different data boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Public release notes credit named contributors and new contributors across multiple releases, alongside an established open contribution process.

Reviewed 2026-11-10.

- Release maintenance and contributor credits: https://github.com/Mintplex-Labs/anything-llm/releases

- Community contribution process: https://github.com/Mintplex-Labs/anything-llm

### Sources

- Official installation and runtime: https://docs.anythingllm.com/installation-docker/overview

- Upstream project and capabilities: https://github.com/Mintplex-Labs/anything-llm

- Current upstream license: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE

- AnythingLLM v1.20.0 release: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0

### Licensing sources

- https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE

### Infrastructure sources

- https://docs.anythingllm.com/installation-docker/overview


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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 self-hosted Docker configuration offers Simple SSO passthrough: a trusted application uses an API key to issue short-lived single-use login links for existing users. It requires multi-user mode and a configured admin. This is a bespoke integration, not native SAML/OIDC federation; the vendor recommends internally exposed instances. Scope: Docker Simple SSO passthrough; not standards-based federation. Source: https://docs.anythingllm.com/configuration (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding. Scope: Upstream v1.20.0 release notes; no consolidated affected-version range is asserted.. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide documents a prebuilt application image or source-built Compose setup. Persistent storage and user permissions must be configured; local model/vector endpoints and their resources are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.anythingllm.com/installation-docker/local-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The Docker requirements list 2 GB RAM, a two-core CPU with AVX2 and 5 GB storage as a small starting profile. Model inference, embeddings, vector storage, documents and concurrency can require much more; verify AVX2 passthrough on virtual machines. This is not an HA or 1-TB production recommendation. Scope: Self-hosted Docker baseline; model services, data and HA additional. Source: https://docs.anythingllm.com/installation-docker/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/Mintplex-Labs/anything-llm/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. AnythingLLM v1.20.0 was published November 17, 2026. It includes access and session hardening plus MCP identity forwarding and timeout changes; keep server and extension versions compatible. Scope: Upstream AnythingLLM self-hosted release. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- AnythingLLM 1.20.0 access hardening (security-advisory): AnythingLLM v1.20.0 hardens embed history, extension API-key authorization, workspace-agent access, password recovery, framing, and document-tool downloads. Scope: Upstream v1.20.0 release notes; no consolidated affected-version range is asserted. Conditions: Applicability depends on enabled embedding, extensions, agents, recovery, and document tools. Action: Upgrade the server and extension to compatible 1.20+ releases and review optional MCP identity forwarding. Source: https://github.com/Mintplex-Labs/anything-llm/releases/tag/v1.20.0; reviewed 2026-11-18.




## Apache Answer

Self-hosted community questions, answers and knowledge content.

- Listing: https://launchinyourcloud.com/directory/apache-answer/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 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: Apache Answer application and persistent database/storage.
- 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://answer.apache.org
- 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 SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database.

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

Apache Answer application and persistent database/storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted community questions, answers and knowledge content.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/apache-answer.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/apache-answer
  Apache Answer application and persistent database/storage. The Railway SQLite recipe needs its writable volume and is not a multi-writer HA deployment; other packages can use a different database. 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 LinkinStars, aichy126, kumfo, 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/apache/answer/graphs/contributors

- Upstream project: https://github.com/apache/answer

### Sources

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

- Railway: https://railway.com/deploy/apache-answer

- Apache-2.0 LICENSE: https://github.com/apache/answer/blob/main/LICENSE

- Releases v2.0.3: https://github.com/apache/answer/releases

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

### Licensing sources

- https://github.com/apache/answer/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/apache-answer.html

- https://railway.com/deploy/apache-answer


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 official plugin guide demonstrates building Answer with GitHub and Google OAuth connector plugins. Include and configure compatible plugins in the deployed binary/image; this is not a claim that the default image includes enterprise SAML/OIDC. Scope: Official plugin-based application-user OAuth authentication. Source: https://answer.apache.org/docs/plugins (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 installation guide supplies Docker/Compose and binary installation options. Persist the data directory, configure the selected database and include required authentication plugins in the built image; default standalone examples do not supply production HA. Scope: Apache Answer application installation; plugin/custom-image build may be required. Source: https://answer.apache.org/docs/installation (reviewed 2026-11-20). Deployment artifact: https://answer.apache.org/docs/installation. Artifact reference: Current official deployment examples; pin binary/container and plugin versions.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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/apache-answer.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## ArchiveBox

Open-source web archiving application for retained, searchable copies of web content.

- Listing: https://launchinyourcloud.com/directory/archivebox/
- 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: Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service.
- 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://archivebox.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.

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

Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Open-source web archiving application for retained, searchable copies of web content.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger ArchiveBox (hostinger): https://www.hostinger.com/applications/archivebox
  Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway Template (railway): https://railway.com/deploy/archivebox-2
  Persistent ArchiveBox container and browser/extraction workers on a VPS or Railway service. Web snapshots are distinct from retiring a transactional application's business schema or implementing statutory records disposition. Keep the archive volume, browser isolation, chosen image version and backup process under operator control.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes pirate, cdvv7788, claude, 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/ArchiveBox/ArchiveBox/graphs/contributors

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

### Sources

- Hostinger ArchiveBox: https://www.hostinger.com/applications/archivebox

- Railway Template: https://railway.com/deploy/archivebox-2

- MIT LICENSE: https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/main/LICENSE

- GitHub Releases: https://github.com/ArchiveBox/ArchiveBox/releases

### Licensing sources

- https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/main/LICENSE

### Infrastructure sources

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

- https://railway.com/deploy/archivebox-2


### 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 versioned guide supports reverse-proxy authentication using a configured username header and a tightly restricted trusted-proxy IP/CIDR; the application middleware consumes it for user login. Configure a compatible upstream identity proxy and strip spoofed headers. This is a specific trusted-proxy integration rather than proof that merely enabling LDAP establishes federation. Scope: ArchiveBox v0.9.77 reverse-proxy application-user SSO boundary. Source: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/docs/Setting-up-Authentication.md (reviewed 2026-11-21). Supporting source: User authentication middleware — https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/archivebox/core/middleware.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The versioned repository supplies Compose configuration and upstream setup guidance for persistent archive data and application services. Pin compatible application/extractor images, configure access, storage and backups, and validate optional workers/dependencies; provider templates are separately packaged. Scope: ArchiveBox v0.9.77 upstream Compose artifact; provider package versions separate. Source: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/docker-compose.yml (reviewed 2026-11-21). Deployment artifact: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/docker-compose.yml. Artifact reference: v0.9.77.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed current release README and Compose reference do not establish a quantitative whole-production-host CPU/RAM/storage baseline. Browser/extractor concurrency, captured sites, media, index retention, workers and storage/backup growth drive capacity. Scope: ArchiveBox v0.9.77 complete production sizing remains unconfirmed. Source: https://github.com/ArchiveBox/ArchiveBox/blob/v0.9.77/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: ArchiveBox; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/ArchiveBox/ArchiveBox/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Arize Phoenix Self-Hosted

AI observability and evaluation server for traces, datasets and application experiments.

- Listing: https://launchinyourcloud.com/directory/phoenix/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.
- Licensing model: source-available
- Installation: Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.
- Architecture: Customer-operated trace/evaluation application with persistent trace and dataset storage
- Operations: Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.
- Product website: https://arize.com/phoenix/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.

Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated trace/evaluation application with persistent trace and dataset storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-observability: AI trace collection, evaluation, datasets, experiments and prompt analysis for instrumented model applications.

- ai-tools: AI development and operations tooling for tracing and evaluation rather than a model-serving runtime.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://arize.com/docs/phoenix/self-hosting (checked 2026-11-12). 


### Cloud deployment evidence

- Phoenix self-hosting deployment options (aws, azure, gcp, railway): https://arize.com/docs/phoenix/self-hosting
  The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Phoenix self-hosted Render Blueprint (render): https://arize.com/docs/phoenix/self-hosting
  The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Arize's June 2026 maintainer account describes actual participation outside the core team: it attributes OIDC authentication to users needing Keycloak/Cognito and credits contributors with expanding framework integrations and OpenInference. The upstream release history shows continuing maintenance. This concerns concrete community involvement rather than repository star counts; it does not certify any named customer's deployment model.

Reviewed 2026-11-10.

- Maintainer account of user-contributed authentication and integrations: https://arize.com/blog/phoenix-10k/

- Current Phoenix maintenance releases: https://github.com/Arize-ai/phoenix/releases

### Sources

- Official installation and runtime: https://arize.com/docs/phoenix/self-hosting

- Upstream project and capabilities: https://github.com/Arize-ai/phoenix

- Current upstream license: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Licensing sources

- https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE

### Infrastructure sources

- https://arize.com/docs/phoenix/self-hosting


### 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. Phoenix documents OAuth2 authorization-code login with OIDC provider discovery, configured alongside application authentication and secret settings. Configure the trusted provider, callback and account policy; client API keys remain a separate surface. Scope: Self-hosted Phoenix UI OAuth2/OIDC. Source: https://arize.com/docs/phoenix/deployment/authentication (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 Phoenix repository provides self-hosting/container documentation for the observability server. Match persistence and authentication settings to the chosen release; instrumented applications and model services remain separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/arize-ai/phoenix (reviewed 2026-11-14). Deployment artifact: https://github.com/arize-ai/phoenix. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The self-hosting guide documents deployment, storage/database configuration and trace retention, but does not establish a complete CPU/RAM minimum for a specified workload. Size span ingestion, retention, database, evaluation/model dependencies and redundant service instances. Hosted Arize AX sizing is a separate offering. Scope: Phoenix self-hosted application and data services; numeric workload sizing unresolved. Source: https://arize.com/docs/phoenix/self-hosting/deploying-phoenix.md (reviewed 2026-11-20).

- License pricing: Documented. Phoenix uses Elastic License 2.0, including limits on offering substantial hosted/managed functionality and bypassing licence controls. This is not an unrestricted Apache/MIT licence or a hosted-service price; review commercial service/support terms separately. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was arize-phoenix-v21.1.0, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream Arize-ai/phoenix release record; commercial editions and deployment packages may differ. Source: https://github.com/Arize-ai/phoenix/releases/tag/arize-phoenix-v21.1.0 (reviewed 2026-11-14).







## Baserow Self-Hosted

Self-hosted no-code database for organizing, relating and collaborating on business data.

- Listing: https://launchinyourcloud.com/directory/baserow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway, render, heroku
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT-licensed core with paid premium features and subscription terms
- Licensing model: open-source
- Installation: Docker, Docker Compose or official Helm chart
- Architecture: Customer-operated application services with PostgreSQL, Redis and file storage
- Operations: Customer operates the application, database and storage, applies updates and configures backups.
- Product website: https://baserow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.

Baserow Open Source Edition is MIT-licensed. The repository separately licenses Premium and Enterprise feature directories, whose production use requires the corresponding paid subscription; publicly visible source does not make those directories open source.

The official guides deploy persistent application containers with PostgreSQL and Redis, either on a server or orchestrated container infrastructure. Fargate is an available hosting path, but the application remains a persistent service.


Cloud evidence scope: Official documentation establishes AWS deployments; other provider compatibility is not inferred.

### Category fit

- no-code-databases: No-code relational tables, views and APIs for collaborative business data; premium capabilities require the applicable license.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-aws (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation/install-with-docker (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-digital-ocean (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-render (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://baserow.io/docs/installation%2Finstall-on-heroku (checked 2026-11-12). 


### Cloud deployment evidence

- Baserow AWS installation options (aws): https://baserow.io/docs/installation%2Finstall-on-aws
  The vendor documents EC2, ECS/Fargate and EKS application deployment options in the customer AWS account. Select the documented image, persistent database and Redis configuration appropriate to the topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Docker image compatibility with Google Cloud Run (gcp): https://baserow.io/docs/installation/install-with-docker
  The upstream guide explicitly designs the all-in-one application image for simple container services such as Google Cloud Run. Use external PostgreSQL, Redis and durable file storage for a stateless runtime; this is an application-hosting compatibility statement, not evidence based only on a Google storage adapter.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow on DigitalOcean App Platform (digitalocean): https://baserow.io/docs/installation%2Finstall-on-digital-ocean
  The vendor guide deploys the Baserow application container, managed PostgreSQL and Redis, and Spaces storage in the customer DigitalOcean account, with application URL and scaling configuration. The example image tag is version-specific; choose and test the intended supported release.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Railway installation (railway): https://baserow.io/docs/installation%2Finstall-on-railway
  The upstream guide creates a Railway project from the Baserow template and configures the deployed application. The guide requires enough memory and a paid plan rather than assuming the free trial is adequate. Railway operates the underlying infrastructure; the customer controls the application project.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Render application template (render): https://baserow.io/docs/installation%2Finstall-on-render
  The upstream guide provides a full application template using paid Render compute and PostgreSQL plans. Its published plan prices and repository branch examples can age; verify the current template, compatible release, resources and data persistence rather than assuming a free production tier.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Baserow Heroku application template (heroku): https://baserow.io/docs/installation%2Finstall-on-heroku
  The upstream guide documents a beta deployment template for the Baserow application and supporting Heroku services, with configuration and scaling instructions. It requires paid resources; review the current template, image, database and file-storage settings before production use.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Product and licensing FAQ: https://baserow.io/faq

- Docker installation: https://baserow.io/docs/installation/install-with-docker

- AWS installation paths: https://baserow.io/docs/installation%2Finstall-on-aws

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/LICENSE

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE

- Licensing and edition terms: https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE

- Baserow on DigitalOcean App Platform: https://baserow.io/docs/installation%2Finstall-on-digital-ocean

- Baserow Railway installation: https://baserow.io/docs/installation%2Finstall-on-railway

- Baserow Render application template: https://baserow.io/docs/installation%2Finstall-on-render

- Baserow Heroku application template: https://baserow.io/docs/installation%2Finstall-on-heroku

### Licensing sources

- https://raw.githubusercontent.com/baserow/baserow/develop/LICENSE

- https://raw.githubusercontent.com/baserow/baserow/develop/premium/LICENSE

- https://raw.githubusercontent.com/baserow/baserow/develop/enterprise/LICENSE

### Infrastructure sources

- https://baserow.io/docs/installation/install-with-docker

- https://baserow.io/docs/installation%2Finstall-on-aws


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. Instance administrators can configure SAML and OAuth/OIDC providers on Advanced or Enterprise with an activated license. This is not established for the free self-hosted edition. Scope: Self-hosted Advanced/Enterprise authentication. Source: https://baserow.io/user-docs/enable-single-sign-on-sso (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 all-in-one Docker guide documents persistence, HTTPS and external database/cache configuration. It recommends an external PostgreSQL service for production and describes database-version upgrade handling. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://baserow.io/docs/installation/install-with-docker (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The official DigitalOcean App Platform guide specifies at least one application container with 1 vCPU and 2 GB RAM, plus separately provisioned managed PostgreSQL, Redis and Spaces storage. Its smaller database example is not the application or complete-host requirement. Scope: Provider-specific stateless application baseline, not a universal all-in-one minimum or HA design. Source: https://baserow.io/docs/installation/install-on-digital-ocean (reviewed 2026-11-20).

- License pricing: Documented. The 2.4.3 Open Source Edition is MIT-licensed, with separate Premium and Enterprise directories. Production use of either paid edition requires the corresponding subscription for the correct number of users and applicable subscription terms; do not apply Cloud prices to a self-hosted contract. Scope: Versioned open-source versus paid-edition software rights; excludes hosting and support. Source: https://github.com/baserow/baserow/blob/2.4.3/LICENSE (reviewed 2026-11-20). Supporting source: Premium edition licence — https://github.com/baserow/baserow/blob/2.4.3/premium/LICENSE. Supporting source: Enterprise edition licence — https://github.com/baserow/baserow/blob/2.4.3/enterprise/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 2.4.3, published 2026-11-14. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream baserow/baserow release record; commercial editions and deployment packages may differ. Source: https://github.com/baserow/baserow/releases/tag/2.4.3 (reviewed 2026-11-14).







## CISO Assistant Community

Community GRC platform with supplier risk assessments, evidence documents and third-party records.

- Listing: https://launchinyourcloud.com/directory/ciso-assistant/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy 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://intuitem.com
- 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 comparison explicitly includes TPRM, evidence/document management and SAML SSO in Community. SCIM, advanced audit trails and other Pro features have separate commercial terms; Pro air-gap claims do not establish Community disconnected support.

AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence.

Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Community GRC platform with supplier risk assessments, evidence documents and third-party records.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/ciso-assistant
  Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy on Railway. The vendor comparison explicitly includes TPRM, evidence/document management and SAML SSO in Community. SCIM, advanced audit trails and other Pro features have separate commercial terms; Pro air-gap claims do not establish Community disconnected support.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ab-smith, nas-tabchiche, Mohamed-Hacene, 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/intuitem/ciso-assistant-community/graphs/contributors

- Upstream project: https://github.com/intuitem/ciso-assistant-community

### Sources

- Railway Template: https://railway.com/deploy/ciso-assistant

- TPRM Guide: https://github.com/intuitem/ciso-assistant-community/blob/main/product-docs/guides/tprm.md

- AGPL-3.0 LICENSE.md: https://github.com/intuitem/ciso-assistant-community/blob/main/LICENSE.md

- GitHub Releases: https://github.com/intuitem/ciso-assistant-community/releases

- Community vs Pro - Feature Comparison — intuitem: https://intuitem.com/compare

- CISO Assistant FAQ — intuitem: https://intuitem.com/faq

### Licensing sources

- https://github.com/intuitem/ciso-assistant-community/blob/main/LICENSE.md

### Infrastructure sources

- https://railway.com/deploy/ciso-assistant


### 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: Documented. Community includes SAML and OIDC single sign-on. Configure the provider, role mapping and recovery access for the selected deployment. Scope: CISO Assistant Community versus Pro; current vendor comparison and FAQ. Source: https://intuitem.com/faq (reviewed 2026-11-19). Supporting source: Community/Pro feature comparison — https://intuitem.com/compare.

- SCIM provisioning: Explicitly unsupported. The vendor specifies SCIM group-based provisioning as a Pro feature; it is not included in the selected Community edition. Scope: CISO Assistant Community versus Pro; current vendor comparison and FAQ. Source: https://intuitem.com/faq (reviewed 2026-11-19). Supporting source: Community/Pro feature comparison — https://intuitem.com/compare.

- Compliance attestations: Not researched.

- Security controls: Documented. The vendor documents TOTP and hardware-key MFA in Community; Pro-only audit and permission features are separate. Scope: CISO Assistant Community versus Pro; current vendor comparison and FAQ. Source: https://intuitem.com/faq (reviewed 2026-11-19). Supporting source: Community/Pro feature comparison — https://intuitem.com/compare.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Railway template defines the Community backend/frontend, database and supporting services. Pin compatible versions, keep secrets stable and validate durable attachments, queues and any AI service before production. Scope: CISO Assistant Community Railway deployment template, separate from Pro and the TPRM feature guide. Source: https://railway.com/deploy/ciso-assistant (reviewed 2026-11-19). Deployment artifact: https://railway.com/deploy/ciso-assistant. Artifact reference: Community Railway template; latest backend/frontend image tags are moving references.

- Minimum footprint / sizing: Documented. The v4.3.3 on-premises prerequisites specify four CPU cores, at least 16 GB RAM and 10 GB storage, with extra capacity for evidence files and lower specifications only for testing. Database choice, workers, concurrency, backups and HA remain deployment-specific. Scope: CISO Assistant v4.3.3 upstream on-premises baseline, not reference-workload HA sizing. Source: https://github.com/intuitem/ciso-assistant-community/blob/v4.3.3/product-docs/installation/prerequisites.md (reviewed 2026-11-21).

- License pricing: Edition-dependent. AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence. Scope: CISO Assistant Community; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/intuitem/ciso-assistant-community/blob/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v4.3.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: CISO Assistant Community upstream application; verify compatibility with the selected package. Source: https://github.com/intuitem/ciso-assistant-community/releases/tag/v4.3.3 (reviewed 2026-11-19).







## Cockpit CMS

Self-hosted structured content and API management application.

- Listing: https://launchinyourcloud.com/directory/cockpit-cms/
- 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: Cockpit Core application with persistent SQLite database and storage 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://getcockpit.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Core is MIT-licensed. Commercial modules and add-ons have separate terms; the single writable SQLite volume does not establish active-active HA.

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

Cockpit Core application with persistent SQLite database and storage on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- content-management: Self-hosted structured content and API management application.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/cockpit
  Cockpit Core application with persistent SQLite database and storage on Railway. Core is MIT-licensed. Commercial modules and add-ons have separate terms; the single writable SQLite volume does not establish active-active HA.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes aheinze, raffaelj, filipmiik, 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/Cockpit-HQ/Cockpit/graphs/contributors

- Upstream project: https://github.com/Cockpit-HQ/Cockpit

### Sources

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

- MIT LICENSE: https://github.com/Cockpit-HQ/Cockpit/blob/develop/LICENSE

- Releases v2.14.1: https://github.com/Cockpit-HQ/Cockpit/releases

### Licensing sources

- https://github.com/Cockpit-HQ/Cockpit/blob/develop/LICENSE

### Infrastructure sources

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


### 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 CMS authentication guide documents OIDC through the Identi module, including provider discovery, PKCE, claim/role mapping and provider examples. Confirm module packaging and entitlement for the selected build; this is Cockpit CMS, not the unrelated Linux Cockpit administration tool. Scope: Current Cockpit-HQ CMS Identi module; package/version compatibility remains deployment-specific. Source: https://getcockpit.com/documentation/core/concepts/authentication (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 project supplies a downloadable CMS ZIP and a container run command with persistent storage. Its example uses a moving core-latest image; pin a compatible release and configure the web server, permissions, backups and secrets. This is an application artifact, not HA IaC. Scope: Current Cockpit-HQ CMS quick start; upstream Core application packaging. Source: https://github.com/Cockpit-HQ/Cockpit (reviewed 2026-11-20). Deployment artifact: https://github.com/Cockpit-HQ/Cockpit/releases. Artifact reference: Choose a release ZIP or pinned compatible container; reviewed quick start uses core-latest.

- Minimum footprint / sizing: Sources checked — unresolved. The upstream requirements list PHP 8.3+, SQLite or MongoDB, a compatible web server and writable application storage. They do not establish a quantitative CPU/RAM/disk production floor for the chosen CMS and database topology. Scope: Current CMS software prerequisites; numeric production sizing remains open. Source: https://github.com/Cockpit-HQ/Cockpit (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Directus Self-Hosted

Self-hosted content and data management with APIs over your SQL database.

- Listing: https://launchinyourcloud.com/directory/directus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Source-available MSCL-1.0-GPL; free Core tier and licensed capabilities; qualifying Open Innovation Grant
- Licensing model: source-available
- Installation: Version-pinned Docker image/Compose with database and optional Redis/cache
- Architecture: Customer-operated API and management Studio with database and asset storage
- Operations: Customer operates containers, database, caching, asset storage, monitoring, backups and upgrades.
- Product website: https://directus.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current Directus 12 uses MSCL-1.0-GPL, replacing older BSL terms. Core has limits; higher limits and advanced features require a paid license or qualifying grant. Verify licensing against the actual release and do not assume all source-available features are unrestricted. This entry excludes Directus Cloud.

Current Directus 12 uses MSCL-1.0-GPL with competing-use and protected-license-functionality restrictions. The free Core tier or qualifying grant does not make the current core OSI-licensed; older releases had different terms.

The reviewed option runs a long-lived Directus container, SQL persistence and optional Redis/storage services. Storage adapters do not establish customer-account deployment support for a named hyperscaler.


### Category fit

- content-management: Configurable content/data backend with management Studio, REST/GraphQL APIs and flows over SQL data.

### Deployment boundaries


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


### Cloud deployment evidence

- Directus 12 community deployment on Railway (railway): https://railway.com/deploy/directus-1
  The inspected community template uses the official Directus 12.6.1 image pinned by digest, PostgreSQL, Redis and bucket storage in a customer Railway project. Confirm current license/tier limits, image compatibility, initial credentials and email configuration; this is not Directus Cloud.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker deployment and persistence: https://directus.com/docs/self-hosting/deploying

- Self-hosting overview and licensing: https://directus.com/docs/self-hosting/overview

- Current official license: https://github.com/directus/directus/blob/main/license

- Core and licensed tier overview: https://directus.com/start

### Licensing sources

- https://github.com/directus/directus/blob/main/license

- https://directus.com/docs/self-hosting/overview

### Infrastructure sources

- https://directus.com/docs/self-hosting/deploying


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. Self-hosted authentication configuration supports OAuth 2.0, OpenID, LDAP and SAML providers. Configure callback URLs and provider settings; this documents protocols, not an independent commercial-license entitlement. Scope: Self-hosted Directus authentication configuration. Source: https://directus.com/docs/configuration/auth-sso (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 deployment guide supplies Compose examples with database, Redis and persistent application storage. Replace placeholder credentials and select compatible image tags; the example is not a complete cloud provisioning template. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://directus.com/docs/self-hosting/deploying (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The self-hosting guide gives a container minimum of 0.25 vCPU and 512 MB RAM and a larger recommended configuration. Database, storage, replicas and workload require separate capacity planning. Scope: Directus container baseline only. Source: https://directus.com/docs/self-hosting/requirements (reviewed 2026-11-14).

- License pricing: Documented. The current self-hosting guide identifies MSCL, a free Core tier and paid higher limits/features. Eligible individuals and small organizations can apply for an Open Innovation Grant. Infrastructure, databases and operational labor are separate; do not apply older BSL revenue rules to the current license. Scope: Current MSCL self-hosting guidance; eligibility and feature limits require the current license terms. Source: https://directus.com/docs/self-hosting/overview (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v12.6.1, published 2026-11-04. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream directus/directus release record; commercial editions and deployment packages may differ. Source: https://github.com/directus/directus/releases/tag/v12.6.1 (reviewed 2026-11-14).







## Dittofeed

Self-hosted customer engagement and messaging orchestration platform.

- Listing: https://launchinyourcloud.com/directory/dittofeed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: render, railway, hostinger
- 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: Dittofeed application, PostgreSQL, ClickHouse and supporting services.
- 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://dittofeed.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.

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

Dittofeed application, PostgreSQL, ClickHouse and supporting services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted customer engagement and messaging orchestration platform.

### Deployment boundaries


- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.dittofeed.com/deployment/self-hosted/render.md (checked 2026-11-19). 

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

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


### Cloud deployment evidence

- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil (render): https://docs.dittofeed.com/deployment/self-hosted/render.md
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/dittofeed-2
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Hostinger (hostinger): https://www.hostinger.com/applications/dittofeed
  Dittofeed application, PostgreSQL, ClickHouse and supporting services. Hosting is separate from sending providers. Preview releases and the lightweight provider package must not be presented as the latest stable production edition.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes maxgurewitz, chandlercraig, neo773, 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/dittofeed/dittofeed/graphs/contributors

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

### Sources

- > ## Documentation Index
> Fetch the complete documentation index at: https://docs.dittofeed.com/llms.txt
> Use this fil: https://docs.dittofeed.com/deployment/self-hosted/render.md

- Railway: https://railway.com/deploy/dittofeed-2

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

- Render Guide: https://docs.dittofeed.com/deployment/self-hosted/render

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

- GitHub Releases: https://github.com/dittofeed/dittofeed/releases

### Licensing sources

- https://raw.githubusercontent.com/dittofeed/dittofeed/main/LICENSE

### Infrastructure sources

- https://docs.dittofeed.com/deployment/self-hosted/render.md

- https://railway.com/deploy/dittofeed-2

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. OIDC-based multi-tenant authentication is documented, but the detailed guide restricts that mode to dittofeed-ee and Dittofeed Cloud. The community lite deployment instead offers a shared-password single-tenant mode. Obtain the Enterprise image/entitlement and configure provider claims and workspace access; anonymous demo mode is unsuitable for production. Scope: Self-hosted Enterprise OIDC versus community/lite authentication; detailed mode restrictions override the general overview. Source: https://docs.dittofeed.com/deployment/self-hosted/auth-modes/multi-tenant.md (reviewed 2026-11-20). Supporting source: Authentication-mode overview — https://docs.dittofeed.com/deployment/self-hosted/auth-modes.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker guide links the lite Compose stack and documents replacing default credentials, secrets and dashboard URLs. It includes PostgreSQL, ClickHouse and workflow services; the vendor also publishes a Helm chart. Choose a compatible pinned release and configure storage, TLS, authentication and backups; Enterprise uses a separately entitled image. Scope: Vendor community/lite deployment recipe, distinct from Enterprise image delivery. Source: https://docs.dittofeed.com/deployment/self-hosted/docker-compose.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dittofeed/dittofeed/blob/main/docker-compose.lite.yaml. Artifact reference: main (moving branch; pin compatible application and dependency versions). Supporting source: Official Kubernetes/Helm recipe — https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md.

- Minimum footprint / sizing: Documented. The Helm guide lists application-container requests/limits of 1 CPU and 512 MiB RAM and ClickHouse memory requests/limits of 1 GiB. These are component configuration defaults, not a whole-stack minimum: PostgreSQL, Temporal, storage, replicas and traffic need separate capacity. They do not size 100 users, 1 TB or HA. Scope: Documented chart component allocations, not total host or production capacity. Source: https://docs.dittofeed.com/deployment/self-hosted/kubernetes.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Docmost Self-Hosted

Self-hosted collaborative wiki and documentation with real-time editing, spaces and page history.

- Listing: https://launchinyourcloud.com/directory/docmost/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; Business and Enterprise features use separate commercial terms.
- Licensing model: open-source
- Installation: Vendor Docker Compose installation with PostgreSQL/Redis, or a community Railway project template.
- Architecture: Persistent web/API and collaborative-editing services with PostgreSQL, Redis and attachment storage
- Operations: Customer manages workspace access, secrets, database and attachment recovery, mail configuration and upgrades. Railway operates the underlying platform within the customer project.
- Product website: https://docmost.com/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used upstream 0.97.0, which includes security updates. Select a current pinned image; the canonical Railway template uses latest. Do not use the older 0.95.0 template unchanged: upstream fixed a private-space metadata issue in 0.96.0. SSO, audit logs, AI and other paid features require appropriate entitlements. Optional AI, mail and link-preview integrations introduce external connections.

Core code is AGPL-3.0. Enterprise directories and paid Business/Enterprise features are commercially licensed; this entry does not classify those features as open source.

Persistent web/API and collaborative-editing services with PostgreSQL, Redis and attachment storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- collaboration: Provides collaborative wiki pages, spaces, comments, attachments, history and documentation search. Paid governance and integration features have separate edition requirements.

### Deployment boundaries


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


### Cloud deployment evidence

- Community Docmost deployment with database, queue and storage (railway): https://railway.com/deploy/docmost
  The canonical community template installs the upstream Docmost image with PostgreSQL, Redis and persistent attachment storage in a customer Railway project. Its image is mutable: select a current pinned release and validate APP_SECRET, database/queue variables, HTTPS and backups against vendor instructions. Paid-feature claims on the template page do not override upstream edition licensing.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

Upstream maintains active releases and security advisories with contributions from multiple participants. Release 0.97.0 records maintenance and security updates; contributor history establishes ongoing participation beyond repository stars.

Reviewed 2026-11-13.

- Reviewed 0.97.0 release: https://github.com/docmost/docmost/releases/tag/v0.97.0

- Contributor history: https://github.com/docmost/docmost/graphs/contributors

### Sources

- Vendor installation, persistence and upgrades: https://docmost.com/docs/installation

- Self-managed edition pricing and features: https://docmost.com/pricing

- Metadata access advisory and fixed release: https://github.com/docmost/docmost/security/advisories/GHSA-c34c-w352-hq95

- Community Docmost deployment with database, queue and storage: https://railway.com/deploy/docmost

- Core and enterprise license boundaries: https://github.com/docmost/docmost

- Exact core license: https://github.com/docmost/docmost/blob/main/LICENSE

- Reviewed 0.97.0 release: https://github.com/docmost/docmost/releases/tag/v0.97.0

- Contributor history: https://github.com/docmost/docmost/graphs/contributors

### Licensing sources

- https://github.com/docmost/docmost

- https://github.com/docmost/docmost/blob/main/LICENSE

### Infrastructure sources

- https://docmost.com/docs/installation

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The vendor self-hosted guide documents SAML, OIDC and LDAP with a paid edition. Identity/group mapping and the applicable license need configuration. Scope: Paid self-hosted Docmost; not Community. Source: https://docmost.com/blog/how-to-set-up-sso-for-a-self-hosted-wiki/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. SCIM user/group provisioning and deactivation require Enterprise. SSO must be configured first; SCIM-managed group membership takes precedence over login-time group sync. Scope: Self-hosted Enterprise. Source: https://docmost.com/blog/how-to-set-up-sso-for-a-self-hosted-wiki/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Edition-dependent. The project documents that the core self-hosted wiki can run air-gapped without external dependencies. Confirm offline licensing and any separately enabled AI or external integration before applying this to a paid configuration. Scope: Core self-hosted wiki capability; not a claim that every integration works offline. Source: https://docmost.com/docs/ (reviewed 2026-11-14).

- Deployment artifact / IaC: Documented. The upstream Compose file defines Docmost, PostgreSQL 18 and Redis 8 with persistent volumes. Replace example secrets and the application URL, enable WebSockets through the proxy, and pin compatible versions instead of relying on latest. Scope: Upstream self-hosting example; not a multi-node HA reference. Source: https://docmost.com/docs/installation (reviewed 2026-11-20). Deployment artifact: https://raw.githubusercontent.com/docmost/docmost/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide and Compose stack establish application, PostgreSQL and Redis dependencies, but publish no CPU/RAM or concurrency minimum in the reviewed instructions. Confirm sizing for users, document/attachment volume and HA before choosing a host. Scope: Self-hosted dependency topology; no quantitative production floor established. Source: https://docmost.com/docs/installation (reviewed 2026-11-20). Supporting source: Upstream Compose dependencies — https://raw.githubusercontent.com/docmost/docmost/main/docker-compose.yml.

- License pricing: Documented. Community is free. Business is listed at $6/seat/month billed annually with a ten-seat minimum; Enterprise has custom pricing. Paid features and self-hosted license activation are separate from running the free core and paying for infrastructure. Scope: Published self-hosted Community, Business and Enterprise plans. Source: https://docmost.com/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v0.97.0, published 2026-10-25. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream docmost/docmost release record; commercial editions and deployment packages may differ. Source: https://github.com/docmost/docmost/releases/tag/v0.97.0 (reviewed 2026-11-14).







## Docspell

Self-hosted document ingestion, OCR, classification and search.

- Listing: https://launchinyourcloud.com/directory/docspell/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, 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; Docker / Compose
- Architecture: Docspell REST server and job executor sharing PostgreSQL and durable document storage.
- 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://docspell.org
- 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 uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.

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

Docspell REST server and job executor sharing PostgreSQL and durable document storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document ingestion, OCR, classification and search.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/docspell
  Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/docspell-1
  Docspell REST server and job executor sharing PostgreSQL and durable document storage. The Railway recipe uses PostgreSQL full-text search rather than Solr. Joex and REST services must reach each other and use matching application versions.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes eikek, scala-steward, eikek-scala-steward, 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/eikek/docspell/graphs/contributors

- Upstream project: https://github.com/eikek/docspell

### Sources

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

- Railway: https://railway.com/deploy/docspell-1

- AGPL-3.0 LICENSE.txt: https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt

- GitHub Releases: https://github.com/eikek/docspell/releases

### Licensing sources

- https://raw.githubusercontent.com/eikek/docspell/master/LICENSE.txt

### Infrastructure sources

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

- https://railway.com/deploy/docspell-1


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 server supports OIDC/OAuth2 sign-in using a configured external provider; multiple providers are supported and Keycloak configuration is documented. Configure registration, collective mapping and provider settings for the selected release. Scope: Self-hosted Docspell REST server authentication. Source: https://docspell.org/docs/configure/authentication/ (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 project maintains a Compose deployment for the REST server, job executor, PostgreSQL and full-text search. Change the documented secrets, persist data and pin compatible image versions; moving latest/nightly tags are not immutable releases. Scope: Upstream Compose deployment; single-machine default, not HA. Source: https://docspell.org/docs/install/docker/ (reviewed 2026-11-20). Deployment artifact: https://github.com/docspell/docker/tree/master/docker-compose. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The project recommends 4 GB RAM for a small board running Joex with its database and Solr, with Joex pool size 1. Its example 1-CPU/4-GB VM is a processing illustration, not validated 100-user, 1-TB or HA capacity; OCR languages and classification affect memory. Scope: Upstream low-resource example; not production/HA workload sizing. Source: https://docspell.org/docs/install/rpi/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Documenso Self-Hosted

Self-hosted electronic-signature and document workflow application with a Railway deployment path.

- Listing: https://launchinyourcloud.com/directory/documenso/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Community Edition; Enterprise Edition uses a commercial license.
- Licensing model: open-source
- Installation: Official Railway template or manual Railway deployment from the upstream repository
- Architecture: Application service with PostgreSQL, SMTP, signing configuration and persistent document data
- Operations: Customer manages the Railway project, application secrets, PostgreSQL recovery, SMTP, signing certificates, domains, access controls, data retention and upgrades; Railway operates the platform.
- Product website: https://documenso.com/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

The official Railway page labels its instructions as a community contribution that may become outdated. Confirm the current upstream image or source revision and template before deployment. Production signing requires correctly protected encryption keys, SMTP and signing-certificate configuration. This entry covers signing workflow automation, not full contract lifecycle management.

Documenso Community Edition is AGPL-3.0. Enterprise Edition uses a separate commercial license; confirm the selected edition and AGPL obligations for modifications and network use.

The Railway deployment runs a long-lived application service and PostgreSQL database, with SMTP and persistent document data.


### Category fit

- workflow-automation: Automates document preparation, signing requests, recipient completion and status-driven electronic-signature workflows through a self-hosted application.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.documenso.com/docs/self-hosting/deployment/railway (checked 2026-11-15). 


### Cloud deployment evidence

- Documenso deployment in a Railway project (railway): https://docs.documenso.com/docs/self-hosting/deployment/railway
  Documenso's official documentation provides an official Railway template and a manual project workflow that provisions the application service and managed PostgreSQL, configures secrets and networking and exposes the customer's deployment URL. The page identifies the guide as a community contribution that may become outdated. This is community-contributed deployment guidance published in the upstream documentation, not a verified vendor support commitment.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

Documenso release v2.22.0 was published on November 13, 2026, and its public contributor history shows continuing upstream participation. This evidence applies to the open-source project, not to paid Enterprise support or the longevity of the Railway template.

Reviewed 2026-11-15.

- Reviewed release v2.22.0: https://github.com/documenso/documenso/releases/tag/v2.22.0

- Upstream contributor history: https://github.com/documenso/documenso/graphs/contributors

### Sources

- Documenso Railway deployment: https://docs.documenso.com/docs/self-hosting/deployment/railway

- Documenso deployment options: https://docs.documenso.com/docs/self-hosting/deployment

- Community and Enterprise licenses: https://docs.documenso.com/docs/policies/licenses

- Reviewed release v2.22.0: https://github.com/documenso/documenso/releases/tag/v2.22.0

- Upstream contributor history: https://github.com/documenso/documenso/graphs/contributors

### Licensing sources

- https://docs.documenso.com/docs/policies/licenses

### Infrastructure sources

- https://docs.documenso.com/docs/self-hosting/deployment/railway


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Organisation SSO supports OIDC identity providers and is explicitly Enterprise-only. An organisation admin/manager configures the redirect, scopes, issuer, client credentials, allowed domains and default role; the self-hosting guide confirms enterprise features require a licence key. Scope: Self-hosted Enterprise organisation user SSO; distinct from individual social sign-in and signer authentication. Source: https://docs.documenso.com/docs/users/organisations/single-sign-on/configuration (reviewed 2026-11-20). Supporting source: Self-hosted Enterprise activation — https://docs.documenso.com/docs/self-hosting.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Railway guide supplies a one-click application/PostgreSQL template and manual setup. It is explicitly a community contribution that may be outdated. SMTP credentials are required for signing-request email; validate the deployed version and configuration. Scope: Documenso Railway community-contributed deployment guide. Source: https://docs.documenso.com/docs/self-hosting/deployment/railway (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The current requirements distinguish testing/development (1 core, 1 GB RAM, 10 GB storage) from recommended production (2+ cores, 2+ GB RAM, 20+ GB storage). PostgreSQL, email delivery, a signing certificate and HTTPS are required; document storage and optional conversion services need separate planning. Scope: Current general self-hosting guidance, not a backdated v2.22.0 specification or an HA/1-TB capacity guarantee. Source: https://docs.documenso.com/docs/self-hosting/getting-started/requirements (reviewed 2026-11-20).

- License pricing: Documented. Community Edition is AGPL-3.0, with the v2.22.0 licence available in the repository. Enterprise Edition uses commercial terms and a licence key for enterprise features. Obtain a self-hosted entitlement and price for the selected features rather than applying hosted subscription prices. Scope: Community versus commercial enterprise licensing; software fees exclude hosting, signing certificates and operations. Source: https://docs.documenso.com/docs/policies/licenses (reviewed 2026-11-20). Supporting source: Versioned licence — https://github.com/documenso/documenso/blob/v2.22.0/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Documize Self-Hosted

Self-hosted knowledge management with structured documents, templates and controlled publication workflows.

- Listing: https://launchinyourcloud.com/directory/documize/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source Community and commercial options; edition features differ
- Licensing model: open-source
- Installation: Native application binary plus a supported customer-managed SQL database
- Architecture: Customer-operated knowledge application and SQL database
- Operations: Customer controls application/database hosting, access, backups and upgrades.
- Product website: https://documize.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Documize documents native binary deployment and supported database choices. Its commercial feature list includes approvals, revisions and lifecycle controls. Match the selected edition to policy workflow requirements; no provider-specific deployment support was verified.

The broad listing includes AGPLv3 Community and commercially offered Community+ features such as approval workflows, version/lifecycle management and audit logs. These feature differences, rather than paid support alone, support open-core classification.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- policy-procedure-management: Adjacent knowledge/documentation platform with structured documents and a review-to-publication lifecycle. Not verified as a dedicated attestation or policy-compliance suite. Approval and lifecycle capabilities depend on edition.

### Deployment boundaries


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


### Cloud deployment evidence

- Documize community deployment on Railway (railway): https://railway.com/deploy/documize
  The community recipe deploys Documize Community with PostgreSQL in a customer Railway project. It builds a community fork rather than a vendor-maintained image; inspect its source and replace unsupported runtime base images before production. No Documize commercial-edition features or vendor support are implied.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the community Documize Railway build (railway): https://github.com/Shinyduo/documize-railway/blob/master/Dockerfile
  The inspected build compiles the Documize Community Go backend and Ember frontend. Its runtime currently uses Alpine 3.16, so update the base and validate compatibility before production; the source establishes a deployment recipe rather than a security certification.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Product capabilities and own-infrastructure operation: https://documize.com/

- Download and installation requirements: https://documize.com/get-started/

- Edition approval and lifecycle features: https://documize.com/pricing/

- License and own-infrastructure terms: https://documize.com/terms/

- Licensing and edition terms: https://github.com/documize/community

### Licensing sources

- https://github.com/documize/community

- https://documize.com/terms/

- https://documize.com/pricing/

### Infrastructure sources

- https://documize.com/

- https://documize.com/get-started/


### 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 versioned Community README documents Keycloak and CAS login alongside LDAP/Active Directory. The current self-hosted pricing page also lists those authentication options for paid plans. Configure the selected backend and account policies; LDAP/password validation alone is not the federation evidence. Scope: Documize v5.14.0 upstream authentication options; selected edition/configuration. Source: https://github.com/documize/community/blob/v5.14.0/README.md (reviewed 2026-11-21). Supporting source: Current self-hosted plans — https://documize.com/pricing/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Documize Community is distributed as a native application executable for supported operating systems, with a separately configured SQL database. Select an application release and compatible database rather than assuming a bundled appliance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/documize/community (reviewed 2026-11-14). Deployment artifact: https://github.com/documize/community/releases. Artifact reference: select a versioned Community release.

- Minimum footprint / sizing: Sources checked — unresolved. The v5.14.0 README identifies the executable and supported external databases but gives no numeric production CPU/RAM/storage baseline. A small binary or third-party estimated RAM tier cannot size concurrent editors, full-text search, attachments, database and HA. Scope: Documize v5.14.0 production hardware capacity remains unconfirmed. Source: https://github.com/documize/community/blob/v5.14.0/README.md (reviewed 2026-11-21).

- License pricing: Documented. Community v5.14.0 is AGPLv3; the vendor separately sells self-hosted annual plans and offers a free activation key for the first five users. Select Community versus activated commercial functionality and obtain current user-limit/support terms; hosted storage and infrastructure costs are separate. Scope: Documize Community source licence versus commercial self-hosted plans. Source: https://documize.com/pricing/ (reviewed 2026-11-21). Supporting source: Community licence — https://github.com/documize/community/blob/v5.14.0/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v5.14.0, published 2025-09-19. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream documize/community release record; commercial editions and deployment packages may differ. Source: https://github.com/documize/community/releases/tag/v5.14.0 (reviewed 2026-11-14).







## DocuSeal Self-Hosted

Self-hosted document forms and electronic-signature workflows with API and webhook integration.

- Listing: https://launchinyourcloud.com/directory/docuseal/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, azure, gcp, railway, heroku, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
- Licensing model: open-source
- Installation: Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.
- Architecture: Rails web application and document-processing jobs with a database, attachments and signing configuration
- Operations: Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.
- Product website: https://www.docuseal.com/
- Source review: 2026-11-19; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.

AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms. Cloudron packaging and platform plans have separate terms; the application license does not grant a free platform subscription.

Web application containers and document-processing jobs with durable database and attachment storage on Cloudron or managed application platforms. Cloud Run container hosting does not establish event-driven function deployment support.


### Category fit

- workflow-automation: Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance.

### Deployment boundaries


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

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/cloudron (checked 2026-11-13). Source: https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml (checked 2026-11-13). 

- linode: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.linode.com/docs/marketplace-docs/guides/cloudron/ (checked 2026-11-13). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloudron.io/installation/ (checked 2026-11-13). 

- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/ (checked 2026-11-13). 

- lumadock: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://lumadock.com/vps-hosting/cloudron (checked 2026-11-13). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps (checked 2026-11-13). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run (checked 2026-11-13). 

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

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/docusealco/docuseal-heroku/blob/master/app.json (checked 2026-11-13). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://github.com/docusealco/docuseal-render/blob/master/render.yaml (checked 2026-11-13). 


### Cloud deployment evidence

- Cloudron EC2 AMI and application installation (aws): https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Droplet deployment (digitalocean): https://marketplace.digitalocean.com/apps/cloudron
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: marketplace-offer; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron customer Linode deployment (linode): https://www.linode.com/docs/marketplace-docs/guides/cloudron/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Cloudron named-provider installation and Marketplace availability (vultr): https://docs.cloudron.io/installation/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.
  Source type: package-platform-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Hostinger customer VPS Cloudron template (hostinger): https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- LumaDock customer VPS Cloudron template (lumadock): https://lumadock.com/vps-hosting/cloudron
  DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Azure Web Apps deployment (azure): https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps
  Installs the actual application container in a customer Azure resource group with PostgreSQL and Blob Storage. Configure secrets, storage and production database network restrictions rather than retaining permissive example firewall rules.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Google Cloud Run deployment (gcp): https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run
  Installs the actual application container in a customer project with Cloud SQL and Google Cloud Storage. Configure keys, bucket access and production database network restrictions. This is application hosting, not a storage-only integration.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor DigitalOcean application specification (digitalocean): https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml
  Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor-linked Railway application template (railway): https://railway.com/deploy/IGoDnc
  Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Heroku application specification (heroku): https://github.com/docusealco/docuseal-heroku/blob/master/app.json
  Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.

- Vendor Render application blueprint (render): https://github.com/docusealco/docuseal-render/blob/master/render.yaml
  Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound mail.
  Source type: vendor-documentation; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The current core has sustained work by two principal maintainers, external code contributions and continuing security releases. Public contributor and release histories establish ongoing maintenance; they do not independently validate every paid feature or customer deployment.

Reviewed 2026-11-19.

- Contributor history: https://github.com/docusealco/docuseal/graphs/contributors

- Reviewed maintenance and security release 3.3.8: https://github.com/docusealco/docuseal/releases/tag/3.3.8

- Release history: https://www.docuseal.com/changelog

### Sources

- Self-hosted edition and boundaries: https://www.docuseal.com/on-premises

- Vendor installation options: https://www.docuseal.com/install

- Production runtime requirements: https://www.docuseal.com/docs/on-premises-server-requirements

- Configuration, secrets and storage: https://www.docuseal.com/docs/configuring-docuseal-via-environment-variables

- Cloudron application operations: https://docs.cloudron.io/packages/docuseal/

- Core application and installation: https://github.com/docusealco/docuseal/blob/3.3.6/README.md

- Attachment storage configuration: https://github.com/docusealco/docuseal/blob/3.3.6/config/storage.yml

- Default storage selection: https://github.com/docusealco/docuseal/blob/3.3.6/config/environments/production.rb

- Pro image, licensing and usage connection: https://www.docuseal.com/docs/on-premises-pro-installation

- Qualified signature edition limitation: https://www.docuseal.com/faq/how-to-use-qes-signing-with-docuseal-on-premises

- Current security release: https://github.com/docusealco/docuseal/releases/tag/3.3.7

- Release and security history: https://www.docuseal.com/changelog

- Core AGPL license: https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE

- Contributor history: https://github.com/docusealco/docuseal/graphs/contributors

- Cloudron application packages and persistent data: https://docs.cloudron.io/apps/

- Cloudron application updates: https://docs.cloudron.io/updates/

- Cloudron database and application-data backups: https://docs.cloudron.io/backups/

- Cloudron platform plans: https://www.cloudron.io/pricing.html

- Cloudron account and platform terms: https://www.cloudron.io/legal/terms.html

- Cloudron account and installation metadata: https://www.cloudron.io/legal/privacy.html

- Exact Cloudron application package versions: https://www.cloudron.io/store/index.html

- Cloudron EC2 AMI and application installation: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci

- Cloudron customer Droplet deployment: https://marketplace.digitalocean.com/apps/cloudron

- Cloudron customer Linode deployment: https://www.linode.com/docs/marketplace-docs/guides/cloudron/

- Cloudron named-provider installation and Marketplace availability: https://docs.cloudron.io/installation/

- Hostinger customer VPS Cloudron template: https://www.hostinger.com/support/8637788-how-to-use-the-cloudron-vps-template-at-hostinger/

- LumaDock customer VPS Cloudron template: https://lumadock.com/vps-hosting/cloudron

- Vendor Azure Web Apps deployment: https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps

- Vendor Google Cloud Run deployment: https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run

- Vendor DigitalOcean application specification: https://github.com/docusealco/docuseal-digitalocean/blob/master/.do/deploy.template.yaml

- Vendor-linked Railway application template: https://railway.com/deploy/IGoDnc

- Vendor Heroku application specification: https://github.com/docusealco/docuseal-heroku/blob/master/app.json

- Vendor Render application blueprint: https://github.com/docusealco/docuseal-render/blob/master/render.yaml

- Railway application Docker source: https://github.com/docusealco/docuseal-railway

- Railway volume persistence: https://docs.railway.com/volumes/reference

- Heroku ephemeral dyno filesystem: https://devcenter.heroku.com/articles/dyno-isolation

- Render free-service production limitations: https://render.com/docs/free

- Vendor application upgrade instructions: https://www.docuseal.com/docs/update-docuseal-to-the-latest-version

- Security-hardening changes in 3.3.7: https://github.com/docusealco/docuseal/compare/3.3.6...3.3.7

- DocuSeal 3.3.8 security release: https://github.com/docusealco/docuseal/releases/tag/3.3.8

- GHSA-78g6-f52x-q3jx: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx

### Licensing sources

- https://github.com/docusealco/docuseal/blob/3.3.6/LICENSE

- https://www.docuseal.com/docs/on-premises-pro-installation

- https://www.cloudron.io/legal/terms.html

- https://www.cloudron.io/pricing.html

### Infrastructure sources

- https://docs.cloudron.io/packages/docuseal/

- https://docs.cloudron.io/installation/

- https://www.docuseal.com/docs/deploying-docuseal-on-azure-web-apps

- https://www.docuseal.com/docs/deploying-docuseal-on-google-cloud-run


### 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: Documented. AWS delivery uses Cloudron’s platform AMI and a separate application package. Cloudron publishes the platform offer; application versions, licensing and support are separate. Scope: Cloudron platform plus separate application package. Source: https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci (reviewed 2026-11-14). Supporting source: Cloudron application package — https://docs.cloudron.io/packages/docuseal/. Offer prodview-aep3gt5elubci: Cloudron UG; Platform AMI; external Cloudron license; package Cloudron 10.0.5 (platform, not application); https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML SSO appears in the self-hosted Pro feature list. It is not established here for the free edition. Scope: Self-hosted Pro. Source: https://www.docuseal.com/on-premises (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. GHSA-78g6-f52x-q3jx affects DocuSeal before 3.3.8. A single unauthenticated request can crash a Ruby application worker before routing or authentication. No workaround is documented; update and restart every web and background process. Scope: DocuSeal versions earlier than 3.3.8. Source: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx (reviewed 2026-11-19). Supporting source: 3.3.8 security release — https://github.com/docusealco/docuseal/releases/tag/3.3.8.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose example defines DocuSeal, PostgreSQL and Caddy with persistent storage. It uses moving application/proxy images and example database credentials; pin compatible versions and replace credentials before deployment. Scope: Upstream Compose example; not a hardened production baseline. Source: https://github.com/docusealco/docuseal/blob/master/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/docusealco/docuseal/blob/master/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. The vendor sizes examples for 10,000 signed documents. For one-off templates with one signer and 500-KB average files it lists 1 vCPU, 1 GB RAM and 12 GB disk; larger files, reused templates and multiple signers have different storage needs. PostgreSQL is recommended for heavy production/API use. Scope: Approximate document-based examples, not a 1-TB or HA installation baseline. Source: https://www.docuseal.com/docs/on-premises-server-requirements (reviewed 2026-11-20).

- License pricing: Documented. The 3.3.8 core is AGPLv3. The on-premises page offers free self-hosting and separately prices Pro at $240 per user/year plus $0.20 per document signed through API or embedding. Confirm billable user/document definitions, currency and current terms before quoting. Scope: Self-hosted core versus paid Pro; advertised amounts are not a 100-user total or infrastructure cost. Source: https://www.docuseal.com/on-premises (reviewed 2026-11-20). Supporting source: Versioned core licence — https://github.com/docusealco/docuseal/blob/3.3.8/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. DocuSeal 3.3.8 was published November 19, 2026. It updates Ruby to address GHSA-78g6-f52x-q3jx; all web and background processes must be restarted so the fixed runtime is active. Scope: Upstream DocuSeal core release; separately packaged provider images may lag. Source: https://github.com/docusealco/docuseal/releases/tag/3.3.8 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/docusealco/docuseal/releases/tag/3.3.7. Supporting source: Security advisory — https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx.



### Vendor alternative positioning

Positioning is not a finding of feature parity.

- docusign: The publisher positions DocuSeal as an alternative for document-signing workflows. Source: https://www.docuseal.com/; reviewed 2026-11-16.

- pandadoc: The publisher positions DocuSeal as an alternative for document-signing workflows. Source: https://www.docuseal.com/; reviewed 2026-11-16.


### Security and lifecycle reviews

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

- DocuSeal 3.3.8 unauthenticated denial-of-service fix (security-advisory): GHSA-78g6-f52x-q3jx allows one unauthenticated request to crash a Ruby application worker before routing or authentication. Scope: DocuSeal versions earlier than 3.3.8. Conditions: Every web and background process still using the affected Ruby runtime remains exposed; the advisory documents no workaround. Action: Upgrade to 3.3.8 or later, restart every Ruby process and verify the active runtime. Source: https://github.com/docusealco/docuseal/security/advisories/GHSA-78g6-f52x-q3jx; reviewed 2026-11-19. Supporting source: 3.3.8 security release — https://github.com/docusealco/docuseal/releases/tag/3.3.8.




## DokuWiki

File-based wiki for documentation and shared knowledge.

- Listing: https://launchinyourcloud.com/directory/dokuwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Cloudron package; Application platform deployment
- Architecture: DokuWiki web application with persistent wiki pages, configuration and attachments.
- 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-h7wozgfyl3vfg
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version.

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

DokuWiki web application with persistent wiki pages, configuration and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: File-based wiki for documentation and shared knowledge.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/dokuwiki.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/dokuwiki
  DokuWiki web application with persistent wiki pages, configuration and attachments. Cloudron, TurnKey and Railway packages are distinct. The Cloudron changelog date for an OAuth plugin is not an upstream wiki release date; verify the installed core version. 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 splitbrain, selfthinker, Klap-in, 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/dokuwiki/dokuwiki/graphs/contributors

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

### Sources

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

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

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

- GPL-2.0 COPYING: https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

- Releases 2026-07-14c: https://github.com/dokuwiki/dokuwiki/releases

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

### Licensing sources

- https://github.com/dokuwiki/dokuwiki/blob/master/COPYING

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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: 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: DokuWiki selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg (reviewed 2026-11-19). Offer prodview-h7wozgfyl3vfg: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-h7wozgfyl3vfg.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The maintainer-provided oauth plugin implements login through OAuth services. It is a separately installed authentication plugin, not a guarantee that the default wiki has corporate SAML/OIDC configured; validate provider-plugin and DokuWiki release compatibility. Scope: CosmoCode DokuWiki OAuth plugin integration. Source: https://raw.githubusercontent.com/cosmocode/dokuwiki-plugin-oauth/master/README (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 DokuWiki container repository documents a non-root image, persistent /storage volume and a Compose example. Configure the initial wiki securely, set writable storage ownership and pin a supported release rather than a moving tag. Scope: Official DokuWiki application container packaging; not cloud-account HA IaC. Source: https://raw.githubusercontent.com/dokuwiki/docker/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/dokuwiki/docker. Artifact reference: master (moving repository); choose a supported version-tagged image.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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/dokuwiki.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## Ente Photos

Self-hosted encrypted photo backup and sharing backend with web clients.

- Listing: https://launchinyourcloud.com/directory/ente-photos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Application platform deployment; Docker / Compose
- Architecture: Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage.
- 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://ente.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.

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

Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- digital-asset-management: Self-hosted encrypted photo backup and sharing backend with web clients.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/ente
  Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/ente-1
  Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.ente-ubuntu-24-04
  Ente Museum API, Photos/Albums web apps, PostgreSQL and object storage. Server image commits and Photos/Auth client releases differ. Encryption depends on client and key handling; the operator still manages service metadata, database and object storage.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes mnvr, ua741, abhinavkgrd, 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/ente/ente/graphs/contributors

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

### Sources

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

- Railway: https://railway.com/deploy/ente-1

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

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

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

### Licensing sources

- https://raw.githubusercontent.com/ente-io/ente/main/LICENSE

### Infrastructure sources

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

- https://railway.com/deploy/ente-1

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The reviewed Museum/self-hosting material establishes Ente account/client setup but does not establish a supported external SAML/OIDC enterprise sign-in path for self-hosted Photos. Ente Auth, account MFA/passkeys and another website's hosted login are not evidence of Photos federation. Scope: Ente Photos clients with a customer-operated Museum backend; product-specific external user federation remains unconfirmed. Source: https://ente.io/help/self-hosting/ (reviewed 2026-11-20). Supporting source: Museum server and client architecture — https://github.com/ente-io/ente/blob/main/server/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Ente publishes a quickstart script that generates Compose/configuration with instance credentials for Museum, PostgreSQL and object storage. This deploys the backend; Photos clients must connect to that instance, and self-hosting a web client is a separate step. Preserve configuration and data volumes when upgrading. Scope: Ente Museum backend supporting Photos; not a complete public web-client or HA deployment. Source: https://github.com/ente-io/ente/blob/main/server/docs/quickstart.md (reviewed 2026-11-20). Deployment artifact: https://github.com/ente-io/ente/blob/main/server/quickstart.sh. Artifact reference: main (moving branch); generated configuration and image versions must be retained. Supporting source: Self-hosted client and server guidance — https://ente.io/help/self-hosting/.

- Minimum footprint / sizing: Sources checked — unresolved. The quickstart specifies Docker and creates Museum, PostgreSQL and object-storage services, but does not give a quantitative whole-stack CPU/RAM/storage minimum. Size original media, encrypted objects, database, backups, clients and any separately hosted web front end for the intended workload. Scope: Ente Photos backend and selected client deployment; lightweight binary claims are not validated production/HA sizing. Source: https://github.com/ente-io/ente/blob/main/server/docs/quickstart.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## ERPNext Supplier Management

Self-hosted supplier records, procurement documents, quotation attachments and supplier scorecards.

- Listing: https://launchinyourcloud.com/directory/erpnext-supplier-management/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-3.0; implementation and support separately arranged
- Licensing model: open-source
- Installation: Frappe installation scripts
- Architecture: Customer-operated ERP application and database
- Operations: Customer or implementation partner operates the application and maintains backups and upgrades.
- Product website: https://frappe.io/erpnext
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

An adjacent procurement comparator: supplier records connect RFQs, quotations, orders, receipts and invoices; source quotations can be retained as attachments. Supplier scorecards support recurring performance evaluation. The reviewed sources do not establish turnkey certificate-of-insurance expiry or supplier-compliance document workflows. ERPNext advisory GHSA-cc74-rc2g-p7hw describes authenticated SQL injection in the Selling and Buying modules that can expose sensitive database and active-session data, enabling administrator account takeover. There is no workaround; upgrade to 15.121.6 or 16.37.0 or later. ERPNext v16.60.0 adds supplier and customer dashboards plus RFQ and account-dimension changes, and includes portal and permission hardening. Review custom supplier workflows and permissions before upgrading.

The listed supplier-management functionality is part of ERPNext, whose official repository uses GPLv3. Commercial hosting, implementation or support services do not convert that application code into an open-core offering.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- vendor-supplier-document-management: An adjacent procurement comparator covering supplier records, quotation attachments and recurring scorecards; turnkey supplier certification and insurance-expiry workflows were not verified.

- erp-crm: Supplier and procurement records within the ERPNext suite, connecting quotations, orders, receipts and invoices. This listing focuses on that ERP workflow.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/erpnext--erp-next (checked 2026-11-12). Source: https://github.com/gridalpha/erpnext-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- ERPNext self-hosted deployment on Railway (railway): https://railway.com/deploy/erpnext--erp-next
  The community recipe runs ERPNext with web, queue, scheduler and realtime services plus MariaDB and Redis in a customer project. It layers Railway-specific startup/storage handling over the upstream ERPNext v16 image. Supplier management is part of that ERPNext application; review versions, backups and integrations separately from vendor-hosted Frappe Cloud.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the ERPNext Railway image (railway): https://github.com/gridalpha/erpnext-railway/blob/main/Dockerfile
  The inspected community wrapper starts from frappe/erpnext:v16 and adapts process supervision and persisted site assets for Railway. Match the selected ERPNext/Frappe release and database requirements before deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting and licensing: https://frappe.io/erpnext/pricing

- Supplier records and linked documents: https://docs.frappe.io/erpnext/supplier

- Supplier quotation attachments: https://docs.frappe.io/erpnext/supplier-quotation

- Supplier scorecards: https://docs.frappe.io/erpnext/supplier-scorecard

- Licensing and edition terms: https://raw.githubusercontent.com/frappe/erpnext/develop/license.txt

- Licensing and edition terms: https://docs.frappe.io/legal/others/license-and-trademark

- ERPNext Selling and Buying SQL-injection advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-cc74-rc2g-p7hw

- ERPNext v16.60.0 release: https://github.com/frappe/erpnext/releases/tag/v16.60.0

- ERPNext cross-scope data advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29

- ERPNext supplier invoice exposure advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8

### Licensing sources

- https://raw.githubusercontent.com/frappe/erpnext/develop/license.txt

- https://docs.frappe.io/legal/others/license-and-trademark

- https://frappe.io/erpnext/pricing

### Infrastructure sources

- https://frappe.io/erpnext/pricing


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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. Frappe documents OIDC-based social login between a Frappe identity-provider server and an application server. Configure the framework clients and review user-role mapping; this is not a supplier-module-specific identity guarantee. Scope: ERPNext/Frappe platform authentication; business-module authorization is separate. Source: https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: ERPNext advisories cover cross-scope business-data access and public supplier e-invoice exposure. Upgrade to a fixed or later supported ERPNext release and recheck supplier, invoice, and cross-company permissions. Scope: GHSA-m668-9q43-8g29 is fixed in 15.124.2 and 16.53.0; GHSA-9jrr-9pr6-7mv8 is fixed in 15.124.0 and 16.52.0.. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29 (reviewed 2026-11-18). Supporting source: Supplier e-invoice advisory — https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Frappe Docker provides a production Compose base and deployment overrides. Its pwd.yml is a disposable demo. Build/select the ERPNext image and matching configuration; this is platform packaging, not a separately versioned supplier-management appliance. Scope: ERPNext platform deployment; supplier-management configuration remains application-specific. Source: https://github.com/frappe/frappe_docker (reviewed 2026-11-14). Deployment artifact: https://github.com/frappe/frappe_docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The official Frappe Docker single-server ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD, with MariaDB, Redis and an HTTPS proxy on that host. This is a small single-bench recipe, not a validated supplier-management capacity or HA minimum for 100 users and 1 TB. Scope: Underlying ERPNext/Frappe single-server example; additional data, workers, backups and replicas require sizing. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20).

- License pricing: Documented. ERPNext is free open-source software under GPLv3. Self-hosting does not require a per-user software subscription; hosting, implementation and support are separate costs. Frappe Cloud prices are managed-hosting prices, not self-hosted licence fees. Scope: ERPNext core, including supplier-management functionality; third-party apps and services have separate terms. Source: https://frappe.io/erpnext/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. ERPNext v16.60.0 was published November 17, 2026. It adds supplier and customer dashboards, RFQ and account-dimension changes, and portal and permission hardening; validate custom workflows and installed Frappe compatibility. Scope: Upstream ERPNext v16 release. Source: https://github.com/frappe/erpnext/releases/tag/v16.60.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- ERPNext Selling and Buying SQL injection (security-advisory): GHSA-cc74-rc2g-p7hw permits database and active-session disclosure, with possible administrator account takeover. Scope: ERPNext Selling/Buying: fixed in 15.121.6 and 16.37.0. This is a platform-module issue, not a separately versioned supplier appliance. Conditions: An authenticated account, including a portal account without assigned roles, can reach the vulnerable endpoint; no victim interaction is required. Action: Install a fixed or later supported patch for the deployed branch. The advisory provides no workaround. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-cc74-rc2g-p7hw; reviewed 2026-11-17.

- ERPNext supplier and business-data access-control fixes (security-advisory): ERPNext advisories cover cross-scope business-data access and public supplier e-invoice exposure. Scope: GHSA-m668-9q43-8g29 is fixed in 15.124.2 and 16.53.0; GHSA-9jrr-9pr6-7mv8 is fixed in 15.124.0 and 16.52.0. Conditions: The first issue requires a low-privilege authenticated user. The invoice issue concerns affected public portal behavior. Action: Upgrade to a fixed or later supported ERPNext release and recheck supplier, invoice, and cross-company permissions. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29; reviewed 2026-11-18. Supporting source: Supplier e-invoice advisory — https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8.




## erxes

Customer-operated business and customer engagement platform.

- Listing: https://launchinyourcloud.com/directory/erxes/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Custom source-available application terms with separately licensed Enterprise components.
- Licensing model: source-available
- Installation: Application platform deployment
- Architecture: erxes XOS application services, database, search and supporting microservices 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://erxes.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The repository mixes a custom licence and commercially licensed Enterprise files. Review the selected modules; public code is not a blanket AGPL grant.

Custom source-available application terms with separately licensed Enterprise components.

erxes XOS application services, database, search and supporting microservices on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Customer-operated business and customer engagement platform.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/erxes
  erxes XOS application services, database, search and supporting microservices on Railway. The repository mixes a custom licence and commercially licensed Enterprise files. Review the selected modules; public code is not a blanket AGPL grant.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

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

- GitHub LICENSE.md (AGPL-3.0 + SaaS restriction): https://raw.githubusercontent.com/erxes/erxes/master/LICENSE.md

- GitHub Releases: https://github.com/erxes/erxes/releases

### Licensing sources

- https://raw.githubusercontent.com/erxes/erxes/master/LICENSE.md

### Infrastructure sources

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


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The published 3.4.25 Google-login button has an empty click handler. Its OAuth client/authorization-server features and password or SaaS magic-link flows do not establish a working self-hosted external identity-provider login. Confirm an implemented callback, account/role mapping and edition/version before claiming Google or generic SAML/OIDC SSO. Scope: Published self-hosted core UI; a placeholder or OAuth server is not proof of external user federation. Source: https://github.com/erxes/erxes/blob/3.4.25/frontend/core-ui/src/modules/auth/login/components/GoogleOAuthButton.tsx (reviewed 2026-11-20). Supporting source: Published core authentication mutations — https://github.com/erxes/erxes/blob/3.4.25/backend/core-api/src/modules/auth/graphql/resolvers/mutations.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published 3.4.25 README and installer deploy selected plugins with Docker Compose and offer an explicit --version option. Review and pin the installer/release, domain/TLS, generated secrets and plugin versions; the Linux installer checks x86_64/AVX requirements for its current images and MongoDB. Source development through pnpm is separate. Scope: Published self-hosted installer, distinct from a Railway package or developer checkout. Source: https://github.com/erxes/erxes/blob/3.4.25/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/erxes/erxes/blob/3.4.25/scripts/install.sh. Artifact reference: 3.4.25 (select explicit deployment version; installer otherwise chooses a newer release).

- Minimum footprint / sizing: Sources checked — unresolved. The installer identifies Docker services and plugin-dependent infrastructure but does not supply a complete production CPU/RAM/storage minimum. The local guide's 4096 MiB Node heap troubleshooting option is per process, not host sizing. Confirm plugin counts, MongoDB/Redis, active users, attachments and HA; current Linux image architecture constraints also apply. Scope: Published installer and local-development guidance; whole-stack production sizing remains unconfirmed. Source: https://github.com/erxes/erxes/blob/3.4.25/scripts/install.sh (reviewed 2026-11-20). Supporting source: Local setup and per-process heap guidance — https://erxes.io/docs/local-setup.

- License pricing: Documented. Custom source-available application terms with separately licensed Enterprise components. Scope: erxes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/erxes/erxes/master/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## EspoCRM Self-Hosted

Self-hosted CRM with sales records, customer-service features and email campaign management.

- Listing: https://launchinyourcloud.com/directory/espocrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; commercial extensions use separate restricted terms
- Licensing model: open-source
- Installation: Official Docker, installation script or manual PHP server installation
- Architecture: Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services.
- Operations: Customer maintains application/database containers or servers, scheduled work, email services, backups, upgrades and selected extension compatibility.
- Product website: https://www.espocrm.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

The core includes campaign management. The feature matrix places BPM and workflows in Advanced Pack, while sales/inventory functions are in Sales Pack. These paid extensions have separate license terms and should not be assumed to be part of the AGPL core. EspoCRM 10.1.2 fixes OAuth Server access tokens being rejected when 2FA is enabled and an administrator temporarily losing access to scopes after another administrator views that user's record access. Operators using OAuth or 2FA should update.

The downloadable core is GNU AGPL version 3. Advanced Pack and other commercial extensions use a separate license restricting redistribution and limiting installation/use. The directory groups open-source and open-core offerings under one filter.

Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services. EspoCRM 10.1 drops support for MariaDB 10.3–10.5, so upgrades require a supported database version.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, leads and sales opportunities; broader ERP functions are not established for the base application.

- marketing-automation: Segmented campaign email, target lists and campaign tracking; workflow/BPM automation is separately offered in Advanced Pack.

### Deployment boundaries


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


### Cloud deployment evidence

- EspoCRM self-hosted deployment on Railway (railway): https://railway.com/deploy/espocrm
  The community template deploys the official espocrm/espocrm image with PostgreSQL and persistent application files in the customer project. Review the selected release, background job configuration, email and backups. Paid workflow or other commercial extensions are not established by this core application deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release feed publishes EspoCRM 10.1.2 dated November 16, 2026. The vendor documents named Red Cross implementations, including the Armenian Red Cross Society and Slovak Red Cross, with links to institutional sources. Those implementations demonstrate adoption without establishing one common hosting model or extension set.

Reviewed 2026-11-16.

- Current maintained download and release: https://www.espocrm.com/download/

- Named institutional adoption examples: https://www.espocrm.com/blog/nonprofits-espocrm/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Sources

- Self-hosted installation, current release and core license: https://www.espocrm.com/download/

- Core and extension feature boundaries: https://www.espocrm.com/features/

- Campaign configuration and email delivery: https://docs.espocrm.com/user-guide/campaigns/

- Open-source application license: https://www.espocrm.com/espocrm-open-source-license/

- Commercial extension restrictions: https://www.espocrm.com/extension-license-agreement/

- Named nonprofit implementations: https://www.espocrm.com/blog/nonprofits-espocrm/

- Application architecture and database requirements: https://github.com/espocrm/espocrm

- EspoCRM 10.1 compatibility changes: https://www.espocrm.com/blog/espocrm-v10-1-released/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Licensing sources

- https://www.espocrm.com/espocrm-open-source-license/

- https://www.espocrm.com/extension-license-agreement/

- https://www.espocrm.com/features/

### Infrastructure sources

- https://www.espocrm.com/download/

- https://github.com/espocrm/espocrm

- https://www.espocrm.com/blog/espocrm-v10-1-released/


### 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. EspoCRM supports external OpenID Connect providers from version 7.3, with optional user creation and team mapping. Portal OIDC is documented from 7.4. Provider MFA and supported client-authentication methods must be checked separately. Scope: Self-hosted EspoCRM; version-specific OIDC and portal configuration. Source: https://docs.espocrm.com/administration/oidc/ (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 vendor Docker repository distinguishes a production prebuilt image from development builds and includes database, daemon and websocket configuration. Replace example database credentials and retain persistent volumes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/espocrm/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/espocrm/docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The server guide specifies supported PHP/database versions and recommends a VPS or dedicated server for production. It does not establish a quantitative whole-host CPU/RAM/storage minimum or an HA profile for the proposed workload. Scope: EspoCRM application, database and scheduled/background work; shared-hosting capability is not a capacity guarantee. Source: https://docs.espocrm.com/administration/server-configuration/ (reviewed 2026-11-20).

- License pricing: Documented. EspoCRM core is distributed under AGPLv3. That licence does not include separately sold extensions, hosting or professional support, and it should not be treated as a quote for those services. Scope: Reviewed open-source core; commercial extensions and services are separate. Source: https://www.espocrm.com/espocrm-open-source-license/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is 10.1.2, published 2026-11-16. 10.1.2 adds OAuth/2FA and administrator-scope fixes; check the 10.1 database compatibility requirements before upgrading. This is a dated release snapshot, not a support or future-cadence promise. Scope: Upstream espocrm/espocrm release record; commercial editions and deployment packages may differ. Source: https://github.com/espocrm/espocrm/releases/tag/10.1.2 (reviewed 2026-11-16).







## Etherpad

Self-hosted real-time collaborative text editor.

- Listing: https://launchinyourcloud.com/directory/etherpad/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 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: Etherpad application, database and persistent plugins and settings.
- 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://etherpad.org
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version.

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

Etherpad application, database and persistent plugins and settings. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted real-time collaborative text editor.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/etherpad.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/etherpad
  Etherpad application, database and persistent plugins and settings. Cloudron and Railway are independently maintained packages. Plugins execute within the deployment and require compatibility and security review. 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 JohnMcLear, rhansen, Pita, 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/ether/etherpad/graphs/contributors

- Upstream project: https://github.com/ether/etherpad

### Sources

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

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

- Apache-2.0 LICENSE: https://github.com/ether/etherpad-lite/blob/develop/LICENSE

- Releases v3.3.19: https://github.com/ether/etherpad-lite/releases

- Etherpad | Cloudron Docs: https://docs.cloudron.io/packages/etherpad/

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

- Etherpad authentication and author-token advisories: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh

### Licensing sources

- https://github.com/ether/etherpad-lite/blob/develop/LICENSE

### Infrastructure sources

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

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


### 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: Sources checked — unresolved. The reviewed configuration includes an embedded OIDC issuer with admin/user clients, and the API supports mapping a host application’s users and permissions. This does not establish login federation to an existing corporate SAML/OIDC IdP for the selected pad/admin deployment. Confirm the supported external-auth plugin or portal integration. Scope: Embedded identity issuer and host API integration are distinct from external-IdP federation. Source: https://raw.githubusercontent.com/ether/etherpad/develop/settings.json.template (reviewed 2026-11-20). Supporting source: Official host-user/API integration design — https://docs.etherpad.org/api/http_api.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker documentation provides container/environment configuration and persistent data/plugin handling. Pin compatible application/plugins, supply a production database and secrets, and configure the reverse proxy. A standalone container does not by itself supply durable clustered operation or external-user SSO. Scope: Upstream Etherpad container deployment and configuration. Source: https://docs.etherpad.org/docker.html (reviewed 2026-11-20). Deployment artifact: https://github.com/ether/etherpad/blob/develop/doc/docker.md. Artifact reference: develop (moving branch); pin application and compatible plugins.

- Minimum footprint / sizing: Documented. The Cloudron package declares 768MB 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/etherpad.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Etherpad; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/ether/etherpad-lite/blob/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Etherpad authentication and author-token advisories (security-advisory): Upstream documents an OIDC login bypass and an author-token isolation correction in separate advisories. Scope: GHSA-62cj-9j72-mfrh and GHSA-746x-9w89-7xv6; consult each notice for its own affected and fixed versions. Conditions: OIDC/password configuration and clients without author tokens change exposure; plugin/package versions must be checked separately. Action: Review both Etherpad advisories and use a compatible fixed server and plugin set; do not treat a provider package update date as an application patch version. Source: https://github.com/ether/etherpad/security/advisories/GHSA-62cj-9j72-mfrh; reviewed 2026-11-19. Supporting source: Author-token isolation advisory — https://github.com/ether/etherpad/security/advisories/GHSA-746x-9w89-7xv6.




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







## Frappe HR Self-Hosted

Self-hosted HR software covering employee records, onboarding, leave, payroll and employee lifecycle events.

- Listing: https://launchinyourcloud.com/directory/frappe-hr/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source; verify applicable component license and support terms
- Licensing model: open-source
- Installation: Frappe installation scripts; Bench and Docker development setups documented
- Architecture: Customer-operated Frappe application and database
- Operations: Customer or implementation partner maintains infrastructure, security, backups and software updates.
- Product website: https://frappe.io/hr
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Employee records include joining, employment, education and exit details. Legal hold, controlled disposition and jurisdiction-specific personnel-file retention were not established. Verify the applicable component license and support terms for the selected distribution. Frappe HR v16.60.0 requires Frappe v16.60 and contains five breaking changes alongside employee-profile, organization-chart, letter, and dashboard work. Review custom HR workflows and access rules before upgrading.

The official Frappe HR repository contains a GPLv3 license. Its pricing page currently labels self-hosting AGPL-3.0; both are open-source licenses, so the model remains open source while the exact version-specific obligations should be checked against the chosen release.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- hr-employee-records-management: Employee records, onboarding, leave, payroll and exit lifecycle are documented; legal hold, controlled disposition and jurisdiction-specific personnel-file retention were not established.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/frappe-hr (checked 2026-11-12). Source: https://github.com/gridalpha/frappe-hr-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Frappe HR self-hosted deployment on Railway (railway): https://railway.com/deploy/frappe-hr
  The community recipe deploys Frappe HR with the Frappe/ERPNext runtime, workers, scheduler, realtime service, MariaDB and Redis in a customer Railway project. It installs the upstream hrms version-16 app on an ERPNext v16 image. Review app/framework version alignment, payroll rules, credentials and backups; this is not Frappe Cloud.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the Frappe HR Railway image (railway): https://github.com/gridalpha/frappe-hr-railway/blob/main/Dockerfile
  The inspected community build installs the upstream frappe/hrms version-16 branch over the official frappe/erpnext v16 image, with Railway-specific process and storage handling. Confirm compatible application releases and modules before production.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting options: https://frappe.io/hr/pricing

- Employee records: https://docs.frappe.io/hr/employee

- HR modules and lifecycle: https://docs.frappe.io/hr/introduction

- Official installation repository: https://github.com/frappe/hrms

- Licensing and edition terms: https://raw.githubusercontent.com/frappe/hrms/develop/license.txt

- Licensing and edition terms: https://docs.frappe.io/legal/others/license-and-trademark

- Frappe HR v16.60.0 release: https://github.com/frappe/hrms/releases/tag/v16.60.0

- Frappe HR SQL injection advisory: https://github.com/frappe/hrms/security/advisories/GHSA-jfmr-9jv9-mrw4

- Frappe HR cross-employee data advisory: https://github.com/frappe/hrms/security/advisories/GHSA-wfc6-cw72-cvhx

### Licensing sources

- https://raw.githubusercontent.com/frappe/hrms/develop/license.txt

- https://frappe.io/hr/pricing

- https://docs.frappe.io/legal/others/license-and-trademark

### Infrastructure sources

- https://frappe.io/hr/pricing

- https://github.com/frappe/hrms


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The shared Frappe login system accepts external OAuth/OpenID logins configured with Social Login Key, including Google and Office 365. Configure the provider and permitted users for the installed Frappe version; this is framework login, not a separate application-specific SAML implementation. Scope: Self-hosted Frappe-based application login; provider configuration and matching framework/app versions required. Source: https://docs.frappe.io/framework/user/en/guides/integration/social_login_key (reviewed 2026-11-20). Supporting source: Frappe login handlers — https://github.com/frappe/frappe/blob/develop/frappe/integrations/oauth2_logins.py. Supporting source: Application framework dependency — https://github.com/frappe/hrms/blob/develop/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Frappe HR advisories cover an SQL injection issue and cross-employee HR data access. Upgrade to a fixed or later supported Frappe HR release and review employee-data permissions. Scope: The SQL issue is fixed in 14.38.2, 15.64.0, and 16.18.0. The cross-employee issue is fixed in 15.58.3 and 16.4.3.. Source: https://github.com/frappe/hrms/security/advisories/GHSA-jfmr-9jv9-mrw4 (reviewed 2026-11-18). Supporting source: Cross-employee data advisory — https://github.com/frappe/hrms/security/advisories/GHSA-wfc6-cw72-cvhx.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The HRMS repository provides a Docker development setup with example administrator credentials. Do not use that recipe as a production baseline; production packaging must include compatible Frappe/ERPNext/HRMS apps. Scope: HRMS development artifact; production deployment requires separate configuration. Source: https://github.com/frappe/hrms (reviewed 2026-11-14). Deployment artifact: https://github.com/frappe/hrms. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The underlying Frappe Docker ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD for a small single bench. It does not size this additional application or establish its whole-stack production/HA minimum; application jobs, database, attachments and replicas still require sizing. Scope: Platform recipe only, not an application-specific Frappe HR/Lending benchmark or Frappe Cloud hosting allocation. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20). Supporting source: Application dependencies — https://github.com/frappe/hrms/blob/develop/README.md.

- License pricing: Documented. The vendor states Frappe HR is free and open source for self-hosting. This does not include infrastructure, email, security, backups, implementation or ongoing operation. Scope: Self-hosted Frappe HR software; hosted-service plans and operating costs are separate. Source: https://frappe.io/hr/pricing (reviewed 2026-11-14).

- Operating cost estimate: Sources checked — unresolved. The pricing FAQ gives an illustrative VPS starting cost but explicitly adds email, security, backups and maintenance. It does not establish a workload/region-specific total operating estimate. Scope: Vendor illustration, not a complete infrastructure-plus-operations estimate. Source: https://frappe.io/hr/pricing (reviewed 2026-11-14).

- Release snapshot / cadence: Documented. Frappe HR v16.60.0 was published November 17, 2026. It requires Frappe v16.60 and identifies five breaking changes; validate custom employee, letter, and dashboard workflows. Scope: Upstream Frappe HR v16 release. Source: https://github.com/frappe/hrms/releases/tag/v16.60.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Frappe HR SQL injection and employee-data access fixes (security-advisory): Frappe HR advisories cover an SQL injection issue and cross-employee HR data access. Scope: The SQL issue is fixed in 14.38.2, 15.64.0, and 16.18.0. The cross-employee issue is fixed in 15.58.3 and 16.4.3. Conditions: Applicability depends on the affected feature, permissions, and installed branch. Action: Upgrade to a fixed or later supported Frappe HR release and review employee-data permissions. Source: https://github.com/frappe/hrms/security/advisories/GHSA-jfmr-9jv9-mrw4; reviewed 2026-11-18. Supporting source: Cross-employee data advisory — https://github.com/frappe/hrms/security/advisories/GHSA-wfc6-cw72-cvhx.




## GrowthBook Self-Hosted

Feature flagging and experimentation platform with a self-operated application and SDKs.

- Listing: https://launchinyourcloud.com/directory/growthbook/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT Expat for core code; specified enterprise directories use the GrowthBook Enterprise License.
- Licensing model: open-source
- Installation: Run the documented Docker Compose application and MongoDB-compatible database; configure production storage and credentials.
- Architecture: Customer-operated Next.js/Express application and statistics engine with MongoDB-compatible metadata storage
- Operations: Customer manages application availability, metadata database, SDK configuration, identity, data connections, backups and upgrades.
- Product website: https://www.growthbook.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

The bundled MongoDB service is a development/staging starting point. Warehouse connections, event tracking and managed database services can cross account boundaries; enterprise-only functionality is not included by the core license. GrowthBook v5.2.1 is a security patch release recommended for all self-hosted users. It updates zlib and multiple dependencies with known vulnerabilities and removes super-linear regular-expression backtracking.

MIT Expat for core code; specified enterprise directories use the GrowthBook Enterprise License. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Next.js/Express application and statistics engine with MongoDB-compatible metadata storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. Building the v5.2.1 image from source downloads zlib through github.com and release-assets.githubusercontent.com; environments with egress allowlists must permit both hosts.


### Category fit

- feature-management: Feature flags and experiment configuration with SDK-based feature evaluation and separately configured data-source analysis.

### Deployment boundaries


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


### Cloud deployment evidence

- GrowthBook community deployment template on Railway (railway): https://railway.com/deploy/growthbook
  This community template deploys the upstream growthbook/growthbook application image with MongoDB in a customer Railway project. Configure distinct frontend and API origins and preserve database/uploads. This is a community deployment path rather than a GrowthBook support commitment or GrowthBook Cloud subscription.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream release history credits many named contributors, including first-time contributions across successive releases, and documents continued maintenance of self-hosted images.

Reviewed 2026-11-10.

- Release maintenance and contributor credits: https://github.com/growthbook/growthbook/releases

- Public upstream project: https://github.com/growthbook/growthbook

### Sources

- Official installation and runtime: https://docs.growthbook.io/self-host

- Upstream project and capabilities: https://github.com/growthbook/growthbook

- Current upstream license: https://raw.githubusercontent.com/growthbook/growthbook/main/LICENSE

- GrowthBook v5.2.1 security patch and build changes: https://github.com/growthbook/growthbook/releases/tag/v5.2.1

### Licensing sources

- https://raw.githubusercontent.com/growthbook/growthbook/main/LICENSE

### Infrastructure sources

- https://docs.growthbook.io/self-host

- https://github.com/growthbook/growthbook/releases/tag/v5.2.1


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. Enterprise SSO is documented for self-hosted GrowthBook through OIDC with named providers or a generic OIDC configuration. Set an active licence key and provider settings, and configure email-domain/account admission and role policy. Standard account login, experiment/SDK identities and SCIM are separate concerns. Scope: Licensed self-hosted Enterprise user login, distinct from Cloud account setup. Source: https://docs.growthbook.io/sso (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 Compose example includes the application and MongoDB with persistent volumes. It uses example credentials and moving images; replace credentials and select compatible pinned versions. Scope: Upstream example, not a hardened production configuration. Source: https://github.com/growthbook/growthbook/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/growthbook/growthbook/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The production guide recommends at least 1 vCPU/2 GB RAM per application instance and at least three instances for fault tolerance. MongoDB and optional separate stats/jobs workers need their own resources; its database example for 1,000 flags/experiments is not 1 TB of application data. Size experiment processing, warehouse queries, uploads and replicas separately. Scope: Current production application reference; database, stats engine and workload capacity remain separate. Source: https://docs.growthbook.io/self-host/production (reviewed 2026-11-20).

- License pricing: Documented. The v5.2.1 licence applies MIT terms to the core, with specified enterprise directories under the GrowthBook Enterprise License. Enterprise SSO on a self-hosted instance requires an active licence key. Hosted plans, self-hosted paid entitlements, infrastructure and support must be priced separately. Scope: Published core/Enterprise source boundary; no Cloud price transferred to self-hosted. Source: https://github.com/growthbook/growthbook/blob/v5.2.1/LICENSE (reviewed 2026-11-20). Supporting source: Self-hosted Enterprise SSO licence requirement — https://docs.growthbook.io/sso.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is v5.2.1, 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 growthbook/growthbook release record; commercial editions, LTS branches and provider packages can differ. Source: https://github.com/growthbook/growthbook/releases/tag/v5.2.1 (reviewed 2026-11-17).




### Security and lifecycle reviews

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

- GrowthBook self-hosted security patch (security-advisory): GrowthBook 5.2.1 updates vulnerable runtime dependencies and removes problematic regular-expression backtracking. Scope: Upstream self-hosted GrowthBook 5.2.1 patch over 5.2.0; not a promise about all commercial packaging. Conditions: The vendor recommends the update to self-hosted users. Source builds now fetch zlib through GitHub and its release-assets host. Action: Apply the compatible security patch and permit the documented download hosts when building behind an egress allowlist. Source: https://github.com/growthbook/growthbook/releases/tag/v5.2.1; reviewed 2026-11-17.




## Harbor

Container and OCI artifact registry for managing software images within customer-operated infrastructure.

- Listing: https://launchinyourcloud.com/directory/harbor/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Harbor.
- Licensing model: open-source
- Installation: Install Harbor on a Docker-capable host or use the documented high-availability Helm deployment on Kubernetes.
- Architecture: Customer-operated registry, API/UI and supporting database/storage services
- Operations: Customer manages artifact storage, database, TLS, identity, scanner configuration, replication, backups and upgrades.
- Product website: https://goharbor.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scanning, signing and replication depend on the components and endpoints configured. Sending images to a remote registry or scanner changes data boundaries. Harbor v2.15.5 bounds audit and manifest request bodies, enforces actual decompression byte limits, redacts sensitive pagination and upload locations in rejection errors, and updates dependencies for high-severity CVEs. Operators on the 2.15 line should upgrade to v2.15.5 or a later supported patch.

Apache License 2.0 for upstream Harbor. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated registry, API/UI and supporting database/storage services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- devops: Private registry for container and OCI artifacts with project permissions, artifact policies, replication and optional security integrations.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/harbor (checked 2026-11-12). Source: https://github.com/gridalpha/harbor-railway/blob/main/core/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Harbor community deployment on Railway (railway): https://railway.com/deploy/harbor
  The community recipe provisions Harbor core, portal, job service, registry, registry control, scanner and proxy roles with PostgreSQL, Redis and object storage. Its component wrappers derive from upstream Harbor images. Review consistent image versions, TLS, authentication, registry storage and scanning/update operations; community packaging does not imply CNCF or project support.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the Harbor Railway core wrapper (railway): https://github.com/gridalpha/harbor-railway/blob/main/core/Dockerfile
  The inspected core wrapper derives from the upstream goharbor/harbor-core image (v2.15.2). Review the corresponding versions and configuration of every Harbor component before deploying the full community template.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Harbor is a CNCF Graduated project with documented foundation oversight and continuing upstream release maintenance.

Reviewed 2026-11-10.

- CNCF graduation and project governance: https://www.cncf.io/projects/harbor/

- Current release history: https://github.com/goharbor/harbor/releases

### Sources

- Official installation and runtime: https://goharbor.io/docs/latest/install-config/

- Upstream project and capabilities: https://github.com/goharbor/harbor

- Current upstream license: https://github.com/goharbor/harbor/blob/main/LICENSE

- Registry functionality: https://goharbor.io/

- Harbor v2.15.5 security hardening and dependency updates: https://github.com/goharbor/harbor/releases/tag/v2.15.5

### Licensing sources

- https://github.com/goharbor/harbor/blob/main/LICENSE

### Infrastructure sources

- https://goharbor.io/docs/latest/install-config/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. Harbor 2.15 documents OIDC browser login and group claims. Choose the authentication mode before adding ordinary local users; Docker/Helm clients use a CLI secret rather than interactive OIDC redirects. Scope: Harbor 2.15 OIDC UI and separate registry CLI authentication. Source: https://goharbor.io/docs/2.15.0/administration/configure-authentication/oidc-auth/ (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. Harbor documents both a Docker-host installer and Kubernetes Helm deployment. Configure HTTPS, image storage and the supported dependency versions; HA has separate prerequisites. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://goharbor.io/docs/latest/install-config/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The Docker-host prerequisites list 2 CPUs, 4 GB RAM and 40 GB disk minimum, with 4 CPUs, 8 GB and 160 GB recommended. Image volume, scanning, retention and HA affect actual sizing. Scope: Harbor deployment prerequisites; not per-node HA sizing or a cost estimate. Source: https://goharbor.io/docs/latest/install-config/installation-prereqs/ (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/goharbor/harbor/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v2.15.5, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream goharbor/harbor release record; commercial editions and deployment packages may differ. Source: https://github.com/goharbor/harbor/releases/tag/v2.15.5 (reviewed 2026-11-14).







## Indico (CERN)

CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

- Listing: https://launchinyourcloud.com/directory/indico/
- 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: Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded 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://getindico.io
- 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 template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite. Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin.

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

Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

- board-committee-governance: CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/indico
  Digest-pinned Indico 3.3.14 application, PostgreSQL 18, Redis, Celery and persistent uploaded files. The Railway template is maintained by a community publisher, rather than CERN support. It pins the current reviewed 3.3.14 image. Older third-party images need separate patch verification: upstream 3.3.14 fixes the offline-copy path traversal advisory. Meetings, attachments and agendas are distinct from a full board-governance suite.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ThiefMaster, pferreir, OmeGak, 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/indico/indico/graphs/contributors

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

### Sources

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

- Template Repo: https://github.com/aalfath/indico-railway-template

- Dockerfile (`3.3.14`): https://raw.githubusercontent.com/aalfath/indico-railway-template/main/Dockerfile

- MIT: https://raw.githubusercontent.com/indico/indico/master/LICENSE

- Releases (`v3.3.14`): https://github.com/indico/indico/releases

- v3.3.14 Changelog: https://raw.githubusercontent.com/indico/indico/v3.3.14/CHANGES.rst

- Indico offline-copy path traversal: https://github.com/indico/indico/security/advisories/GHSA-h57f-c9j4-577x

### Licensing sources

- https://raw.githubusercontent.com/indico/indico/master/LICENSE

### Infrastructure sources

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


### 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. Indico uses Flask-Multipass authentication/identity providers, with documented SAML and Shibboleth configurations and extensible providers. Configure the actual provider and identity/group mapping; LDAP directory authentication alone is not labelled federated SSO. Scope: Indico 3.3 stable production authentication; provider-specific configuration required. Source: https://docs.getindico.io/en/stable/config/auth/ (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. Official production guides install Indico, Celery, Redis and PostgreSQL on supported Debian/Ubuntu or Alma/Rocky systems. The nginx guide directs Shibboleth SSO deployments to Apache; configure the chosen web/authentication stack rather than treat all recipes as interchangeable. This is a single-machine installation procedure, not a cloud HA template. Scope: Indico 3.3 stable production installation; Apache is required for the documented Shibboleth integration. Source: https://docs.getindico.io/en/stable/installation/production/deb/nginx/ (reviewed 2026-11-20). Deployment artifact: https://docs.getindico.io/en/stable/installation/production/deb/nginx/. Artifact reference: Stable 3.3 guide; match supported package versions and web/authentication configuration. Supporting source: Production Apache alternative — https://docs.getindico.io/en/stable/installation/production/deb/apache/.

- Minimum footprint / sizing: Sources checked — unresolved. The full production instructions describe Indico/Celery/Redis/PostgreSQL and worker/reload settings but do not establish a complete CPU/RAM/storage floor or 100-user/1-TB HA capacity. Worker RSS thresholds are not host sizing. Confirm attachment storage, background jobs and concurrency. Scope: Production install and process settings; quantitative workload/HA sizing remains open. Source: https://docs.getindico.io/en/stable/installation/production/deb/nginx/ (reviewed 2026-11-20). Supporting source: Production Apache installation settings — https://docs.getindico.io/en/stable/installation/production/deb/apache/.

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Indico offline-copy path traversal (security-advisory): The upstream advisory identifies local file disclosure in offline-copy generation. Scope: Indico <3.3.14; fixed in 3.3.14 (GHSA-h57f-c9j4-577x / CVE-2026-107398). Conditions: Exposure depends on the ability to generate the affected offline copy; verify the exact upstream advisory. Action: Use Indico 3.3.14 or a later compatible fixed version; an older Azure image is not covered by the Railway template’s version pin. Source: https://github.com/indico/indico/security/advisories/GHSA-h57f-c9j4-577x; reviewed 2026-11-19.




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







## Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

- Listing: https://launchinyourcloud.com/directory/langfuse/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.
- Licensing model: open-source
- Installation: Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
- Architecture: Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage
- Operations: Customer operates the deployment, persistence, access policies, retention, backups and scaling.
- Product website: https://langfuse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.

The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.


Cloud evidence scope: Documented provider-specific deployment

### Category fit

- ai-observability: LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.

- ai-tools: Self-hosted LLM observability, evaluations and prompt-management platform.

- observability: Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

### Deployment boundaries


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

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

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

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/railway (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://langfuse.com/self-hosting/deployment/render (checked 2026-11-12). 


### Cloud deployment evidence

- Langfuse customer cloud deployment on AWS (aws): https://langfuse.com/self-hosting/deployment/aws
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Azure (azure): https://langfuse.com/self-hosting/deployment/azure
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse customer cloud deployment on Google Cloud (gcp): https://langfuse.com/self-hosting/deployment/gcp
  The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v3 community Railway deployment (railway): https://langfuse.com/self-hosting/deployment/railway
  The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Langfuse v4 community Render Blueprint (render): https://langfuse.com/self-hosting/deployment/render
  The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose on a VM: https://langfuse.com/self-hosting/deployment/docker-compose

- Self-hosting architecture and provider dependencies: https://langfuse.com/self-hosting

- AWS account Terraform deployment: https://langfuse.com/self-hosting/deployment/aws

- Azure account Terraform deployment: https://langfuse.com/self-hosting/deployment/azure

- Google Cloud account Terraform deployment: https://langfuse.com/self-hosting/deployment/gcp

- Core and enterprise licensing: https://github.com/langfuse/langfuse/blob/main/LICENSE

- Licensing and edition terms: https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

- Langfuse v3 community Railway deployment: https://langfuse.com/self-hosting/deployment/railway

- Langfuse v4 community Render Blueprint: https://langfuse.com/self-hosting/deployment/render

- Langfuse v4.82.0 release: https://github.com/langfuse/langfuse/releases/tag/v4.82.0

### Licensing sources

- https://github.com/langfuse/langfuse/blob/main/LICENSE

- https://github.com/langfuse/langfuse/blob/main/ee/LICENSE

### Infrastructure sources

- https://langfuse.com/self-hosting/deployment/docker-compose

- https://langfuse.com/self-hosting/deployment/aws

- https://langfuse.com/self-hosting/deployment/azure

- https://langfuse.com/self-hosting/deployment/gcp


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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 self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review. Scope: Self-hosted OAuth/OIDC sign-in. Source: https://langfuse.com/self-hosting/security/authentication-and-sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports. Scope: Upstream Compose recipe; supporting-service operations remain customer responsibilities. Source: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/langfuse/langfuse/blob/main/docker-compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint. Scope: Langfuse Web/Worker resource recommendation; backing services additional. Source: https://langfuse.com/self-hosting/deployment/infrastructure/containers (reviewed 2026-11-20).

- License pricing: Documented. Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Scope: Upstream Langfuse self-hosted release. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- Langfuse GitHub Enterprise SSO SSRF fix (security-advisory): Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. Conditions: Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target. Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity. Source: https://github.com/langfuse/langfuse/releases/tag/v4.82.0; reviewed 2026-11-18.




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







## LibreChat Self-Hosted

Self-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.

- Listing: https://launchinyourcloud.com/directory/librechat/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT
- Licensing model: open-source
- Installation: Official Railway one-click template or Docker on a DigitalOcean Ubuntu Droplet
- Architecture: Containerized web and API services with application databases, retrieval services and customer-configured model endpoints
- Operations: Customer manages the Railway project or DigitalOcean Droplet, application secrets, model credentials, data services, backups, scaling and upgrades. Railway operates its platform; Droplet users also maintain the operating system and Docker runtime.
- Product website: https://www.librechat.ai/
- Source review: 2026-11-15; cloud review: 2026-11-15; licensing review: 2026-11-15; infrastructure review: 2026-11-15

### Scope and qualifications

The Railway path runs in the customer's project on platform-managed infrastructure; the DigitalOcean path uses a customer-operated Droplet. External model, embedding, search and tool providers receive data according to customer configuration. Review generated secrets, public networking, persistent data services and image updates before production use.

LibreChat is MIT-licensed. The licenses and commercial terms of configured model providers, tools and external services are separate.

LibreChat runs persistent application, database and retrieval containers in a Railway project or on a DigitalOcean Droplet.


### Category fit

- ai-applications-rag: Provides self-hosted multi-model chat, agents, file-backed retrieval and tool use over customer-selected model and data services.

- ai-tools: Provides a self-hosted interface and orchestration layer for model endpoints, agents, MCP tools, authentication and administrative controls.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/railway (checked 2026-11-15). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.librechat.ai/docs/remote/digitalocean (checked 2026-11-15). 


### Cloud deployment evidence

- LibreChat one-click deployment on Railway (railway): https://www.librechat.ai/docs/remote/railway
  LibreChat documents creating a Railway account, reviewing the template's three containers and environment variables, deploying the services and accessing the resulting LibreChat URL in the customer's Railway project.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.

- LibreChat deployment on DigitalOcean (digitalocean): https://www.librechat.ai/docs/remote/digitalocean
  The upstream guide creates an Ubuntu Droplet in the customer DigitalOcean project, configures a user and firewall, then links to the Docker installation steps. The example is for a small personal deployment, not a production sizing guarantee.
  Source type: vendor-documentation; reviewed: 2026-11-15; vendor support: not-assessed.


### Community and maintenance

LibreChat documents a community of hundreds of contributors and maintains its implementation in a public upstream repository. Contributor history establishes active project participation; it does not establish support for a specific Railway template release.

Reviewed 2026-11-15.

- LibreChat project and community: https://www.librechat.ai/about

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

### Sources

- LibreChat Railway deployment: https://www.librechat.ai/docs/remote/railway

- LibreChat project, self-hosting and MIT license: https://www.librechat.ai/about

- LibreChat upstream repository: https://github.com/LibreChat-AI/LibreChat

- LibreChat contributor history: https://github.com/LibreChat-AI/LibreChat/graphs/contributors

- LibreChat deployment on DigitalOcean: https://www.librechat.ai/docs/remote/digitalocean

### Licensing sources

- https://www.librechat.ai/about

### Infrastructure sources

- https://www.librechat.ai/docs/remote/railway

- https://www.librechat.ai/docs/remote/digitalocean


### 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 official self-hosted authentication guide documents OAuth2/OpenID Connect and SAML, with separately configured LDAP and local accounts. Configure the selected provider, registration policy, account linking and administrator recovery; external model credentials are a separate authentication surface. Scope: Self-hosted LibreChat user authentication. Source: https://www.librechat.ai/docs/configuration/authentication (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 Railway guide describes its repository deploy button, three-container configuration and required environment variables. Review persistence and optional integrations before production; the one-click recipe does not establish a minimum production footprint. Scope: LibreChat Railway deployment guide; moving template and configured features. Source: https://www.librechat.ai/docs/remote/railway (reviewed 2026-11-16).

- Minimum footprint / sizing: Documented. The Docker guide lists 1 vCPU and 1 GiB RAM minimum for LibreChat containers, recommending at least 2 GB allocated to Docker with the default backing services. MongoDB, search, RAG/pgvector, storage and HA need sizing; locally hosted models require additional compute and often GPUs. Scope: Official Docker starting profile; model inference and production HA excluded. Source: https://www.librechat.ai/docs/local/docker (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is MIT licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/danny-avila/LibreChat/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## LibreDesk

Self-hosted shared inbox and customer support desk.

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

### Scope and qualifications

Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.

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

LibreDesk application, PostgreSQL, cache and persistent attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Self-hosted shared inbox and customer support desk.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/libredesk
  LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/libredesk
  LibreDesk application, PostgreSQL, cache and persistent attachments. Provider templates and upstream releases have separate update cycles; email credentials and external channels determine communication data flows.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes abhinavxd, csr4422, jleroy, 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/abhinavxd/libredesk/graphs/contributors

- Upstream project: https://github.com/abhinavxd/libredesk

### Sources

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

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE

- GitHub Releases: https://github.com/abhinavxd/libredesk/releases

### Licensing sources

- https://raw.githubusercontent.com/abhinavxd/libredesk/main/LICENSE

### Infrastructure sources

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

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


### 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. Agents can use Google, Microsoft or a custom OpenID Connect provider. Create local agent accounts first: LibreDesk matches the provider email to an existing agent and does not create accounts through SSO. Configure the issuer, credentials and registered callback URL. Scope: Current upstream agent-login configuration, also described by published v2.9.2 source. Source: https://docs.libredesk.io/configuration/sso (reviewed 2026-11-20). Supporting source: Published v2.9.2 feature and installation reference — https://github.com/abhinavxd/libredesk/blob/v2.9.2/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published v2.9.2 recipe supplies Compose and configuration files for LibreDesk, PostgreSQL and Redis, or a standalone release binary. Set encryption material and the initial administrator password, pin compatible images and configure TLS, persistence and backups. Scope: Published upstream release recipe; the quickstart image tags still require an explicit pin. Source: https://github.com/abhinavxd/libredesk/blob/v2.9.2/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/abhinavxd/libredesk/blob/v2.9.2/docker-compose.yml. Artifact reference: v2.9.2. Supporting source: Current installation and encryption-key guide — https://docs.libredesk.io/getting-started/installation.

- Minimum footprint / sizing: Sources checked — unresolved. The installation guide identifies the application, PostgreSQL and Redis but does not establish a whole-stack CPU/RAM/storage minimum for the selected workload. Size ticket/message throughput, attachments, retention, database and redundancy separately; a single binary does not imply a tiny HA deployment. Scope: Upstream topology confirmed; numeric production sizing remains unconfirmed. Source: https://docs.libredesk.io/getting-started/installation (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## LiteLLM Proxy Self-Hosted

Self-hosted AI API gateway providing model routing, access controls and usage tracking.

- Listing: https://launchinyourcloud.com/directory/litellm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
- Licensing model: open-source
- Installation: Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.
- Architecture: Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints
- Operations: Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
- Product website: https://www.litellm.ai/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.

The gateway has an MIT-licensed base and separately licensed enterprise features. The enterprise documentation describes a license key enabling restricted capabilities in the gateway, beyond paid hosting or support alone.

The gateway runs as provisioned application containers or Kubernetes workloads; persistent key/spend storage can use PostgreSQL. Inference compute is a separate dependency rather than included in the gateway.


### Category fit

- ai-inference-gateways: Self-hosted model API gateway for routing, virtual keys, spend tracking and policy enforcement. It routes inference requests; it is not an inference engine for all supported models.

- ai-tools: Self-hosted AI API gateway providing model routing, access controls and usage tracking.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 


### Cloud deployment evidence

- LiteLLM production deployment (aws, azure, gcp): https://docs.litellm.ai/docs/proxy/deploy
  Official production guidance covers EKS, AKS and GKE with Helm, plus Terraform on AWS and Google Cloud. The proxy, database and Redis deployment is separate from the model services it calls.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- LiteLLM Railway and Render deployment options (railway, render): https://docs.litellm.ai/docs/proxy/deploy
  The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production deployment: https://docs.litellm.ai/docs/proxy/deploy

- Gateway request flow and functionality: https://docs.litellm.ai/docs/simple_proxy

- MIT core and enterprise exception: https://github.com/BerriAI/litellm/blob/main/LICENSE

- Licensing and edition terms: https://docs.litellm.ai/docs/enterprise

- Supply-chain incident and Cosign verification guidance: https://docs.litellm.ai/blog/security-incident-oct-21-2026

- Canonical LiteLLM incident investigation: https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain

- LiteLLM v1.110.0 release: https://github.com/BerriAI/litellm/releases/tag/v1.110.0

- LiteLLM v1.108.11 LTS release: https://github.com/BerriAI/litellm/releases/tag/v1.108.11

- LiteLLM v1.110.1: https://github.com/BerriAI/litellm/releases/tag/v1.110.1

- LiteLLM v1.108.12 LTS: https://github.com/BerriAI/litellm/releases/tag/v1.108.12

### Licensing sources

- https://github.com/BerriAI/litellm/blob/main/LICENSE

- https://docs.litellm.ai/docs/enterprise

### Infrastructure sources

- https://docs.litellm.ai/docs/proxy/deploy


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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 Admin UI documents OIDC SSO. From 1.76.0, it is free for up to five users; larger deployments require an Enterprise licence. Configure issuer, callbacks, roles and database/master-key prerequisites. This is Admin UI identity, distinct from model API virtual keys. Scope: LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies. Source: https://docs.litellm.ai/docs/proxy/admin_ui_sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Release images and Helm charts use keyless Cosign from v1.111.0-dev.3; verify the documented workflow identity and issuer. Earlier releases use historical keys. The October 21 v1.107.0 compromise also affected mutable image tags; compare digests and exposure windows because affected images had valid historical signatures. Follow the incident remediation guidance for executed artifacts. Current advisory review: LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Current review: v1.108.12 LTS fixes tool_policy allowing a /v1/messages request through when a blocked tool name exceeded 64 characters. Upgrade the maintained LTS line and retest tool-policy enforcement. Scope: LiteLLM 1.108 LTS /v1/messages tool_policy; standard and other maintained lines require their own release review. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: Canonical incident investigation — https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain. Supporting source: Prior security-controls source — https://docs.litellm.ai/blog/security-incident-oct-21-2026.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm guide documents Kubernetes installation and configurable database/secret settings. Select matching chart/image versions and review the separate scaling and production-readiness guidance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.litellm.ai/docs/proxy/deploy/helm (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current production guide starts load testing at 1 vCPU and 4 GiB per worker, preferably one worker per Kubernetes pod. Memory depends on queued requests, payloads, stream duration and logging. PostgreSQL, Redis for multiple workers/instances, HA and model inference are additional. Scope: Gateway per-worker load-test starting point; backing services and inference excluded. Source: https://docs.litellm.ai/docs/proxy/prod (reviewed 2026-11-20).

- License pricing: Documented. Core code outside litellm/enterprise is MIT licensed; the enterprise directory has separate terms. Enterprise features and support need separate entitlement and pricing. Upstream model APIs, infrastructure and operating labour are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. LiteLLM v1.110.1 was published November 19, 2026. It refreshes the Wolfi base and changes the UI image to slim nginx, removing curl. The maintained v1.108.12 LTS line fixes a tool_policy bypass for blocked tool names longer than 64 characters. Scope: Upstream LiteLLM standard release; select and maintain either the standard or LTS line. Source: https://github.com/BerriAI/litellm/releases/tag/v1.110.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/BerriAI/litellm/releases/tag/v1.110.0. Supporting source: LiteLLM v1.108.11 LTS — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: v1.108.12 LTS security fix — https://github.com/BerriAI/litellm/releases/tag/v1.108.12.




### Security and lifecycle reviews

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

- LiteLLM LTS proxy security fixes (security-advisory): LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Scope: LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release. Conditions: Applicability depends on Bedrock guardrails and team-setting permissions. Action: Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.11; reviewed 2026-11-18.

- LiteLLM 1.108.12 LTS tool-policy fix (security-advisory): LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages. Scope: LiteLLM 1.108 LTS /v1/messages tool-policy enforcement. Conditions: The request must use a blocked tool name longer than 64 characters. Action: Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12; reviewed 2026-11-19.




## Mail-Archiver

Open-source email archiving, search and export service with a community Railway deployment.

- Listing: https://launchinyourcloud.com/directory/mail-archiver/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Mail-Archiver application, PostgreSQL and persistent archive storage.
- 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/s1t5/mail-archiver
- 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 template follows a moving application image. Review current upstream retention, deletion-lock and audit-export settings, pin the chosen release, and verify backup/restore and authentication before production use.

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

Mail-Archiver application, PostgreSQL and persistent archive storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- records-management: Open-source email archiving, search and export service with a community Railway deployment.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/mail-archiver
  Mail-Archiver application, PostgreSQL and persistent archive storage. The Railway template follows a moving application image. Review current upstream retention, deletion-lock and audit-export settings, pin the chosen release, and verify backup/restore and authentication before production use.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes s1t5, Zappo-II, tilwegener, 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/s1t5/mail-archiver/graphs/contributors

- Upstream project: https://github.com/s1t5/mail-archiver

### Sources

- Railway Template: https://railway.com/deploy/mail-archiver

- Mail-Archiver Docs: https://s1t5.github.io/mail-archiver/

- GPL-3.0 LICENSE: https://raw.githubusercontent.com/s1t5/mail-archiver/main/LICENSE

- GitHub Releases: https://github.com/s1t5/mail-archiver/releases

### Licensing sources

- https://raw.githubusercontent.com/s1t5/mail-archiver/main/LICENSE

### Infrastructure sources

- https://railway.com/deploy/mail-archiver


### 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 upstream OIDC guide configures a provider authority, client credentials/scopes and callback, with user approval/provisioning and optional password-login disablement. This is archive-user SSO, separately from Microsoft/Gmail OAuth used to import mail. Review role creation and auto-approval deliberately. Scope: Mail-Archiver upstream application-user OIDC configuration. Source: https://s1t5.github.io/mail-archiver/OIDC_Implementation/ (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. Upstream documents Docker Compose for the application and PostgreSQL, persistent volumes, environment/secrets and optional reverse-proxy/TLS configuration. The example uses moving image tags: select a compatible release and database version, then test backup and upgrades. Scope: Upstream Mail-Archiver Compose deployment reference; provider template packaging separate. Source: https://s1t5.github.io/mail-archiver/Setup/ (reviewed 2026-11-21). Deployment artifact: https://s1t5.github.io/mail-archiver/Setup/. Artifact reference: Current upstream setup documentation reviewed on this date.

- Minimum footprint / sizing: Sources checked — unresolved. The setup guide identifies application/PostgreSQL services and configurable background jobs, but does not establish quantitative production CPU/RAM/storage requirements. Size ingestion, attachment/index work, concurrent searches, original messages, retention and HA separately. Scope: Mail-Archiver complete production hardware baseline remains unconfirmed. Source: https://s1t5.github.io/mail-archiver/Setup/ (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

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







## Memos

Self-hosted lightweight notes, documents and knowledge timeline.

- Listing: https://launchinyourcloud.com/directory/memos/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, 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: Cloudron package; Application platform deployment; Docker / Compose
- Architecture: Memos application, SQLite database and attachment storage.
- 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://usememos.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system.

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

Memos application, SQLite database and attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted lightweight notes, documents and knowledge timeline.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/memos.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/memos-3
  Memos application, SQLite database and attachment storage. Cloudron, Hostinger and Railway packages have distinct upgrade cycles. Multi-user notes do not establish a regulated document-retention system. 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 boojack, johnnyjoygh, athurg, 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/usememos/memos/graphs/contributors

- Upstream project: https://github.com/usememos/memos

### Sources

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

- Railway: https://railway.com/deploy/memos-3

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

- MIT LICENSE: https://raw.githubusercontent.com/usememos/memos/main/LICENSE

- GitHub Releases: https://github.com/usememos/memos/releases

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

### Licensing sources

- https://raw.githubusercontent.com/usememos/memos/main/LICENSE

### Infrastructure sources

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

- https://railway.com/deploy/memos-3


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. Memos documents external OAuth2/SSO providers separately from local passwords and API tokens. Providers map a stable external identity to a local user; account linking and registration policy control admission. Password login can be disabled for regular users while retaining an admin recovery path. Scope: Self-hosted Memos current authentication configuration; verify compatibility with the installed release and any provider package. Source: https://usememos.com/docs/configuration/authentication (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 deployment guide provides a Docker container with persistent application data; its README also links Compose, Kubernetes and binary options. Choose a published version and compatible database/configuration, then configure HTTPS, backups and instance authentication. Scope: Self-hosted Memos application/data deployment; not a complete HA cloud stack. Source: https://usememos.com/docs/deploy/docker (reviewed 2026-11-20). Deployment artifact: https://github.com/usememos/memos. Artifact reference: main (moving branch); 26.11.1 release snapshot is recorded separately.

- Minimum footprint / sizing: Documented. The Cloudron package declares 256MB 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/memos.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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







## Nextcloud Server

Self-hosted file synchronization and sharing server for team document collaboration.

- Listing: https://launchinyourcloud.com/directory/nextcloud-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Server core; review selected applications separately
- Licensing model: open-source
- Installation: Official Nextcloud AIO or documented Linux/PHP server installation
- Architecture: Persistent web application, SQL database and file storage; the documented manual installation uses a Linux, Apache, MariaDB and PHP stack.
- Operations: Customer operates the server, storage, backups and upgrades; select a supported release and deployment method.
- Product website: https://nextcloud.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted Server and file-sharing capabilities. The installation manual distinguishes official AIO from community Snap, VM and Docker options, which Nextcloud GmbH does not officially support. Review separately selected applications, integrations and enterprise support terms.

This classification covers Nextcloud Server, whose repository provides the GNU Affero GPL version 3. It does not classify every separately installed application or commercial service.

The official manual documents a persistent Linux web/database installation and an official AIO deployment.


### Category fit

- document-management: File synchronization, sharing and collaborative file workspaces; this entry does not establish regulated records-management capabilities.

- collaboration: Shared file workspaces for teams, with additional collaboration applications available in the Nextcloud ecosystem.

### Deployment boundaries


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


### Cloud deployment evidence

- Nextcloud Server community deployment on Railway (railway): https://railway.com/deploy/nextcloud
  The community template deploys the official Nextcloud container with PostgreSQL, a persistent application volume and bucket storage in a customer Railway project. Review the selected release, trusted domains/proxies, background jobs, object-storage configuration and backups. Optional Office, Talk and third-party apps can require additional services; they are not implied by this server deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Official case studies describe self-hosted or on-premise deployments at Milieudefensie, CSIC and Sorbonne University. The official changelog records the 35.0.3 maintenance release on November 12, 2026. These are product adoption and maintenance signals, not a claim that each adopter uses the same edition or installation method.

Reviewed 2026-11-13.

- Organizational deployments and customer stories: https://nextcloud.com/customers/

- Server maintenance releases: https://nextcloud.com/changelog/

### Sources

- Linux installation and deployment options: https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html

- Nextcloud Files capabilities: https://nextcloud.com/files/

- Nextcloud Server license: https://raw.githubusercontent.com/nextcloud/server/master/COPYING

- Nextcloud maintenance changelog: https://nextcloud.com/changelog/

- Official customer implementation stories: https://nextcloud.com/customers/

### Licensing sources

- https://raw.githubusercontent.com/nextcloud/server/master/COPYING

### Infrastructure sources

- https://docs.nextcloud.com/server/stable/admin_manual/installation/source_installation.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 Nextcloud-maintained SSO/SAML app supports SAML 2.0 and environment-based authentication. Enable a compatible app release and configure the provider; the repository distinguishes tested providers from theoretical protocol compatibility. Scope: Nextcloud SSO/SAML application; server/app compatibility must be checked. Source: https://github.com/nextcloud/user_saml (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. Nextcloud AIO publishes a multi-container application bundle. Review its host/volume/port requirements and enabled optional services; the bundle has a different footprint from a minimal PHP server installation. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nextcloud/all-in-one (reviewed 2026-11-14). Deployment artifact: https://github.com/nextcloud/all-in-one. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The versioned manual lists 128 MB minimum and 512 MB recommended RAM per PHP process. This is not a total host/AIO minimum: database, concurrent processes, apps, previews and storage need additional resources. Scope: Nextcloud 33 per-process memory, not whole-server sizing. Source: https://docs.nextcloud.com/server/33/admin_manual/installation/system_requirements.html (reviewed 2026-11-14).

- License pricing: Documented. The Server core is AGPL-3.0. This does not price Enterprise support, optional applications, hosting or operating labour; review those separately for the selected deployment. Scope: Nextcloud Server core; applications and commercial subscriptions excluded. Source: https://raw.githubusercontent.com/nextcloud/server/master/COPYING (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v33.0.11, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream nextcloud/server release record; commercial editions and deployment packages may differ. Source: https://github.com/nextcloud/server/releases/tag/v33.0.11 (reviewed 2026-11-14).







## NocoDB Self-Hosted

Spreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.

- Listing: https://launchinyourcloud.com/directory/nocodb/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license.
- Licensing model: source-available
- Installation: Run the official Docker image with persistent storage or use its documented Compose-based server installer.
- Architecture: Customer-operated application with persistent metadata/database services and optional connected databases
- Operations: Customer manages app services, databases, access rules, secrets, backups, upgrades and any paid license.
- Product website: https://nocodb.com/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The upstream license changed in January 2026; this is classified as source-available. Internal-tool Interfaces are a licensed feature, while AI apps have separate availability. Connected databases, AI providers and integrations can send data outside the account. NocoDB 2026.10.2 restricts shared views and dashboards to displayed fields, limits forms to their own fields, prevents Editors from reading workflow-step secrets and caps workflow webhook bodies at 1 MB. It also restores NC_SSO=oidc, requires unchanged RelayState for SAML IdP-initiated login and repairs air-gapped license refresh. Retest public shares, forms, workflow permissions and SSO after upgrading.

Current upstream master/develop code uses the Sustainable Use License: internal business or noncommercial/personal use is permitted, with distribution and other restrictions. Paid self-hosted features require a separate license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Official Docker images run the NocoDB application on a customer-controlled host with persistent storage and a configured SQLite or PostgreSQL metadata backend; the server installer adds supporting services.


### Category fit

- no-code-databases: Spreadsheet-style database interface with linked records, views, forms and programmatic access.

- internal-tools: Interfaces build focused internal pages, dashboards and approval views on base data. The reviewed release limits Interfaces to licensed self-hosted Business plans and above.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://nocodb.com/docs/self-hosting/installation/community-methods (checked 2026-11-12). 


### Cloud deployment evidence

- NocoDB community cloud installation methods (aws, gcp, digitalocean, railway): https://nocodb.com/docs/self-hosting/installation/community-methods
  The upstream community-methods guide includes full application deployment on DigitalOcean App Platform and a Railway template alongside AWS ECS/Fargate and Google Cloud Run. NocoDB explicitly does not maintain these methods or give them first-class installation support. Review image licensing, database configuration, persistence and production requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

NocoDB's published adopter list names Accenture, Bosch and American Express. Its official GitHub discussion records actual exchanges between named users and maintainer o1lab about the 2026 license change, including critical feedback, while the release history shows continuing maintenance. These are adoption and participation signals; they do not establish which edition or hosting model any named organization uses.

Reviewed 2026-11-10.

- Vendor-published named organization adoption claims: https://nocodb.com/

- Observed user/maintainer discussion of the license change: https://github.com/nocodb/nocodb/discussions/12891

- Current maintenance releases: https://github.com/nocodb/nocodb/releases

### Sources

- Upstream project and capabilities: https://github.com/nocodb/nocodb

- Current upstream license: https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

- Internal Interfaces and self-hosted plan availability: https://nocodb.com/docs/changelog/2026.08.0

- Product functionality: https://nocodb.com/docs/product

- NocoDB 2026.10.2 release: https://github.com/nocodb/nocodb/releases/tag/2026.10.2

### Licensing sources

- https://raw.githubusercontent.com/nocodb/nocodb/develop/LICENSE.md

### Infrastructure sources

- https://github.com/nocodb/nocodb


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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 authentication guide documents SAML and OIDC providers and explicitly describes on-premises SSO configuration without Cloud DNS-domain verification. SSO is associated with paid self-hosted plans; optional password login alongside SSO has a separate on-premises setting. Scope: Paid self-hosted user federation; verify the selected Business/Scale/Enterprise entitlement rather than assuming Community includes SSO. Source: https://nocodb.com/docs/product-docs/account-settings/authentication (reviewed 2026-11-20). Supporting source: Self-hosted plans and licensing — https://nocodb.com/docs/self-hosting.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. NocoDB 2026.10.2 prevents shared views and dashboards from returning hidden fields, prevents forms from writing unrelated fields, hides workflow secrets from Editors and limits webhook request bodies. Upgrade and retest shares, forms, workflows and SSO. Scope: NocoDB self-hosted access controls documented in the 2026.10.2 release; no broader affected-version range was published. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream repository publishes an installer that generates a PostgreSQL/Redis/Traefik Compose stack. Re-running can upgrade the application; inspect the script, preserve secrets/data and control version changes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/nocodb/nocodb (reviewed 2026-11-14). Deployment artifact: https://github.com/nocodb/nocodb/blob/develop/docker-compose/1_Auto_Upstall/noco.sh. Artifact reference: develop installer (moving).

- Minimum footprint / sizing: Documented. The self-hosting guide lists a minimum of 2 vCPU, 2 GB RAM and 10 GB disk, and a production recommendation of 4 vCPU, 8 GB RAM and 50 GB or more disk. Database, attachments, workload and replication require additional sizing. Scope: Single-server starting guidance; not a complete HA design or 1-TB storage allowance. Source: https://nocodb.com/docs/self-hosting (reviewed 2026-11-20).

- License pricing: Documented. The 2026.10.2 licence identifies the Sustainable Use License for the master/develop code: use and modification are limited to internal business, personal or non-commercial purposes, with restricted distribution. Commercial/self-hosted paid features require separate entitlements; this is not an unrestricted OSI open-source licence. Scope: Reviewed source-available terms; confirm commercial use and paid features for the intended deployment. Source: https://github.com/nocodb/nocodb/blob/2026.10.2/LICENSE.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. NocoDB 2026.10.2 was published November 19, 2026. It fixes shared-view, dashboard, form and workflow authorization boundaries, restores NC_SSO=oidc, changes SAML IdP-initiated RelayState handling and repairs air-gapped license refresh. Scope: Upstream NocoDB self-hosted release; paid-feature and license behavior remains edition-dependent. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/nocodb/nocodb/releases/tag/2026.10.1.




### Security and lifecycle reviews

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

- NocoDB 2026.10.2 access-control hardening (security-advisory): NocoDB 2026.10.2 prevents hidden-field disclosure in shares, unrelated form writes and workflow-secret disclosure to Editors, and caps webhook request bodies. Scope: NocoDB self-hosted behavior documented in the 2026.10.2 release; no universal affected-version range was published. Conditions: Public shares or dashboards, forms, Editor access to workflows, configured-key webhooks, OIDC or SAML determine exposure and upgrade impact. Action: Upgrade to 2026.10.2 or later and retest shares, forms, workflows, OIDC and SAML IdP-initiated login. Source: https://github.com/nocodb/nocodb/releases/tag/2026.10.2; reviewed 2026-11-19.




## Odoo On-Premise

Self-hosted ERP and CRM applications for sales pipelines, business records and operational workflows.

- Listing: https://launchinyourcloud.com/directory/odoo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Community LGPLv3; Enterprise uses the Odoo Enterprise Edition License; individual add-ons may have other licenses
- Licensing model: open-source
- Installation: Linux packages or source installation with PostgreSQL
- Architecture: Customer-operated Odoo application server and PostgreSQL database
- Operations: Customer or implementation partner hosts the application, secures it, manages backups and applies updates.
- Product website: https://www.odoo.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope this entry to an installation on customer-selected systems rather than Odoo Online or Odoo.sh. Enterprise requires valid subscription entitlements, and the documented registration mechanism periodically contacts Odoo validation services. Do not assume every business app is included in Community.

The listed on-premise offering spans LGPLv3 Community and the separately licensed Enterprise edition. Enterprise and certain app code use restrictive commercial licenses; the fact that some source is accessible does not make all editions LGPL.

Official packages install Odoo as a persistent Linux service and require PostgreSQL. Windows packages are documented for testing/local instances, with production deployment discouraged.


### Category fit

- erp-crm: Modular business applications spanning CRM, sales, accounting, inventory and operations; applications and entitlements vary between Community and Enterprise.

### Deployment boundaries


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


### Cloud deployment evidence

- Odoo Community 19 deployment on Railway (railway): https://railway.com/deploy/odoo-crm-erp
  The community template deploys the official odoo:19.0 Community image with PostgreSQL and persistent application storage in a customer Railway project. It does not establish access to Enterprise modules. Review database-version compatibility, administrator credentials, filestore backups and the enabled modules; platform resource charges still apply.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official packaged installation documentation source: https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst

- Community and Enterprise licenses: https://raw.githubusercontent.com/odoo/documentation/19.0/content/legal/licenses.rst

- Business application scope: https://raw.githubusercontent.com/odoo/odoo/19.0/README.md

- On-premise registration and validation: https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise.rst

- CRM workflow: https://raw.githubusercontent.com/odoo/documentation/19.0/content/applications/sales/crm.rst

### Licensing sources

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/legal/licenses.rst

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst

### Infrastructure sources

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst


### 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. Odoo 19 documents Google account sign-in using the OAuth Authentication module and a configured Google OAuth client. This establishes Google OAuth login; it does not establish arbitrary SAML providers or automatic enterprise user provisioning. Scope: Odoo 19 Google sign-in; configure both the external provider and the Odoo database. Source: https://www.odoo.com/documentation/19.0/applications/general/users/google.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 Odoo 19 documentation identifies official Community nightly packages and Community/Enterprise downloads for supported operating systems. Enterprise downloads require a paying on-premise customer or partner account; packages also require PostgreSQL and other dependencies. Scope: Odoo 19 packaged installers; not an IaC template or Odoo Online entitlement. Source: https://www.odoo.com/documentation/19.0/administration/on_premise/packages.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. Odoo 19 provides production worker-sizing guidance: approximately six concurrent users per worker, a CPU rule of (cores × 2) + 1, and RAM estimates for light versus heavy workers. Add cron workers, PostgreSQL, storage and replicas; these are sizing rules, not a fixed 100-user HA minimum. Scope: Odoo 19 Linux multiprocess deployment; named users differ from concurrent users. Source: https://www.odoo.com/documentation/19.0/administration/on_premise/deploy.html (reviewed 2026-11-20).

- License pricing: Documented. Odoo 19 Community is LGPLv3; Enterprise has a separate proprietary licence. The per-user Custom subscription includes the on-premise option. Hosting, implementation, custom-code maintenance and in-app services can add costs; Odoo.sh hosting is excluded from the displayed subscription. Scope: Odoo Community versus Enterprise Custom on-premise; displayed currency and introductory discounts vary. Source: https://www.odoo.com/pricing-plan (reviewed 2026-11-20). Supporting source: Odoo 19 licences — https://www.odoo.com/documentation/19.0/legal/licenses.html.

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




## OpenSearch

Distributed search and analytics engine with vector retrieval, operational-data analysis and OpenSearch Dashboards visualizations.

- Listing: https://launchinyourcloud.com/directory/opensearch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.
- Licensing model: open-source
- Installation: Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.
- Architecture: Customer-operated distributed cluster with index shards and replicas on persistent storage, plus optional Dashboards and ingestion components
- Operations: Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
- Product website: https://opensearch.org/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Sample deployments and demo security settings require production configuration. Official images distributed through Amazon ECR are not evidence of an AWS-specific deployment. The listing covers self-operated OpenSearch; Amazon OpenSearch Service and other managed services are separate delivery models. Embeddings and AI connectors can involve external models or services. OpenSearch 3.10.0 removes experimental Views and macOS x64 archives and fixes remote-store data-loss or stall paths, bulk-index corruption, heap leaks, snapshot queue stalls, remote-translog issues, and OOM behavior. Validate plugins, Dashboards, and storage recovery before upgrading.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

Official Docker images run OpenSearch nodes and Dashboards on compatible container hosts. Persistent index storage and host memory and kernel settings are operational requirements; distribution through a cloud registry does not establish a provider deployment badge.


### Category fit

- databases-vector: Indexes and searches vectors alongside metadata, with lexical, nearest-neighbor, semantic and hybrid retrieval. Embedding generation requires an appropriate configured model or externally generated vectors.

- data-analytics: Distributed search and aggregation engine with OpenSearch Dashboards for exploring and visualizing indexed data.

- observability: Search and analytics over ingested operational data, including log analysis and monitoring; collection, ingestion and dashboard configuration remain deployment work.

- ai-tools: Vector storage, semantic search and retrieval for AI applications and RAG. Embedding generation and model connectors have separately configured runtimes and data flows.

### Deployment boundaries


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


### Cloud deployment evidence

- Self-operated OpenSearch and Dashboards on Railway (railway): https://railway.com/deploy/opensearch-analytics
  The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The OpenSearch Software Foundation is organized under the Linux Foundation. Official release records show OpenSearch 3.9.0 released on 29 September 2026 and continuing maintenance planning. Project case studies describe production adoption by Atlassian, LINE and other organizations; managed-service case studies demonstrate project adoption rather than proving self-hosted account boundaries.

Reviewed 2026-11-10.

- OpenSearch Software Foundation: https://opensearch.org/foundation/

- Current releases and maintenance policy: https://opensearch.org/releases/

- Current released artifacts: https://opensearch.org/downloads/

- Named production case studies: https://opensearch.org/case-studies/

### Sources

- OpenSearch Core capabilities and architecture: https://opensearch.org/platform/opensearch-core/

- Vector search documentation: https://docs.opensearch.org/latest/vector-search/

- Official Docker installation: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- Security demo configuration: https://docs.opensearch.org/latest/security/configuration/demo-configuration/

- Release downloads and Apache-2.0 licensing: https://opensearch.org/downloads/

- Upstream Apache-2.0 license: https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

- OpenSearch 3.10.0 release: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0

### Licensing sources

- https://github.com/opensearch-project/OpenSearch/blob/main/LICENSE.txt

### Infrastructure sources

- https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/

- https://opensearch.org/platform/opensearch-core/


### 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 Security plugin supports the SAML 2.0 browser SSO profile, primarily for OpenSearch Dashboards. This is not a general authentication method for every direct OpenSearch client/API call. Scope: OpenSearch Security plugin and Dashboards browser login. Source: https://docs.opensearch.org/latest/security/authentication-backends/saml/ (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 Docker installation guide provides official images and Compose examples. Configure the required administrator password, persistent data and security settings; demo certificates/settings are not a production security baseline. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide sets a default 1-GB JVM heap and recommends allocating about half of system RAM to heap. It does not establish one complete production minimum: data/index size, roles, replicas, ingestion, Dashboards, vectors and storage performance must be sized separately. A JVM default is not HA capacity. Scope: Upstream JVM/install defaults; full production footprint unresolved. Source: https://docs.opensearch.org/latest/install-and-configure/install-opensearch/index/ (reviewed 2026-11-20).

- License pricing: Documented. The OpenSearch core is Apache-2.0 licensed. Plugins and bundled components require their own licence review; commercial support, managed Amazon OpenSearch Service, model services and infrastructure have separate prices. Scope: Upstream OpenSearch core licence; managed service pricing excluded. Source: https://raw.githubusercontent.com/opensearch-project/OpenSearch/main/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. OpenSearch 3.10.0 was published November 18, 2026. It removes experimental Views and macOS x64 archives and contains material remote-store, indexing, heap, snapshot, translog, and OOM fixes; match OpenSearch Dashboards and plugins to 3.10. Scope: Upstream OpenSearch 3.10 release. Source: https://github.com/opensearch-project/OpenSearch/releases/tag/3.10.0 (reviewed 2026-11-18).







## OpenSlides

Self-hosted assembly governance for agendas, motions, elections and meeting participation.

- Listing: https://launchinyourcloud.com/directory/openslides/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT open-source license
- Licensing model: open-source
- Installation: Official osmanage utility and Docker Compose
- Architecture: Customer-operated meeting, authentication and voting services
- Operations: Customer operates containers, application data, HTTPS, backups and upgrades.
- Product website: https://openslides.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The official project documents assembly management and a Docker Compose installation. This is a narrower meeting/decision workflow alternative rather than a complete board governance document system. No specific hyperscaler deployment was verified.

The listed self-hosted OpenSlides project is distributed under the MIT license. Hosting/support offerings are separate from the source-code license.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- board-committee-governance: Adjacent formal meeting and assembly governance for agendas, motions, elections and participation. Not a complete board-records retention or board-pack compliance suite. Assess the particular board process and records requirements.

### Deployment boundaries


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


### Cloud deployment evidence

- OpenSlides 4.3 community deployment on Railway (railway): https://railway.com/deploy/openslides
  The community template documents the OpenSlides 4.3 service architecture, including proxy, client, backend roles, authentication, voting, media, realtime components, PostgreSQL and Redis. Adapters provide generated secret files for Railway. Verify every image is pinned to a mutually compatible release and review backups, public endpoints and voting/meeting requirements; this is not vendor-managed hosting.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official functions and license: https://github.com/OpenSlides/OpenSlides

- Official self-hosted installation: https://github.com/OpenSlides/OpenSlides/blob/main/INSTALL.md

### Licensing sources

- https://github.com/OpenSlides/OpenSlides

### Infrastructure sources

- https://github.com/OpenSlides/OpenSlides/blob/main/INSTALL.md


### 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. OpenSlides documents SAML SSO through its authentication service, including provider metadata, certificates and user attributes. Configure the identity provider, account mapping and role/meeting assignment for a compatible service release; this is application-user login rather than only internal service tokens. Scope: OpenSlides 4 SAML authentication service; release-specific setup. Source: https://github.com/OpenSlides/OpenSlides/wiki/SSO (reviewed 2026-11-21). Supporting source: Authentication-service documentation — https://github.com/OpenSlides/openslides-auth-service/blob/main/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream installation instructions use the manage tool to generate Docker Compose deployment files. Configure hostname, secrets, persistence and the matching OpenSlides service versions; review breaking-change instructions before upgrading. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/OpenSlides/OpenSlides/blob/main/INSTALL.md (reviewed 2026-11-14). Deployment artifact: https://github.com/OpenSlides/OpenSlides. Artifact reference: main installation instructions (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The versioned installation manual explains the generated multi-service Compose stack, database, secrets and updates but does not provide numeric production host CPU/RAM/storage requirements. Size simultaneous participants, voting/projectors, database and operational replicas rather than treating a working development stack as capacity evidence. Scope: OpenSlides 4.3.7 production sizing remains unconfirmed. Source: https://github.com/OpenSlides/OpenSlides/blob/4.3.7/INSTALL.md (reviewed 2026-11-21).

- License pricing: Documented. The OpenSlides 4.3.7 repository is MIT licensed. Component/dependency licences and paid hosting, assistance and maintenance agreements remain separate; source availability does not include commercial operational services. Scope: Versioned OpenSlides repository licence. Source: https://github.com/OpenSlides/OpenSlides/blob/4.3.7/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was 4.3.7, published 2026-11-03. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream OpenSlides/OpenSlides release record; commercial editions and deployment packages may differ. Source: https://github.com/OpenSlides/OpenSlides/releases/tag/4.3.7 (reviewed 2026-11-14).







## Paperless-ngx

Community document management with OCR, full-text search, metadata and ingestion workflows.

- Listing: https://launchinyourcloud.com/directory/paperless-ngx/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-3.0; conversion tools and other bundled components have separate licenses.
- Licensing model: open-source
- Installation: Official Docker Compose installer; provider tutorial on Vultr or a community Railway application/database/queue template.
- Architecture: Application, OCR and background worker processes with persistent documents, PostgreSQL and Redis
- Operations: Customer operates application permissions, ingestion, backups, secrets and upgrades. Railway manages its platform resources; a Vultr VM also requires customer OS/container maintenance.
- Product website: https://docs.paperless-ngx.com/
- Source review: 2026-11-17; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

Review used upstream 3.5.0. Pin a current image before importing documents and coordinate database/document backups. The canonical Railway template uses a mutable latest tag; its setup text does not certify production readiness. An older separately reviewed 3.0.5 template predates an AI-permission fix and is not the recommended package. Optional email, document converters and AI integrations need separate access and data-flow review. Release 3.5.0 moves bulk operations to asynchronous processing, adds manual workflow triggers, tightens configuration-view and descendant-tag permissions, clears sessions automatically, and fixes the default MFA trusted-authentication setting. Some installations must adjust PAPERLESS_ALLOWED_HOSTS before upgrading.

The listed community application is GPL-3.0; optional integrations and container dependencies retain their own terms.

Application, OCR and background worker processes with persistent documents, PostgreSQL and Redis. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- document-management: Scans, OCRs, classifies and searches documents with tags, correspondents, metadata and processing workflows. Do not equate personal/team archiving with regulated retention or legal hold.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system (checked 2026-11-13). 

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


### Cloud deployment evidence

- Vultr-hosted Paperless-ngx application deployment guide (vultr): https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system
  Provider documentation installs the application, database, queue and HTTPS reverse proxy on an operator-controlled Linux server. Pin compatible current images, protect persistent document/database paths and manage VM updates. This establishes hosting guidance, not upstream vendor support.
  Source type: provider-guide; reviewed: 2026-11-13; vendor support: not-assessed.

- Community Railway Paperless-ngx stack (railway): https://railway.com/deploy/paperless-ngx
  The template provisions the application with PostgreSQL, Redis and a persistent volume in the customer project. Railway operates the platform. Pin and verify a current patched application image and volume paths against upstream instructions; the template documentation is not a tested deployment guarantee.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The community maintains repeated releases, a public security-advisory process, and substantial contributions from multiple maintainers. The reviewed 3.5.0 release adds workflow improvements and permission, session, and MFA fixes from distinct contributors; admission does not depend on popularity counts.

Reviewed 2026-11-17.

- Reviewed 3.5.0 release and upgrade note: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0

- Contributor history: https://github.com/paperless-ngx/paperless-ngx/graphs/contributors

### Sources

- Upstream Compose installation and project scope: https://github.com/paperless-ngx/paperless-ngx

- Vultr Docker Compose deployment with PostgreSQL and TLS: https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system

- AI workflow advisory; use current patched releases: https://github.com/paperless-ngx/paperless-ngx/security/advisories/GHSA-c8f3-pqr2-rr24

- Community Railway Paperless-ngx stack: https://railway.com/deploy/paperless-ngx

- Upstream license: https://github.com/paperless-ngx/paperless-ngx/blob/main/LICENSE

- Reviewed 3.5.0 release and upgrade note: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0

- Contributor history: https://github.com/paperless-ngx/paperless-ngx/graphs/contributors

### Licensing sources

- https://github.com/paperless-ngx/paperless-ngx/blob/main/LICENSE

### Infrastructure sources

- https://github.com/paperless-ngx/paperless-ngx

- https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system

- https://railway.com/deploy/paperless-ngx


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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. OIDC sign-in is documented through django-allauth providers. Configure the provider application and PAPERLESS_SOCIALACCOUNT_PROVIDERS; group mapping and trusted-proxy settings require separate review. Scope: Upstream self-hosted authentication configuration. Source: https://raw.githubusercontent.com/paperless-ngx/paperless-ngx/main/docs/configuration.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 upstream PostgreSQL Compose example records required environment files, persistent data/import/export storage and application services. Review the matching release and credentials before deploying. Scope: Upstream PostgreSQL-backed recipe; different provider templates may package other releases. Source: https://github.com/paperless-ngx/paperless-ngx/blob/main/docker/compose/docker-compose.postgres.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/paperless-ngx/paperless-ngx/blob/main/docker/compose/docker-compose.postgres.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. Vultr's deployment example requires at least 2 CPU cores and 4 GB RAM for its application, PostgreSQL, Redis and reverse-proxy stack. It uses an older application image; this provider example is not an upstream HA minimum or a sizing guarantee for the current release. Scope: Provider-authored single-server recipe; version and workload qualification required. Source: https://docs.vultr.com/how-to-deploy-paperless-ngx-open-source-document-management-system (reviewed 2026-11-20).

- License pricing: Documented. The upstream core uses GPL-3.0. This records source-code licensing, not an infrastructure, support or managed-hosting price. Bundled conversion tools have their own terms. Scope: Upstream Paperless-ngx core licence. Source: https://raw.githubusercontent.com/paperless-ngx/paperless-ngx/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Paperless-ngx permissions and MFA defaults review (security-advisory): Release 3.5.0 fixes configuration/tag permissions and the default trusted-authentication behavior for MFA, and adds session cleanup. Scope: Upstream Paperless-ngx 3.5.0 release fixes; no CVE or complete affected-version range is established by this release record. Conditions: Authentication mode, tag inheritance and configuration permissions determine applicability. Provider templates may use different image tags. Action: Pin the selected image, back up documents and the database, review PAPERLESS_ALLOWED_HOSTS and verify permissions and MFA configuration after upgrading. Source: https://github.com/paperless-ngx/paperless-ngx/releases/tag/v3.5.0; reviewed 2026-11-17.




## Papra Self-Hosted

Lightweight document archive with text extraction, organization sharing, tagging and search.

- Listing: https://launchinyourcloud.com/directory/papra/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0; dependencies and independently maintained packaging retain their own terms.
- Licensing model: open-source
- Installation: Upstream Docker/Compose installation or a community Railway template with persistent database storage and a document bucket.
- Architecture: Persistent application container with SQLite/libSQL metadata and local or object document storage
- Operations: Customer manages application access, secrets, storage, backups and updates. Railway operates its underlying platform; the community template runs in the customer project.
- Product website: https://papra.app/
- Source review: 2026-11-13; cloud review: 2026-11-13; licensing review: 2026-11-13; infrastructure review: 2026-11-13

### Scope and qualifications

The reviewed application release is 26.7.1; Papra fixes only the latest version. Pin a current image and preserve database, documents and encryption keys together. The Railway wrapper adds initial-account setup and storage permissions; Mailpit captures mail until a real relay is configured. Optional OCR/model services, intake email and webhooks can send content outside the installation.

The self-hosted Papra application is AGPL-3.0. Hosted Papra service terms are separate; a chart or wrapper license does not replace application terms.

Persistent application container with SQLite/libSQL metadata and local or object document storage. The application uses persistent processes; managed cloud infrastructure does not remove its state, backup or upgrade requirements.


### Category fit

- document-management: Stores documents with extracted text, tags, custom properties, organization access and full-text retrieval. This is a lightweight archive, not a formal records-retention or legal-hold system.

### Deployment boundaries


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


### Cloud deployment evidence

- Community Papra application deployment in a Railway project (railway): https://railway.com/deploy/papra-dms
  Deploys the application, persistent metadata volume, document bucket and mail-capture service into the customer Railway project. This is independent packaging, not upstream support certification. Review the wrapper and pin a current application image; retain storage/encryption secrets and configure a production mail relay.
  Source type: community-template; reviewed: 2026-11-13; vendor support: not-assessed.


### Community and maintenance

The upstream changelog records continuing application releases and fixes, including 26.7.1, and contributions from external participants. The contributor history and community packaging provide participation signals beyond star counts; this does not establish enterprise support or production suitability for every workload.

Reviewed 2026-11-13.

- Application changelog and external contributions: https://docs.papra.app/changelog/

- Upstream contributor history: https://github.com/papra-hq/papra/graphs/contributors

### Sources

- Official Docker installation and persistence: https://docs.papra.app/self-hosting/using-docker/

- Application configuration: https://docs.papra.app/self-hosting/configuration/

- Internal and external content extraction: https://docs.papra.app/guides/content-extraction/

- Railway wrapper source and initialization: https://github.com/gridalpha/papra-railway

- Community Papra application deployment in a Railway project: https://railway.com/deploy/papra-dms

- Upstream application license: https://github.com/papra-hq/papra/blob/main/LICENSE

- Application changelog and external contributions: https://docs.papra.app/changelog/

- Upstream contributor history: https://github.com/papra-hq/papra/graphs/contributors

### Licensing sources

- https://github.com/papra-hq/papra/blob/main/LICENSE

### Infrastructure sources

- https://docs.papra.app/self-hosting/using-docker/

- https://railway.com/deploy/papra-dms


### 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 self-hosted configuration supports GitHub and Google OAuth sign-in and a configurable list of custom OAuth providers through Better Auth. This establishes external sign-in, not SAML support or enterprise provisioning; configure the chosen provider and registration policy. Scope: Self-hosted OAuth provider configuration. Source: https://docs.papra.app/self-hosting/configuration/ (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 Docker guide identifies ghcr.io/papra-hq/papra, recommends the rootless variant and documents persistent database/document storage and AUTH_SECRET. The default latest tag moves. Scope: Upstream Papra application image; not the separate CLI package release. Source: https://docs.papra.app/self-hosting/using-docker/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The official Docker guide documents persistent application data and optional extraction components but does not give a validated CPU/RAM minimum. Size document storage, extraction concurrency and any external models separately; a one-container command is not HA sizing. Scope: Self-hosted Docker distribution; numeric production sizing unresolved. Source: https://docs.papra.app/self-hosting/using-docker/ (reviewed 2026-11-20).

- License pricing: Documented. The upstream project is licensed under AGPL-3.0. This records the source licence; it does not price infrastructure, hosted service, optional model providers or support. Scope: Papra upstream core source licence. Source: https://raw.githubusercontent.com/papra-hq/papra/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Parseable OSS

Self-hosted telemetry data lake for querying logs, metrics and traces stored in columnar files.

- Listing: https://launchinyourcloud.com/directory/parseable-oss/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 for the OSS project. Standalone and distributed OSS deployment guides are available; Enterprise software/support has separate terms.
- Licensing model: open-source
- Installation: Install OSS with Helm in standalone or distributed mode on the documented AWS path, or use the Railway standalone template. Pin application/chart versions and review the migration requirements for older charts.
- Architecture: Customer-operated standalone server or separate OSS ingestor/querier workloads use local staging and durable object storage for Parquet telemetry.
- Operations: The customer manages credentials, data ingestion, persistent staging, object storage, access configuration, retention, backups and upgrades.
- Product website: https://www.parseable.com/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

The standalone example is a single pod; distributed OSS has a separate vendor guide and is not automatically an HA guarantee. Chart 3.2.4 defaults to application v3.2.3, whereas the reviewed upstream release is v3.2.7. Existing standalone charts through 3.0.2 need a new 3.1.0+ installation and verified data migration. Railway uses a moving edge image, paid Buckets and a persistent staging volume. Disable optional usage statistics with P_SEND_ANONYMOUS_USAGE_DATA=false when required; this alone does not establish air-gapped operation.

AGPL-3.0 applies to the reviewed OSS release. Official guides cover both standalone and distributed OSS; Enterprise entitlements remain separate.

Standalone or distributed OSS runs in customer-operated persistent containers/Kubernetes workloads, with durable object storage and staging configured independently.


### Category fit

- observability: The application ingests and queries operational telemetry and provides dashboards and alerting.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks (checked 2026-11-20). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/railway (checked 2026-11-20). 


### Cloud deployment evidence

- Parseable OSS on Amazon EKS (aws): https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks
  The vendor documents EKS application hosting and IAM roles for the S3-backed installation. Pair the provider-specific settings with the standalone OSS Helm guide.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Parseable OSS on Railway (railway): https://www.parseable.com/docs/self-hosted/installation/standalone/railway
  The upstream template runs the application in the customer's Railway project with a Railway Bucket for durable objects and a persistent volume for staged events.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Community and maintenance

The upstream project has sustained public contributor history (including nikhilsinhaparseable, nitisht, trueleo) and a reviewed dated v3.2.7 release. This establishes maintenance/community participation rather than a production suitability, support or capacity guarantee.

Reviewed 2026-11-20.

- Public contributor history: https://github.com/parseablehq/parseable/graphs/contributors

- Reviewed dated upstream release: https://github.com/parseablehq/parseable/releases/tag/v3.2.7

### Sources

- Parseable OSS source and AGPL-3.0 license: https://github.com/parseablehq/parseable

- Standalone OSS Helm installation: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

- AWS deployment overview: https://www.parseable.com/docs/self-hosted/aws

- Upstream Parseable releases: https://github.com/parseablehq/parseable/releases

- Usage statistics and opt-out: https://www.parseable.com/docs/self-hosted/telemetry

- Parseable OSS on Amazon EKS: https://www.parseable.com/docs/self-hosted/installation/standalone/aws-eks

- Parseable OSS on Railway: https://www.parseable.com/docs/self-hosted/installation/standalone/railway

- Distributed OSS configuration: https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss

- Official Railway template: https://railway.com/deploy/parseable-1

- Buyer evidence: sso: https://www.parseable.com/docs/user-guide/openid

- Explicit OSS feature inclusion: https://www.parseable.com/pricing

- Buyer evidence: securityControls: https://www.parseable.com/docs/user-guide/rbac

- Runtime configuration and telemetry: https://www.parseable.com/docs/self-hosted/configuration

- Buyer evidence: licensePricing: https://github.com/parseablehq/parseable/blob/v3.2.7/LICENSE

- Buyer evidence: release: https://github.com/parseablehq/parseable/releases/tag/v3.2.7

- Public contributor history: https://github.com/parseablehq/parseable/graphs/contributors

### Licensing sources

- https://github.com/parseablehq/parseable

- https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

### Infrastructure sources

- https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss

- https://www.parseable.com/docs/self-hosted/installation/standalone/railway


### 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. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Single sign-on: Documented. Parseable OSS supports OIDC sign-in. Configure the issuer, client credentials, redirect URI and OIDC environment for the selected standalone/distributed mode; Parseable roles still control authorization after login. This does not establish SCIM provisioning. Scope: Configured OSS OIDC login; enterprise support and SCIM are separate. Source: https://www.parseable.com/docs/user-guide/openid (reviewed 2026-11-20). Supporting source: Explicit OSS feature inclusion — https://www.parseable.com/pricing.

- SCIM provisioning: Sources checked — unresolved. The reviewed sources do not establish a SCIM endpoint and supported user/group lifecycle for this edition. SSO and just-in-time account creation are not SCIM evidence. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Security controls: Documented. OSS documentation provides OIDC authentication, role/privilege controls and API keys. Apply object-store least privilege and protect ingestion/query endpoints. The Railway template uses a moving edge image and a generated admin password when one is not supplied; pin and review the deployed version. Usage-statistics opt-out is separate from identity, storage and optional external integrations. Scope: Configured OSS access controls and deployment credentials. Source: https://www.parseable.com/docs/user-guide/rbac (reviewed 2026-11-20). Supporting source: OSS OIDC configuration — https://www.parseable.com/docs/user-guide/openid. Supporting source: Railway admin credentials and moving image — https://www.parseable.com/docs/self-hosted/installation/standalone/railway. Supporting source: Runtime configuration and telemetry — https://www.parseable.com/docs/self-hosted/configuration.

- Air-gapped operation: Sources checked — unresolved. The reviewed sources do not establish a complete disconnected installation, update and licensing workflow. A telemetry opt-out alone does not establish air-gapped support; review registry, package, identity and optional external-service dependencies. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected Parseable chart 3.2.4 supports OSS standalone and distributed values; its default appVersion is v3.2.3, separate from the reviewed v3.2.7 upstream release. Override an image only after compatibility checks. Standalone chart 3.0.2 or older requires a separate 3.1.0+ installation, verified data migration and traffic cutover rather than an in-place upgrade. The Railway template uses a moving edge image. Scope: Versioned OSS Helm artifact and explicitly moving Railway template. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss (reviewed 2026-11-20). Deployment artifact: https://charts.parseable.com/helm-releases/parseable-3.2.4.tgz. Artifact reference: parseable chart 3.2.4; default appVersion v3.2.3; sha256:02e96d14ca94b55cacb8d30964ee42bf58b3c3add4ecaf571838463c95d8cbdf. Supporting source: Distributed OSS configuration — https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss. Supporting source: Official Railway template — https://railway.com/deploy/parseable-1. Supporting source: Railway image/storage details — https://www.parseable.com/docs/self-hosted/installation/standalone/railway.

- Minimum footprint / sizing: Documented. The standalone OSS example requests 250m CPU/1 GiB and limits 500m CPU/4 GiB for the application, with example 5 GiB staging/data volumes depending on storage mode. The distributed example separates ingestors and queriers. These are example requests, not HA throughput minima; object storage, replicated infrastructure and workload capacity are additional. Scope: Vendor example application resources; excludes production HA/database and object-storage sizing. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss (reviewed 2026-11-20). Supporting source: Distributed OSS topology — https://www.parseable.com/docs/self-hosted/installation/distributed/k8s-helm-oss.

- License pricing: Documented. Parseable OSS v3.2.7 uses AGPL-3.0, and the pricing page lists the OSS software tier at $0. Enterprise licensing/support and the customer’s infrastructure and operating labor are separate. Scope: Versioned upstream OSS licence and software-price tier. Source: https://github.com/parseablehq/parseable/blob/v3.2.7/LICENSE (reviewed 2026-11-20). Supporting source: OSS pricing and OIDC inclusion — https://www.parseable.com/pricing.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Parseable OSS: reviewed customer-cloud deployment. Source: https://github.com/parseablehq/parseable (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed upstream Parseable OSS snapshot is v3.2.7, published November 17, 2026. Helm chart 3.2.4 defaults to the older v3.2.3 application image, while the Railway template uses edge. Treat application, chart and template versions separately. Scope: Upstream OSS application; packaging defaults and moving templates may lag or differ. Source: https://github.com/parseablehq/parseable/releases/tag/v3.2.7 (reviewed 2026-11-20).




### Security and lifecycle reviews

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

- Parseable standalone chart migration boundary (lifecycle): Standalone installations using chart 3.0.2 or earlier require a separate 3.1.0+ installation and data migration; the vendor warns against a direct chart upgrade. Scope: Existing OSS standalone installations through chart 3.0.2; new installations are not affected by this transition. Conditions: The guide also distinguishes PVC/temporary staging choices and immutable StatefulSet volume templates. Action: Create a separate target installation, migrate and verify data, and switch traffic after verification. Follow storage expansion/migration instructions for the selected backend. Source: https://www.parseable.com/docs/self-hosted/installation/standalone/k8s-oss; reviewed 2026-11-20.




## Penpot

Self-hosted collaborative interface design and prototyping platform.

- Listing: https://launchinyourcloud.com/directory/penpot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, 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: Application platform deployment
- Architecture: Penpot frontend, backend, exporter, PostgreSQL, cache and object storage.
- 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://penpot.app
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.

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

Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted collaborative interface design and prototyping platform.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform (checked 2026-11-19). 

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


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform
  Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/penpot
  Penpot frontend, backend, exporter, PostgreSQL, cache and object storage. Design data, object storage, exports and database must be backed up together; externally configured integrations remain outside the server.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes niwinz, Alotor, superalex, 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/penpot/penpot/graphs/contributors

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

### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform

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

- MPL-2.0 LICENSE: https://github.com/penpot/penpot/blob/develop/LICENSE

- Releases v2.19.3: https://github.com/penpot/penpot/releases

### Licensing sources

- https://github.com/penpot/penpot/blob/develop/LICENSE

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-penpot-open-source-design-and-prototyping-platform

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 self-hosted configuration guide documents generic OIDC and named OAuth providers. Configure the backend credentials, enabled-login flags and callback URL; LDAP and the application admin surface are separate considerations. Scope: Penpot self-hosted application-user identity configuration. Source: https://help.penpot.app/technical-guide/configuration/ (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 self-hosting guide supplies a Compose file with frontend, backend, exporter, PostgreSQL and persistent assets. Replace the example master secret/database credentials and pin compatible images. A single PostgreSQL container is not database HA. Scope: Upstream Penpot Compose deployment; verify compatibility with the selected provider package. Source: https://help.penpot.app/technical-guide/getting-started/docker/ (reviewed 2026-11-20). Deployment artifact: https://raw.githubusercontent.com/penpot/penpot/develop/docker/images/docker-compose.yaml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Documented. The upstream settings guide describes 4 CPUs/16 GB RAM as a reference and recommends an elastic 50–100 GB database starting point for up to ten editors, with growth driven by files and usage. These are vendor guidelines, not a validated 100-user/1-TB HA configuration; add database/asset backups and replicas separately. Scope: Upstream reference settings and elastic database guidance; not a guaranteed capacity benchmark. Source: https://help.penpot.app/technical-guide/getting-started/recommended-settings/ (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## Plausible Community Edition

Website analytics tracker and dashboard available as a self-hosted Community Edition.

- Listing: https://launchinyourcloud.com/directory/plausible-ce/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPLv3 for Plausible Community Edition. Commercial/cloud-only features and branding have separate terms.
- Licensing model: open-source
- Installation: Use the official Community Edition Docker Compose repository and configure the application, PostgreSQL and ClickHouse services.
- Architecture: Customer-operated analytics application, tracker endpoint and persistent analytics databases
- Operations: Customer manages tracker delivery, ingestion, databases, email configuration, TLS, backups and CE upgrades.
- Product website: https://plausible.io/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Use the CE feature list when evaluating functionality; managed-service funnels, revenue metrics, SSO and other features are not automatically available in the self-hosted edition. Plausible Community Edition v3.2.1 removes the /storybook endpoint after CVE-2026-8467 showed it could permit remote code execution when exposed to an untrusted network. Upgrade affected v3.0–v3.2 deployments to v3.2.1 or later; until upgraded, block /storybook at the reverse proxy or equivalent network layer.

AGPLv3 for Plausible Community Edition. Commercial/cloud-only features and branding have separate terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated analytics application, tracker endpoint and persistent analytics databases. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website traffic, referral and event analytics using the self-hosted Community Edition tracker and dashboard; some commercial cloud features are excluded.

### Deployment boundaries


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


### Cloud deployment evidence

- Plausible Community Edition deployment on Railway (railway): https://railway.com/deploy/plausible--plausible-community-edition
  This community template deploys the Plausible Community Edition image with PostgreSQL, ClickHouse and a mail service in a customer project. ClickHouse uses community configuration packaging. Review image versions, storage and outbound email, and create the initial owner promptly; this is distinct from paid Plausible Analytics hosting.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official contribution documentation credits community work on the tracker, integrations and self-hosting. The upstream release stream includes ongoing Community Edition maintenance.

Reviewed 2026-11-10.

- Documented community contributions: https://plausible.io/docs/contribute

- Community Edition release maintenance: https://github.com/plausible/analytics/releases

### Sources

- Official installation and runtime: https://github.com/plausible/community-edition

- Upstream project and capabilities: https://github.com/plausible/analytics

- Current upstream license: https://raw.githubusercontent.com/plausible/analytics/master/LICENSE.md

- Current self-hosted edition scope: https://plausible.io/self-hosted-web-analytics

- Plausible CE v3.2.1 remote-code-execution fix: https://github.com/plausible/analytics/releases/tag/v3.2.1

### Licensing sources

- https://raw.githubusercontent.com/plausible/analytics/master/LICENSE.md

### Infrastructure sources

- https://github.com/plausible/community-edition


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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: Explicitly unsupported. The vendor explicitly excludes SSO from Community Edition. SSO in the managed Cloud feature set does not establish that the AGPL self-hosted CE distribution includes it. Scope: Plausible Community Edition versus managed Cloud feature comparison. Source: https://plausible.io/self-hosted-web-analytics (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 versioned CE recipe supplies a Compose stack for Plausible, PostgreSQL and ClickHouse. Configure the base URL and unique secret, persistent storage and either automatic TLS or your reverse proxy; follow the matching release upgrade instructions. Scope: Versioned Community Edition v3.2.1 deployment stack. Source: https://github.com/plausible/community-edition/blob/v3.2.1/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/plausible/community-edition/blob/v3.2.1/compose.yml. Artifact reference: v3.2.1.

- Minimum footprint / sizing: Documented. The reviewed Community Edition recipe recommends at least 2 GB RAM and a CPU supporting SSE 4.2 or NEON for its analytics/database stack. Size retention and traffic separately. Scope: Versioned Community Edition v3.2.1 deployment recipe. Source: https://github.com/plausible/community-edition/blob/v3.2.1/README.md (reviewed 2026-11-14).

- License pricing: Documented. Community Edition is free to self-host under AGPLv3; operators pay for hosting and maintenance. Cloud subscription features and services are separate, and the vendor excludes SSO and several premium features from CE. Review AGPL obligations for modifications and redistribution. Scope: Community Edition software terms, excluding cloud charges and managed Cloud subscriptions. Source: https://plausible.io/self-hosted-web-analytics (reviewed 2026-11-20). Supporting source: Published v3.2.1 application licence — https://github.com/plausible/analytics/blob/v3.2.1/LICENSE.md.

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Plausible CE storybook code-execution advisory (security-advisory): CVE-2026-8467 concerns the exposed /storybook endpoint; the 3.2.1 CE patch removes it. Scope: Plausible Community Edition v3.0–v3.2 image tags, including the prerelease aliases enumerated by the vendor; fixed in v3.2.1. Conditions: The endpoint must be reachable from a public or other untrusted network. This is a review of an existing disclosure, not a new vulnerability announcement. Action: Upgrade affected CE installations to v3.2.1 or later. Until then, block /storybook at the reverse proxy or an equivalent boundary. Source: https://github.com/plausible/analytics/releases/tag/v3.2.1; reviewed 2026-11-17.




## RAGFlow

Document processing and retrieval platform for building RAG and agentic knowledge applications.

- Listing: https://launchinyourcloud.com/directory/ragflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, alibaba, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms.
- Licensing model: open-source
- Installation: Versioned upstream Docker Compose, provider-specific VM packages or community deployment templates; select a path compatible with the intended RAGFlow release.
- Architecture: Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services
- Operations: Customer manages document storage, indexing, app services, access controls, model endpoints, backups and upgrades.
- Product website: https://ragflow.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Deployment options include customer AWS, Azure and Google Cloud infrastructure, Alibaba Compute Nest, and a Railway project. The evidence trail identifies the publishers and template versions. Hosting RAGFlow does not automatically self-host its LLM, embeddings or reranker; choose private or local model endpoints where required.

Apache License 2.0 for upstream RAGFlow; models, data assets and dependencies retain their own terms. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated document/retrieval application with deployment-specific stateful storage and configured model services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- ai-applications-rag: Document understanding, knowledge ingestion and retrieval-augmented/agentic question answering with configurable LLM, embedding and reranking endpoints.

- ai-tools: Self-hosted document ingestion, retrieval and context infrastructure for AI applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html (checked 2026-11-12). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/ragflow-ai (checked 2026-11-12). Source: https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Community RAGFlow deployment on AWS ECS Fargate through stdapi.ai (aws): https://github.com/stdapi-ai/samples/tree/main/getting_started_ragflow
  The sample provisions the RAGFlow application and workers, OpenSearch, Aurora PostgreSQL, Valkey, S3 and a Bedrock gateway in the customer AWS account. Source inspection confirms the v0.26.4 Python image pin; it does not establish compatibility with the 1.0 Go rewrite. This community integration also requires the separately billed stdapi.ai gateway and Bedrock access. Review its documented networking, client-security, availability and cost limitations before use.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- cloudimg RAGFlow Azure VM deployment and operations guide (azure): https://www.cloudimg.co.uk/guides/ragflow-on-ubuntu-24-04-azure/
  The image publisher documents an Azure VM in the customer subscription running the complete Compose stack, including Elasticsearch, MySQL, MinIO, Redis and a local embedding service. Its guide pins RAGFlow v0.26.4, not 1.0. This is a third-party repackaged image with additional support charges, not an upstream-endorsed distribution. Confirm image access, current patch/migration requirements, TLS configuration and the separately configured chat-model endpoint.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.26.4.

- Techlatest RAGFlow VM deployment in a customer Google Cloud project (gcp): https://www.techlatest.net/support/ragflow_support/gcp_gettingstartedguide/index.html
  The image publisher documents selecting the customer project, deployment service account, zone, network and Compute Engine VM, then completing RAGFlow initialization and configuring its bundled Ollama models. This is a third-party packaged deployment; the guide does not establish a specific current RAGFlow release or 1.0 compatibility. Confirm the image version, support charges, model licenses, resource sizing and network exposure before use.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- RAGFlow Community deployment on Alibaba Cloud Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/ragflow-community-edition-service-instance-deployment-document
  Alibaba Cloud documents provisioning a RAGFlow Community service instance with customer ECS, VPC and vSwitch parameters. This is distinct from the managed AI-Native Database Service integration. Review image version, access controls, model endpoints and the broad example RAM permissions before production.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted.

- Community RAGFlow Railway application stack (railway): https://railway.com/deploy/ragflow-ai
  This community template deploys the application, Elasticsearch, MySQL, Redis, a local embedding service and object storage into the customer Railway project. Its linked Dockerfile pins upstream RAGFlow v0.27.1 with a Railway startup/configuration wrapper. The template is not proof of 1.0 compatibility or upstream support; review migrations and the separately configured chat-model endpoint. Railway manages the underlying infrastructure.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.

- Railway deployment image source and release pin (railway): https://github.com/gridalpha/ragflow-railway/blob/main/Dockerfile
  Source inspection confirms the v0.27.1 base image and the custom configuration, nginx and startup wrapper used by the linked Railway template. The upstream 1.0 release changes the architecture and requires its documented migration path; do not substitute a new image tag without reviewing the complete stack.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed. Edition: Community / upstream open-source; third-party distribution where noted. Versions: 0.27.1.


### Community and maintenance

Current release notes document continued 2026 releases and dozens of named contributors across successive versions; the upstream README records a 1.0.0 release on 6 November 2026.

Reviewed 2026-11-10.

- Current releases and contributors: https://github.com/infiniflow/ragflow/releases

- Release chronology and deployment instructions: https://raw.githubusercontent.com/infiniflow/ragflow/main/README.md

### Sources

- Upstream project and capabilities: https://github.com/infiniflow/ragflow

- Current upstream license: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

- RAGFlow 1.0 release and migration requirements: https://ragflow.io/docs/v1.0.0/release_notes

### Licensing sources

- https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE

### Infrastructure sources

- https://github.com/infiniflow/ragflow


### 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: Sources checked — unresolved. A vendor maintainer identifies OAuth2/OIDC SSO in Enterprise, while the reviewed v1.0.0 Go deployment reference does not establish a supported federation configuration for that OSS release. Older OAuth configuration examples must not be assumed compatible with the new backend. Confirm edition, release and identity-provider configuration. Scope: RAGFlow v1.0 Go OSS versus Enterprise federation; current entitlement/configuration unresolved. Source: https://raw.githubusercontent.com/infiniflow/ragflow/v1.0.0/docker/README.md (reviewed 2026-11-20). Supporting source: Vendor-maintainer Enterprise SSO statement — https://github.com/infiniflow/ragflow/issues/15882.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v1.0.0 Compose file includes a separate dependency configuration and reads its image selection from the release environment. Use the matching release configuration; this artifact does not establish a migration path or compatibility for older provider packages. Scope: Upstream v1.0.0 Compose; not evidence of compatibility with the listed 0.x provider packages. Source: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/infiniflow/ragflow/blob/v1.0.0/docker/docker-compose.yml. Artifact reference: v1.0.0. Supporting source: Versioned RAGFlow 1.0.0 quickstart — https://ragflow.io/docs/v1.0.0/.

- Minimum footprint / sizing: Documented. The 1.0 quickstart recommends a starting point of 4 CPU cores, 16 GB RAM and 50 GB free disk. Models, document engines and concurrency can require more; this does not size the older third-party cloud packages. Scope: Upstream 1.0 quickstart; provider packages may target 0.x. Source: https://ragflow.io/docs/v1.0.0/ (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Model weights and external model APIs require their own review. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/infiniflow/ragflow/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.0.0, published 2026-11-06. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream infiniflow/ragflow release record; commercial editions and deployment packages may differ. Source: https://github.com/infiniflow/ragflow/releases/tag/v1.0.0 (reviewed 2026-11-14).







## Rallly

Self-hosted group scheduling polls and meeting coordination.

- Listing: https://launchinyourcloud.com/directory/rallly/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock, 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: Cloudron package; Application platform deployment
- Architecture: Rallly application, PostgreSQL, persistent storage and outbound email.
- 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://rallly.co
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.

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

Rallly application, PostgreSQL, persistent storage and outbound email. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- collaboration: Self-hosted group scheduling polls and meeting coordination.

### Deployment boundaries


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

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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/rallly.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/rallly
  Rallly application, PostgreSQL, persistent storage and outbound email. Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery. 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 lukevella, snyk-bot, jonas-hoebenreich, 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/lukevella/rallly/graphs/contributors

- Upstream project: https://github.com/lukevella/rallly

### Sources

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

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

- AGPL-3.0 LICENSE: https://github.com/lukevella/rallly/blob/main/LICENSE

- Releases v4.17.1: https://github.com/lukevella/rallly/releases

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

### Licensing sources

- https://github.com/lukevella/rallly/blob/main/LICENSE

### Infrastructure sources

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

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 self-hosting guide documents Google, Microsoft Entra ID and generic OIDC login from v3.4 onward. Configure callback URLs, verified email claims and linking policy; multi-user licence entitlements are a separate consideration. Scope: Rallly self-hosted user identity; review the selected v4 deployment and license. Source: https://support.rallly.co/self-hosting/single-sign-on (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 installer provisions a Compose stack, generates secrets and supports external database, object storage and reverse-proxy settings. Review the downloaded script before execution, pin compatible images and plan backups; this is not a production HA template. Scope: Current official self-hosting stack and installer. Source: https://support.rallly.co/self-hosting/installation/docker (reviewed 2026-11-20). Deployment artifact: https://get.rallly.co. Artifact reference: Moving official installer; inspect and pin the selected application/stack release.

- Minimum footprint / sizing: Documented. The Cloudron package declares 2048MB 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/rallly.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

- License pricing: Documented. The current self-hosting guide states free personal use and asks multi-user installations to purchase a licence key. It lists Plus at $49, Organization at $499 and Enterprise from $999; keys cover Rallly v4.x with tier/user/space limits. Activation requires the licensing service. These runtime-plan terms add detail beyond the repository’s AGPL notice. Scope: Published Rallly v4 self-hosting licence-key tiers; confirm applicable user/space allocation and quote. Source: https://support.rallly.co/self-hosting/licensing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

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







## Safebucket

Open-source on-premises file-sharing software with a community Railway deployment.

- Listing: https://launchinyourcloud.com/directory/safebucket/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Safebucket application, PostgreSQL and MinIO-backed object storage.
- 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://docs.safebucket.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The template follows moving images. Activity and notifier defaults can use ephemeral filesystem storage; configure durable activity logging and outbound notification services before relying on audit records or external-sharing workflows.

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

Safebucket application, PostgreSQL and MinIO-backed object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Open-source on-premises file-sharing software with a community Railway deployment.

- data-rooms-ma-document-management: Open-source on-premises file-sharing software with a community Railway deployment.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway Template (railway): https://railway.com/deploy/safebucket
  Safebucket application, PostgreSQL and MinIO-backed object storage. The template follows moving images. Activity and notifier defaults can use ephemeral filesystem storage; configure durable activity logging and outbound notification services before relying on audit records or external-sharing workflows.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes yohanleb, Renizmy, pedorich-n, 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/safebucket/safebucket/graphs/contributors

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

### Sources

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

- GitHub README: https://github.com/safebucket/safebucket

- Apache-2.0 LICENSE: https://github.com/safebucket/safebucket/blob/main/LICENSE

- GitHub Releases: https://github.com/safebucket/safebucket/releases

### Licensing sources

- https://github.com/safebucket/safebucket/blob/main/LICENSE

### Infrastructure sources

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


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 official README documents user SSO through an external OpenID Connect provider, with local accounts for external users. Provider, redirect/origin and role settings must be configured for the installed release; this is not a SAML or SCIM support claim. Scope: Safebucket v0.8.1 upstream user authentication; match the selected provider package and OIDC configuration. Source: https://github.com/safebucket/safebucket/blob/v0.8.1/README.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 official full-stack local recipe publishes Compose definitions for Safebucket, PostgreSQL, RustFS, Valkey, NATS, Loki and Mailpit. It is a production-like local environment with sample credentials and test email, so production secrets, storage, email, HTTPS and resilience require separate configuration. Scope: Safebucket complete local stack; distinguish the full recipe from the lighter deployment and a production HA design. Source: https://docs.safebucket.io/getting-started/local-full-deployment (reviewed 2026-11-20). Deployment artifact: https://github.com/safebucket/safebucket/blob/main/deployments/local/full/docker-compose.yml. Artifact reference: main (moving branch); match the selected application release.

- Minimum footprint / sizing: Documented. The full local Compose guide asks for at least 1 GB RAM available to its containers. This is a local-startup allowance, not a whole-host production or HA minimum; database, object storage, caching, events, logs, files and backup growth need separate workload sizing. Scope: Safebucket production-like local recipe; no validated 100-user, 1 TB or redundant topology is established. Source: https://docs.safebucket.io/getting-started/local-full-deployment (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## SendPortal

Self-hosted email marketing, subscriber and campaign management.

- Listing: https://launchinyourcloud.com/directory/sendportal/
- 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: Laravel application, PostgreSQL, Redis, queues and scheduler 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://sendportal.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

An external approved sending provider is required for real delivery; provider free credits are not a durable operating-cost estimate.

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

Laravel application, PostgreSQL, Redis, queues and scheduler on Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted email marketing, subscriber and campaign management.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/sendportal
  Laravel application, PostgreSQL, Redis, queues and scheduler on Railway. An external approved sending provider is required for real delivery; provider free credits are not a durable operating-cost estimate.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes JonoB, dljfield, mauricius, 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/mettle/sendportal/graphs/contributors

- Upstream project: https://github.com/mettle/sendportal

### Sources

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

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/mettle/sendportal/master/LICENSE

- GitHub Releases: https://github.com/mettle/sendportal/releases

### Licensing sources

- https://raw.githubusercontent.com/mettle/sendportal/master/LICENSE

### Infrastructure sources

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


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The v4.0.0.1 standalone application configures a local session guard and API-token guard. The vendor also permits embedding SendPortal in another Laravel application, but that does not establish a supported SAML/OIDC integration for the standalone product or provider template. Confirm the actual authentication package, callback and user/workspace mapping. Scope: Published standalone authentication versus an integration/customization possibility. Source: https://github.com/mettle/sendportal/blob/v4.0.0.1/config/auth.php (reviewed 2026-11-20). Supporting source: Embedding as a Laravel package — https://sendportal.io/docs/v4/getting-started/package-installation.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v4 guide installs the standalone application from its release branch, runs Composer, then configures its web server and application settings. Embedding it as a Laravel package is a separate path. Pin the v4.0.0.1 application and compatible runtime/dependencies, then configure database, email services, secrets, scheduled tasks and TLS. Scope: Versioned standalone installation; not a complete preconfigured provider image. Source: https://sendportal.io/docs/v4/getting-started/installation (reviewed 2026-11-20). Deployment artifact: https://github.com/mettle/sendportal/tree/v4.0.0.1. Artifact reference: v4.0.0.1.

- Minimum footprint / sizing: Sources checked — unresolved. The v4 installation guide lists PHP, Composer, web-server and database requirements but no numeric whole-stack CPU/RAM/storage minimum. Size campaigns, subscriber volume, queues, delivery rate, retention and redundancy; PHP compatibility and an application package do not establish a 1 TB HA deployment footprint. Scope: Versioned runtime requirements; complete production sizing remains unconfirmed. Source: https://sendportal.io/docs/v4/getting-started/installation (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## SuiteCRM Self-Hosted

Open-source, customer-operated CRM with marketing campaigns and configurable record workflows.

- Listing: https://launchinyourcloud.com/directory/suitecrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 application; separately selected extensions and services have their own terms
- Licensing model: open-source
- Installation: Official prebuilt SuiteCRM 8 package and server installation guide
- Architecture: Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.
- Operations: Customer configures and maintains the web/database stack, scheduled and background work, email transport, backups and software security updates.
- Product website: https://suitecrm.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the downloadable self-hosted CRM. Campaigns and workflow configuration are documented, but external email delivery and optional integrations need their own operational arrangements. Confirm compatibility requirements before upgrading; community extensions are separately scoped.

The downloadable application core is GNU AGPL version 3. Paid hosting, implementation and support do not change the listed core license; review any separate extension licenses.

Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, opportunities, quotes and service processes; this is CRM rather than a complete financial ERP.

- marketing-automation: Targeted email campaigns and configurable workflows around CRM records; campaign delivery requires configured email and background jobs.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/suitecrm (checked 2026-11-12). Source: https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- SuiteCRM 8 community deployment on Railway (railway): https://railway.com/deploy/suitecrm
  The community recipe deploys SuiteCRM 8.10 with PHP/Apache, its scheduler and asynchronous worker, plus MariaDB and persistent application storage. The build downloads the upstream SuiteCRM release. Review current versions, initial administrator credentials, mail integration and backups; this does not include separately licensed extensions or vendor-hosted service.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the SuiteCRM Railway image (railway): https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile
  The inspected image downloads SuiteCRM-Core v8.10.2 from the upstream release repository and uses PHP 8.3. Confirm the compatibility matrix and update the release and database together when maintaining the deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release notes document SuiteCRM 8.10.2 security and maintenance work released July 31, 2026, and credit community contributors. The vendor case study describes Humanetics Innovative Solutions using SuiteCRM for customer visibility, sales workflows and targeted campaigns; the study does not establish the hosting model of every adopter.

Reviewed 2026-11-10.

- Security maintenance and contributor acknowledgements: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Named customer implementation: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Sources

- SuiteCRM 8 installation: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/

- Self-hosting and paid service scope: https://suitecrm.com/pricing/

- Marketing campaigns: https://docs.suitecrm.com/8.x/user/marketing-outreach/campaigns-overview/

- Configurable workflows: https://docs.suitecrm.com/admin/administration-panel/workflow/

- Application license: https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- Current security and maintenance releases: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Humanetics implementation case study: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Licensing sources

- https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- https://suitecrm.com/pricing/

### Infrastructure sources

- https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/


### 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 SuiteCRM 8.7.0+ guide documents SAML configuration and explicitly notes that IdP-initiated logout and POST binding to the logout service are unsupported. Review the stated session-timeout behavior and user mappings. Scope: SuiteCRM 8.7.0+ SAML; logout limitations do not imply login is unsupported. Source: https://docs.suitecrm.com/8.x/admin/configuration/saml/8.7.0-saml-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 SuiteCRM 8 guide documents downloading the prebuilt application package and completing server installation. Configure the compatible PHP/database stack, permissions and scheduled jobs for the selected release. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The SuiteCRM 8 installation and compatibility guides establish supported web/PHP/database combinations and recommend the pre-built installation package for production. They do not establish a quantitative whole-stack resource floor or an HA sizing profile. Scope: SuiteCRM 8 application, database and background processing; PHP limits are not whole-host memory requirements. Source: https://docs.suitecrm.com/8.x/admin/compatibility-matrix/ (reviewed 2026-11-20). Supporting source: Production installation package — https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/.

- License pricing: Documented. The vendor states there are no per-user software licence fees for SuiteCRM. Hosting, setup and support are paid services and must be budgeted separately from the open-source software. Scope: Self-hosted SuiteCRM core; managed hosting and optional services are not included. Source: https://suitecrm.com/pricing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v8.10.2, published 2026-07-31. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream SuiteCRM/SuiteCRM-Core release record; commercial editions and deployment packages may differ. Source: https://github.com/SuiteCRM/SuiteCRM-Core/releases/tag/v8.10.2 (reviewed 2026-11-14).







## Supabase Self-Hosted

Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.

- Listing: https://launchinyourcloud.com/directory/supabase/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0
- Licensing model: open-source
- Installation: Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server image
- Architecture: Customer-operated PostgreSQL database and containerized backend services
- Operations: Customer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
- Product website: https://supabase.com/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

The listed self-hosted distribution uses open-source components; the Supabase platform repository is Apache-2.0. Managed-cloud features and paid support are separate from this public self-hosted distribution, and bundled components retain their own licenses.

The official installation runs PostgreSQL and supporting services through Docker Compose on a Linux server or VPS. This is persistent application infrastructure, even when it exposes functions.


### Category fit

- backend-platforms: PostgreSQL-based application backend with authentication, APIs, storage, realtime and functions; self-hosting does not include every managed-platform feature.

- databases-vector: A PostgreSQL-based application data platform with database APIs, authentication and storage services. This entry covers the self-hosted stack.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/supabase-community/supabase-on-aws (checked 2026-11-21). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/guides/supabase (checked 2026-11-21). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application (checked 2026-11-21). 


### Cloud deployment evidence

- Supabase community AWS CloudFormation/CDK deployment (aws): https://github.com/supabase-community/supabase-on-aws
  This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.
  Source type: community-template; reviewed: 2026-11-21; vendor support: not-assessed.

- Self-host Supabase in a Railway project (railway): https://railway.com/guides/supabase
  Railway documents a community template for PostgreSQL, authentication, REST, storage, and Studio. The services communicate over private networking in the customer’s Railway project. Railway operates the underlying platform.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.

- Deploy the Supabase Marketplace application on Vultr Compute (vultr): https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application
  Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Self-hosting scope and responsibilities: https://supabase.com/docs/guides/self-hosting

- Official Docker deployment: https://supabase.com/docs/guides/self-hosting/docker

- Platform repository license: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- Self-host Supabase in a Railway project: https://railway.com/guides/supabase

- Deploy the Supabase Marketplace application on Vultr Compute: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application

### Licensing sources

- https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- https://supabase.com/docs/guides/self-hosting

### Infrastructure sources

- https://supabase.com/docs/guides/self-hosting/docker


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted Auth service supports external OAuth providers, including a configurable Keycloak issuer. This serves end users of applications built on Supabase; it does not establish organizational SSO for the self-hosted Studio/admin dashboard. Review provider, redirect, signup and administrative access separately. Scope: Self-hosted application-user Auth service; Studio federation excluded. Source: https://raw.githubusercontent.com/supabase/auth/master/README.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 upstream docker directory contains the multi-service Compose stack and related environment/configuration files. Follow the self-hosting guide for a matching deployment version and replace secrets. Scope: Self-hosted multi-service stack; not the monthly developer newsletter version. Source: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. For all components, the guide gives 2 CPU cores, 4 GB RAM and 40 GB SSD as a minimum; 4 cores, 8 GB+ and 80 GB+ SSD are recommended. Optional analytics increases requirements. Scope: Docker stack for development and small-to-medium production; not every workload. Source: https://supabase.com/docs/guides/self-hosting/docker (reviewed 2026-11-14).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Typebot

Self-hosted visual conversation and form builder.

- Listing: https://launchinyourcloud.com/directory/typebot/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: vultr, hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.
- Licensing model: source-available
- Installation: Application platform deployment; Docker / Compose
- Architecture: Typebot builder and viewer, database, object storage and mail configuration.
- 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://typebot.io
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.

FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion.

Typebot builder and viewer, database, object storage and mail configuration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted visual conversation and form builder.

### Deployment boundaries


- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder (checked 2026-11-19). 

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

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production (checked 2026-11-19). 


### Cloud deployment evidence

- Vultr Docs (vultr): https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Hostinger (hostinger): https://www.hostinger.com/applications/typebot
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production
  Typebot builder and viewer, database, object storage and mail configuration. Current FSL-1.1-Apache-2.0 terms impose restrictions before the future Apache conversion. Provider descriptions calling it open source do not override that licence.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Vultr Docs: https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder

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

- Railway: https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production

- GitHub LICENSE (FSL-1.1-Apache-2.0): https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE

- GitHub Releases: https://github.com/baptisteArno/typebot.io/releases

### Licensing sources

- https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE

### Infrastructure sources

- https://docs.vultr.com/how-to-deploy-typebot-open-source-conversational-form-builder

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

- https://railway.com/deploy/typebot-open-source-chatbot-builder-with-postgres--typebot-production


### 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. Self-hosted builder authentication supports named social providers, Microsoft Entra ID, Keycloak and a custom OIDC provider. Published v3.19.1 code registers these providers with its login/session flow. Configure issuer/callback URLs, trusted identity/email and workspace admission policy; this authenticates editors, not every bot respondent, and does not establish SCIM. Scope: Self-hosted builder/editor login, checked against published v3.19.1 implementation. Source: https://docs.typebot.com/self-hosting/configuration.md (reviewed 2026-11-20). Supporting source: Published provider configuration — https://github.com/baptisteArno/typebot.io/blob/v3.19.1/packages/auth/src/lib/providers.ts. Supporting source: Published authentication/session wiring — https://github.com/baptisteArno/typebot.io/blob/v3.19.1/packages/auth/src/lib/nextAuth.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide links a Compose stack for separate builder/viewer applications, PostgreSQL and Redis. The v3.19.1 file still selects latest application images and a sample database password; pin compatible images, replace credentials, and configure the encryption secret, login provider, URLs, TLS and optional object storage. Scope: Vendor Docker recipe with versioned source; source-file tag alone does not pin container images. Source: https://docs.typebot.com/self-hosting/deploy/docker.md (reviewed 2026-11-20). Deployment artifact: https://github.com/baptisteArno/typebot.io/blob/v3.19.1/docker-compose.yml. Artifact reference: v3.19.1 (recipe uses moving latest application image tags).

- Minimum footprint / sizing: Sources checked — unresolved. The Docker guide establishes builder, viewer, database and cache roles, with optional object storage, but does not specify whole-stack production CPU/RAM/storage minima. Size editor sessions, concurrent conversations, uploads and integrations separately; provider tutorial/demo allocations do not validate a 100-user, 1 TB HA deployment. Scope: Current upstream deployment topology; numeric workload and HA sizing remains unconfirmed. Source: https://docs.typebot.com/self-hosting/deploy/docker.md (reviewed 2026-11-20).

- License pricing: Documented. FSL-1.1-Apache-2.0; competing commercial use is restricted before the future Apache conversion. Scope: Typebot; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/baptisteArno/typebot.io/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Umami

Self-hosted website and event analytics application with dashboards and PostgreSQL storage.

- Listing: https://launchinyourcloud.com/directory/umami/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean, fly, heroku, northflank, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for upstream Umami.
- Licensing model: open-source
- Installation: Build from source, run the official prebuilt container or use its Docker Compose application/PostgreSQL setup.
- Architecture: Customer-operated web analytics service and PostgreSQL database
- Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
- Product website: https://umami.is/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.

MIT License for upstream Umami. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated web analytics service and PostgreSQL database. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- web-analytics: Website and event analytics through a deployed tracking endpoint and analytics application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-digitalocean (checked 2026-11-12). 

- fly: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-fly-io (checked 2026-11-12). 

- heroku: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-heroku (checked 2026-11-12). 

- northflank: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-northflank (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.umami.is/docs/guides/running-on-railway (checked 2026-11-12). 


### Cloud deployment evidence

- Umami self-hosting on a DigitalOcean Droplet (digitalocean): https://docs.umami.is/docs/guides/running-on-digitalocean
  The project documents running the Umami application and PostgreSQL on a customer Droplet with PM2 and Nginx. The guide links older Ubuntu setup examples; use currently supported OS and Node.js versions, configure HTTPS and maintain backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Fly.io (fly): https://docs.umami.is/docs/guides/running-on-fly-io
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Heroku (heroku): https://docs.umami.is/docs/guides/running-on-heroku
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Northflank (northflank): https://docs.umami.is/docs/guides/running-on-northflank
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Umami self-hosted deployment on Railway (railway): https://docs.umami.is/docs/guides/running-on-railway
  The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Upstream release notes document current runtime/security work and credit multiple named contributors across successive releases.

Reviewed 2026-11-10.

- Maintenance and named release contributors: https://github.com/umami-software/umami/releases

- Public upstream project: https://github.com/umami-software/umami

### Sources

- Official installation and runtime: https://docs.umami.is/docs/install

- Upstream project and capabilities: https://github.com/umami-software/umami

- Current upstream license: https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

- Umami self-hosted deployment on Fly.io: https://docs.umami.is/docs/guides/running-on-fly-io

- Umami self-hosted deployment on Heroku: https://docs.umami.is/docs/guides/running-on-heroku

- Umami self-hosted deployment on Northflank: https://docs.umami.is/docs/guides/running-on-northflank

- Umami self-hosted deployment on Railway: https://docs.umami.is/docs/guides/running-on-railway

### Licensing sources

- https://raw.githubusercontent.com/umami-software/umami/master/LICENSE

### Infrastructure sources

- https://docs.umami.is/docs/install


### 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The API documents an SSO token endpoint requiring existing authentication and Redis. This does not establish a generic SAML/OIDC enterprise identity-provider integration or its edition entitlement. Scope: Authenticated token exchange checked; enterprise federation remains unresolved. Source: https://docs.umami.is/docs/api-reference/sso (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 official guide documents source builds, application containers and Compose. It explicitly identifies the HelmForge Kubernetes chart as third-party; change the default administrator password and configure the database and secrets. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.umami.is/docs/install (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The install guide requires the application runtime and a PostgreSQL database, but does not give a numeric whole-stack production CPU/RAM/storage minimum. Event volume, retention, query concurrency and HA determine capacity; provider demo allocations are not a 100-user, 1 TB HA sizing guarantee. Scope: Current upstream self-hosted topology; whole-system sizing remains unconfirmed. Source: https://docs.umami.is/docs/install (reviewed 2026-11-20).

- License pricing: Documented. The reviewed v3.5.0 application is MIT-licensed and can be self-hosted without a core software subscription. Retain the required copyright/licence notices; hosting, database, operations and Umami Cloud services are separate costs. Scope: Published self-hosted application terms; not a Cloud plan quote. Source: https://github.com/umami-software/umami/blob/v3.5.0/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v3.5.0, published 2026-11-12. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream umami-software/umami release record; commercial editions and deployment packages may differ. Source: https://github.com/umami-software/umami/releases/tag/v3.5.0 (reviewed 2026-11-14).







## useSend

Self-hosted email campaign and transactional messaging application.

- Listing: https://launchinyourcloud.com/directory/usesend/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, 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; Docker / Compose
- Architecture: useSend application, PostgreSQL, queues and AWS SES/SNS integration.
- 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://useSend.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.

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

useSend application, PostgreSQL, queues and AWS SES/SNS integration. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- marketing-automation: Self-hosted email campaign and transactional messaging application.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/usesend
  useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/usesend
  useSend application, PostgreSQL, queues and AWS SES/SNS integration. The application runs in the selected provider account; SES/SNS is an external sending dependency and does not establish AWS application hosting. Scope IAM permissions to the required sending resources.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes KMKoushik, harshsbhat, magicspon, 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/usesend/useSend/graphs/contributors

- Upstream project: https://github.com/usesend/useSend

### Sources

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

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

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/usesend/useSend/main/LICENSE

- GitHub Releases: https://github.com/usesend/useSend/releases

### Licensing sources

- https://raw.githubusercontent.com/usesend/useSend/main/LICENSE

### Infrastructure sources

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

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


### 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 self-hosting guide documents GitHub login; published v1.10.4 code also registers Google when configured. The code permits an initial bootstrap account, then requires an existing account or team invitation. Configure provider credentials, trusted email/account linking and callbacks. Email codes, SES credentials and API/SMTP tokens are separate; generic SAML/OIDC federation is not established. Scope: Named external login providers for the self-hosted application, with published account-admission behavior. Source: https://docs.usesend.com/self-hosting/overview.md (reviewed 2026-11-20). Supporting source: Published v1.10.4 provider and account-admission code — https://github.com/usesend/useSend/blob/v1.10.4/apps/web/src/server/auth.ts.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official production Docker guide links a Compose stack; the v1.10.4 recipe includes the app, PostgreSQL, Redis and RustFS image storage. Pin the application image instead of latest and configure provider login, secrets, persistent data and TLS. AWS SES/SNS delivery and optional public image URLs require separate configuration; the SMTP proxy is a different service. Scope: Published application stack, distinct from the separate SMTP-server Compose example. Source: https://docs.usesend.com/get-started/set-up-docker.md (reviewed 2026-11-20). Deployment artifact: https://github.com/usesend/useSend/blob/v1.10.4/docker/prod/compose.yml. Artifact reference: v1.10.4 (application image tag is latest; pin a compatible deployment version). Supporting source: Official self-hosting dependencies and settings — https://docs.usesend.com/self-hosting/overview.md.

- Minimum footprint / sizing: Sources checked — unresolved. The official guide establishes an app, PostgreSQL, Redis, SES/SNS and optional image-storage topology but no complete production CPU/RAM/storage minimum. Size campaign volume, queue concurrency, email-content retention and storage before selecting instances; 100 internal users and 1 TB alone do not specify delivery throughput or HA capacity. Scope: Current self-hosted topology; whole-system production sizing remains unconfirmed. Source: https://docs.usesend.com/self-hosting/overview.md (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

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







## UVdesk Community

Community service desk for support tickets and customer communications.

- Listing: https://launchinyourcloud.com/directory/uvdesk/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open Software License 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: UVdesk application, MySQL, files and mail services in 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://www.uvdesk.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The template includes Mailpit; mail capture or testing is not a production outbound email service. Configure approved SMTP delivery and mailbox access.

Open Software License 3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

UVdesk application, MySQL, files and mail services in Railway. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- customer-support: Community service desk for support tickets and customer communications.

### Deployment boundaries


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


### Cloud deployment evidence

- Railway (railway): https://railway.com/deploy/uvdesk-helpdesk
  UVdesk application, MySQL, files and mail services in Railway. The template includes Mailpit; mail capture or testing is not a production outbound email service. Configure approved SMTP delivery and mailbox access.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes papnoisanjeev, komal-sh-27, PeopleInside, 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/uvdesk/community-skeleton/graphs/contributors

- Upstream project: https://github.com/uvdesk/community-skeleton

### Sources

- Railway: https://railway.com/deploy/uvdesk-helpdesk

- GitHub LICENSE.txt (OSL-3.0): https://raw.githubusercontent.com/uvdesk/community-skeleton/master/LICENSE.txt

- GitHub Releases: https://github.com/uvdesk/community-skeleton/releases

### Licensing sources

- https://raw.githubusercontent.com/uvdesk/community-skeleton/master/LICENSE.txt

### Infrastructure sources

- https://railway.com/deploy/uvdesk-helpdesk


### 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: Sources checked — unresolved. The vendor advertises social-login/SSO apps for its SaaS support portal, while the reviewed Community v1.1.8 security configuration uses application form login. These sources do not confirm a version-compatible external identity-provider integration for Community agents or customers. A Symfony authentication extension would need an actual supported configuration. Scope: Community Edition versus SaaS app boundary; no positive SSO availability established. Source: https://github.com/uvdesk/community-skeleton/blob/v1.1.8/config/packages/security.yaml (reviewed 2026-11-20). Supporting source: Vendor social-login app, labelled SaaS — https://www.uvdesk.com/en/apps/social-login-app/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The published Community v1.1.8 README documents Composer project creation or downloading the release, followed by helpdesk configuration; Docker and persistent-container guides are linked separately. Pin the selected version, install dependencies, configure database/mail and protect the application. A provider template may package a different release. Scope: Published Community release installation instructions. Source: https://github.com/uvdesk/community-skeleton/blob/v1.1.8/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/uvdesk/community-skeleton/releases/tag/v1.1.8. Artifact reference: v1.1.8.

- Minimum footprint / sizing: Documented. The v1.1.8 README lists at least 4 GB RAM and a 1 GHz processor with a PHP/web-server/MySQL stack. This is an upstream starting point, not ticket/attachment retention capacity or an HA topology. Review the version-matched supported OS/runtime rather than copying the README's old OS examples unchanged. Scope: Published upstream Community baseline; whole-stack HA and 1 TB data capacity require further sizing. Source: https://github.com/uvdesk/community-skeleton/blob/v1.1.8/README.md (reviewed 2026-11-20).

- License pricing: Documented. Open Software License 3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: UVdesk Community; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/uvdesk/community-skeleton/master/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## XWiki

Self-hosted enterprise wiki and structured knowledge application platform.

- Listing: https://launchinyourcloud.com/directory/xwiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU LGPL-2.1 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: XWiki application, PostgreSQL, persistent files and search components.
- 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.hostinger.com/applications/xwiki
- 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 pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.

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

XWiki application, PostgreSQL, persistent files and search components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted enterprise wiki and structured knowledge application platform.

### Deployment boundaries


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

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


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/xwiki
  XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Railway (railway): https://railway.com/deploy/xwiki-1
  XWiki application, PostgreSQL, persistent files and search components. The Railway recipe pins XWiki 18.9.0; upstream 17.10 LTS maintenance releases have a separate release line. Run the Distribution Wizard and validate extensions when upgrading.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes tmortagne, vmassol, mflorea, 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/xwiki/xwiki-platform/graphs/contributors

- Upstream project: https://github.com/xwiki/xwiki-platform

### Sources

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

- Railway: https://railway.com/deploy/xwiki-1

- LGPL-2.1 LICENSE: https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE

- GitHub Releases: https://github.com/xwiki/xwiki-platform/releases

### Licensing sources

- https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE

### Infrastructure sources

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

- https://railway.com/deploy/xwiki-1


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 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 OpenID Connect Authenticator extension provides OIDC sign-in and synchronization. It is installed through Extension Manager, is LGPL-2.1 licensed, and requires XWiki 14.10.2 or later; commercial support is separate. Scope: XWiki with separately installed OIDC Authenticator extension. Source: https://extensions.xwiki.org/xwiki/bin/view/Extension/OpenID%20Connect/OpenID%20Connect%20Authenticator/ (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. Official installation options include a production-capable Docker image, Debian packages or a WAR distribution. Production requires a supported database, persistent application data and compatible Java/container versions; the standalone HSQLDB demo is not the production baseline. Scope: Official XWiki distribution options. Source: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/ (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/_/xwiki. Artifact reference: Select an explicit compatible image tag; no artifact is installed by this review.

- Minimum footprint / sizing: Documented. The Tiny guideline is 2 CPU cores, 2 GB RAM and 5 GB disk for up to 25 active users; Small is 2 cores, 4 GB and 20 GB for up to 250. These single-machine application/database profiles depend on document and request volume and do not establish HA or 1-TB capacity. Scope: Upstream single-machine sizing profiles; workload dimensions must all be checked. Source: https://www.xwiki.org/xwiki/bin/view/documentation/xs/admin/installation/xwiki-instance-sizing/ (reviewed 2026-11-20).

- License pricing: Documented. GNU LGPL-2.1 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: XWiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/xwiki/xwiki-platform/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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







## Zammad

Self-hosted helpdesk and ticketing application for customer service and internal support teams.

- Listing: https://launchinyourcloud.com/directory/zammad/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 repository license for the core application
- Licensing model: open-source
- Installation: Official Linux packages; Docker Compose and Kubernetes alternatives are documented
- Architecture: Persistent application and worker services with PostgreSQL, Redis and a web proxy; Elasticsearch is strongly recommended for search.
- Operations: Customer runs the application stack, database, backups and security updates; follow supported distribution and release requirements.
- Product website: https://zammad.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the self-hosted helpdesk core. The official repository supplies an AGPL-3.0 license, although the marketing open-source page labels it GPL v3; verify the license shipped with the selected release. Zammad 7.2.3 is a critical security release and self-hosted operators should upgrade immediately. Package installations using nginx or Apache must update the reverse-proxy configuration for the Remote-User header; Docker images include the change.

The listed self-hosted core repository supplies the GNU Affero GPL version 3. The vendor describes the full helpdesk as open source; separately purchased services or integrations are outside this classification. Marketing shorthand says GPL v3, so check the selected release's supplied license for exact terms.

The official system documentation describes persistent Linux application services, PostgreSQL, Redis and proxy services, with container-stack alternatives. Elasticsearch is strongly recommended rather than a hard dependency.


### Category fit

- customer-support: Agent helpdesk with tickets, customer communication, configurable fields and a knowledge base.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/zammad (checked 2026-11-12). Source: https://github.com/gridalpha/zammad-railway/blob/main/zammad/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- Zammad community deployment on Railway (railway): https://railway.com/deploy/zammad
  The community recipe deploys Zammad application roles with PostgreSQL, Redis, Memcached and Elasticsearch in a customer project. Its wrapper builds on the official Zammad image and adapts storage/bootstrap configuration for Railway. Review all image versions, object-storage settings, credentials, email integration and upgrades; this is not Zammad hosted service.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the Zammad Railway application wrapper (railway): https://github.com/gridalpha/zammad-railway/blob/main/zammad/Dockerfile
  The inspected application wrapper derives from ghcr.io/zammad/zammad and supplies Railway-specific startup/bootstrap behavior. The tag is configurable; pin and review it together with the backing services rather than assuming that latest remains compatible.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Official case studies document daily customer-support use by Nextcloud and De'Longhi, without establishing every customer's hosting model. The release page records the 7.2.3 critical security update on November 11, 2026, and directs self-hosted installations to upgrade immediately, providing maintenance evidence beyond repository popularity.

Reviewed 2026-11-13.

- Named customer-support adopters: https://zammad.com/en/customers

- Nextcloud implementation story: https://zammad.com/en/customers/nextcloud

- Recent feature and security maintenance: https://zammad.com/en/product/releases

- 7.2.3 critical security release: https://zammad.com/en/product/releases/7-2-3

### Sources

- Official Linux package installation: https://docs.zammad.org/en/latest/install/package.html

- Server, database and deployment prerequisites: https://docs.zammad.org/en/latest/prerequisites/software.html

- Helpdesk and customer support features: https://zammad.com/en/product/features

- Zammad core repository license: https://raw.githubusercontent.com/zammad/zammad/develop/LICENSE

- Vendor open-source policy: https://zammad.com/en/company/open-source

- Supported and emergency security releases: https://zammad.com/en/product/releases

- November 2026 critical security release: https://zammad.com/en/product/releases/7-2-3

- Customer support implementation stories: https://zammad.com/en/customers

- Nextcloud customer support case study: https://zammad.com/en/customers/nextcloud

### Licensing sources

- https://raw.githubusercontent.com/zammad/zammad/develop/LICENSE

- https://zammad.com/en/company/open-source

### Infrastructure sources

- https://docs.zammad.org/en/latest/install/package.html

- https://docs.zammad.org/en/latest/prerequisites/software.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 administrator guide documents SAML and OpenID Connect login with your identity provider. Configure issuer/client credentials, claim mapping and account-linking policy; this does not establish automatic lifecycle provisioning. Scope: Self-hosted Zammad application login, with administrator configuration. Source: https://admin-docs.zammad.org/en/latest/settings/security/third-party/openid-connect.html (reviewed 2026-11-20). Supporting source: SAML configuration — https://admin-docs.zammad.org/en/latest/settings/security/third-party/saml.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide links the Zammad Docker Compose repository and its deployment scenarios. Vendor support covers the Zammad application, not Docker/Compose or Portainer-specific problems; configure HTTPS separately. Scope: Official self-hosted Compose deployment; infrastructure support is separate. Source: https://docs.zammad.org/en/latest/install/docker-compose.html (reviewed 2026-11-14). Deployment artifact: https://github.com/zammad/zammad-docker-compose. Artifact reference: master (moving branch; select matching release/scenario).

- Minimum footprint / sizing: Documented. The hardware guide gives a 2-core, 6 GB RAM minimum baseline with PostgreSQL, plus 4 GB if Elasticsearch shares the host. Its Docker guide separately says at least 4 GB for containers; these are different baselines, not a complete production sizing plan. Scope: Current self-hosted hardware guidance; selected topology and ticket load govern sizing. Source: https://docs.zammad.org/en/latest/prerequisites/hardware.html (reviewed 2026-11-14). Supporting source: Docker-specific prerequisites — https://docs.zammad.org/en/latest/install/docker-compose.html.

- License pricing: Documented. The self-hosted application uses AGPLv3; commercial support is purchased separately. The current pricing page lists annual support packages rather than the hosted per-agent subscription. Your team remains responsible for updates, backups and availability; support, AI usage and infrastructure have their own terms and costs. Scope: Self-hosted support versus hosted subscription; no transfer of hosted seat prices. Source: https://zammad.com/en/pricing#self-hosted (reviewed 2026-11-20). Supporting source: Published Zammad 7.2.3 AGPL licence — https://github.com/zammad/zammad/blob/7.2.3/LICENSE.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## ZITADEL Self-Hosted

Application identity platform that can run as a self-operated service with its own PostgreSQL database.

- Listing: https://launchinyourcloud.com/directory/zitadel/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate.
- Licensing model: open-source
- Installation: Deploy the official Docker Compose stack with ZITADEL API, login application, reverse proxy and PostgreSQL, then apply the documented hardening configuration.
- Architecture: Customer-operated Go API, login application and PostgreSQL behind a configured proxy
- Operations: Customer manages identity storage, cryptographic keys, proxy/TLS, backups, email/SMS providers and updates.
- Product website: https://zitadel.com/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The Compose guide is a starting point for a homelab or semi-production installation. The current contribution guide states that engineering focus on next-generation work limits community PR review capacity for this codebase; evaluate the supported release roadmap. External identity and message providers remain separate. ZITADEL v4.20.4 enables PKCE by default for Google, GitHub, GitLab, and Azure AD identity providers and hardens SMS OTP and password history. Revalidate external IdP callbacks and authentication policy after upgrading. ZITADEL v4.20.5 fixes a Login V2 MFA bypass in which a first-factor-only session could add a new authenticator even when a second factor was already configured. Upgrade and verify authenticator-enrolment policy.

GNU Affero General Public License version 3 for the reviewed upstream code; commercial products and agreements are separate. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated Go API, login application and PostgreSQL behind a configured proxy. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- identity-access-management: Application identity and access management with user/organization administration and configured authentication flows.

### Deployment boundaries


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


### Cloud deployment evidence

- ZITADEL community deployment template on Railway (railway): https://railway.com/deploy/zitadel-1
  The community template uses official ZITADEL server and login images with PostgreSQL in a customer Railway project. Review server/login version alignment, initial administrator credentials and the production checklist; Login V2 requires additional service-user configuration. This is separate from ZITADEL Cloud.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Official project information reports more than 200 contributors, and the upstream release history records continuing 2026 maintenance. Current contribution guidance explicitly discloses reduced review capacity while the team builds its next generation.

Reviewed 2026-11-10.

- Contributor community: https://zitadel.com/about

- Current release maintenance: https://github.com/zitadel/zitadel/releases

- Current contribution-capacity caveat: https://raw.githubusercontent.com/zitadel/zitadel/main/CONTRIBUTING.md

### Sources

- Official installation and runtime: https://zitadel.com/docs/self-hosting/deploy/compose

- Upstream project and capabilities: https://github.com/zitadel/zitadel

- Current upstream license: https://raw.githubusercontent.com/zitadel/zitadel/main/LICENSE

- ZITADEL v4.20.4 release: https://github.com/zitadel/zitadel/releases/tag/v4.20.4

- ZITADEL v4.20.5 release: https://github.com/zitadel/zitadel/releases/tag/v4.20.5

- ZITADEL authenticator-enrolment fix: https://github.com/zitadel/zitadel/commit/59827a8ec6dd0c23acbba5d0ebdf41fdc857d66c

### Licensing sources

- https://raw.githubusercontent.com/zitadel/zitadel/main/LICENSE

### Infrastructure sources

- https://zitadel.com/docs/self-hosting/deploy/compose


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 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. ZITADEL can broker external OIDC and SAML identity providers for applications, with instance-wide or organization-specific login policies. Configure permitted providers, callbacks, claims and account linking/creation policy. Being an identity platform does not automatically integrate every application or establish SCIM lifecycle provisioning. Scope: ZITADEL identity-brokering role and external IdP configuration; not an assertion that every client is preconfigured. Source: https://zitadel.com/docs/guides/integrate/identity-providers/introduction (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. v4.20.5 fixes Login V2 authenticator enrolment accepting a first-factor-only session despite an existing second factor. Upgrade and test MFA enrolment. Scope: ZITADEL Login V2 authenticator enrolment. Source: https://github.com/zitadel/zitadel/releases/tag/v4.20.5 (reviewed 2026-11-19). Supporting source: Fix commit — https://github.com/zitadel/zitadel/commit/59827a8ec6dd0c23acbba5d0ebdf41fdc857d66c.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Compose guide deploys API, login application, reverse proxy and PostgreSQL and then describes hardening. It is a homelab/semi-production starting point, not a full HA architecture. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://zitadel.com/docs/self-hosting/deploy/compose (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The production guide separates an approximately 512 MB application process from database capacity and password-hashing peaks. Its minimal HA reference uses three nodes at 4 CPU cores and 16 GB RAM each, or about 8 GB without nonessential telemetry services. Database sizing and actual login/request load still need validation; 512 MB is not an HA stack minimum. Scope: Current self-hosted production/HA reference, distinct from application-process memory. Source: https://zitadel.com/docs/self-hosting/manage/production (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream application uses GNU AGPLv3. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote. Scope: ZITADEL v4.20.5 upstream source; software terms only, excluding infrastructure and operations. Source: https://github.com/zitadel/zitadel/blob/v4.20.5/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. ZITADEL v4.20.5 was published November 18, 2026. It requires the configured second factor before a session may add an authenticator, closing a Login V2 MFA-bypass path. Scope: Upstream ZITADEL v4 release. Source: https://github.com/zitadel/zitadel/releases/tag/v4.20.5 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/zitadel/zitadel/releases/tag/v4.20.4.




### Security and lifecycle reviews

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

- ZITADEL v4.20.5 Login V2 MFA-enrolment fix (security-advisory): v4.20.5 requires the configured second factor before a session may add a new authenticator. Scope: ZITADEL Login V2 authenticator enrolment. Conditions: The path requires an account with an existing second factor and a first-factor-only session that could previously enrol another authenticator. Action: Upgrade to v4.20.5 or later and test MFA enrolment and recovery flows. Source: https://github.com/zitadel/zitadel/releases/tag/v4.20.5; reviewed 2026-11-19. Supporting source: Fix commit — https://github.com/zitadel/zitadel/commit/59827a8ec6dd0c23acbba5d0ebdf41fdc857d66c.



