
# Correspondence management on Azure

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

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

3 listings.


## Adobe Experience Manager 6.5 Forms (Correspondence Management)

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

- Listing: https://launchinyourcloud.com/directory/adobe-aem-forms/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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


### Cloud deployment evidence

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


### Sources

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. AEM 6.5 provides a SAML 2.0 Web SSO handler with signed/encrypted assertions, user creation and group synchronization. It is disabled until configured with provider/entity information and trust material. This establishes the AEM/OSGi web-login path, not automatic SSO for every Forms JEE or desktop component. Scope: AEM 6.5 platform web authentication used by the Forms deployment; choose the applicable runtime and repository paths. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/saml-2-0-authenticationhandler (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Adobe documents installing AEM 6.5 Quickstart and a compatible Forms add-on package through its package-management workflow. Downloads require entitled Adobe access. Select the matching Forms runtime/service pack and deployment topology; this is licensed application installation, not a public Terraform or complete cloud template. Scope: AEM 6.5 Forms on OSGi installation path; Forms JEE and Correspondence Management components require their applicable guides. Source: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/osgi-installation/installing-configuring-aem-forms-osgi (reviewed 2026-11-20). Deployment artifact: https://experience.adobe.com/downloads. Artifact reference: AEM 6.5 Quickstart plus compatible Forms add-on/service pack; entitled download selection required. Supporting source: Base AEM installation — https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy.

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

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Hyperscience Hypercell

Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

- Listing: https://launchinyourcloud.com/directory/hyperscience/
- 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: Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard.
- 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.hyperscience.ai/deployment/docs/helm-chart
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor. Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds.

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

Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- correspondence-management: Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

- ai-tools: Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (checked 2026-11-19). 


### Cloud deployment evidence

- Helm Chart (AWS/GCP) (aws, gcp): https://help.hyperscience.ai/deployment/docs/helm-chart
  Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Kubernetes Installation Overview (azure): https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview
  Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard. The Helm guide supplies complete AWS and GCP values, including application storage permissions. Registry integration alone is not a hosting badge. Hypercell application versions, Helm charts and Kubernetes support dates are separate. The October 2026 decoder advisory and the current v44 flow/block upgrade instructions must be checked before exposing document processing; hosted FedRAMP claims do not transfer to this installation. The vendor Azure reference diagram depicts the complete platform, Blob storage and PostgreSQL; its namespace label still says GKE, so validate the Azure-specific values with the vendor.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Helm Chart (AWS/GCP): https://help.hyperscience.ai/deployment/docs/helm-chart

- Kubernetes Installation Overview: https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview

- hsk8s CLI (ECR/GAR): https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli

- Gov Mailrooms & Correspondence: https://www.hyperscience.ai/blog/the-trusted-ai-infrastructure-behind-modern-government/

- Hyperscience EULA: https://www.hyperscience.ai/legal-documents/eula/

- V44 Release Notes (2026-11-18): https://help.hyperscience.ai/docs/v44-release-notes

- Security Advisory (2026-10-30): https://help.hyperscience.ai/docs/security-advisory

- Helm Releases: https://help.hyperscience.ai/deployment/docs/news-and-release-notes

- Hypercell Brotli decoder remediation: https://help.hyperscience.ai/docs/security-advisory

### Licensing sources

- https://www.hyperscience.ai/legal-documents/eula/

### Infrastructure sources

- https://help.hyperscience.ai/deployment/docs/helm-chart

- https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The private-cloud deployment guide documents SP-initiated SAML federation using IdP metadata, attribute mapping and signed/encrypted assertion settings. Only one of SAML, OIDC, LDAP or Google authentication can be enabled. Confirm the application/chart version and licensed integration before rollout. Scope: Private-cloud/on-premises Hyperscience identity configuration. Source: https://help.hyperscience.ai/deployment/docs/saml.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies an entitled Helm chart and hsk8s tooling, with AWS/GCP values examples and separate application-image delivery. Pin chart and application versions independently; configure external secrets, database, storage and worker/GPU tiers. Sample image tags do not establish the current supported release. Scope: Commercial Hypercell Kubernetes distribution; entitled artifacts required. Source: https://help.hyperscience.ai/deployment/docs/helm-chart (reviewed 2026-11-20). Deployment artifact: https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli. Artifact reference: Vendor-provided HS_HELM_CHART; choose compatible application/chart releases.

- Minimum footprint / sizing: Sources checked — unresolved. The VM guide requires at least 8 logical cores with a 1:4 CPU-to-GB-RAM ratio and documents throughput examples. These VM numbers do not establish the complete Helm/Kubernetes namespace, trainer, database and object-store footprint. Obtain current chart resource values and workload/HA sizing; ORCA GPU requirements are separate. Scope: VM baseline documented; selected Kubernetes production footprint unresolved. Source: https://help.hyperscience.ai/deployment/docs/infrastructure-requirements.md (reviewed 2026-11-20). Supporting source: Kubernetes dependencies and deployment boundary — https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview.md.

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Hypercell Brotli decoder remediation (security-advisory): The vendor documents CVE-2026-111497 and version-dependent PDF/HTTP response exposure. Scope: Hypercell v33.0–v44.0; the vendor lists fixes 44.0.2, 43.2.5, 42.3.19, 42.0.27, 41.0.39 and 40.0.39. Other or archived lines need an agreed upgrade path. Conditions: PDF decoding is an additional path in v42–v44; earlier listed versions have configured HTTP-response exposure. SaaS patching does not patch customer installations. Action: Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds. Source: https://help.hyperscience.ai/docs/security-advisory; reviewed 2026-11-19.



