
# Document management on AWS

Compare documented Document management deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/document-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: AWS account
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

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

### Private connectivity

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

### Cross-account operations

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

### Government environments

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

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

24 listings.


## Adobe Experience Manager 6.5 Forms (Correspondence Management)

Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

- Listing: https://launchinyourcloud.com/directory/adobe-aem-forms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms 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://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AEM 6.5 Forms is separate from AEM as a Cloud Service and Adobe Managed Services. Production Forms capabilities require their own licence. Adobe's VM support remains subject to its technical requirements and reproducibility rules; supported S3 or Blob datastores do not make every cloud-native service supported.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- correspondence-management: Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

- document-management: Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements (checked 2026-11-19). 


### Cloud deployment evidence

- AEM 6.5 Tech Reqs (aws, azure): https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements
  Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components. AEM 6.5 Forms is separate from AEM as a Cloud Service and Adobe Managed Services. Production Forms capabilities require their own licence. Adobe's VM support remains subject to its technical requirements and reproducibility rules; supported S3 or Blob datastores do not make every cloud-native service supported.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AEM 6.5 Tech Reqs: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements

- Correspondence Management: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/letters-correspondences/cm-overview

- AEM 6.5 Licensing & Deploy: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy

- AEM 6.5.26.0 Release Notes: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes

### Licensing sources

- https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy

### Infrastructure sources

- https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements


### 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. AEM 6.5 provides a SAML 2.0 Web SSO handler with signed/encrypted assertions, user creation and group synchronization. It is disabled until configured with provider/entity information and trust material. This establishes the AEM/OSGi web-login path, not automatic SSO for every Forms JEE or desktop component. Scope: AEM 6.5 platform web authentication used by the Forms deployment; choose the applicable runtime and repository paths. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/saml-2-0-authenticationhandler (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. Adobe documents installing AEM 6.5 Quickstart and a compatible Forms add-on package through its package-management workflow. Downloads require entitled Adobe access. Select the matching Forms runtime/service pack and deployment topology; this is licensed application installation, not a public Terraform or complete cloud template. Scope: AEM 6.5 Forms on OSGi installation path; Forms JEE and Correspondence Management components require their applicable guides. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/osgi-installation/installing-configuring-aem-forms-osgi (reviewed 2026-11-20). Deployment artifact: https://experience.adobe.com/downloads. Artifact reference: AEM 6.5 Quickstart plus compatible Forms add-on/service pack; entitled download selection required. Supporting source: Base AEM installation — https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy.

- Minimum footprint / sizing: Sources checked — unresolved. Adobe lists base AEM installation requirements and separate Forms temporary-space/topology requirements, but these do not establish a complete Correspondence Management production sizing profile. Author/publish roles, document services, storage and redundant instances must be sized for the selected Forms runtime and workload. Scope: AEM 6.5 Forms/Correspondence Management; generic AEM minima and installer temporary space are not a validated whole-system HA floor. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/osgi-installation/installing-configuring-aem-forms-osgi (reviewed 2026-11-20). Supporting source: General AEM technical requirements — https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements.

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Adobe Experience Manager 6.5 Forms (Correspondence Management); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Alfresco Content Services + Governance Services

Customer-operated content and records management with retention and record-declaration workflows.

- Listing: https://launchinyourcloud.com/directory/alfresco-governance/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Community and commercial editions; capabilities and support differ
- Licensing model: open-source
- Installation: Distribution ZIP/module installation; underlying platform container/Helm options
- Architecture: Customer-operated content repository, search and database
- Operations: Customer operates repository, search, database, backups and upgrades. Enterprise container access requires vendor credentials.
- Product website: https://www.hyland.com/en/products/alfresco
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-14

### Scope and qualifications

Governance Services adds records management to Alfresco Content Services. Select the exact edition and supported production installation. Storage connectors do not establish provider-specific deployment support, and the documented development Docker Compose configuration is not a recommended production topology. Hyland’s current supported-platform documentation lists Governance Services 26.2. The retained 25.2 installation page is version-specific, so verify the selected Content Services and Governance Services versions against the current compatibility matrix.

This broad combined Content Services/Governance listing spans LGPL-3.0 Community software and commercially licensed Enterprise software with additional enterprise extensions. Community-only deployments and Enterprise deployments have different rights/features.

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

- records-management: Records lifecycle management with file plans, retention schedules, declaration and auditing. Community and commercial editions differ. Docker Compose examples are for development/testing; review a supported production topology.

- document-management: Content Services provides the content repository and document management; Governance Services adds records lifecycle capabilities.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Alfresco/acs-deployment/blob/master/docs/helm/eks-deployment.md (checked 2026-11-12). Source: https://github.com/Alfresco/docs-alfresco/blob/master/governance-services/7.4/install/index.md (checked 2026-11-12). 


### Cloud deployment evidence

- Alfresco Content Services deployment on Amazon EKS (aws): https://github.com/Alfresco/acs-deployment/blob/master/docs/helm/eks-deployment.md
  The vendor documents customer-operated ACS Enterprise and Community deployments on EKS, including persistent storage and customized repository/Share images. Evidence covers the ACS platform on which Governance Services is installed. Add the compatible Governance Services images or modules, required entitlements and production configuration; the separate development-only Compose example is not a production recommendation.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Alfresco Governance Services 7.4 add-on installation (aws): https://github.com/Alfresco/docs-alfresco/blob/master/governance-services/7.4/install/index.md
  The vendor versioned 7.4 manual documents Governance Services distribution ZIP/AMP installation on the compatible ACS platform and a development/test-only Compose option. Pair the add-on documentation with the ACS EKS deployment evidence and confirm the supported ACS/Governance release combination and commercial entitlements. This is not a claim that the development Compose file is a production topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Versions: Governance Services 7.4; confirm compatible ACS release.


### Sources

- Current Alfresco documentation: https://docs.hyland.com/p/alfresco

- Governance Services 25.2 installation options: https://support.hyland.com/r/Alfresco/Alfresco-Governance-Services/25.2/Alfresco-Governance-Services/Install

- Official container installation source and limitations: https://github.com/alfresco/docs-alfresco/blob/master/governance-services/7.2/install/docker.md

- Licensing and edition terms: https://github.com/Alfresco/alfresco-community-repo

- Licensing and edition terms: https://docs.alfresco.com/governance-services/community/

- Licensing and edition terms: https://pages.alfresco.com/rs/alfresco/images/en-enterprise-community-edition-comparison.pdf

- Licensing and edition terms: https://connect.hyland.com/t5/alfresco-blog/open-source-licensing/ba-p/173240

- Current Alfresco supported platforms and Governance Services releases: https://docs.hyland.com/r/Current/Alfresco-Supported-Platforms

### Licensing sources

- https://github.com/Alfresco/alfresco-community-repo

- https://docs.alfresco.com/governance-services/community/

- https://pages.alfresco.com/rs/alfresco/images/en-enterprise-community-edition-comparison.pdf

- https://connect.hyland.com/t5/alfresco-blog/open-source-licensing/ba-p/173240

### Infrastructure sources

- https://support.hyland.com/r/Alfresco/Alfresco-Governance-Services/25.2/Alfresco-Governance-Services/Install

- https://github.com/alfresco/docs-alfresco/blob/master/governance-services/7.2/install/docker.md

- https://docs.hyland.com/r/Current/Alfresco-Supported-Platforms


### Buyer diligence


Research coverage: 4/12 fields (33%); 1 documented, 3 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 official Identity Service source describes SAML federation for Alfresco Content Services, the parent platform. It does not establish the current Governance Services/ACS/Identity Service supported-version combination or commercial entitlement. Confirm that matrix for the selected governance installation. Scope: Parent-platform federation documented; current Governance Services combination unresolved. Source: https://raw.githubusercontent.com/Alfresco/docs-alfresco/master/identity-service/latest/index.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 archived 7.2 Docker Compose instructions are explicitly for development and test. Enterprise images require Quay credentials through Alfresco Support; do not treat this recipe as a supported production architecture. Scope: Alfresco Governance Services 7.2 Enterprise container recipe; historical, not current-release certification. Source: https://github.com/alfresco/docs-alfresco/blob/master/governance-services/7.2/install/docker.md (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The version-7.2 Compose source cites a 16-GB required memory setting while describing lower troubleshooting allocations. It explicitly limits Compose to development/test. This does not establish a current production or HA footprint for ACS plus Governance Services and supporting search/database components. Scope: Legacy development/test container recipe; current production sizing unresolved. Source: https://raw.githubusercontent.com/Alfresco/docs-alfresco/master/governance-services/7.2/install/docker.md (reviewed 2026-11-20).

- License pricing: Sources checked — unresolved. The reviewed installation source requires customer-issued Quay credentials for Enterprise Governance images. Community source licensing does not establish those commercial entitlements, supported ACS/AGS combinations or pricing. Obtain a current subscription and module quote for the selected deployment. Scope: Enterprise distribution access; current licence/pricing terms unresolved. Source: https://raw.githubusercontent.com/Alfresco/docs-alfresco/master/governance-services/7.2/install/docker.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Apryse Fluent

Customer-hosted document-template management and rendering software for automated business output.

- Listing: https://launchinyourcloud.com/directory/apryse-fluent/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer; Docker / Compose
- Architecture: Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App 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://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Customer-hosted document-template management and rendering software for automated business output.

- workflow-automation: Customer-hosted document-template management and rendering software for automated business output.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EC2 Guide (aws): https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2
  Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Container Apps (azure): https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment
  Fluent Manager or RESTful Engine with a database on AWS EC2, Azure Container Apps or Azure App Service. This is a template and document-generation layer. A separate case, CRM or correspondence application supplies intake, assignment and response deadlines. The documented Azure scaling examples are starting configurations; component licensing and a production HA design require their own review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS EC2 Guide: https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2

- Azure Container Apps: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment

- Azure App Service Engine: https://fluent.apryse.com/documentation/engine-guide/Fluent%20RESTful%20Engines/DeployingJavaRESTfulEngineAzureAppService

- License Types: https://fluent.apryse.com/documentation/store-guide/Licensing/types

- Apryse Legal: https://apryse.com/legal

- Release Schedule: https://fluent.apryse.com/documentation/support-guide/ReleaseSchedule

### Licensing sources

- https://fluent.apryse.com/documentation/store-guide/Licensing/types

- https://apryse.com/legal

### Infrastructure sources

- https://fluent.apryse.com/documentation/manager-guide/hosting/HostingManagerOnEC2

- https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerContainerAppDeployment


### 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. Fluent Manager supports SAML 2.0 as a service provider; the vendor identifies Microsoft Entra ID and Keycloak as tested providers. A Global Administrator configures the integration. This is Manager user login, not an SSO claim for the headless Fluent rendering engine. Scope: Fluent Manager component; check the selected Manager version and IdP configuration. Source: https://fluent.apryse.com/documentation/manager-guide/sso/ManagerSSO (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 provides a version-matched Kotlin helper script that generates a Docker Compose deployment for Manager frontend, backend and database. Match the script version to Manager and configure durable data, secrets and HTTPS; the script is not a complete cloud/HA template. Scope: Fluent Manager deployment; headless engine and Designer are separate components. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerDockerDeployment (reviewed 2026-11-20). Deployment artifact: https://fluent.apryse.com/documentation/downloads. Artifact reference: Select helper script x.y.z matching Fluent Manager x.y.z from the linked vendor download.

- Minimum footprint / sizing: Documented. The Manager Docker guide lists a minimum of two CPU cores, 4 GB RAM and 12 GB disk, including 7 GB for its database and 5 GB for containers/images. Storage grows with templates. This baseline does not size rendering-engine workloads, replicas or a 100-user, 1 TB HA deployment. Scope: Fluent Manager frontend/backend/database baseline; not the complete Fluent product family or a throughput guarantee. Source: https://fluent.apryse.com/documentation/manager-guide/hosting/ManagerDockerDeployment (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Apryse Fluent; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://fluent.apryse.com/documentation/store-guide/Licensing/types (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Docassemble

Self-hosted guided interviews and automated document assembly.

- Listing: https://launchinyourcloud.com/directory/docassemble/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, aws
- 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: Docker / Compose
- Architecture: Docassemble Docker application, database, persistent interviews and generated documents.
- 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://docassemble.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 vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.

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

Docassemble Docker application, database, persistent interviews and generated documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted guided interviews and automated document assembly.

### Deployment boundaries


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

- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docassemble.org/docs/installation.html (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/docassemble
  Docassemble Docker application, database, persistent interviews and generated documents. The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Docassemble EC2 Docs (aws): https://docassemble.org/docs/installation.html
  Docassemble Docker application, database, persistent interviews and generated documents. The vendor explicitly recommends AWS EC2. Azure Blob integration is storage evidence only, not Azure application hosting; interview authors must validate legal content and external integrations.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jhpyle, jpylephilalegal, BryceStevenWilley, 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/jhpyle/docassemble/graphs/contributors

- Upstream project: https://github.com/jhpyle/docassemble

### Sources

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

- Docassemble EC2 Docs: https://docassemble.org/docs/installation.html

- MIT LICENSE.txt: https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt

- GitHub Releases: https://github.com/jhpyle/docassemble/releases

### Licensing sources

- https://raw.githubusercontent.com/jhpyle/docassemble/master/LICENSE.txt

### Infrastructure sources

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

- https://docassemble.org/docs/installation.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The server documents external OAuth sign-in with providers including Auth0, Keycloak, Authentik and Azure. Configure each provider and account-linking/admin policies. The guide warns that external authentication affects its optional server-side answer-encryption model. Scope: Self-hosted server external authentication. Source: https://docassemble.org/docs/config.html#oauth (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 recommends the jhpyle/docassemble Docker distribution, including for production, with persistent configuration/data and optional external database or object storage. Select a versioned image and review production settings rather than using the minimal demonstration command unchanged. Scope: Official Docker distribution; infrastructure provisioning and HA not supplied by the one-line example. Source: https://docassemble.org/docs/installation.html (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/jhpyle/docassemble. Artifact reference: Select an explicit image tag for deployment.

- Minimum footprint / sizing: Documented. The project reports roughly 800–900 MB RAM during normal operation but recommends at least 4 GB because updates can use substantially more. This is a baseline server recommendation, not tested capacity for 100 users, 1 TB or HA. Scope: Upstream single-machine memory recommendation. Source: https://docassemble.org/docs/installation.html (reviewed 2026-11-20).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Fedora Repository

Open-source preservation repository with an AWS Terraform deployment.

- Listing: https://launchinyourcloud.com/directory/fedora-repository/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- 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: Terraform; Package / binary installer
- Architecture: Fedora Repository application on EC2 with PostgreSQL in RDS.
- 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://wiki.lyrasis.org/display/FF/Fedora+Repository+Home
- 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 is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.

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

Fedora Repository application on EC2 with PostgreSQL in RDS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- archives-collections-management: Open-source preservation repository with an AWS Terraform deployment.

- document-management: Open-source preservation repository with an AWS Terraform deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer (checked 2026-11-19). 


### Cloud deployment evidence

- fcrepo-aws-deployer (aws): https://github.com/fcrepo-exts/fcrepo-aws-deployer
  Fedora Repository application on EC2 with PostgreSQL in RDS. The repository is a preservation backend, not a complete public catalog or accession interface. The deployer's default instance and database are an example, not an HA sizing commitment; retain separate application and deployment-module versions.
  Source type: community-template; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes cbeer, ajs6f, whikloj, 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/fcrepo/fcrepo/graphs/contributors

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

### Sources

- fcrepo-aws-deployer: https://github.com/fcrepo-exts/fcrepo-aws-deployer

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

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

### Licensing sources

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

### Infrastructure sources

- https://github.com/fcrepo-exts/fcrepo-aws-deployer


### 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 Fedora deployment material identifies servlet-container/application security, but does not establish a version-matched external SAML/OIDC login configuration for the repository. A Java authentication library or cloud account IAM alone is not sufficient evidence of a supported user-federation path. Scope: Fedora Repository application authentication; institutional front ends and external reverse-proxy integrations need their own configuration evidence. Source: https://github.com/fcrepo/fcrepo/blob/main/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 Fedora community publishes a Terraform AWS deployer for the application and RDS, while upstream publishes WAR artifacts for a servlet container. The Terraform inputs and application/server versions must be matched; review its example database/instance defaults rather than treating the recipe as a current production or HA certification. Scope: Community-maintained Fedora AWS deployment recipe; provider path and upstream application artifacts have separate versions. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/fcrepo-exts/fcrepo-aws-deployer/tree/master. Artifact reference: master (moving branch); select compatible Fedora, servlet-container and database versions. Supporting source: Upstream runtime packaging — https://github.com/fcrepo/fcrepo/blob/main/README.md.

- Minimum footprint / sizing: Documented. The community AWS recipe defaults to a t3.small application instance and a small RDS database with a 10 GB allocation. These configurable example values do not establish a production minimum; verify currently supported database classes/engine versions, repository-object storage, index/load growth, backups and redundancy separately. Scope: Fedora community AWS recipe defaults, not a validated 1 TB repository or HA design. Source: https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/README.md (reviewed 2026-11-20). Supporting source: Configurable recipe inputs — https://github.com/fcrepo-exts/fcrepo-aws-deployer/blob/master/variables.tf.

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

- Operating cost estimate: Not researched.

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







## FileRun

Commercial self-hosted file management and sharing platform.

- Listing: https://launchinyourcloud.com/directory/filerun/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Application platform deployment; Docker / Compose
- Architecture: FileRun application and database on a Websoft9 customer-cloud VM.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://support.websoft9.com/en/docs/filerun/
- 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 package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

FileRun application and database on a Websoft9 customer-cloud VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted file management and sharing platform.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Websoft9 FileRun (aws, azure, alibaba): https://support.websoft9.com/en/docs/filerun/
  FileRun application and database on a Websoft9 customer-cloud VM. The application package sits on a separately installed Websoft9 platform. FileRun annual subscriptions and licensed domain terms are separate from platform and cloud bills.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Websoft9 FileRun: https://support.websoft9.com/en/docs/filerun/

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

- Websoft9 Azure: https://support.websoft9.com/en/docs/install-azure/

- Websoft9 Alibaba: https://support.websoft9.com/en/docs/install-alibabacloud/

- FileRun Pricing & Terms: https://filerun.com/pricing

- FileRun 2026 Updates: https://docs.filerun.com/api_2026_3_changes

### Licensing sources

- https://filerun.com/pricing

### Infrastructure sources

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


### 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. Current FileRun ships OpenID Connect and OAuth2 plugins, with SAML available through SimpleSAMLphp. Only one authentication plugin can be active at once; test its configuration and review local-superuser exceptions and licence entitlement. Scope: FileRun 2026.3 authentication plugins. Source: https://docs.filerun.com/authentication_integration (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 publishes Compose YAML for FileRun and MariaDB with persistent directories, and optional Tika/Elasticsearch. Its application image floats; pin a compatible release, replace example secrets and configure HTTPS and backups. Scope: Official self-hosted Compose recipe; not HA. Source: https://docs.filerun.com/docker (reviewed 2026-11-20). Deployment artifact: https://docs.filerun.com/docker. Artifact reference: Moving documentation; select a versioned application image.

- Minimum footprint / sizing: Sources checked — unresolved. The current guide gives a PHP floor of 20 MB per request and a 256-MB Docker PHP limit, with database memory additional. The Docker guide requires at least 2 GB for optional Elasticsearch. It does not establish total CPU/RAM sizing for a production or HA workload; previews and indexing materially change capacity. Scope: FileRun 2026.3 component guidance; total production minimum unresolved. Source: https://docs.filerun.com/requirements (reviewed 2026-11-20). Supporting source: Optional indexing memory — https://docs.filerun.com/docker.

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: FileRun; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://filerun.com/pricing (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## FormKiQ

Document management platform and API deployed into your AWS account.

- Listing: https://launchinyourcloud.com/directory/formkiq/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: platform
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless, hybrid
- License: Open-source Core; commercial editions
- Licensing model: open-source
- Installation: AWS CloudFormation
- Architecture: Managed AWS services
- Operations: Customer-operated deployment; confirm the support and upgrade arrangements for your edition.
- Product website: https://formkiq.com/
- Source review: 2026-11-17; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-17

### Scope and qualifications

The documented AWS stack includes API Gateway, Lambda, S3 and DynamoDB. Components vary by edition and optional modules. Review the exact template, IAM permissions and outbound integrations before deploying. FormKiQ Core 1.19.2 adds multi-attribute DynamoDB search, JSON attributes, fine-grained API permissions, custom API-key claims, content-only deletion, optional S3 Transfer Acceleration, and deployment hardening. Typesense upgrades must replace the plaintext TypesenseApiKey parameter with TypesenseApiKeySecretArn; automation using the renamed User Auth API outputs must adopt AuthApi and AuthApiUrl, and certificate deployments must apply template-upgrade.yaml before template.yaml.

The platform family has an open-source Core edition plus commercially licensed editions and capability modules. This classification covers that combined platform offering.

Serverless core; optional modules or search can add container or provisioned search workloads, producing a hybrid configuration. Confirm the selected edition and modules.


### Category fit

- document-management: Document management platform and API deployed into your AWS account.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/getting-started/quick-start (checked 2026-11-12). Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ Core AWS account deployment (aws): https://docs.formkiq.com/docs/getting-started/quick-start
  The publisher documents CloudFormation provisioning of the application and backing services in the customer AWS account. This is the public Core installation; licensed commercial editions use their separately supplied templates.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- AWS quick start: https://docs.formkiq.com/docs/getting-started/quick-start

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://github.com/formkiq/formkiq-core

- Licensing and edition terms: https://formkiq.com/pricing/

- FormKiQ Core v1.19.2 release and upgrade notes: https://github.com/formkiq/formkiq-core/releases/tag/v1.19.2

- FormKiQ Core v1.19.2 full changelog: https://docs.formkiq.com/docs/changelog/v1.19.2

### Licensing sources

- https://github.com/formkiq/formkiq-core

- https://formkiq.com/pricing/

### Infrastructure sources

- https://docs.formkiq.com/docs/platform/overview

- https://github.com/formkiq/formkiq-core/releases/tag/v1.19.2

- https://docs.formkiq.com/docs/changelog/v1.19.2


### 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 commercial-edition tutorial integrates SAML through Amazon Cognito managed login and requires stack/app-client configuration. The tutorial targets Essentials, Advanced or Enterprise; Cognito Essentials/Plus tier is a separate AWS prerequisite. Scope: FormKiQ Essentials/Advanced/Enterprise console SSO; not an unqualified Core or solution entitlement. Source: https://docs.formkiq.com/docs/tutorials/Identity%20Management/microsoft-entra-id (reviewed 2026-11-14). Supporting source: Cognito managed-login configuration — https://docs.formkiq.com/docs/tutorials/Identity%20Management/cognito-saml-provider.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The architecture documents encryption in transit/at rest, JWT/IAM/API-key authentication and site-level access boundaries. Advanced access-control options and SSO depend on the commercial configuration. These are documented controls, not a customer-deployment attestation. Scope: FormKiQ platform architecture; confirm the selected edition, modules and deployed configuration. Source: https://docs.formkiq.com/docs/platform/overview (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Core quickstart publishes region-specific CloudFormation templates; this artifact is the reviewed us-east-1 template for Core 1.19.2. Essentials, Advanced and Enterprise use customer-specific templates supplied by FormKiQ. Scope: FormKiQ Core 1.19.2 only; commercial editions and configured solutions need their own deployment scope. Source: https://docs.formkiq.com/docs/getting-started/quick-start (reviewed 2026-11-14). Deployment artifact: https://formkiq-core-distribution-us-east-1.s3.amazonaws.com/1.19.2/template.yaml. Artifact reference: Core 1.19.2; us-east-1.

- Minimum footprint / sizing: Documented. Core uses managed AWS services and does not require customer-operated application servers. Optional search, private networking and integrations can add VPC, container or search capacity. No fixed workload capacity or total monthly operating cost follows from this architecture. Scope: Core application runtime; optional search and commercial modules sized separately. Source: https://docs.formkiq.com/docs/platform/overview (reviewed 2026-11-16).

- License pricing: Documented. Core has no software license charge. Annual production license prices are USD 18,000 for Essentials and USD 26,000 for the Advanced base platform. Enterprise is quoted. AWS usage, Advanced add-on modules and services are separate; three-month proof-of-value terms differ. Scope: Base editions, not total solution or operating costs; prices checked 2026-11-16. Source: https://formkiq.com/pricing/ (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.19.2, 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 formkiq/formkiq-core release record; commercial editions and deployment packages may differ. Source: https://github.com/formkiq/formkiq-core/releases/tag/v1.19.2 (reviewed 2026-11-14).




### Security and lifecycle reviews

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

- FormKiQ Core 1.19.2 authorization and deployment review (security-advisory): The release restores caller authorization for upload-URL and watermarked-download generation and hardens AWS deployment configuration. Scope: FormKiQ Core 1.19.2 release notes; this is not an assertion that every commercial edition or configured solution is affected. Conditions: Exposure depends on deployed authorization paths and infrastructure. The release does not establish a complete affected-version range or a CVE. Action: Review the authorization fixes and upgrade sequence, including the Typesense secret parameter and certificate templates. Source: https://github.com/formkiq/formkiq-core/releases/tag/v1.19.2; reviewed 2026-11-17.




## Foswiki

Self-hosted enterprise wiki with structured forms, revision history and attachments.

- Listing: https://launchinyourcloud.com/directory/foswiki/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0-or-later for Foswiki; bundled extensions can have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Foswiki application, web server and persistent wiki 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://foswiki.org/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS TurnKey and Azure cloudimg are independent repackagers. Appliance and upstream Foswiki version numbers must remain separate. Verify the packaged Foswiki version and apply the access-control corrections supplied in 2.1.11 or a compatible later release.

GNU GPL-2.0-or-later for Foswiki; bundled extensions can have separate terms.

Foswiki application, web server and persistent wiki data. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted enterprise wiki with structured forms, revision history and attachments.

### Deployment boundaries


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

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


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-lz2gv45alfwki
  Foswiki application, web server and persistent wiki data. AWS TurnKey and Azure cloudimg are independent repackagers. Appliance and upstream Foswiki version numbers must remain separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki
  Foswiki application, web server and persistent wiki data. AWS TurnKey and Azure cloudimg are independent repackagers. Appliance and upstream Foswiki version numbers must remain separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes gac410, MichaelDaum, LievenLitaer, 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/foswiki/distro/graphs/contributors

- Upstream project: https://github.com/foswiki/distro

### Sources

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

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki

- GPL-2.0 COPYING: https://raw.githubusercontent.com/foswiki/distro/master/core/COPYING

- GitHub Tags: https://github.com/foswiki/distro/tags

- Selected edition licence text: https://raw.githubusercontent.com/foswiki/distro/master/core/LICENSE

- Foswiki access-control corrections: https://github.com/foswiki/distro/releases/tag/FoswikiRelease02x01x11

### Licensing sources

- https://raw.githubusercontent.com/foswiki/distro/master/core/COPYING

- https://raw.githubusercontent.com/foswiki/distro/master/core/LICENSE

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki


### Buyer diligence


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

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


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. 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: Foswiki selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.foswiki?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Supporting source: AWS delivery and package version — https://aws.amazon.com/marketplace/pp/prodview-lz2gv45alfwki. Offer cloudimg1647283583153.foswiki: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.foswiki. Offer prodview-lz2gv45alfwki: TurnKey GNU/Linux; Amazon Machine Image (AMI); package 19.0.3; https://aws.amazon.com/marketplace/pp/prodview-lz2gv45alfwki.

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

- Single sign-on: Documented. Foswiki's published SamlLoginContrib extension documents SAML 2.0 authentication, service-provider metadata, signing keys and a SAML LoginManager. Install and configure the extension separately; this is an extension path, not evidence that a particular marketplace image has it enabled or that LDAP alone supplies SSO. Scope: Foswiki with SamlLoginContrib version 14 documentation (December 2025); verify extension/dependency compatibility with the selected package. Source: https://foswiki.org/Extensions/SamlLoginContrib (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 publishes the 2.1.11 source/archive distribution and an installation guide covering the Perl/web-server dependencies, archive extraction, Apache configuration and configure workflow. This is upstream application installation; the Azure/AWS repackager images have separate package versions and defaults. Scope: Foswiki upstream installation; verify the selected OS, Perl modules, extensions and provider package separately. Source: https://foswiki.org/System/InstallationGuide (reviewed 2026-11-20). Deployment artifact: https://foswiki.org/Download/FoswikiRelease02x01x11. Artifact reference: FoswikiRelease02x01x11 / Foswiki 2.1.11 upstream distribution.

- Minimum footprint / sizing: Sources checked — unresolved. The official installation guide lists web-server/Perl dependencies and configuration steps but does not establish a quantitative whole-host CPU/RAM/storage floor for the proposed wiki. Content, attachments, search/extensions, concurrent users and backups require workload sizing. Scope: Foswiki application and chosen extensions; dependency prerequisites and marketplace VM sizes are not universal production/HA minima. Source: https://foswiki.org/System/InstallationGuide (reviewed 2026-11-20).

- License pricing: Documented. GNU GPL-2.0-or-later for Foswiki; bundled extensions can have separate terms. Scope: Foswiki; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/foswiki/distro/master/core/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Foswiki access-control corrections (security-advisory): Foswiki 2.1.11 fixes access checks in changes, preview, viewfile and oops handling. Scope: CVE-2026-2861 and the Foswiki 2.1.11 release notes; check individual scripts and the installed application version. Conditions: Third-party appliance and VM package labels do not by themselves establish the included Foswiki patch level. Action: Verify the packaged Foswiki version and apply the access-control corrections supplied in 2.1.11 or a compatible later release. Source: https://github.com/foswiki/distro/releases/tag/FoswikiRelease02x01x11; reviewed 2026-11-19.




## Hyland OnBase On-Premise

Customer-hosted enterprise content and case platform for document-heavy business processes.

- Listing: https://launchinyourcloud.com/directory/onbase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial OnBase licenses and separately scoped modules
- Licensing model: commercial-only
- Installation: Vendor or partner-assisted on-premises installation
- Architecture: Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.
- Operations: Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
- Product website: https://www.hyland.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This entry covers licensed OnBase on-premises deployments. Category memberships describe documented platform configurations and integrations, not separately included turnkey applications. Loan tracking, claims integrations and other service solutions need scope and licensing confirmation.

The selected OnBase on-premises product is commercially licensed. Its current on-premises terms restrict production copies and require applicable fees for additional environments and certain access; modules and integrations follow the contracted scope.

Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.


### Category fit

- document-management: Enterprise content repository with capture, document workflows and integration with business applications.

- records-management: Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.

- contract-management: Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.

- financial-application-management: Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.

- case-management: Configurable case applications connect case data, documents, tasks and approvals.

- correspondence-management: Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.

- vendor-supplier-document-management: Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.

- hr-employee-records-management: Employee-file access, applicant-document routing and employee onboarding/offboarding workflows.

- policy-procedure-management: Electronic policy distribution and policy/procedure sign-off workflows in the HR document-management scope.

- claims-management: Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.

- workflow-automation: Content and case workflows with routing, rules and low-code WorkView applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 


### Cloud deployment evidence

- Hyland partner statement on customer-managed OnBase cloud deployments (aws, azure, gcp): https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/
  Hyland-authorized integration partner Reveille explicitly describes OnBase 18+ in customer-managed AWS, Azure and Google Cloud environments, separately from OnBase Cloud. This is the partner's compatibility statement, not a Hyland installation guide or cloud-support certification. Confirm the current OnBase release, Windows/database topology, licenses and vendor support agreement; Reveille itself is not required for self-hosting.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed. Versions: OnBase 18+ in partner statement; confirm current release.

- Hyland identification of Reveille as an authorized integration partner (aws, azure, gcp): https://www.hyland.com/en/partners/reveille
  Hyland identifies Reveille as an authorized build partner for OnBase and other Hyland platforms. This corroborates the source relationship, not an independent certification of every deployment listed by the partner; use its customer-managed-cloud statement together with OnBase installation and commercial requirements.
  Source type: partner-relationship; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- OnBase platform capabilities: https://www.hyland.com/en/solutions/products/onbase

- On-premises product terms: https://legal.hyland.com/pst-on-premise-multi-products

- WorkView business application examples: https://www.hyland.com/en/resources/articles/workview-product-overview

- HR files and policy sign-offs: https://www.hyland.com/en/resources/terminology/human-resources/document-management

- OnBase workflow routing: https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview

- Correspondence document integration: https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction

- Loan-document tracking solution: https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking

- Insurance claims integration case study: https://www.hyland.com/en/customers/p-c-insurer

### Licensing sources

- https://legal.hyland.com/pst-on-premise-multi-products

### Infrastructure sources

- https://legal.hyland.com/pst-on-premise-multi-products


### 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 Foundation 26.1 Web Client documents Integration for Single Sign-On and configuration of automatic login. Hyland identity-service authentication is also module-specific; confirm client coverage, identity-provider compatibility and licensed integrations for the selected solution. Scope: OnBase Foundation 26.1 Web Client configuration; not a blanket claim for every module. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Configuration/Web.config-Configuration/appSettings?contentId=stz0b9kK0lYB~c4sf1hbkA (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 Foundation 26.1 Web Server is delivered through vendor setup.exe/MSI installation media with documented interactive and silent configuration. Application Server installation is a prerequisite; no public cloud-provisioning template is established by this installer guide. Scope: Vendor-supplied OnBase Web Server installation media, not public IaC. Source: https://docs.hyland.com/r/OnBase/Web-Server/Foundation-26.1/Web-Server/Installation/Installation/Running-the-Installer?contentId=6JGslGq~Cra0GizajFYkbA (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. Foundation 26.1 lists a 2.4-GHz dual-core minimum, 4 GB RAM for Web Server and 8 GB for 64-bit Application Server, with 16 GB recommended for each. These are dedicated-role requirements; database, files, other modules, HA and workload capacity are additional. Scope: OnBase Foundation 26.1 Web/Application role minima; not the complete solution. Source: https://docs.hyland.com/r/OnBase/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Foundation-26.1/Technical-Requirements-Overview-for-New-Installations-and-Upgrades/Part-6-Web/Application-Server-and-Core-Services-Hardware-Requirements/64-Bit-Server-Hardware-Requirements?contentId=UToZTDrd9HvkQpjb7tURJQ (reviewed 2026-11-20).

- License pricing: Documented. The current on-premises terms distinguish production, disaster-recovery and separately licensed non-production use. Confirm the purchased product/client/API permissions and environments in the agreement; these terms do not supply a public total price. Scope: OnBase on-premises terms v1.2, effective 2026-06-23; customer order may add conditions. Source: https://legal.hyland.com/pst-on-premise-multi-products (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Joplin Server

Personal-use self-hosted synchronization server for Joplin notes.

- Listing: https://launchinyourcloud.com/directory/joplin-server/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.
- Licensing model: source-available
- Installation: Cloudron package; Docker / Compose
- Architecture: Joplin Server, database and persistent 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://joplinapp.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 Server Personal Use License permits personal non-commercial use and restricts use by business entities and commercial sharing without written permission. This is not a default option for a 100-user business deployment. Desktop/client licences and releases do not establish server rights or Server 3.7.6 publication dates.

Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization.

Joplin Server, database and persistent attachment storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Personal-use self-hosted synchronization server for Joplin notes.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/joplin-server.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.


### Sources

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

- Hostinger: https://www.hostinger.com/applications/joplin-server

- Joplin Server Personal Use License: https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md

- GitHub Releases: https://github.com/laurent22/joplin/releases

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

### Licensing sources

- https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md

### Infrastructure sources

- https://www.cloudron.io/store/joplin-server.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. Joplin Server documents SAML user authentication using SP/IdP configuration and server environment settings. Its API and website must use the same base URL for SAML. Commercial organisational use requires the appropriate Server Business rights; this does not establish hosted Cloud plan entitlements. Scope: Self-hosted Joplin Server SAML; supported clients, session policy and business licensing must be checked. Source: https://joplinapp.org/help/apps/server/saml/ (reviewed 2026-11-20). Supporting source: Server Business and self-hosted licensing context — https://joplinapp.org/help/apps/joplin_server_business/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official server README provides versioned Docker images and a production PostgreSQL/Compose setup; the SQLite example is for testing. Configure public URL, database, credentials and reverse proxy before use. Select the appropriate commercial licence for an organisation. Scope: Joplin Server application plus separately provisioned production database and persistent content storage. Source: https://github.com/laurent22/joplin/blob/dev/packages/server/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/laurent22/joplin/blob/dev/docker-compose.server.yml. Artifact reference: dev (moving branch); use a compatible published server image tag.

- Minimum footprint / sizing: Documented. The Server Business guide lists two CPU cores/four threads, at least 4 GB RAM (8 GB recommended) and 50 GB SSD plus content growth. These are moderate-load deployment requirements, not the smaller Cloudron package allocation or a validated 100-user, 1 TB HA topology. Scope: Joplin Server Business self-hosted baseline; provider-package allocations, external content storage and redundancy are separate. Source: https://joplinapp.org/help/apps/joplin_server_business/ (reviewed 2026-11-20). Supporting source: Previously reviewed Cloudron app package allocation — https://www.cloudron.io/store/joplin-server.html.

- License pricing: Edition-dependent. Joplin Server Personal Use License; personal non-commercial use only unless the vendor provides written authorization. Scope: Joplin Server; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/laurent22/joplin/dev/packages/server/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Laserfiche Self-Hosted

Self-hosted document and records platform with forms and configurable business process automation.

- Listing: https://launchinyourcloud.com/directory/laserfiche-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial self-hosted software; license and module entitlements apply
- Licensing model: commercial-only
- Installation: Licensed Laserfiche 12 Windows installers
- Architecture: Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.
- Operations: Customer operates supported Windows servers, repository/database backups and product updates; follow the chosen modules installation requirements.
- Product website: https://www.laserfiche.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 self-hosted product. Use-case pages describe platform workflows; confirm availability and licensing for the chosen version and modules. The current support matrix requires Windows Server Desktop Experience and explicitly excludes Docker and Kubernetes deployment for self-hosted applications.

This record covers the commercial self-hosted Laserfiche product. Installation and activation require licensed application entitlements; marketplace templates do not confer a license to the underlying platform.

Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.


### Category fit

- document-management: Repository, capture, search and document process automation on customer-operated servers.

- records-management: Document lifecycle, retention, access controls and disposition; configure schedules for the organization.

- contract-management: Configurable contract creation, approval and records workflows; confirm the selected self-hosted modules.

- financial-application-management: Document routing and automation for loan applications, illustrated by the vendor banking case study.

- case-management: Forms, repository content and process workflows for service case management; implementation is configured to the case process.

- hr-employee-records-management: Employee records, onboarding approvals and access controls for HR processes.

- claims-management: Low-code claims review and approval workflows; does not establish an insurance policy or adjudication core.

- workflow-automation: Forms and document workflows for routing, approvals and task automation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Laserfiche reseller installation terms for customer AWS and Azure environments (aws, azure): https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf
  Cities Digital installation terms, published in the municipal meeting packet on PDF page 40, explicitly cover new Azure or AWS environments and exclude Laserfiche Cloud from that section. The client supplies Windows, SQL Server and network configuration and validates workflows. This documents a reseller-assisted self-hosted path; confirm the current server version, license, support scope and implementation fees.
  Source type: public-procurement-record; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted installation overview: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- Current operating system and deployment support: https://support.laserfiche.com/kb/1012418/raw

- Business process solutions: https://www.laserfiche.com/solutions/

- Document and records capabilities: https://www.laserfiche.com/products/document-and-records-management/

- Loan application automation case study: https://www.laserfiche.com/resources/customer-stories/growin-bank-expedites-loan/

- Insurance claims workflows: https://www.laserfiche.com/solutions/financial-services/insurance/

- Software license agreement and legal resources: https://www.laserfiche.com/legal/

### Licensing sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://www.laserfiche.com/legal/

### Infrastructure sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://support.laserfiche.com/kb/1012418/raw


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 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. Laserfiche 12 Directory Server accepts SAML 2.0 identity providers using imported metadata and claim mappings. Configure the licensing site, client integrations and local-account policy; this does not establish every optional module or Cloud entitlement. Scope: Laserfiche 12 self-hosted Directory Server federation. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/admin-lfds-saml-identity-provider.htm (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. Laserfiche 12 uses a product installer that selects applications, detects installed versions and offers updates. Follow new-installation, repository and system-specification instructions; this page is not a public IaC package. Scope: Laserfiche self-hosted version 12 installer and initial configuration. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The current supported-platforms list establishes Windows Server and database compatibility, but does not supply a complete Laserfiche 12 CPU/RAM topology. Public numeric checklists found cover version 11 or older. Obtain a version-12 component and HA sizing design rather than applying those legacy minima. Scope: Laserfiche 12 self-hosted hardware sizing unresolved. Source: https://support.laserfiche.com/kb/1012418/pdf (reviewed 2026-11-20). Supporting source: Older version-11 server minimum is not a version-12 sizing recommendation — https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Subsystems/LFAdmin/Content/Installation/Laserfiche_Server_%28United%29_pre_check.htm.

- License pricing: Sources checked — unresolved. The self-hosted Directory Server workflow requires a licensing site registering the repository server. The reviewed integration documentation does not establish current licence prices, user metrics or maintenance terms; obtain an on-premises quote rather than applying Laserfiche Cloud prices. Scope: Self-hosted licence delivery established; commercial pricing and terms unresolved. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/config-lfm-configuration-page-connection.htm (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Limina DEID Container

Commercial containerized de-identification engine for sensitive text and document processing.

- Listing: https://launchinyourcloud.com/directory/limina/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Customer EKS Helm deployment or AWS ECS CloudFormation stack running licensed CPU or GPU containers.
- 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.getlimina.ai/installation/aws/eks-guide
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Formerly Private AI. The automated ECS stack is a prototyping starting point and production guide, with capacity and security review required. Website terms do not substitute for the applicable container licence/order. Redaction output still needs disclosure-policy and accuracy review.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Customer EKS Helm deployment or AWS ECS CloudFormation stack running licensed CPU or GPU containers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- freedom-of-information: Commercial containerized de-identification engine for sensitive text and document processing.

- document-management: Commercial containerized de-identification engine for sensitive text and document processing.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.getlimina.ai/installation/aws/eks-guide (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS Guide (aws): https://docs.getlimina.ai/installation/aws/eks-guide
  Customer EKS Helm deployment or AWS ECS CloudFormation stack running licensed CPU or GPU containers. Formerly Private AI. The automated ECS stack is a prototyping starting point and production guide, with capacity and security review required. Website terms do not substitute for the applicable container licence/order. Redaction output still needs disclosure-policy and accuracy review.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS EKS Guide: https://docs.getlimina.ai/installation/aws/eks-guide

- AWS ECS CloudFormation: https://docs.getlimina.ai/installation/aws/automated-ecs-guide

- Terms of Use: https://www.getlimina.ai/en/terms-of-use

- OpenAPI v4.5.2: https://docs.getlimina.ai/openapi/privateai_4.5.2.json

- GitHub Org: https://github.com/privateai

### Licensing sources

- https://www.getlimina.ai/en/terms-of-use

### Infrastructure sources

- https://docs.getlimina.ai/installation/aws/eks-guide


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 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 reviewed container deployment documentation establishes deployment/cluster access and API-oriented processing, but does not establish external SAML/OIDC user sign-in for the DEID container itself. AWS IAM/EKS identity and a separately hosted customer portal are not proof of application-user federation. Scope: Limina self-hosted DEID container user/authentication surface; hosted API and portal capabilities are not transferred. Source: https://docs.getlimina.ai/installation/aws/eks-guide (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. Limina publishes nested CloudFormation templates to provision an EC2-backed ECS cluster, networking, bastion and the CPU container. The guide describes a prototyping starting point and production guide, not production validation. GPU use needs AMI, ECS agent and task changes; changing only the image tag is insufficient. Scope: Limina CPU-container AWS ECS template; review nested files, IAM, secrets, capacity and selected container entitlement. Source: https://docs.getlimina.ai/installation/aws/automated-ecs-guide (reviewed 2026-11-20). Deployment artifact: https://privateai-infrastructure.s3.amazonaws.com/ecs/main.yaml. Artifact reference: main.yaml at an unversioned S3 URL; retain/pin the reviewed parent and nested templates.

- Minimum footprint / sizing: Documented. The EKS guide calls for worker memory greater than 16 GB; the GPU variant also needs a GPU-enabled node image and more than 30 GB disk. It recommends a larger instance such as m5zn.3xlarge for image/PDF processing. These are deployment recommendations, not a complete model/concurrency or HA capacity guarantee. Scope: Limina EKS worker guidance; select CPU/GPU container, models, storage and replica capacity for the actual workload. Source: https://docs.getlimina.ai/installation/aws/eks-guide (reviewed 2026-11-20).

- License pricing: Sources checked — unresolved. The public website Terms of Use do not establish the self-hosted DEID container’s commercial licence, price or support rights; obtain the applicable software agreement. Scope: Selected self-hosted commercial product; contract confirmation remains necessary. Source: https://www.getlimina.ai/en/terms-of-use (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## LiquidFiles (Self-Hosted Virtual Appliance)

Commercial self-hosted appliance for controlled external file delivery and shared files.

- Listing: https://launchinyourcloud.com/directory/liquidfiles/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: VM image
- Architecture: LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image.
- 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.liquidfiles.com/install/ec2.html
- 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 documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted appliance for controlled external file delivery and shared files.

- data-rooms-ma-document-management: Commercial self-hosted appliance for controlled external file delivery and shared files.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/ec2.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/azure.html (checked 2026-11-19). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.liquidfiles.com/install/digital_ocean.html (checked 2026-11-19). 


### Cloud deployment evidence

- EC2 Guide (aws): https://docs.liquidfiles.com/install/ec2.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://docs.liquidfiles.com/install/azure.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- DigitalOcean Guide (digitalocean): https://docs.liquidfiles.com/install/digital_ocean.html
  LiquidFiles virtual appliance and persistent transfer storage on EC2, Azure VMs or a DigitalOcean custom image. The vendor documents all three actual appliance deployments. Expiring shares, FileDrops and delivery controls are distinct from a full transaction-management platform. Match appliance licences, current supported release and storage/backup requirements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- EC2 Guide: https://docs.liquidfiles.com/install/ec2.html

- Azure Guide: https://docs.liquidfiles.com/install/azure.html

- DigitalOcean Guide: https://docs.liquidfiles.com/install/digital_ocean.html

- License Overview: https://docs.liquidfiles.com/license/overview.html

- v4.3.x Release Notes: https://docs.liquidfiles.com/release_notes/version_4-3-x.html

### Licensing sources

- https://docs.liquidfiles.com/license/overview.html

### Infrastructure sources

- https://docs.liquidfiles.com/install/ec2.html

- https://docs.liquidfiles.com/install/azure.html

- https://docs.liquidfiles.com/install/digital_ocean.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 appliance supports SAML sign-on, metadata exchange, email NameID and group assignment, with optional per-group enforcement. The vendor documents a safeguard local-login path and warns against forcing every external user into the internal IdP. Scope: Self-hosted LiquidFiles SAML authentication. Source: https://docs.liquidfiles.com/authentication/sso_using_saml.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 vendor documents deployment from its EC2 appliance AMI, with cloud-instance, storage and network configuration steps. The appliance contains its own OS; this is a vendor appliance installation path, not an upstream Terraform or CloudFormation template. Select the current regional image and licence. Scope: Official AWS appliance deployment; infrastructure provisioning remains customer work. Source: https://docs.liquidfiles.com/install/ec2.html (reviewed 2026-11-20). Deployment artifact: https://docs.liquidfiles.com/install/ec2.html. Artifact reference: Regional AMI selection described in vendor guide.

- Minimum footprint / sizing: Documented. The vendor recommends 1–2 CPUs, 2 GB RAM and 10 GB disk plus transfer storage. One GB RAM is for testing and can swap. File volume, disk/network throughput, backup and HA must be sized separately; the appliance OS is included. Scope: Vendor appliance baseline; transfer storage and HA excluded. Source: https://docs.liquidfiles.com/install/system_requirements.html (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: LiquidFiles (Self-Hosted Virtual Appliance); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.liquidfiles.com/license/overview.html (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## LogicalDOC Commercial On-Premise

Customer-hosted commercial document platform for controlled business files and supplier documentation.

- Listing: https://launchinyourcloud.com/directory/logicaldoc-commercial/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial edition under LogicalDOC EULA; separate Community Edition exists
- Licensing model: commercial-only
- Installation: Licensed on-premises server installation
- Architecture: Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.
- Operations: Customer manages application, database, document storage, backups and upgrades; agree support scope and required commercial capabilities.
- Product website: https://www.logicaldoc.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 a licensed commercial on-premises edition, not Community Edition feature parity. The supplier-document example uses configured metadata, expiry dates and periodic reports; it is a document process rather than a supplier-assessment service.

The selected licensed commercial edition follows LogicalDOC EULA restrictions. This classification does not cover the separate open-source Community Edition.

Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.


### Category fit

- document-management: Searchable repository, metadata, versioning and configurable document workflows in a commercial on-premises deployment.

- vendor-supplier-document-management: Supplier certificate storage, expiry tracking and configured reports, documented in the Lesepidado implementation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 


### Cloud deployment evidence

- LogicalDOC private-cloud deployment options (aws, azure, gcp): https://www.logicaldoc.com/
  The vendor explicitly offers private-cloud installation on AWS, Azure and Google Cloud, separately from its managed LogicalDOC Cloud service. Confirm the commercial edition, system requirements and support agreement.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- On-premises deployment: https://www.logicaldoc.com/product/on-premise-dms

- Application and storage architecture: https://www.logicaldoc.com/product/architecture

- On-premises supplier certificate implementation: https://www.logicaldoc.com/blog/660-lesepidado-logicaldoc-case-study

- Commercial end-user license: https://www.logicaldoc.com/eula

### Licensing sources

- https://www.logicaldoc.com/eula

### Infrastructure sources

- https://www.logicaldoc.com/product/on-premise-dms

- https://www.logicaldoc.com/product/architecture


### 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 commercial administration guide documents SAML 2.0 service-provider integration, login-time account creation and optional single logout. It does not establish that every Business/Enterprise license includes the feature; confirm licensed features and test the identity provider. Scope: Commercial LogicalDOC documentation; edition/contract entitlement not established. Source: https://docs.logicaldoc.com/en/access-control/saml-single-sign-on (reviewed 2026-11-14).

- SCIM provisioning: Sources checked — unresolved. The SAML guide describes user creation at first login. It does not establish a SCIM provisioning/deprovisioning API or licensed entitlement; login-time account creation must not be labeled SCIM. Scope: SAML/JIT documentation checked; SCIM remains unresolved. Source: https://docs.logicaldoc.com/en/access-control/saml-single-sign-on (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes a logicaldoc/logicaldoc image and links its Docker distribution source. A licence activation code is required, including for evaluation. The catalog entry is dated 2018; confirm a currently supported image tag and matching database/Java requirements before adopting it. Scope: Vendor commercial Docker distribution; current supported artifact version must be confirmed. Source: https://www.logicaldoc.com/download/docker-images (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/logicaldoc/logicaldoc/. Artifact reference: Select a vendor-supported immutable image; catalog entry date is not a current release.

- Minimum footprint / sizing: Documented. The current vendor matrix specifies a dedicated 64-bit 2.5-GHz eight-core server, 24 GB memory and 512 GB fast disk for application deployment. It lists JDK 25 and current OS baselines. Concurrency, repository data, configuration and HA require additional sizing; older installation guides show different minima. Scope: Current vendor commercial-server requirements; verify against selected release. Source: https://www.logicaldoc.com/resources/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. The on-premises offer requires commercial licences and directs buyers to request a quote. No numeric price is established by the reviewed product page. Agree user counts, edition, term and maintenance separately from hosting and operating costs. Scope: Commercial on-premises offer; quoted licence terms, not Community pricing. Source: https://www.logicaldoc.com/product/on-premise-dms (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## M-Files On-Premises

Customer-operated document vault and information-governance platform with metadata-driven workflows.

- Listing: https://launchinyourcloud.com/directory/m-files-on-premises/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription software; on-premises and support entitlements follow the order
- Licensing model: commercial-only
- Installation: Licensed Windows Server installation; vendor implementation planning
- Architecture: Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.
- Operations: Customer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.
- Product website: https://www.m-files.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Only customer-operated M-Files deployment is listed. The documented SOP and records patterns require configuration and possibly selected components. Confirm the available edition, deployment scope and integrations rather than assuming that every separately packaged cloud solution is included.

Commercial M-Files server subscription software. The EULA covers ordered on-premises or cloud software and associated licenses/support; this entry selects on-premises operation.

Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.


### Category fit

- document-management: Metadata-driven document vaults with controlled access, document relationships and workflows.

- records-management: Configurable records retention and disposition rules with document history and audit trails.

- policy-procedure-management: Configured SOP, compliance and training workflows supported by metadata, permissions and document lifecycle controls; not a separately verified turnkey policy module.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 


### Cloud deployment evidence

- M-Files self-managed cloud deployment (aws, azure, gcp): https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html
  The vendor documents customer-managed Windows Server virtual machines on AWS, Azure and Google Cloud as the same server deployment model used on-premises. This is distinct from M-Files Cloud; confirm server, vault/database and licensing requirements.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated deployment options: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html

- Records retention and disposition: https://www.m-files.com/supplemental/records-management/

- SOP, training and governance application patterns: https://www.m-files.com/wp-content/uploads/2023/07/How-M-Files-Mitigates-Risks-for-Accounting-Firms.pdf

- Software subscription license agreement: https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ

### Licensing sources

- https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ

### Infrastructure sources

- https://userguide.m-files.com/user-guide/latest/eng/deployment_options.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 vault authentication guide explicitly links on-premises Microsoft Entra configuration and OAuth 2.0/OIDC providers for any environment. Client/web-add-in configuration and licensed implementation requirements remain separate. Scope: M-Files document-vault authentication; not Hubshare or automatic cloud login setup. Source: https://userguide.m-files.com/user-guide/latest/eng/document_vault_authentication.html (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The guide documents subscription-level SCIM for on-premises servers joined to M-Files Manage. A separate vault-level Entra SCIM method requires Entra ID Premium and limits Entra authentication to Desktop; on-premises plugin-based synchronization is also documented. Scope: M-Files on-premises provisioning; Manage connection, method and client limitations differ. Source: https://userguide.m-files.com/user-guide/latest/eng/user_synchronization_entra_id.html (reviewed 2026-11-16).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies an installation package containing Server, Admin and optional desktop components. The guide links the latest package through the vendor download portal and documents advanced installation options. Package access and entitlements must be obtained; this is not a public infrastructure template. Scope: Current on-premises Windows installer distribution. Source: https://www.userguide.m-files.com/user-guide/latest/eng/Installing_the_software.html (reviewed 2026-11-20). Deployment artifact: https://product.m-files.com/downloads/. Artifact reference: Vendor latest-download portal; authenticated or entitled access may be required.

- Minimum footprint / sizing: Documented. The single-server guide lists 2 CPU cores, 1 GB RAM and 300 MB for M-Files Server itself. Its examples scale to 4 cores/4 GB for 50,000 objects and 8 cores/16 GB plus SQL Server for one million. File storage, database, backups and HA need separate sizing; these are object-count examples, not a 100-user guarantee. Scope: Vendor single-server guidelines; application storage and HA excluded. Source: https://userguide.m-files.com/user-guide/latest/eng/hardware_guidelines_for_single_server_environments.html (reviewed 2026-11-20).

- License pricing: Documented. The on-premises server is linked to a customer subscription using an initial licence from M-Files Manage. Automated renewal needs outbound licensing endpoints. This establishes subscription/licence delivery, not a published per-user price or infrastructure cost. Scope: On-premises server subscription and licence automation. Source: https://userguide.m-files.com/user-guide/latest/eng/?contextId=133304 (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## MyWorkDrive

Commercial private-cloud file access and controlled sharing across organizations.

- Listing: https://launchinyourcloud.com/directory/myworkdrive/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: VM image; Package / binary installer
- Architecture: MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure.
- 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.myworkdrive.com/file-server/cloud/aws
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The M&A use case concerns cross-organization access to files, including after a transaction. It is not a complete deal-process or legal-review application. Directory integration, share permissions, externally shared data and licence counts require deliberate configuration.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial private-cloud file access and controlled sharing across organizations.

- data-rooms-ma-document-management: Commercial private-cloud file access and controlled sharing across organizations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.myworkdrive.com/file-server/cloud/aws (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.myworkdrive.com/file-server/azure (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Guide (aws): https://www.myworkdrive.com/file-server/cloud/aws
  MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure. The M&A use case concerns cross-organization access to files, including after a transaction. It is not a complete deal-process or legal-review application. Directory integration, share permissions, externally shared data and licence counts require deliberate configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Guide (azure): https://www.myworkdrive.com/file-server/azure
  MyWorkDrive application and controlled file shares on customer AWS or Azure Windows infrastructure. The M&A use case concerns cross-organization access to files, including after a transaction. It is not a complete deal-process or legal-review application. Directory integration, share permissions, externally shared data and licence counts require deliberate configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Guide: https://www.myworkdrive.com/file-server/cloud/aws

- Azure Guide: https://www.myworkdrive.com/file-server/azure

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

- M&A Data Room: https://www.myworkdrive.com/mergers-acquisitions

- Pricing Plans: https://www.myworkdrive.com/pricing-plans

- Release Notes: https://www.myworkdrive.com/kb/articles/server-release-notes

### Licensing sources

- https://www.myworkdrive.com/pricing-plans

### Infrastructure sources

- https://www.myworkdrive.com/file-server/cloud/aws

- https://www.myworkdrive.com/file-server/azure


### 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: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from MyWorkDrive. Its package version is MyWorkDrive File Sharing Server 7.3.1.48; verify the contained application and required entitlements separately. Scope: MyWorkDrive selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-6mpsk5rxrewac (reviewed 2026-11-19). Offer prodview-6mpsk5rxrewac: MyWorkDrive; Amazon Machine Image (AMI); package MyWorkDrive File Sharing Server 7.3.1.48; https://aws.amazon.com/marketplace/pp/prodview-6mpsk5rxrewac.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Active Directory mode supports SAML 2.0 providers, including Entra ID, Okta and OneLogin, with optional SSO enforcement. Entra ID directory mode uses native Microsoft login instead; select the identity mode at installation and review delegation and logout configuration. Scope: Server identity mode affects the authentication path. Source: https://www.myworkdrive.com/kb/articles/server-setup-guide (reviewed 2026-11-20). Supporting source: Entra ID mode differs from SAML mode — https://www.myworkdrive.com/kb/articles/getting-started-with-myworkdrive-version-7-using-entra-id-identity-and-azure-storage.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The server setup guide uses MyWorkDrive-Setup.exe downloaded from the customer portal, installing required IIS/.NET components. It documents administrator-run Windows installation and activation; this is customer-delivered software, not a public cloud provisioning template. Scope: Vendor Windows server installer delivery. Source: https://www.myworkdrive.com/kb/articles/server-setup-guide (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. The server guide requires a dedicated supported Windows server, at least 2 virtual CPUs and 4 GB RAM, and recommends 60 GB disk for OS, software, logs and temporary files. File storage, directory services and HA are additional; larger workloads require the vendor sizing guide. Scope: Dedicated access server minimum; file storage and HA excluded. Source: https://www.myworkdrive.com/kb/articles/server-setup-guide (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: MyWorkDrive; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.myworkdrive.com/pricing-plans (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## NirvaShare

Commercial self-hosted gateway for controlled sharing of customer object storage.

- Listing: https://launchinyourcloud.com/directory/nirvashare/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; VM image
- Architecture: NirvaShare application services on a customer VM with configured object-storage and identity-provider access.
- 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-k6zpjoiopyrzs
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

NirvaShare application services on a customer VM with configured object-storage and identity-provider access. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial self-hosted gateway for controlled sharing of customer object storage.

- data-rooms-ma-document-management: Commercial self-hosted gateway for controlled sharing of customer object storage.

### Deployment boundaries


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

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/nirvashare (checked 2026-11-19). 

- vultr: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://nirvashare.com/docs/deployment/cloud-platforms/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace CFT (aws): https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/nirvashare
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Cloud Platforms (vultr): https://nirvashare.com/docs/deployment/cloud-platforms/
  NirvaShare application services on a customer VM with configured object-storage and identity-provider access. The named provider paths install the application; connecting to another provider's storage or identity service does not add that provider's hosting badge. Review the actual packaged OS/application versions and the selected identity and sharing entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

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

- DO Marketplace: https://marketplace.digitalocean.com/apps/nirvashare

- Cloud Platforms: https://nirvashare.com/docs/deployment/cloud-platforms/

- AWS CFT Docs: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/

- Pricing: https://nirvashare.com/pricing/

- Release Notes: https://nirvashare.com/release-notes/

### Licensing sources

- https://nirvashare.com/pricing/

### Infrastructure sources

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

- https://marketplace.digitalocean.com/apps/nirvashare

- https://nirvashare.com/docs/deployment/cloud-platforms/


### 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: Documented. The reviewed AWS offer delivers CloudFormation Template (CFT) from Nirvato Software Pvt Ltd. Its package version is 6.4.1; verify the contained application and required entitlements separately. Scope: NirvaShare selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs (reviewed 2026-11-19). Offer prodview-k6zpjoiopyrzs: Nirvato Software Pvt Ltd; CloudFormation Template (CFT); package 6.4.1; https://aws.amazon.com/marketplace/pp/prodview-k6zpjoiopyrzs.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SAML 2.0 identity providers can protect shares using external-SSO login profiles. The vendor documents metadata exchange with Entra ID and separate admin-console SSO configuration; review entitlement, claim mapping and enforcement for each surface. Scope: Self-hosted share access; admin console configured separately. Source: https://nirvashare.com/docs/tutorials/share-files-from-smb-storage-with-entra-id-active-directory-users-using-sso/ (reviewed 2026-11-20). Supporting source: Admin-console SSO configuration properties — https://nirvashare.com/docs/deployment/nirvashare-config-properties/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes inline CloudFormation YAML that creates EC2, security rules and an installation bootstrap. Its 2025 example uses a fixed AMI, t2.medium and 40-GB disk, below the current 100-GB requirement, and exposes SSH/application ports publicly. Update region/image, storage, ingress and bootstrap pinning before use; it is not a hardened production template. Scope: Legacy vendor CloudFormation example; conflicts with current sizing and requires review. Source: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/ (reviewed 2026-11-20). Deployment artifact: https://nirvashare.com/docs/deployment/nirvashare-installation-in-aws-using-cloud-formation/. Artifact reference: Documentation updated 2025-01-10; not executed. Supporting source: Current minimum disk requirement — https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/.

- Minimum footprint / sizing: Documented. The vendor specifies at least 2 CPU cores, 4 GB RAM and 100 GB disk, recommending 8 GB RAM or more on a supported Linux distribution. Object/file storage, optional services and HA are additional; this is a baseline, not validated 100-user capacity. Scope: Vendor Linux server baseline; workload and HA sizing excluded. Source: https://nirvashare.com/docs/deployment/system-requirements-for-nirvashare/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: NirvaShare; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://nirvashare.com/pricing/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Nuxeo Platform

Extensible content repository and digital asset management platform.

- Listing: https://launchinyourcloud.com/directory/nuxeo-platform/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 source; distribution access, support subscriptions and add-on entitlements have separate conditions.
- Licensing model: open-source
- Installation: Deploy the documented Docker image, ZIP distribution or Kubernetes Helm chart.
- Architecture: Long-running Java application/container deployment with external production services.
- Operations: Manage runtime services, storage, configuration, backups, upgrades and subscription or package access.
- Product website: https://www.hyland.com/en/products/nuxeo
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current LTS Docker images are private: customers request registry access through support or sales. Trial/default-image language does not grant production access to every package.

The current license documentation states Apache 2.0 for Nuxeo source and explicitly says there is no separate closed enterprise version. Subscription, private-image access and marketplace-package conditions remain material procurement constraints.

Docker/ZIP deployments run a persistent Java server; Helm runs containers. These own-infrastructure paths are classified as servers.


### Category fit

- digital-asset-management: Dedicated DAM functions cover ingestion, organization, media metadata, versioning, workflows, search and distribution.

- document-management: A configurable content repository with document metadata, versions and workflow; implementation is required.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://doc.nuxeo.com/nxdoc/2023/nuxeo-reference-architectures/ (checked 2026-11-12). 


### Cloud deployment evidence

- Nuxeo customer-operated reference architecture on AWS (aws): https://doc.nuxeo.com/nxdoc/2023/nuxeo-reference-architectures/
  The vendor reference architecture explicitly describes AWS as the target IaaS, Nuxeo server instances on Amazon Machine Images, load balancing and backing services. The reviewed page is scoped to LTS 2023; confirm the architecture and supported components for the selected maintained LTS release. Current production images require customer registry access; this is separate from Nuxeo Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

LTS 2025.27 was released October 26, 2026. Hyland identifies Electronic Arts as a Nuxeo adopter for media asset workflows.

Reviewed 2026-11-10.

- Current server release notes: https://doc.nuxeo.com/nxdoc/nuxeo-server-release-notes/

- Named Electronic Arts adoption: https://www.hyland.com/en/resources/articles/dam-vs-pim

### Sources

- LTS installation options and Connect prerequisites: https://doc.nuxeo.com/nxdoc/installation/

- Private Docker image access: https://doc.nuxeo.com/nxdoc/docker-image/

- Current DAM documentation: https://doc.nuxeo.com/nxdoc/dam/

- Versioning and asset workflow: https://doc.nuxeo.com/nxdoc/manage-and-organize/

- Software licenses: https://doc.nuxeo.com/nxdoc/licenses/

- Current LTS maintenance: https://doc.nuxeo.com/nxdoc/nuxeo-server-release-notes/

- Infrastructure or licensing evidence: https://doc.nuxeo.com/userdoc/adding-features/

### Licensing sources

- https://doc.nuxeo.com/nxdoc/licenses/

- https://doc.nuxeo.com/nxdoc/docker-image/

- https://doc.nuxeo.com/userdoc/adding-features/

### Infrastructure sources

- https://doc.nuxeo.com/nxdoc/installation/

- https://doc.nuxeo.com/nxdoc/docker-image/


### 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 LTS 2025 installation matrix lists SAML, OpenID, Kerberos and CAS authentication integrations. Configure the selected authentication module and verify identity-provider and distribution entitlements. Scope: Nuxeo Platform LTS 2025 authentication compatibility. Source: https://doc.nuxeo.com/nxdoc/installation/ (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 LTS 2025 guide publishes a Nuxeo Helm repository for Kubernetes. The chart references a private vendor image by default, requiring authorized registry access; select matching platform/chart versions and provision the other required services. Scope: Nuxeo LTS 2025 Helm deployment; not an anonymously downloadable application image. Source: https://doc.nuxeo.com/nxdoc/kubernetes-helm-chart/ (reviewed 2026-11-14). Deployment artifact: https://packages.nuxeo.com/repository/helm-releases-public/. Artifact reference: select a released chart and matching licensed Nuxeo image.

- Minimum footprint / sizing: Documented. The vendor lists 2 CPUs, 2 GB RAM and 1 GB disk merely to start a server. Production databases, search, content storage and HA require separately sized resources; this is not a 100-user or 1-TB production recommendation. Scope: LTS 2025 server startup minimum; production architecture excluded. Source: https://doc.nuxeo.com/nxdoc/installation/ (reviewed 2026-11-20).

- License pricing: Documented. Nuxeo identifies Apache-2.0 source licensing and separately recommends a support subscription. Access to the current private distribution image and optional packages must be agreed; public source licensing does not establish a subscription price. Scope: Nuxeo Platform source licence and separate distribution/support access. Source: https://doc.nuxeo.com/nxdoc/licenses/ (reviewed 2026-11-20). Supporting source: Current image-access requirements — https://doc.nuxeo.com/nxdoc/installation/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## OpenKM Professional

Customer-hosted document management for configured correspondence registration and response workflows.

- Listing: https://launchinyourcloud.com/directory/openkm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Professional edition; other editions differ
- Licensing model: commercial-only
- Installation: Java/server installation with database and document-processing dependencies
- Architecture: Customer-operated document repository and workflow application
- Operations: Customer operates the server; implementation, support and upgrade arrangements depend on the vendor agreement.
- Product website: https://www.openkm.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 Professional edition is documented as an own-server deployment, distinct from OpenKM Cloud. The vendor correspondence article describes capture, assignment, deadlines and response context. No specific hyperscaler deployment was verified.

This entry specifically lists OpenKM Professional, the commercial own-server edition. The vendor separate Community edition does not change the license model of the listed Professional product.

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

- correspondence-management: Configurable document/workflow platform with documented correspondence registration, assignment, deadlines and response context. Correspondence workflows require configuration; the source describes an application pattern, not guaranteed turnkey equivalence.

- document-management: Document management with a customer-hosted repository, document processing and configurable workflows; this listing covers the Professional edition.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://openkm.ro/compararea-editiilor/ (checked 2026-11-12). Source: https://www.dpci.com/case-studies/openkm-document-management-agbu (checked 2026-11-12). 


### Cloud deployment evidence

- OpenKM Professional regional edition comparison: AWS installation option (aws): https://openkm.ro/compararea-editiilor/
  OpenKM's official Romanian site lists Amazon Web Services as an optional installation service for Professional, separately from Community and OpenKM Cloud. This is an edition compatibility statement rather than a current-release installation guide. Confirm the selected Professional version, customer account, infrastructure, license and support scope with OpenKM.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- OpenKM vendor-assisted installation in AGBU's AWS environment (aws): https://www.dpci.com/case-studies/openkm-document-management-agbu
  Implementation partner DPCI describes provisioning an AWS environment on behalf of AGBU and granting the OpenKM technical team access to install and configure the application. This corroborates customer-environment installation; the case does not identify a current release or prove Professional licensing by itself, so use the separate edition comparison and current vendor agreement.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Correspondence workflow example: https://www.openkm.com/blog/correspondence-management-software-with-openkm.html

- Own-server Professional edition: https://www.openkm.com/en/document-management.html

- Official installation requirements: https://docs.openkm.com/okm-7.1/installation/

- Licensing and edition terms: https://docs.openkm.com/

### Licensing sources

- https://www.openkm.com/en/document-management.html

- https://docs.openkm.com/

### Infrastructure sources

- https://docs.openkm.com/okm-7.1/installation/


### 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. The vendor edition matrix includes OAuth/SAML authentication for Professional, while Community is excluded. Obtain the supported protocol, identity-provider configuration and version entitlement for the selected Professional release; the matrix does not validate every client. Scope: Professional edition; Community differs. Source: https://www.openkm.com/en/comparison-of-versions.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 7.1 Professional guide publishes Compose YAML using its private professional image, MySQL and persistent volumes. The example image is 7.1.13; obtain registry access, select a supported release, replace example credentials and review production configuration. This is not the Community installer. Scope: Professional 7.1 private-image Compose example. Source: https://docs.openkm.com/okm-7.1/using-docker/ (reviewed 2026-11-20). Deployment artifact: https://docs.openkm.com/okm-7.1/using-docker/#docker-compose. Artifact reference: 7.1 guide; example image 7.1.13.

- Minimum footprint / sizing: Documented. The 7.1 guide recommends at least 4 GB RAM, identifies 2 GB as the lower memory boundary, and gives a dual-core 3.20-GHz CPU example for 30–50 concurrent users. Repository versions and database/storage needs are additional; reconcile this older guide with the selected supported Professional release and HA design. Scope: Vendor 7.1 hardware guidance; limited workload example, not HA. Source: https://docs.openkm.com/okm-7.1/hardware-and-software-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. Professional is a commercial, supported edition with installation and updates included in the vendor comparison. The public edition matrix does not quote a price; request a Professional licence/support quote. Community licensing and installer availability do not establish Professional pricing. Scope: Professional commercial edition; price requires a vendor quote. Source: https://www.openkm.com/en/comparison-of-versions.html (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Philter by Philterd (Self-Hosted / Cloud Marketplace)

Open-source API that identifies and redacts sensitive information in text and PDFs.

- Listing: https://launchinyourcloud.com/directory/philter/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: VM image
- Architecture: Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application.
- 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.philterd.ai
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations. Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process.

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

Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- freedom-of-information: Open-source API that identifies and redacts sensitive information in text and PDFs.

- document-management: Open-source API that identifies and redacts sensitive information in text and PDFs.

### Deployment boundaries


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

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.philterd.ai/philter/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy
  Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Marketplace VM (azure): https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter
  Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Philter: Open Source, Self-Hosted PII & PHI Redaction API (gcp): https://www.philterd.ai/philter/
  Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jzonthemtn, AzazelSensei, 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/philterd/philter/graphs/contributors

- Upstream project: https://github.com/philterd/philter

### Sources

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

- Azure Marketplace VM: https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter

- Philter: Open Source, Self-Hosted PII & PHI Redaction API: https://www.philterd.ai/philter/

- Apache-2.0 LICENSE.txt: https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt

- Philterd Pricing: https://philterd.ai/pricing/

- AWS Marketplace EULA PDF: https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs

- GitHub Releases: https://github.com/philterd/philter/releases

- Philter runtime and library corrections: https://github.com/philterd/philter/releases/tag/4.0.1

### Licensing sources

- https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt

- https://philterd.ai/pricing/

- https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs

### Infrastructure sources

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

- https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter

- https://www.philterd.ai/philter/


### Buyer diligence


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

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


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from Philterd, LLC. The publisher package and upstream application have separate maintenance. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Philterd. Its package version is 4.0.1; verify the contained application and required entitlements separately. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace) selected Azure public offer. Source: https://catalogapi.azure.com/offers/philterdllc1687189098111.philter?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Supporting source: AWS delivery and package version — https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy. Offer philterdllc1687189098111.philter: Philterd, LLC; Virtual machine; https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter. Offer prodview-y32h6usoum7zy: Philterd; Amazon Machine Image (AMI); package 4.0.1; https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy.

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

- Single sign-on: Sources checked — unresolved. Philter documents API keys and optional password sign-in for its own users, while its separate UI is described as in development. The reviewed material does not establish an external SAML/OIDC user-federation path for the self-hosted redaction service. API bearer/session keys are not sufficient SSO evidence. Scope: Philter redaction API authentication; separate UI, cloud marketplace subscription and customer portal sign-in are distinct surfaces. Source: https://github.com/philterd/philter/blob/main/docs/docs/sign_in_security.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 README publishes versioned philterd/philter Docker images, including 4.0.1, and a Compose recipe that builds the checked-out source. Use the released image for a release-specific deployment, configure API credentials and persistence/cache services, and distinguish source builds from the marketplace package. Scope: Philter 4.0.1 upstream runtime packaging; not a complete provider infrastructure or HA template. Source: https://github.com/philterd/philter/blob/4.0.1/README.md (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/philterd/philter. Artifact reference: philterd/philter:4.0.1; upstream documentation states there is no latest tag.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed runtime and configuration documentation does not establish a quantitative whole-host CPU/RAM/storage floor for the selected redaction workload. Document rendering, OCR/models, request concurrency, cache and durable data can change memory and storage needs; per-document limits are not host sizing. Scope: Self-hosted Philter application and selected processing/cache dependencies; marketplace VM size is not a universal minimum. Source: https://github.com/philterd/philter/blob/4.0.1/README.md (reviewed 2026-11-20). Supporting source: Runtime settings and processing limits — https://github.com/philterd/philter/blob/main/docs/docs/settings.md.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

- Philter runtime and library corrections (security-advisory): Philter 4.0.1 updates Brotli and Jackson-related dependencies. Scope: The Philter 4.0.1 release identifies corrected dependencies; no blanket affected range is inferred for independently patched systems. Conditions: Exposure depends on the actual Ubuntu/JVM libraries and configured document/API processing. Action: Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process. Source: https://github.com/philterd/philter/releases/tag/4.0.1; reviewed 2026-11-19.




## Reveal Enterprise Private Deployment

Customer-operated review and e-discovery platform with redaction, audit and production workflows.

- Listing: https://launchinyourcloud.com/directory/reveal-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Reveal application services, Kubernetes/Helm and provider-specific database/object-storage 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://www.revealdata.com/rpd
- 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 documents AWS and Azure customer-controlled deployments. Apply the exact 2026.6 compatibility matrix, including the Azure S3Proxy testing qualification. Optional AI, translation and transcription paths can involve AWS subscriptions or a Reveal-managed Bedrock service; private hosting does not make every feature disconnected.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- freedom-of-information: Customer-operated review and e-discovery platform with redaction, audit and production workflows.

- document-management: Customer-operated review and e-discovery platform with redaction, audit and production workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.revealdata.com/rpd-2026-6/docs/system-overview (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix (checked 2026-11-19). 


### Cloud deployment evidence

- RPD System Overview (AWS EC2/EKS/S3) (aws): https://docs.revealdata.com/rpd-2026-6/docs/system-overview
  Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services. The vendor documents AWS and Azure customer-controlled deployments. Apply the exact 2026.6 compatibility matrix, including the Azure S3Proxy testing qualification. Optional AI, translation and transcription paths can involve AWS subscriptions or a Reveal-managed Bedrock service; private hosting does not make every feature disconnected.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Compatibility Matrix (AWS/Azure) (azure): https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix
  Reveal application services, Kubernetes/Helm and provider-specific database/object-storage services. The vendor documents AWS and Azure customer-controlled deployments. Apply the exact 2026.6 compatibility matrix, including the Azure S3Proxy testing qualification. Optional AI, translation and transcription paths can involve AWS subscriptions or a Reveal-managed Bedrock service; private hosting does not make every feature disconnected.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- RPD System Overview (AWS EC2/EKS/S3): https://docs.revealdata.com/rpd-2026-6/docs/system-overview

- Compatibility Matrix (AWS/Azure): https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix

- Reveal Private Deployment: https://www.revealdata.com/rpd

- RPD FAQs (S3/KMS/IAM): https://docs.revealdata.com/rpd-2026-6/docs/reveal-private-deployment-faqs

- PDF Redaction Workflow: https://docs.revealdata.com/rpd-2026-6/docs/pdf-redaction-workflow-sequence-1

- DSAR/Records Workflow: https://docs.revealdata.com/rpd-2026-6/docs/dsar-data-subject-access-request-use-case

- Reveal MSA PDF (On-Premises & SaaS): https://assets.applytosupply.digitalmarketplace.service.gov.uk/g-cloud-15/documents/724143/788391829807931-terms-and-conditions-2026-01-09-1357.pdf

- Reveal SaaS Terms (MSA Precedence): https://www.revealdata.com/saas-terms-of-service

- RPD 2026.6 8.19 Release Notes (2026-08-19): https://docs.revealdata.com/rpd-2026-6/docs/2026-6-8-19-patch-release-notes-reveal

- RPD 2026.6 8.15 Redaction Fix (2026-08-15): https://docs.revealdata.com/rpd-2026-6/docs/2026-6-8-15-patch-release-notes-reveal

### Licensing sources

- https://assets.applytosupply.digitalmarketplace.service.gov.uk/g-cloud-15/documents/724143/788391829807931-terms-and-conditions-2026-01-09-1357.pdf

- https://www.revealdata.com/saas-terms-of-service

### Infrastructure sources

- https://docs.revealdata.com/rpd-2026-6/docs/system-overview

- https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix


### 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 RPD manual documents SAML and OpenID Connect integration and coordination with Reveal Support. Its examples use Reveal-hosted authentication URLs; confirm the actual private-instance realm, identity-service location and metadata rather than assuming those example hosts or fully local authentication. Scope: Reveal Private Deployment 2026.6 manual; provider configuration, support activation and the instance authentication boundary must be established. Source: https://docs.revealdata.com/rpd-2026-6/docs/reveal-sso-documentation (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The public RPD overview and compatibility matrix describe Kubernetes, mixed Windows/Linux services and database roles, but do not identify a complete version-matched production Helm/image/installer bundle. Obtain the entitled release artifacts and component compatibility instructions for the selected private deployment. Scope: Reveal Private Deployment 2026.6 application artifacts; architecture and software compatibility do not identify the actual licensed installation bundle. Source: https://docs.revealdata.com/rpd-2026-6/docs/software-compatibility-matrix (reviewed 2026-11-20). Supporting source: System and component overview — https://docs.revealdata.com/rpd-2026-6/docs/system-overview.

- Minimum footprint / sizing: Documented. Reveal publishes a reference profile for 50 concurrent users and 10 TB under management. It includes two SQL database roles at 16 CPUs/64 GB each, a separate PostgreSQL database, search nodes and additional processing/management/storage roles. Use the complete table; those example allocations are not universal minima or a 100-user HA benchmark. Scope: RPD 2026.6 reference architecture and workload; named users, concurrent users, data phases and all dependent roles must be sized separately. Source: https://docs.revealdata.com/rpd-2026-6/docs/system-overview (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Reveal Enterprise Private Deployment; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://assets.applytosupply.digitalmarketplace.service.gov.uk/g-cloud-15/documents/724143/788391829807931-terms-and-conditions-2026-01-09-1357.pdf (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Tonic Textual

Commercial self-hosted text and document de-identification software installed with an official Helm chart.

- Listing: https://launchinyourcloud.com/directory/tonic-textual/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Textual API and ML containers, GPU-capable AWS compute, PostgreSQL/RDS 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://github.com/TonicAI/textual_helm_charts
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The AWS sizing recommendations cover distinct application, ML and database components. Quay pull credentials and a software entitlement are obtained during onboarding. The public Helm-chart licence does not grant a licence to the commercial Textual application.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Textual API and ML containers, GPU-capable AWS compute, PostgreSQL/RDS and object storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- freedom-of-information: Commercial self-hosted text and document de-identification software installed with an official Helm chart.

- document-management: Commercial self-hosted text and document de-identification software installed with an official Helm chart.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/system-requirements (checked 2026-11-19). 


### Cloud deployment evidence

- AWS System Requirements (aws): https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/system-requirements
  Textual API and ML containers, GPU-capable AWS compute, PostgreSQL/RDS and object storage. The AWS sizing recommendations cover distinct application, ML and database components. Quay pull credentials and a software entitlement are obtained during onboarding. The public Helm-chart licence does not grant a licence to the commercial Textual application.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS System Requirements: https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/system-requirements

- Helm Chart Repo: https://github.com/TonicAI/textual_helm_charts

- K8s Helm Guide: https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/deploying-on-kubernetes-with-helm

- Tonic Terms & Conditions: https://www.tonic.ai/terms-and-conditions

- Textual Release Notes: https://www.tonic.ai/product-release-notes/textual

- Helm Commits: https://github.com/TonicAI/textual_helm_charts/commits/main.atom

### Licensing sources

- https://www.tonic.ai/terms-and-conditions

### Infrastructure sources

- https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/system-requirements


### 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. Self-hosted Textual supports configured external SSO providers including Azure, GitHub, Google, Keycloak, Okta and generic OpenID Connect. Environment variables configure the connection; REQUIRE_SSO_AUTH can disable local email/password login. Cloud-provider options and configuration differ from the self-hosted product. Scope: Tonic Textual self-hosted user sign-in; external IdP policy and version-specific settings apply. Source: https://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-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. Tonic publishes a Textual Helm chart and OCI installation instructions. Configure a specific Textual image version supplied by Tonic, an application database, licence and encryption secret; chart/image versions and optional model integrations must be selected separately. Scope: Self-hosted Textual Kubernetes application chart; provision the cluster, database, storage and GPU capacity separately. Source: https://github.com/TonicAI/textual_helm_charts/blob/main/README.MD (reviewed 2026-11-20). Deployment artifact: https://github.com/TonicAI/textual_helm_charts. Artifact reference: main (moving branch); chart and Textual image version must be matched. Supporting source: Kubernetes deployment procedure — https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/deploying-on-kubernetes-with-helm.

- Minimum footprint / sizing: Documented. The vendor recommends a 16-GB-VRAM Nvidia GPU and at least 6 GB GPU RAM per ML worker, or an m5.2xlarge CPU-only fallback with slower performance. Its separate PostgreSQL baseline is two vCPUs, 2 GB RAM and 100 GB storage. Additional workers, files, backups and HA need workload sizing. Scope: Self-hosted Textual inference and separate application database; GPU VRAM is not host RAM or validated 100-user capacity. Source: https://docs.tonic.ai/textual/textual-install-administer/deploying-a-self-hosted-instance/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Tonic Textual; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.tonic.ai/terms-and-conditions (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## TriliumNext Notes

Self-hosted hierarchical personal notes and document knowledge base.

- Listing: https://launchinyourcloud.com/directory/triliumnext-notes/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, digitalocean, linode, vultr, hostinger, lumadock
- 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
- Architecture: TriliumNext server with persistent database 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://triliumnotes.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 server is primarily a single-user knowledge base; published notes and sharing do not establish a multi-user enterprise collaboration suite.

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

TriliumNext server with persistent database and attachments. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted hierarchical personal notes and document knowledge base.

### Deployment boundaries


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

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

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

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

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

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


### Cloud deployment evidence

- Cloudron Store (aws, digitalocean, linode, vultr, hostinger, lumadock): https://www.cloudron.io/store/triliumnext-notes.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.


### Community and maintenance

The reviewed upstream contributor history includes eliandoran, zadam, adoriandoran, 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/TriliumNext/Trilium/graphs/contributors

- Upstream project: https://github.com/TriliumNext/Trilium

### Sources

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

- AGPL-3.0 LICENSE: https://github.com/TriliumNext/Trilium/blob/main/LICENSE

- Releases v0.107.0: https://github.com/TriliumNext/Trilium/releases

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

### Licensing sources

- https://github.com/TriliumNext/Trilium/blob/main/LICENSE

### Infrastructure sources

- https://www.cloudron.io/store/triliumnext-notes.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. TriliumNext documents external OpenID Connect login and links the integration from its published v0.107.0 README. OIDC replaces the local web password login and delegates MFA to the provider. Configure the identity accepted by this personal-notes instance; this does not make it a multi-tenant team repository. Scope: TriliumNext v0.107.0 server authentication; verify the packaged server version and provider algorithm/settings. Source: https://github.com/TriliumNext/Trilium/blob/v0.107.0/README.md (reviewed 2026-11-20). Supporting source: OpenID Connect configuration — https://docs.triliumnotes.org/user-guide/setup/server/openid-connect.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The project publishes Docker images and Compose instructions with a persistent Trilium data directory. Select a version matching the desktop/sync clients rather than automatically following latest; configure proxy/authentication, ownership, backups and upgrades for the installed server. Scope: TriliumNext self-hosted server; upstream and Cloudron package versions/allocations are separate. Source: https://docs.triliumnotes.org/user-guide/setup/server/installation/docker (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/triliumnext/trilium. Artifact reference: v0.107.0 upstream source reviewed; choose its matching published image tag, not an unpinned latest upgrade.

- 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/triliumnext-notes.html (reviewed 2026-11-19). Supporting source: Cloudron platform requirements — https://docs.cloudron.io/installation/.

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

- Operating cost estimate: Not researched.

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






