
# Policy & procedure management on Azure

Compare documented Policy & procedure management deployments on Azure, including operating responsibility, licensing and deployment evidence.

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

6 listings.


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







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







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







## Paramify

Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

- Listing: https://launchinyourcloud.com/directory/paramify/
- 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: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: EKS or AKS application containers, PostgreSQL, object storage and workload identity.
- 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/paramify/support
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.

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

EKS or AKS application containers, PostgreSQL, object storage and workload identity. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Customer-operated compliance-documentation and security-plan platform installed with the vendor's platform installer or Helm.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.paramify.com/deploy-ppi-eks.html (checked 2026-11-19). 

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

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example (checked 2026-11-19). 


### Cloud deployment evidence

- AWS EKS via PPI (aws): https://docs.paramify.com/deploy-ppi-eks.html
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure AKS via Helm (azure): https://docs.paramify.com/deploy-helm-azure.html
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- # Paramify configuration
#
# Example install:
#   helm registry login registry.paramify.com --username paramify@mycompan (gcp): https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example
  EKS or AKS application containers, PostgreSQL, object storage and workload identity. AWS and Azure guides deploy the actual platform into customer infrastructure. The public access agreement describes SaaS and does not replace the buyer's self-hosted order or licence terms. Compliance-document generation is not an authorization or attestation of the installation. The GKE example includes the actual application Helm install, GCS provider, database, secrets and workload identity alongside its Terraform infrastructure.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS EKS via PPI: https://docs.paramify.com/deploy-ppi-eks.html

- Azure AKS via Helm: https://docs.paramify.com/deploy-helm-azure.html

- # Paramify configuration
#
# Example install:
#   helm registry login registry.paramify.com --username paramify@mycompan: https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example

- GCP GKE Terraform: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf

- Deployment Options: https://docs.paramify.com/deployment-options.html

- Paramify Policies & SSPs: https://www.paramify.com/

- Terms & Conditions: https://www.paramify.com/legal/terms-and-conditions

- Access & Services Agreement: https://www.paramify.com/legal/access-and-services-agreement

- Support Commits (`2026-10-29`): https://github.com/paramify/support/commits/main.atom

- Legacy Release Notes: https://docs.paramify.com/release-notes.html

### Licensing sources

- https://www.paramify.com/legal/terms-and-conditions

- https://www.paramify.com/legal/access-and-services-agreement

### Infrastructure sources

- https://docs.paramify.com/deploy-ppi-eks.html

- https://docs.paramify.com/deploy-helm-azure.html

- https://raw.githubusercontent.com/paramify/support/main/gcp/values-gke.yaml.example


### 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. The vendor explicitly supports Google, Microsoft and Okta login in self-hosted environments, with provider/client setup guides and application-local permissions. The overview still describes SAML as planned; do not treat that date or email magic links as confirmation of current SAML capability. Scope: Paramify self-hosted documented provider login; planned SAML excluded. Source: https://docs.paramify.com/login-options.html (reviewed 2026-11-21). Supporting source: Okta configuration — https://docs.paramify.com/login-okta.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for EKS or AKS application containers, PostgreSQL, object storage and workload identity. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Paramify deployment example; review the full linked installation instructions. Source: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf (reviewed 2026-11-19). Deployment artifact: https://github.com/paramify/support/blob/main/gcp/gcp-paramify-gke-infra.tf. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed installation examples identify Kubernetes, PostgreSQL and object storage, while an example Node heap option configures one process. They do not establish complete production CPU/RAM/storage capacity; document generation workers, database, cluster overhead and HA need workload sizing. Scope: Paramify complete production footprint remains unconfirmed. Source: https://docs.paramify.com/deploy-ppi-eks.html (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. Deployment requires a Paramify licence and registry credentials, but the public SaaS access agreement does not establish the self-hosted software order, price or support scope. Scope: Selected self-hosted commercial product; contract confirmation remains necessary. Source: https://www.paramify.com/legal/terms-and-conditions (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## RegScale

Commercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides.

- Listing: https://launchinyourcloud.com/directory/regscale/
- 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: Kubernetes manifests
- Architecture: RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE.
- 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://regscale.readme.io/docs/aws-ecs.md
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.

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

RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Commercial self-hosted governance and policy platform with provider-specific container and Kubernetes guides.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://regscale.readme.io/docs/aws-ecs.md (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://regscale.readme.io/docs/azure-aca.md (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://regscale.readme.io/docs/gcp-cloud-run.md (checked 2026-11-19). 


### Cloud deployment evidence

- AWS ECS (aws): https://regscale.readme.io/docs/aws-ecs.md
  RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure ACA (azure): https://regscale.readme.io/docs/azure-aca.md
  RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Cloud Run (gcp): https://regscale.readme.io/docs/gcp-cloud-run.md
  RegScale application containers, SQL database and persistent evidence storage on ECS/EKS, ACA/AKS or Cloud Run/GKE. The guides describe the actual application and evidence storage in customer cloud resources. The reviewed core chart is 3.2.0 with appVersion 6.35.0.1; the separate orchestration-hub chart has a different appVersion. Chart creation timestamps do not establish application release publication dates.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS ECS: https://regscale.readme.io/docs/aws-ecs.md

- Azure ACA: https://regscale.readme.io/docs/azure-aca.md

- GCP Cloud Run: https://regscale.readme.io/docs/gcp-cloud-run.md

- K8s Helm: https://regscale.readme.io/docs/kubernetes-deployment.md

- Policies Module: https://regscale.readme.io/docs/policies.md

- RegScale Licensing Docs: https://regscale.readme.io/docs/setup-general.md

- RegScale ESLA: https://regscale.com/enterprise-software-license-agreement/

- Helm Index YAML: https://regscale.github.io/helm/index.yaml

### Licensing sources

- https://regscale.readme.io/docs/setup-general.md

- https://regscale.com/enterprise-software-license-agreement/

### Infrastructure sources

- https://regscale.readme.io/docs/aws-ecs.md

- https://regscale.readme.io/docs/azure-aca.md

- https://regscale.readme.io/docs/gcp-cloud-run.md


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The vendor documents OAuth2/OIDC or SAML2 user SSO, with only one active method per tenant and configured first-login provisioning. Set issuer/client or metadata, identity claims and role policy for the selected installation; orchestration-hub compatibility and service credentials are separate. Scope: Current RegScale tenant user federation and configuration. Source: https://regscale.readme.io/docs/setup-single-sign-on-sso (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 AWS guide supplies an ECS Fargate task definition and CLI workflow with ALB/TLS, EFS, external SQL Server and secrets; Kubernetes deployment is separately documented. Select compatible image/chart versions and licences. The example is configurable infrastructure guidance, not a complete turnkey HA stack. Scope: RegScale current vendor AWS ECS deployment reference. Source: https://regscale.readme.io/docs/aws-ecs (reviewed 2026-11-21). Deployment artifact: https://regscale.readme.io/docs/aws-ecs. Artifact reference: Current vendor guide reviewed on this date. Supporting source: Kubernetes deployment — https://regscale.readme.io/docs/kubernetes-deployment.

- Minimum footprint / sizing: Documented. The sizing guide separates evaluation (web 2 vCPU/4 GB, database 4 vCPU/16 GB) from recommended production (web 4 vCPU/8 GB, database 8 vCPU/32 GB). Its HA tier starts with two or more web nodes and separately sized database availability. Monitor actual imports, users, reporting, storage and backups rather than treating these as workload guarantees. Scope: Current RegScale component/tier baselines; evaluation, production and HA distinguished. Source: https://regscale.readme.io/docs/sizing-guide (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP Process Control (On-Premise)

Licensed SAP internal-control and policy lifecycle management application.

- Listing: https://launchinyourcloud.com/directory/sap-process-control/
- 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: Package / binary installer
- Architecture: SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs.
- 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.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.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 SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.

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

SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- policy-procedure-management: Licensed SAP internal-control and policy lifecycle management application.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/netweaver-guides (checked 2026-11-19). 


### Cloud deployment evidence

- AWS SAP NetWeaver Guides (aws): https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html
  SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure SAP Planning Guide (azure): https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide
  SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP SAP NetWeaver Guides (gcp): https://docs.cloud.google.com/sap/docs/netweaver-guides
  SAP Process Control 12.0 add-on on NetWeaver AS ABAP 7.52 and a supported database on certified customer cloud VMs. The SAP Master Guide identifies the actual add-on, required ABAP platform and installation sequence; pair it with the provider NetWeaver deployment guide. Separate development, test and production landscapes are recommended. Check licensed products, current SAP Notes and the customer-specific Product Availability Matrix; the GRC for HANA 2026 roadmap is not a licence or version for Process Control 12.0.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS SAP NetWeaver Guides: https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html

- Azure SAP Planning Guide: https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide

- GCP SAP NetWeaver Guides: https://docs.cloud.google.com/sap/docs/netweaver-guides

- AWS Launch Wizard SAP: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html

- GCP Business Suite on HANA: https://docs.cloud.google.com/sap/docs/architectures/sap-business-suite-on-hana

- PC 12.0 SP27 Admin Guide PDF (2025-01-08): https://help.sap.com/doc/d83af7d22baa49829e464111338e9c12/12.0.27/en-US/loio60d658f576b6452eb0f943c04b354018_en.pdf

- PC 12.0 Master Guide PDF: https://help.sap.com/doc/3110c68ac50046cc8a035bfe348a9bc3/12.0.13/en-US/loio4570e559019f40a587bc3dce4fafbbbd_4570e559019f40a587bc3dce4fafbbbd_en.pdf

- SAP Process Control Course: https://learning.sap.com/courses/discovering-the-key-functionalities-of-sap-process-control

- SAP GRC for HANA 2026 PAM PDF: https://help.sap.com/doc/4d01ca92f5884240ab864b9ff08776a6/12.0.26/en-US/SAP%20GRC%20FOR%20HANA,%202026%20_PAM.pdf

- SAP On-Premise Variants: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

- SAP Security Notes (2026-11-10): https://support.sap.com/en/my-support/knowledge-base/security-notes-news.html

- SAP 2040 Maintenance Commitment: https://support.sap.com/en/release-upgrade-maintenance/maintenance-information/maintenance-strategy/s4hana-business-suite7.html

### Licensing sources

- https://help.sap.com/doc/4d01ca92f5884240ab864b9ff08776a6/12.0.26/en-US/SAP%20GRC%20FOR%20HANA,%202026%20_PAM.pdf

- https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Infrastructure sources

- https://docs.aws.amazon.com/sap/latest/sap-netweaver/welcome.html

- https://learn.microsoft.com/en-us/azure/sap/workloads/planning-guide

- https://docs.cloud.google.com/sap/docs/netweaver-guides


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed deployment and Process Control material does not establish the selected GRC portal/UI and its actual SSO configuration. NetWeaver or SAP workforce identity features alone do not confirm the complete customer-managed Process Control user login path. Scope: SAP Process Control selected-release user identity remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (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. AWS Launch Wizard automates supported SAP NetWeaver platform landscapes and customer-supplied installation media, including distributed and HA patterns. This provisions the underlying platform, not the Process Control application configuration. Verify GRC/NetWeaver/database compatibility, licences and application installation separately. Scope: SAP Process Control parent-platform infrastructure automation; GRC application delivery is separate. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21). Deployment artifact: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html. Artifact reference: Current AWS Launch Wizard SAP guide.

- Minimum footprint / sizing: Sources checked — unresolved. Provider deployment patterns require input sizing and do not establish GRC Process Control production capacity. Obtain supported application/database memory, concurrent control/test workflows, batch jobs, data growth and HA requirements for the selected release. Scope: SAP Process Control workload sizing remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- License pricing: Sources checked — unresolved. The master guide identifies the Process Control 12.0 add-on and separately licensed Risk Management and Access Control products, but does not establish the selected customer licence or pricing. The GRC for HANA 2026 roadmap is a different scope. Scope: Selected self-managed application or customer-cloud service; contract confirmation required. Source: https://help.sap.com/doc/3110c68ac50046cc8a035bfe348a9bc3/12.0.13/en-US/loio4570e559019f40a587bc3dce4fafbbbd_4570e559019f40a587bc3dce4fafbbbd_en.pdf (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






