
# Vendor & supplier document management

Supplier onboarding, document validation, expiry and qualification.

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


Supplier onboarding, document validation, expiry and qualification.

9 listings.


## Archer Third-Party Governance

Commercial customer-hosted third-party risk and governance application on the Archer platform.

- Listing: https://launchinyourcloud.com/directory/archer-tprm/
- 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: Supported Archer application and database VMs on customer AWS or Azure 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://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Use the current On-Premises release and sizing matrix with the selected Third-Party Governance entitlement. The dated cloud guide's example instance types do not establish a current HA workload or price estimate. Archer SaaS is separate.

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

Supported Archer application and database VMs on customer AWS or Azure infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Commercial customer-hosted third-party risk and governance application on the Archer platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm (checked 2026-11-19). 


### Cloud deployment evidence

- AWS & Azure Cloud Hosting (aws, azure): https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm
  Supported Archer application and database VMs on customer AWS or Azure infrastructure. Use the current On-Premises release and sizing matrix with the selected Third-Party Governance entitlement. The dated cloud guide's example instance types do not establish a current HA workload or price estimate. Archer SaaS is separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS & Azure Cloud Hosting: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm

- Third-Party Governance: https://www.archerirm.com/third-party-governance

- Archer On-Premise Agreement PDF: https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_37b1c77af24d434d8e85335dcdeca740.pdf

- Legal Center: https://www.archerirm.com/company/legal-center

- On-Prem Release Notes (2025.12.05): https://help.archerirm.cloud/archerreleasenotes/content/rnhome/archer_releases_onprem.htm

- On-Prem Maintenance PDF: https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_45d0859400a24fbf8969ac1e40fc3d4d.pdf

### Licensing sources

- https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_37b1c77af24d434d8e85335dcdeca740.pdf

- https://www.archerirm.com/company/legal-center

### Infrastructure sources

- https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm


### 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. Archer documents instance-level SSO configuration including Windows-integrated and SAML modes, identity-provider connections and user/attribute provisioning. Configure the selected supported release and directory/trust settings. Third-Party Governance uses the Archer platform; this is not evidence for the separate SaaS identity surface. Scope: Archer platform 2024.09 user SSO configuration underlying TPRM; release compatibility required. Source: https://help.archerirm.cloud/platform_2024_09/en-us/content/archercontrolpanel/acp_inst_sso_configuring.htm (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Public cloud-hosting guidance describes supported deployment context, but the requested installation page requires login and the reviewed material does not expose a current customer-delivery artifact. Obtain the entitled installer and supported database/platform version; do not infer a complete installation template from hosting guidance. Scope: Archer self-managed installation artifact remains unconfirmed. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_cloud_hosting.htm (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The 2024.11 small-environment guide specifies a database server with four dedicated cores/16 GB RAM and separate combined web/services server with four cores/16 GB; disk and HA/load-balancer/SQL cluster requirements are additional. This historical platform sizing example requires revalidation for the selected current release and TPRM workload. Scope: Archer 2024.11 small-environment component minimums; current-release and solution sizing separate. Source: https://help.archerirm.cloud/install_2024_11/en-us/content/platform/installation/performancesizing/pt_small_environment.htm (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Archer Third-Party Governance; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.archerirm.com/wp-content/uploads/2026/07/4d99d5_37b1c77af24d434d8e85335dcdeca740.pdf (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## CISO Assistant Community

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

- Listing: https://launchinyourcloud.com/directory/ciso-assistant/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 Community images; the enterprise directory and Pro images have a separate commercial licence.
- Licensing model: open-source
- Installation: Application platform deployment
- Architecture: Django API and worker, SvelteKit frontend, PostgreSQL, Qdrant and Caddy on Railway.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://intuitem.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor comparison explicitly includes TPRM, evidence/document management and SAML SSO in Community. SCIM, advanced audit trails and other Pro features have separate commercial terms; Pro air-gap claims do not establish Community disconnected support.

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

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


### Category fit

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

### Deployment boundaries


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


### Cloud deployment evidence

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


### Community and maintenance

The reviewed upstream contributor history includes ab-smith, nas-tabchiche, Mohamed-Hacene, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/intuitem/ciso-assistant-community/graphs/contributors

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

### Sources

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

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

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

- Compliance attestations: Not researched.

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

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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







## eramba (Enterprise Self-Hosted)

Source-available commercial GRC software with supplier-assessment and policy workflows.

- Listing: https://launchinyourcloud.com/directory/eramba-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial source-available Enterprise terms; source access does not permit unrestricted modification or redistribution.
- Licensing model: source-available
- Installation: Docker / Compose
- Architecture: Eramba's persistent Docker stack on customer AWS or Azure 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.eramba.org/learning/courses/12/episodes/274
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor explicitly says Community and Enterprise code are not open source and restrict modification and redistribution. This entry selects licensed Enterprise Online Assessments; questionnaires and linked third-party evidence require configuration.

Commercial source-available Enterprise terms; source access does not permit unrestricted modification or redistribution.

Eramba's persistent Docker stack on customer AWS or Azure infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Source-available commercial GRC software with supplier-assessment and policy workflows.

- policy-procedure-management: Source-available commercial GRC software with supplier-assessment and policy workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.eramba.org/learning/courses/12/episodes/274 (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.eramba.org/learning/courses/12/episodes/274 (checked 2026-11-19). 


### Cloud deployment evidence

- Docker Install Guide (aws, azure): https://www.eramba.org/learning/courses/12/episodes/274
  Eramba's persistent Docker stack on customer AWS or Azure infrastructure. The vendor explicitly says Community and Enterprise code are not open source and restrict modification and redistribution. This entry selects licensed Enterprise Online Assessments; questionnaires and linked third-party evidence require configuration.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Docker Install Guide: https://www.eramba.org/learning/courses/12/episodes/274

- Vendor Assessments: https://www.eramba.org/learning/courses/81

- License FAQs: https://www.eramba.org/faqs

- Release History: https://www.eramba.org/releases

### Licensing sources

- https://www.eramba.org/faqs

### Infrastructure sources

- https://www.eramba.org/learning/courses/12/episodes/274


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted user-administration guide documents SAML and Google OAuth alongside LDAP, with one remote connector active at a time and separately enabled portal access. Local recovery accounts may remain. Configure/test the connector and selected edition rather than treating LDAP password validation alone as federation. Scope: eramba on-premises documented user identity connectors and portal configuration. Source: https://www.eramba.org/learning/courses/78 (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker installation course explicitly covers Community and Enterprise on premises, deployment configuration, Enterprise activation, updates and backups. Use its supported Compose repository and compatible images, protect secrets and validate storage/permissions; SaaS deployment is a separate offering. Scope: eramba Enterprise on-premises Docker installation and lifecycle guide. Source: https://www.eramba.org/learning/courses/12/episodes/274 (reviewed 2026-11-21). Deployment artifact: https://www.eramba.org/learning/courses/12/episodes/274. Artifact reference: Current vendor Docker installation course.

- Minimum footprint / sizing: Documented. The Docker guide lists minimum 1 vCPU, 4 GB RAM plus 10 GB swap and at least 3 GB data storage; recommended compute is 2 vCPU/8 GB RAM. Provide extra database/attachments, background/PDF work and backups. These host baselines are not a benchmark or complete HA deployment. Scope: eramba Docker host minimum/recommended resources; complete workload capacity separate. Source: https://www.eramba.org/learning/courses/12/episodes/274 (reviewed 2026-11-21).

- License pricing: Documented. Commercial source-available Enterprise terms; source access does not permit unrestricted modification or redistribution. Scope: eramba (Enterprise Self-Hosted); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.eramba.org/faqs (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## ERPNext Supplier Management

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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


### Cloud deployment evidence

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

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


### Sources

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

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

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

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

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

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

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

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

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

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

### Licensing sources

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

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

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Frappe documents OIDC-based social login between a Frappe identity-provider server and an application server. Configure the framework clients and review user-role mapping; this is not a supplier-module-specific identity guarantee. Scope: ERPNext/Frappe platform authentication; business-module authorization is separate. Source: https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

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

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

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




### Security and lifecycle reviews

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

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

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




## FormKiQ Vendor and Supplier Document Management

Collect, verify, and manage the lifecycle of vendor and supplier documentation with expiry tracking, renewal automation, and audit-ready records.

- Listing: https://launchinyourcloud.com/directory/formkiq-vendor-supplier-document-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/vendor-supplier-document-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- vendor-supplier-document-management: Supplier onboarding, document validation, expiry and qualification.

### Deployment boundaries


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


### Cloud deployment evidence

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


### Sources

- Vendor and Supplier Document Management solution: https://formkiq.com/solutions/vendor-supplier-document-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

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

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

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

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/vendor-supplier-document-management/

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


### Buyer diligence


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

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

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Vendor and Supplier Document Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/vendor-supplier-document-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Vendor documents retain access controls and retention. An expiry flag does not suspend a supplier automatically; procurement changes require authorised decisions and integration. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Vendor and Supplier Document Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/vendor-supplier-document-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Vendor and Supplier Document Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/vendor-supplier-document-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Vendor and Supplier Document Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/vendor-supplier-document-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Advanced or Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Vendor and Supplier Document Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/vendor-supplier-document-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## IBM OpenPages on Software Hub

Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.

- Listing: https://launchinyourcloud.com/directory/ibm-openpages/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm
- 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: Kubernetes manifests
- Architecture: OpenPages 9.2.1.1 cartridge on IBM Software Hub 5.4 Patch 4 and customer Red Hat OpenShift on IBM Cloud.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/ibm-cloud-docs/cloud-pak-data
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cartridge version and underlying Software Hub/OpenShift matrix must be matched. Standalone OpenPages 9.2.2 release availability does not establish that version for the selected cartridge. IBM-hosted OpenPages as a Service is a different deployment.

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

OpenPages 9.2.1.1 cartridge on IBM Software Hub 5.4 Patch 4 and customer Red Hat OpenShift on IBM Cloud. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.

- vendor-supplier-document-management: Licensed governance, risk and third-party-control application installed as a Software Hub cartridge.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md (checked 2026-11-19). 


### Cloud deployment evidence

- CP4D Services Install (OpenPages) (ibm): https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md
  OpenPages 9.2.1.1 cartridge on IBM Software Hub 5.4 Patch 4 and customer Red Hat OpenShift on IBM Cloud. The cartridge version and underlying Software Hub/OpenShift matrix must be matched. Standalone OpenPages 9.2.2 release availability does not establish that version for the selected cartridge. IBM-hosted OpenPages as a Service is a different deployment.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- CP4D Services Install (OpenPages): https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md

- IBM OpenPages: https://www.ibm.com/products/openpages

- OpenPages 9.2.1 on IBM Software Hub: https://www.ibm.com/support/pages/node/7282885

- OpenPages Cartridge Supported Environments: https://www.ibm.com/support/pages/node/6347144

- IBM Cloud ROKS Docs: https://cloud.ibm.com/docs/openshift?topic=openshift-getting-started

- IBM OpenPages License (L-CBML-R8TYAW): https://www14.software.ibm.com/cgi-bin/weblap/lap.pl?li_formnum=L-CBML-R8TYAW

- OpenPages 9.2 Fix List (9.2.2.1): https://www.ibm.com/support/pages/ibm-openpages-92-fix-list

- OpenPages 9.2.2 Release Notice: https://www.ibm.com/support/pages/node/7289843

- CP4D Docs Commits: https://github.com/ibm-cloud-docs/cloud-pak-data/commits/master

### Licensing sources

- https://www14.software.ibm.com/cgi-bin/weblap/lap.pl?li_formnum=L-CBML-R8TYAW

### Infrastructure sources

- https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md


### 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. Software Hub documents centrally managed access to OpenPages instances, including a default administrator used to configure directory/SSO integration and synchronised users/groups. This is the Software Hub-hosted service identity boundary; standalone OpenPages application-server instructions and IBM SaaS authentication are separate deployment paths. Scope: OpenPages on IBM Software Hub 5.4 platform identity and instance access. Source: https://www.ibm.com/docs/en/software-hub/5.4.x?topic=groups-managing-access-openpages-instances (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The cloud guide documents installing the licensed service, but does not establish a public versioned OpenPages cartridge deployment artifact for the selected customer entitlement. Scope: OpenPages cartridge installation workflow versus the base Software Hub platform. Source: https://github.com/ibm-cloud-docs/cloud-pak-data/blob/master/install-services.md (reviewed 2026-11-19).

- Minimum footprint / sizing: Documented. The published Software Hub 5.2 x86 table gives OpenPages operand minimums of 6 vCPU/20 GB RAM with 252 GB persistent storage for the described Db2-backed configuration, plus operator/catalog overhead. This version-specific reference excludes the OpenShift/Software Hub platform and is not a validated current 5.4 or HA workload baseline; recheck the selected release and database placement. Scope: Published Software Hub 5.2 OpenPages component example; current-release/platform/HA sizing requires validation. Source: https://www.ibm.com/docs/en/software-hub/5.2.x?topic=requirements-x86-64-hardware (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. The selected OpenPages cartridge has its own version/entitlement scope. A base Software Hub licence does not establish the customer’s OpenPages purchase, users or price. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://www.ibm.com/support/pages/node/6347144 (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.







## SimpleRisk (with Vendor Risk Management Extra)

Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra.

- Listing: https://launchinyourcloud.com/directory/simplerisk-vrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- 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: SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension.
- 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.simplerisk.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 listed supplier workflow requires the commercial Extra; the core project's open-source licence does not include it. An AWS image is a deployment path, not a guarantee that software spend counts toward a buyer's commitment.

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

SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- vendor-supplier-document-management: Self-hosted SimpleRisk with the separately licensed Vendor Risk Management Extra.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.simplerisk.com/kb/01-04-installing-on-cloud (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.simplerisk.com/kb/01-04-installing-on-cloud (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.simplerisk.com/kb/01-04-installing-on-cloud (checked 2026-11-19). 


### Cloud deployment evidence

- Cloud Install KB (AWS AMI) (aws, azure, gcp): https://support.simplerisk.com/kb/01-04-installing-on-cloud
  SimpleRisk application AMI or installed application stack plus the licensed supplier-risk extension. The listed supplier workflow requires the commercial Extra; the core project's open-source licence does not include it. An AWS image is a deployment path, not a guarantee that software spend counts toward a buyer's commitment.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Cloud Install KB (AWS AMI): https://support.simplerisk.com/kb/01-04-installing-on-cloud

- VRM Extra: https://www.simplerisk.com/extras/vendor-risk-management

- Pricing & Editions: https://www.simplerisk.com/pricing

- SimpleRisk 20261105-001 Release: https://www.simplerisk.com/product-releases/whats-new-simplerisk-20261105-001-release

- GitHub Releases: https://github.com/simplerisk/code/releases

### Licensing sources

- https://www.simplerisk.com/pricing

### Infrastructure sources

- https://support.simplerisk.com/kb/01-04-installing-on-cloud


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The Custom Authentication Extra adds SAML with provider metadata, trusted domain and mapped user type, alongside LDAP/AD. Licence/enable that Extra separately from Vendor Risk Management, configure the IdP and user lifecycle, and retain recovery access; base local login does not include the same identity integration. Scope: SimpleRisk SAML via separately enabled Custom Authentication Extra. Source: https://support.simplerisk.com/kb/custom-authentication-extra-installation-and-administration-guide (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor documents Linux/cloud and Docker installation, with configuration, persistence and separately activated Extras. Select compatible base application/DB and licensed VRM/authentication components, then configure HTTPS, backups and updates; installing the base does not activate all Extras. Scope: SimpleRisk upstream Docker installation plus separately licensed Extras. Source: https://support.simplerisk.com/kb/01-03-installing-via-docker (reviewed 2026-11-21). Deployment artifact: https://support.simplerisk.com/kb/01-03-installing-via-docker. Artifact reference: Current vendor Docker installation guide.

- Minimum footprint / sizing: Documented. The system guide suggests small deployments at 1–2 vCPU/2 GB RAM/20 GB disk and mid-size deployments at 2–4 vCPU/4–8 GB/50–100 GB. Large programs separate database and web tiers with 4+ vCPU/8+ GB per tier. These workload examples require tuning for frameworks, imports, evidence, audit growth and HA. Scope: SimpleRisk current deployment-size starting points; not a fixed VRM/HA minimum. Source: https://support.simplerisk.com/kb/01-01-system-requirements (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






