
# Document management on Azure

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

Canonical page: https://launchinyourcloud.com/clouds/azure/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: Subscription and resource group
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal (checked 2026-11-20).
- Network: Virtual Network (VNet)
- Identity and access: Microsoft Entra identities and Azure RBAC
- Installation guidance: Bicep/ARM templates or Terraform; review deployment scope and role assignments.
- Guidance source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview
- Guidance reviewed: 2026-11-10


### Private offers

Microsoft Marketplace private offers negotiate product pricing and terms. Confirm the exact offer, billing scope and benefit eligibility rather than assuming all purchases count toward a commitment.
Source: https://learn.microsoft.com/en-us/marketplace/private-offers-overview (reviewed 2026-11-14).

### Private connectivity

Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability.
Source: https://learn.microsoft.com/en-us/azure/private-link/private-link-overview (reviewed 2026-11-14).

### Cross-tenant operations

Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor.
Source: https://learn.microsoft.com/en-us/azure/lighthouse/overview (reviewed 2026-11-14).

### Government environments

Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government.
Source: https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome (reviewed 2026-11-14).

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

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







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







## DocuWare On-Premise

Customer-operated document repository, email capture and document-workflow platform on Azure VMs.

- Listing: https://launchinyourcloud.com/directory/docuware-on-premises/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: 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: Licensed DocuWare installation on Azure Windows Server VMs
- Architecture: Windows Server application VMs and a database on the same or separate 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.docuware.com/en-us/knowledgebase/article/KBA-37193
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.

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

Windows Server application VMs and a database on the same or separate VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Customer-operated document repository, email capture and document-workflow platform on Azure VMs.

- workflow-automation: Customer-operated document repository, email capture and document-workflow platform on Azure VMs.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.docuware.com/en-us/knowledgebase/article/KBA-37193 (checked 2026-11-19). 


### Cloud deployment evidence

- Azure VM KBA-37193 (azure): https://support.docuware.com/en-us/knowledgebase/article/KBA-37193
  Windows Server application VMs and a database on the same or separate VM. The Azure knowledge-base article excludes Azure SQL and Azure Blob Storage. Its MSMQ/Azure Service Bus workaround applies to older versions; the vendor's clarification says messaging changed in 7.13 and later. This is a configurable document workflow, rather than a packaged public-correspondence case system.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure VM KBA-37193: https://support.docuware.com/en-us/knowledgebase/article/KBA-37193

- Connect to Mail: https://knowledgecenter.docuware.com/docs/connect-to-mail.md

- Workflow Designer: https://knowledgecenter.docuware.com/docs/web-based-workflow-designer.md

- Client Licenses: https://knowledgecenter.docuware.com/docs/docuware-license-model.md

- DocuWare 7.15: https://knowledgecenter.docuware.com/docs/news-docuware-version-715.md

- 7.15 Release Notes: https://knowledgecenter.docuware.com/docs/news-715-technical-release-notes.md

### Licensing sources

- https://knowledgecenter.docuware.com/docs/docuware-license-model.md

### Infrastructure sources

- https://support.docuware.com/en-us/knowledgebase/article/KBA-37193


### 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 Identity Service supports OIDC sign-on with external identity providers for locally installed DocuWare systems. Configure provider integration and review enforcement, local exceptions and edition/version requirements. Scope: DocuWare on-premises Identity Service; hosted Cloud is a separate deployment. Source: https://knowledgecenter.docuware.com/docs/integration-embedding-in-itinfrastructure (reviewed 2026-11-20). Supporting source: Entra ID setup applies to on-premises organizations — https://support.docuware.com/en-US/knowledgebase/article/KBA-36308.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The documented installation uses a vendor-supplied software ZIP and licence file, with frontend, backend and full-text roles. The package is supplied to the customer; the public guide is not a public Terraform or CloudFormation artifact. Scope: Vendor 7.12 installation/package delivery; verify version-specific installation guide. Source: https://knowledgecenter.docuware.com/docs/install-docuware-on-premises-version-712 (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. The 7.14 matrix lists DocuWare Services at 4 CPU cores/8 GB RAM/64 GB disk minimum, with 8 cores/16 GB recommended. Database resources, full-text service, document storage and HA are additional; recheck the matrix for a different version. Scope: DocuWare 7.14 service minimum; not a complete production or HA footprint. Source: https://knowledgecenter.docuware.com/docs/docuware-version-714-on-premises-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: DocuWare On-Premise; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://knowledgecenter.docuware.com/docs/docuware-license-model.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







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







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







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







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







## OpenDocMan

Self-hosted document repository with check-in/out, revision and workflow controls.

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

### Scope and qualifications

The image publisher is cloudimg. Check its packaged application version against upstream 2.10 maintenance rather than assuming the image always contains the newest release.

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

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


### Category fit

- document-management: Self-hosted document repository with check-in/out, revision and workflow controls.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.opendocman-ubuntu-24-04
  OpenDocMan application, database and document storage in a cloudimg Azure VM. The image publisher is cloudimg. Check its packaged application version against upstream 2.10 maintenance rather than assuming the image always contains the newest release.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes stephenlawrence, gh-org-bot-odm, raralala14, 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/opendocman/opendocman/graphs/contributors

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

### Sources

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

- GPL-2.0 LICENSE.txt: https://raw.githubusercontent.com/opendocman/opendocman/master/LICENSE.txt

- GitHub Commits: https://github.com/opendocman/opendocman/commits/master

### Licensing sources

- https://raw.githubusercontent.com/opendocman/opendocman/master/LICENSE.txt

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The current upstream README and environment configuration describe local account credentials and installation but do not establish a supported SAML/OIDC workflow. Obtain a release-specific federation design and support statement before assuming corporate SSO; this is an open question, not a claim that integration is impossible. Scope: Upstream self-hosted authentication; federation unresolved. Source: https://raw.githubusercontent.com/opendocman/opendocman/master/README.md (reviewed 2026-11-20). Supporting source: Environment configuration reviewed — https://raw.githubusercontent.com/opendocman/opendocman/master/.env.sample.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README documents Compose deployment with separate application/database services, persistent configuration and file data, and a secret-generation helper. Select a release, review the Compose configuration and protect the installer; this source recipe is separate from third-party marketplace image packaging. Scope: Upstream Compose installation; provider images may package a different release. Source: https://raw.githubusercontent.com/opendocman/opendocman/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/opendocman/opendocman/blob/master/docker-compose.yml. Artifact reference: master (moving branch; verify selected release artifact).

- Minimum footprint / sizing: Sources checked — unresolved. The environment template sets PHP_MEMORY_LIMIT=512M and the README identifies PHP 8.2 with MySQL/MariaDB. A PHP memory limit is not a total server minimum. No validated CPU/RAM, document-volume or HA profile is established by these sources. Scope: Upstream component configuration; total hardware sizing unresolved. Source: https://raw.githubusercontent.com/opendocman/opendocman/master/.env.sample (reviewed 2026-11-20). Supporting source: Runtime and database requirements — https://raw.githubusercontent.com/opendocman/opendocman/master/README.md.

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

- Operating cost estimate: Not researched.

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







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







## SeedDMS

Self-hosted document repository with versions, approval workflows and access controls.

- Listing: https://launchinyourcloud.com/directory/seeddms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU GPL-2.0 for the reviewed SeedDMS 6.0 branch; separately licensed extensions require their own review.
- Licensing model: open-source
- Installation: VM image
- Architecture: SeedDMS 6 application, database and persistent documents in a cloudimg Azure VM.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.seeddms-ubuntu-24-04
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The third-party package and upstream SeedDMS release line have separate maintenance. Licence terms and bundled libraries must be checked for the selected package.

GNU GPL-2.0 for the reviewed SeedDMS 6.0 branch; separately licensed extensions require their own review.

SeedDMS 6 application, database and persistent documents in a cloudimg Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Self-hosted document repository with versions, approval workflows and access controls.

### Deployment boundaries


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


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.seeddms-ubuntu-24-04
  SeedDMS 6 application, database and persistent documents in a cloudimg Azure VM. The third-party package and upstream SeedDMS release line have separate maintenance. Licence terms and bundled libraries must be checked for the selected package.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The project’s public discussion archive records maintainer Uwe Steinmann and community contributors diagnosing notification bugs and discussing patches and the Codeberg migration in July 2026. This is evidence of an active user/contributor community, rather than a production-support guarantee.

Reviewed 2026-11-19.

- SeedDMS maintainer and community technical discussion: https://sourceforge.net/p/seeddms/mailman/seeddms-discuss/

- SeedDMS project and user reports: https://sourceforge.net/projects/seeddms/

### Sources

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

- SeedDMS About: https://www.seeddms.org/

- Codeberg GPL-2.0 LICENSE: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-5.1.x/LICENSE

- SeedDMS Download (6.0.42): https://www.seeddms.org/download/

- SeedDMS Changelog: https://www.seeddms.org/changelog/

- SeedDMS RSS (2026-10): https://www.seeddms.org/index.xml

- Codeberg Repo (2026-11): https://codeberg.org/seeddms

- Selected edition licence text: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/LICENSE

### Licensing sources

- https://www.seeddms.org/

- https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-5.1.x/LICENSE

- https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/LICENSE

### Infrastructure sources

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


### Buyer diligence


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

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


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

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

- Single sign-on: Sources checked — unresolved. The official download page points to externally maintained OpenID Connect and ForwardAuth extensions and directs support to their developers. This establishes possible extension paths, but not core-native federation, current 6.0 compatibility or a supported marketplace-image configuration. Confirm those details before relying on SSO. Scope: Third-party extension pointers; selected-release federation support unresolved. Source: https://www.seeddms.org/download/ (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 a 6.0 source branch with Composer/Phing packaging instructions and links installable distributions from its official download page. This is a PHP application distribution, not a public cloud provisioning template. Keep repository data and configuration outside the public web root and select a supported package. Scope: Upstream 6.0 application build/distribution. Source: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/README.md (reviewed 2026-11-20). Deployment artifact: https://www.seeddms.org/download/. Artifact reference: 6.0 release line; choose the versioned distribution. Supporting source: Official download options — https://www.seeddms.org/download/.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed official 6.0 source/build and distribution pages do not establish a validated CPU/RAM minimum or HA topology. Size the PHP application, database, document storage and extraction/preview processes together; a PHP package download is not production sizing. Scope: Upstream 6.0 distribution; numeric production sizing unresolved. Source: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/README.md (reviewed 2026-11-20). Supporting source: Distribution and extension scope — https://www.seeddms.org/download/.

- License pricing: Documented. GNU GPL-2.0 for the reviewed SeedDMS 6.0 branch; separately licensed extensions require their own review. Scope: SeedDMS; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://codeberg.org/SeedDMS/seeddms/raw/branch/seeddms-6.0.x/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SharePoint Server Subscription Edition

Commercial collaboration, content and document management server farm deployed on customer-operated Microsoft Azure infrastructure.

- Listing: https://launchinyourcloud.com/directory/sharepoint-server-subscription-edition/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Server/CAL licensing; Subscription Edition requires active Software Assurance or a subscription license.
- Licensing model: commercial-only
- Installation: Install Microsoft media on Windows Server Azure virtual machines, then configure the farm with the configuration wizard or PowerShell
- Architecture: Customer-operated Windows Server farm with Active Directory and SQL Server or Azure SQL Managed Instance.
- Operations: Customer manages Windows and SharePoint servers, identity, SQL, load balancing, certificates, search, storage, backups, patching and availability.
- Product website: https://learn.microsoft.com/en-us/sharepoint/sharepoint-server
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers SharePoint Server Subscription Edition, not SharePoint Online or Microsoft 365. It is a manually installed farm rather than an Azure-managed SaaS or one-click service. Azure SQL Database other than Managed Instance and SQL Server Express are unsupported for SharePoint databases. Windows Server, SQL Server and supporting Azure resources have separate licensing and costs; enterprise functionality can require additive Enterprise CALs. Monthly Public Update builds are supported for one year. The November 10, 2026 update brings SharePoint Server Subscription Edition to build 16.0.20326.20278 and fixes multiple RCE, elevation, disclosure, spoofing, and bypass CVEs. Workflow Manager requires KB5002799; SharePoint 2010 workflows and InfoPath Forms Services are removed July 13, 2027, after InfoPath support ended July 14, 2026.

SharePoint Server uses commercial Server/CAL terms. Subscription Edition entitlement requires active Software Assurance or subscription licensing; Windows Server, SQL Server and additive Enterprise CAL entitlements are separate where applicable.

SharePoint Server Subscription Edition runs on Windows Server virtual machines with persistent database, identity and supporting services. Production generally uses a multi-server farm.


### Category fit

- document-management: Document libraries, metadata, content types, versioning, workflows, governance and retention on a customer-operated farm.

- collaboration: Sites, shared content and team collaboration capabilities delivered by the self-managed product.

- content-management: Authoring, publishing and managing intranet and site content in a self-managed farm.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure (checked 2026-11-17). 


### Cloud deployment evidence

- SharePoint Server Subscription Edition farms on Azure IaaS (azure): https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure
  Microsoft documents development/test, disaster-recovery and production SharePoint Server farms on Azure virtual machines, and the page applies to Subscription Edition. This is customer-operated IaaS, not SharePoint Online.
  Source type: provider-guide; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Designing a SharePoint Server farm in Azure: https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure

- Deploy SharePoint Server with Azure SQL Managed Instance: https://learn.microsoft.com/en-us/sharepoint/administration/deploy-azure-sql-managed-instance-with-sharepoint-servers

- SharePoint Server in Microsoft Azure: https://learn.microsoft.com/en-us/sharepoint/administration/sharepoint-server-in-microsoft-azure

- Subscription Edition installation overview: https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se

- SharePoint Server licensing guidance: https://www.microsoft.com/licensing/guidance/SharePoint-Server

- SharePoint Server Product Terms: https://www.microsoft.com/licensing/terms/productoffering/SharePointServer/MPSA

- Document management in SharePoint Server: https://learn.microsoft.com/en-us/sharepoint/governance/document-management-in-sharepoint-server

- SharePoint Server servicing policy: https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-server-se

- SharePoint Server Subscription Edition November 2026 update KB5002945: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945

### Licensing sources

- https://www.microsoft.com/licensing/guidance/SharePoint-Server

- https://www.microsoft.com/licensing/terms/productoffering/SharePointServer/MPSA

### Infrastructure sources

- https://learn.microsoft.com/en-us/sharepoint/administration/designing-a-sharepoint-server-farm-in-azure

- https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The licensed Server/farm installation is documented, but a current first-party Marketplace offer delivering Subscription Edition was not established. Microsoft 365 offers are a different product. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://www.microsoft.com/licensing/guidance/SharePoint-Server (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Server licences/CALs and separately billed Azure resources do not establish that SharePoint software spend counts toward a cloud commitment. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://www.microsoft.com/licensing/guidance/SharePoint-Server (reviewed 2026-11-17).

- Single sign-on: Documented. Subscription Edition supports OIDC 1.0 through a trusted identity-token issuer. Microsoft documents an Entra ID setup; Windows and claims-based authentication alternatives have different configuration requirements. Scope: SharePoint Server Subscription Edition, not SharePoint Online. Source: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/oidc-1-0-authentication (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. The Server OIDC guide establishes federation, not a SCIM service. SharePoint Online/Entra provisioning evidence cannot be transferred to Subscription Edition. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/oidc-1-0-authentication (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed SharePoint Server Subscription Edition material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/set-up-oidc-auth-in-sharepoint-server-with-msaad (reviewed 2026-11-17).

- Security controls: Documented. Configure the trusted OIDC issuer and farm properties for the selected server update level. Identity-provider access, certificates and SharePoint authorization remain separate customer responsibilities. Current advisory review: Build 16.0.20326.20278 fixes multiple remote-code-execution, elevation, information-disclosure, spoofing, and security-bypass CVEs. Apply KB5002945 with its prerequisites and plan migration from SharePoint 2010 workflows and InfoPath Forms Services before July 13, 2027. Scope: Subscription Edition identity trust and certificates SharePoint Server Subscription Edition November 10, 2026 update KB5002945.. Source: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/set-up-oidc-auth-in-sharepoint-server-with-msaad.

- Air-gapped operation: Sources checked — unresolved. The Server installation overview does not establish a complete isolated prerequisite, activation, identity and monthly-update workflow. Azure deployment alone is not evidence of isolation. Scope: Reviewed public evidence for SharePoint Server Subscription Edition; unresolved within this edition/deployment. Source: https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. The vendor documents installation media, prerequisite installation and farm configuration with supported Windows/SQL components. Azure deployment is customer-managed IaaS; the evidence is not a one-click Marketplace farm. Scope: Subscription Edition installation workflow. Source: https://learn.microsoft.com/en-us/sharepoint/install/install-overview-spserver-se (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. Microsoft publishes separate minimum CPU, memory and disk requirements for development, evaluation and production farm roles. Database hosts and additional farm roles must be sized separately; a development single-server example does not establish HA capacity. Scope: Subscription Edition role/topology sizing matrix. Source: https://learn.microsoft.com/en-us/sharepoint/install/hardware-and-topology-requirements-for-sharepoint-server-subscription-editon (reviewed 2026-11-17).

- License pricing: Documented. SharePoint Server uses commercial Server/CAL terms. Subscription Edition entitlement requires active Software Assurance or subscription licensing; Windows Server, SQL Server and additive Enterprise CAL entitlements are separate where applicable. Scope: SharePoint Server Subscription Edition: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.microsoft.com/licensing/guidance/SharePoint-Server (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Only Azure deployment is confirmed here. Obtain the farm-role topology, Server/CAL/Windows/SQL licences and Azure region; no AWS farm support is inferred. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://learn.microsoft.com/en-us/sharepoint/install/hardware-and-topology-requirements-for-sharepoint-server-subscription-editon (reviewed 2026-11-17).

- Release snapshot / cadence: Documented. The November 10, 2026 update is build 16.0.20326.20278 and includes security fixes. Workflow Manager requires KB5002799, and SharePoint 2010 workflows plus InfoPath Forms Services are scheduled for removal July 13, 2027. Scope: SharePoint Server Subscription Edition. Source: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945 (reviewed 2026-11-18).




### Security and lifecycle reviews

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

- SharePoint Server Subscription Edition November 2026 security update (security-advisory): Build 16.0.20326.20278 fixes multiple remote-code-execution, elevation, information-disclosure, spoofing, and security-bypass CVEs. Scope: SharePoint Server Subscription Edition November 10, 2026 update KB5002945. Conditions: Installed components and the individual CVE prerequisites determine applicability. Workflow Manager requires KB5002799. Action: Apply KB5002945 with its prerequisites and plan migration from SharePoint 2010 workflows and InfoPath Forms Services before July 13, 2027. Source: https://support.microsoft.com/en-us/servicing/office/hotfix/sharepoint/5002945; reviewed 2026-11-18.




## Siemens Teamcenter (Quality & Document Control)

Commercial product-lifecycle platform with controlled technical documents and quality-management options.

- Listing: https://launchinyourcloud.com/directory/siemens-teamcenter/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: 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 Azure Teamcenter client, web, enterprise and resource tiers with supported database/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://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Microsoft documents the complete Azure application architecture, including multi-zone storage choices. Generic quality and technical-document features do not establish a ready-made clinical-regulatory or medical-device validation solution.

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

Customer Azure Teamcenter client, web, enterprise and resource tiers with supported database/storage services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- document-management: Commercial product-lifecycle platform with controlled technical documents and quality-management options.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Baseline (azure): https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline
  Customer Azure Teamcenter client, web, enterprise and resource tiers with supported database/storage services. Microsoft documents the complete Azure application architecture, including multi-zone storage choices. Generic quality and technical-document features do not establish a ready-made clinical-regulatory or medical-device validation solution.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure Baseline: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline

- Azure NetApp: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-plm-netapp-files

- Quality & Compliance: https://plm.sw.siemens.com/en-US/teamcenter/solutions/quality-compliance-management/

- Document Mgmt: https://plm.sw.siemens.com/en-US/teamcenter/solutions/document-management/

- Siemens Software Terms: https://www.siemens.com/en-us/company/customer-partner-terms/sw-terms/

- Teamcenter Blog: https://blogs.sw.siemens.com/teamcenter/

### Licensing sources

- https://www.siemens.com/en-us/company/customer-partner-terms/sw-terms/

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline


### 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. Microsoft's customer-managed Teamcenter architecture documents application SSO through Microsoft Entra ID using SAML and Teamcenter Security Services. This is a configured Teamcenter integration, not merely Azure control-plane IAM. Validate the selected Teamcenter/TCSS release and identity topology. Scope: Teamcenter application and Active Workspace/rich-client architecture on Azure; provider-documented integration, not a vendor support entitlement. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline (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 provider architecture explains Teamcenter infrastructure and discusses infrastructure automation, but does not identify a complete public Teamcenter application installer or end-to-end version-matched IaC bundle. Licensed Teamcenter/TCSS components and their installation sequence still require the appropriate Siemens release media and guidance. Scope: Teamcenter customer-managed Azure application deployment artifacts; ARM/storage automation alone is not the product installer. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-baseline (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The provider guidance separates web, enterprise, database, file-management and visualization roles and recommends application sizing with an Azure architect. It does not establish a quantitative whole-stack floor for the selected Teamcenter/quality/document-control workload. Size compute, database and file I/O together. Scope: Teamcenter PLM on Azure; architecture, storage throughput and VM-family recommendations are not a validated 100-user HA sizing profile. Source: https://learn.microsoft.com/en-us/azure/architecture/example-scenario/manufacturing/teamcenter-plm-netapp-files (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Siemens Teamcenter (Quality & Document Control); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.siemens.com/en-us/company/customer-partner-terms/sw-terms/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






