{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Formal correspondence intake, assignment, replies and response evidence.","formkiqSolution":"correspondence-management","id":"correspondence-management","name":"Correspondence management"},"cloud":{"boundary":"Subscription and resource group","classificationReview":{"reviewed":"2026-11-20","source":"https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal","summary":"Navigation group for the documented infrastructure offering; read each application path for its actual account boundary."},"defaultBoundary":"cloud-account","diligence":[{"reviewed":"2026-11-14","source":"https://learn.microsoft.com/en-us/marketplace/private-offers-overview","summary":"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.","topic":"Private offers"},{"reviewed":"2026-11-14","source":"https://learn.microsoft.com/en-us/azure/private-link/private-link-overview","summary":"Azure Private Link uses private endpoints in a virtual network for supported Azure and partner services. Check application support, DNS and service availability.","topic":"Private connectivity"},{"reviewed":"2026-11-14","source":"https://learn.microsoft.com/en-us/azure/lighthouse/overview","summary":"Azure Lighthouse supports delegated management with customer-controlled scopes and actions. Agree the roles, audit requirements and revocation plan for the selected vendor.","topic":"Cross-tenant operations"},{"reviewed":"2026-11-14","source":"https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome","summary":"Azure Government uses isolated US datacenters and networks. Commercial Azure documentation alone does not establish a product path or compliance in Government.","topic":"Government environments"}],"id":"azure","identity":"Microsoft Entra identities and Azure RBAC","install":"Bicep/ARM templates or Terraform; review deployment scope and role assignments.","name":"Microsoft Azure","network":"Virtual Network (VNet)","providerType":"cloud-infrastructure","reviewed":"2026-11-10","short":"Azure","source":"https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview"},"kind":"cloud-category","listings":[{"architecture":"Customer-operated AEM author/publish application VMs with supported Java, persistence and Forms components.","categories":["correspondence-management","document-management"],"category":"Correspondence management","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws","azure"],"notes":"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.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AEM 6.5 Tech Reqs","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Licensed AEM 6.5 Forms installation with a native correspondence-management and letters application.","diligence":{"footprint":{"reviewed":"2026-11-20","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","status":"inconclusive","summary":"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.","supportingSources":[{"title":"General AEM technical requirements","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements"}]},"iac":{"artifactRef":"AEM 6.5 Quickstart plus compatible Forms add-on/service pack; entitled download selection required","artifactUrl":"https://experience.adobe.com/downloads","reviewed":"2026-11-20","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","status":"documented","summary":"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.","supportingSources":[{"title":"Base AEM installation","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy"}]},"licensePricing":{"reviewed":"2026-11-19","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","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"availability":"available","reviewed":"2026-11-20","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","status":"documented","summary":"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."}},"id":"adobe-aem-forms","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements"],"install":"Package / binary installer","installMethods":["package"],"kind":"product","license":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModel":"commercial-only","licenseModelNotes":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModelSources":["https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Adobe Experience Manager 6.5 Forms (Correspondence Management)","notes":"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.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"AEM 6.5 Tech Reqs","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements"},{"title":"Correspondence Management","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/letters-correspondences/cm-overview"},{"title":"AEM 6.5 Licensing \u0026 Deploy","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/deploying/deploy"},{"title":"AEM 6.5.26.0 Release Notes","url":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/release-notes/release-notes"}],"url":"https://launchinyourcloud.com/directory/adobe-aem-forms/","website":"https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/introduction/technical-requirements"},{"architecture":"Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.","categories":["document-management","records-management","contract-management","financial-application-management","case-management","correspondence-management","vendor-supplier-document-management","hr-employee-records-management","policy-procedure-management","claims-management","workflow-automation"],"category":"Document management","categoryFit":{"case-management":"Configurable case applications connect case data, documents, tasks and approvals.","claims-management":"Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.","contract-management":"Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.","correspondence-management":"Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.","document-management":"Enterprise content repository with capture, document workflows and integration with business applications.","financial-application-management":"Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.","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.","records-management":"Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.","vendor-supplier-document-management":"Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.","workflow-automation":"Content and case workflows with routing, rules and low-code WorkView applications."},"cloudEvidence":[{"applicableVersions":["OnBase 18+ in partner statement; confirm current release"],"clouds":["aws","azure","gcp"],"notes":"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.","reviewed":"2026-11-12","sourceType":"partner-evidence","title":"Hyland partner statement on customer-managed OnBase cloud deployments","url":"https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/","vendorSupport":"not-assessed"},{"clouds":["aws","azure","gcp"],"notes":"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.","reviewed":"2026-11-12","sourceType":"partner-relationship","title":"Hyland identification of Reveille as an authorized integration partner","url":"https://www.hyland.com/en/partners/reveille","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0,1],"operator":"customer"}],"description":"Customer-hosted enterprise content and case platform for document-heavy business processes.","diligence":{"footprint":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-20","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","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-16","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","status":"documented","summary":"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."},"sso":{"availability":"available","reviewed":"2026-11-20","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","status":"documented","summary":"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."}},"id":"onbase","infrastructure":["servers"],"infrastructureNotes":"Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://legal.hyland.com/pst-on-premise-multi-products"],"install":"Vendor or partner-assisted on-premises installation","installMethods":["other"],"kind":"platform","license":"Commercial OnBase licenses and separately scoped modules","licenseModel":"commercial-only","licenseModelNotes":"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.","licenseModelSources":["https://legal.hyland.com/pst-on-premise-multi-products"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Hyland OnBase On-Premise","notes":"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.","operations":"Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.","publisher":false,"reviewed":"2026-11-13","sources":[{"title":"OnBase platform capabilities","url":"https://www.hyland.com/en/solutions/products/onbase"},{"title":"On-premises product terms","url":"https://legal.hyland.com/pst-on-premise-multi-products"},{"title":"WorkView business application examples","url":"https://www.hyland.com/en/resources/articles/workview-product-overview"},{"title":"HR files and policy sign-offs","url":"https://www.hyland.com/en/resources/terminology/human-resources/document-management"},{"title":"OnBase workflow routing","url":"https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview"},{"title":"Correspondence document integration","url":"https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction"},{"title":"Loan-document tracking solution","url":"https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking"},{"title":"Insurance claims integration case study","url":"https://www.hyland.com/en/customers/p-c-insurer"}],"url":"https://launchinyourcloud.com/directory/onbase/","website":"https://www.hyland.com/"},{"advisories":[{"action":"Apply the fix for the installed Hypercell line and follow the documented sequential upgrades or temporary workarounds.","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.","id":"2026-11-19-hypercell-brotli","listingIds":["hyperscience"],"reviewed":"2026-11-19","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.","source":"https://help.hyperscience.ai/docs/security-advisory","summary":"The vendor documents CVE-2026-111497 and version-dependent PDF/HTTP response exposure.","title":"Hypercell Brotli decoder remediation","type":"security-advisory"}],"architecture":"Hyperscience Helm application, database, object storage, workers and separately prepared container registry on AWS or GKE Standard.","categories":["correspondence-management","ai-tools"],"category":"Correspondence management","categoryFit":{"ai-tools":"Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.","correspondence-management":"Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure."},"cloudEvidence":[{"clouds":["aws","gcp"],"notes":"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.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Helm Chart (AWS/GCP)","url":"https://help.hyperscience.ai/deployment/docs/helm-chart","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"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.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Kubernetes Installation Overview","url":"https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"VM baseline documented; selected Kubernetes production footprint unresolved","source":"https://help.hyperscience.ai/deployment/docs/infrastructure-requirements.md","status":"inconclusive","summary":"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.","supportingSources":[{"title":"Kubernetes dependencies and deployment boundary","url":"https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview.md"}]},"iac":{"artifactRef":"Vendor-provided HS_HELM_CHART; choose compatible application/chart releases","artifactUrl":"https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli","reviewed":"2026-11-20","scope":"Commercial Hypercell Kubernetes distribution; entitled artifacts required","source":"https://help.hyperscience.ai/deployment/docs/helm-chart","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-19","scope":"Hyperscience Hypercell; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://www.hyperscience.ai/legal-documents/eula/","status":"documented","summary":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Private-cloud/on-premises Hyperscience identity configuration","source":"https://help.hyperscience.ai/deployment/docs/saml.md","status":"documented","summary":"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."}},"id":"hyperscience","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://help.hyperscience.ai/deployment/docs/helm-chart","https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview"],"install":"Helm / Kubernetes operator; Kubernetes manifests","installMethods":["helm","kubernetes"],"kind":"product","license":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModel":"commercial-only","licenseModelNotes":"Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.","licenseModelSources":["https://www.hyperscience.ai/legal-documents/eula/"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Hyperscience Hypercell","notes":"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.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Helm Chart (AWS/GCP)","url":"https://help.hyperscience.ai/deployment/docs/helm-chart"},{"title":"Kubernetes Installation Overview","url":"https://help.hyperscience.ai/deployment/docs/kubernetes-installation-overview"},{"title":"hsk8s CLI (ECR/GAR)","url":"https://help.hyperscience.ai/deployment/docs/artifacts-management-and-hsk8s-hyperscience-kubernetes-cli"},{"title":"Gov Mailrooms \u0026 Correspondence","url":"https://www.hyperscience.ai/blog/the-trusted-ai-infrastructure-behind-modern-government/"},{"title":"Hyperscience EULA","url":"https://www.hyperscience.ai/legal-documents/eula/"},{"title":"V44 Release Notes (2026-11-18)","url":"https://help.hyperscience.ai/docs/v44-release-notes"},{"title":"Security Advisory (2026-10-30)","url":"https://help.hyperscience.ai/docs/security-advisory"},{"title":"Helm Releases","url":"https://help.hyperscience.ai/deployment/docs/news-and-release-notes"},{"title":"Hypercell Brotli decoder remediation","url":"https://help.hyperscience.ai/docs/security-advisory"}],"url":"https://launchinyourcloud.com/directory/hyperscience/","website":"https://help.hyperscience.ai/deployment/docs/helm-chart"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/azure/correspondence-management/"}