
# Hyperscience Hypercell

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

Canonical page: https://launchinyourcloud.com/directory/hyperscience/
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.


1 listing.


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



