Correspondence management on Google Cloud
Formal correspondence intake, assignment, replies and response evidence.
2 documented options on Google Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.
Read this page as JSON or Markdown.
| Listing | Documented clouds | Deployment and infrastructure | Licensing | Installation | Operations and limitations |
|---|---|---|---|---|---|
| Hyland OnBase On-Premise | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial OnBase licenses and separately scoped modules | Vendor or partner-assisted on-premises installation | Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.Scope and evidenceThis 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.
Cloud evidence reviewed 2026-11-12 |
| Hyperscience Hypercell | AWS, Azure, Google Cloud | Customer-operated Servers / containers | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. | Helm / Kubernetes operator; Kubernetes manifests | 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.Scope and evidenceThe 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.
Cloud evidence reviewed 2026-11-19 |
Deployment evidence and category fit
Hyland OnBase On-Premise
Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.
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.
- Hyland partner statement on customer-managed OnBase cloud deployments ↗
Partner evidence · Reviewed 2026-11-12 · Version: OnBase 18+ in partner statement; confirm current release. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Hyland identification of Reveille as an authorized integration partner ↗
Partner relationship · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
Cloud evidence reviewed 2026-11-12. Full listing and qualifications
Hyperscience Hypercell
Commercial document-intake and extraction platform installed into customer Kubernetes infrastructure.
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.
- Helm Chart (AWS/GCP) ↗
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.
Cloud evidence reviewed 2026-11-19. Full listing and qualifications
Deployment and procurement checks
- Private offers
- Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement. Provider source ↗ · Reviewed 2026-11-14
- Private connectivity
- Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture. Provider source ↗ · Reviewed 2026-11-14
- External workload access
- Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles. Provider source ↗ · Reviewed 2026-11-14
- Regulated environments
- Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification. Provider source ↗ · Reviewed 2026-11-14
For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.
Plan this deployment
Account boundary: Google Cloud project. Access: IAM policies and service accounts. Network: VPC network.
Provider documentation ↗ · Guidance reviewed 2026-11-10. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.
Compare this category across clouds · Search these listings · Compare 2–4 listings