Hyperscience Hypercell

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

9 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Hypercell Brotli decoder remediation

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.

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.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Helm / Kubernetes operator; Kubernetes manifests

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Helm Chart (AWS/GCP) ↗ · Source checked 2026-11-19

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Kubernetes Installation Overview ↗ · Source checked 2026-11-19

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Helm Chart (AWS/GCP) ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodHelm / Kubernetes operator; Kubernetes manifests
InfrastructureServers / containers
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.
Licensing modelCommercial Only
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
LicenseCommercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Private-cloud/on-premises Hyperscience identity configuration · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Commercial Hypercell Kubernetes distribution; entitled artifacts required · Source ↗ · Deployment artifact ↗ (Vendor-provided HS_HELM_CHART; choose compatible application/chart releases) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

VM baseline documented; selected Kubernetes production footprint unresolved · Source ↗ · Kubernetes dependencies and deployment boundary ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

Hyperscience Hypercell; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

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.

Category fit

Correspondence management
Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.
AI tools & infrastructure
Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.

Compare within Correspondence management

  • Adobe Experience Manager 6.5 Forms (Correspondence Management)Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • FormKiQ Correspondence Management Directory PublisherManage formal correspondence from intake and assignment to approved replies, response deadlines, dispatch evidence, follow-up, and closure in FormKiQ.
    • AWS
    Customer-operated · Commercial Only
  • Hyland OnBase On-PremiseCustomer-hosted enterprise content and case platform for document-heavy business processes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • OpenKM ProfessionalCustomer-hosted document management for configured correspondence registration and response workflows.
    • AWS
    Customer-operated · Commercial Only
  • Quadient Inspire Flex via ORDACommercial customer-communications software packaged as a bring-your-own-licence AWS image by ORDA.
    • AWS
    Customer-operated · Commercial Only

These products address related workflows; read their category-fit notes before comparing scope. See all of Correspondence management →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Helm Chart (AWS/GCP) ↗ · AWS, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

    • Kubernetes Installation Overview ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory