Document management on Google Cloud

Document platforms, repositories and APIs.

4 documented options on Google Cloud. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Hyland OnBase On-PremiseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial OnBase licenses and separately scoped modules

Vendor or partner-assisted on-premises installationCustomer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
Scope and evidence

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

    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 identification of Reveille as an authorized integration partner — 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.

    Partner relationship · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

LogicalDOC Commercial On-PremiseAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial edition under LogicalDOC EULA; separate Community Edition exists

Licensed on-premises server installationCustomer manages application, database, document storage, backups and upgrades; agree support scope and required commercial capabilities.
Scope and evidence

Scope is a licensed commercial on-premises edition, not Community Edition feature parity. The supplier-document example uses configured metadata, expiry dates and periodic reports; it is a document process rather than a supplier-assessment service.

  • LogicalDOC private-cloud deployment options — The vendor explicitly offers private-cloud installation on AWS, Azure and Google Cloud, separately from its managed LogicalDOC Cloud service. Confirm the commercial edition, system requirements and support agreement.

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

Cloud evidence reviewed 2026-11-12

M-Files On-PremisesAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial subscription software; on-premises and support entitlements follow the order

Licensed Windows Server installation; vendor implementation planningCustomer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.
Scope and evidence

Only customer-operated M-Files deployment is listed. The documented SOP and records patterns require configuration and possibly selected components. Confirm the available edition, deployment scope and integrations rather than assuming that every separately packaged cloud solution is included.

  • M-Files self-managed cloud deployment — The vendor documents customer-managed Windows Server virtual machines on AWS, Azure and Google Cloud as the same server deployment model used on-premises. This is distinct from M-Files Cloud; confirm server, vault/database and licensing requirements.

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

Cloud evidence reviewed 2026-11-12

Philter by Philterd (Self-Hosted / Cloud Marketplace)AWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

VM imageCustomer 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 evidence

Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations. Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process.

  • AWS Marketplace AMI — Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.

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

  • Azure Marketplace VM — Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.

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

  • Philter: Open Source, Self-Hosted PII & PHI Redaction API — Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.

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

Cloud evidence reviewed 2026-11-19

Deployment evidence and category fit

Hyland OnBase On-Premise

Enterprise content repository with capture, document workflows and integration with business applications.

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

LogicalDOC Commercial On-Premise

Searchable repository, metadata, versioning and configurable document workflows in a commercial on-premises deployment.

Scope is a licensed commercial on-premises edition, not Community Edition feature parity. The supplier-document example uses configured metadata, expiry dates and periodic reports; it is a document process rather than a supplier-assessment service.

  • LogicalDOC private-cloud deployment options ↗

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

    The vendor explicitly offers private-cloud installation on AWS, Azure and Google Cloud, separately from its managed LogicalDOC Cloud service. Confirm the commercial edition, system requirements and support agreement.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

M-Files On-Premises

Metadata-driven document vaults with controlled access, document relationships and workflows.

Only customer-operated M-Files deployment is listed. The documented SOP and records patterns require configuration and possibly selected components. Confirm the available edition, deployment scope and integrations rather than assuming that every separately packaged cloud solution is included.

  • M-Files self-managed cloud deployment ↗

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

    The vendor documents customer-managed Windows Server virtual machines on AWS, Azure and Google Cloud as the same server deployment model used on-premises. This is distinct from M-Files Cloud; confirm server, vault/database and licensing requirements.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Philter by Philterd (Self-Hosted / Cloud Marketplace)

Open-source API that identifies and redacts sensitive information in text and PDFs.

Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations. Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process.

  • Philter: Open Source, Self-Hosted PII & PHI Redaction API ↗

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

    Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Apache-2.0 upstream self-hosting and the paid turnkey AMI are separate procurement options. This is a disclosure-preparation component, not a complete FOI deadline, appeal or case-management system. The AMI's application version and software/support charge must be kept distinct from infrastructure costs. The vendor also explicitly identifies its Google Cloud Marketplace application, separate from optional redaction-service integrations.

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