
# Document management on Google Cloud

Compare documented Document management deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/document-management/
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.


## Provider guidance

- Account boundary: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### 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.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (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.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (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.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (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.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

The listings below have evidence for Google Cloud. Read each cloud evidence note for the applicable package, edition and support qualifications.

4 listings.


## Hyland OnBase On-Premise

Customer-hosted enterprise content and case platform for document-heavy business processes.

- Listing: https://launchinyourcloud.com/directory/onbase/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial OnBase licenses and separately scoped modules
- Licensing model: commercial-only
- Installation: Vendor or partner-assisted on-premises installation
- Architecture: Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.
- Operations: Customer maintains on-premises infrastructure and backups; agree implementation, upgrades and support responsibilities with Hyland or its partner.
- Product website: https://www.hyland.com/
- Source review: 2026-11-13; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

Customer-hosted enterprise application, document storage and database; deployment sizing and modules require implementation planning.


### Category fit

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

- records-management: Retention and destruction workflows for electronic documents; WorkView also supports tracking physical records.

- contract-management: Configurable WorkView contract applications and document workflows; confirm modules and implementation scope.

- financial-application-management: Loan-document tracking and integration with loan origination systems; this supports the document process rather than replacing a lending core.

- case-management: Configurable case applications connect case data, documents, tasks and approvals.

- correspondence-management: Configurable OnBase workflows can store and route correspondence documents with related case work; implementation is solution-specific.

- vendor-supplier-document-management: Vendor case records and supporting documents in WorkView and accounts-payable workflows; not a dedicated supplier-risk service.

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

- claims-management: Document capture and workflows integrated with insurance claims systems; not a replacement for claims adjudication software.

- workflow-automation: Content and case workflows with routing, rules and low-code WorkView applications.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/ (checked 2026-11-12). Source: https://www.hyland.com/en/partners/reveille (checked 2026-11-12). 


### Cloud deployment evidence

- Hyland partner statement on customer-managed OnBase cloud deployments (aws, azure, gcp): https://www.reveillesoftware.com/solutions/reveille-for-hyland-onbase/
  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.
  Source type: partner-evidence; reviewed: 2026-11-12; vendor support: not-assessed. Versions: OnBase 18+ in partner statement; confirm current release.

- Hyland identification of Reveille as an authorized integration partner (aws, azure, gcp): https://www.hyland.com/en/partners/reveille
  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.
  Source type: partner-relationship; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- OnBase platform capabilities: https://www.hyland.com/en/solutions/products/onbase

- On-premises product terms: https://legal.hyland.com/pst-on-premise-multi-products

- WorkView business application examples: https://www.hyland.com/en/resources/articles/workview-product-overview

- HR files and policy sign-offs: https://www.hyland.com/en/resources/terminology/human-resources/document-management

- OnBase workflow routing: https://docs.hyland.com/r/OnBase/Workflow/Foundation-23.1/Workflow/Overview/Workflow-Overview

- Correspondence document integration: https://docs.hyland.com/r/OnBase/Application-Client-Connector/Foundation-24.1/Application-Client-Connector/Overview/Introduction

- Loan-document tracking solution: https://community.hyland.com/kb/articles/1332-hyland-services-loan-document-tracking

- Insurance claims integration case study: https://www.hyland.com/en/customers/p-c-insurer

### Licensing sources

- https://legal.hyland.com/pst-on-premise-multi-products

### Infrastructure sources

- https://legal.hyland.com/pst-on-premise-multi-products


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 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 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. 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 (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 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. 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 (reviewed 2026-11-20).

- Minimum footprint / sizing: Documented. 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. 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 (reviewed 2026-11-20).

- License pricing: Documented. 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. 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 (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## LogicalDOC Commercial On-Premise

Customer-hosted commercial document platform for controlled business files and supplier documentation.

- Listing: https://launchinyourcloud.com/directory/logicaldoc-commercial/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial edition under LogicalDOC EULA; separate Community Edition exists
- Licensing model: commercial-only
- Installation: Licensed on-premises server installation
- Architecture: Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.
- Operations: Customer manages application, database, document storage, backups and upgrades; agree support scope and required commercial capabilities.
- Product website: https://www.logicaldoc.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

The selected licensed commercial edition follows LogicalDOC EULA restrictions. This classification does not cover the separate open-source Community Edition.

Persistent application with relational metadata database, document file storage and search services; selected components depend on edition.


### Category fit

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

- vendor-supplier-document-management: Supplier certificate storage, expiry tracking and configured reports, documented in the Lesepidado implementation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.logicaldoc.com/ (checked 2026-11-12). 


### Cloud deployment evidence

- LogicalDOC private-cloud deployment options (aws, azure, gcp): https://www.logicaldoc.com/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- On-premises deployment: https://www.logicaldoc.com/product/on-premise-dms

- Application and storage architecture: https://www.logicaldoc.com/product/architecture

- On-premises supplier certificate implementation: https://www.logicaldoc.com/blog/660-lesepidado-logicaldoc-case-study

- Commercial end-user license: https://www.logicaldoc.com/eula

### Licensing sources

- https://www.logicaldoc.com/eula

### Infrastructure sources

- https://www.logicaldoc.com/product/on-premise-dms

- https://www.logicaldoc.com/product/architecture


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 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 commercial administration guide documents SAML 2.0 service-provider integration, login-time account creation and optional single logout. It does not establish that every Business/Enterprise license includes the feature; confirm licensed features and test the identity provider. Scope: Commercial LogicalDOC documentation; edition/contract entitlement not established. Source: https://docs.logicaldoc.com/en/access-control/saml-single-sign-on (reviewed 2026-11-14).

- SCIM provisioning: Sources checked — unresolved. The SAML guide describes user creation at first login. It does not establish a SCIM provisioning/deprovisioning API or licensed entitlement; login-time account creation must not be labeled SCIM. Scope: SAML/JIT documentation checked; SCIM remains unresolved. Source: https://docs.logicaldoc.com/en/access-control/saml-single-sign-on (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes a logicaldoc/logicaldoc image and links its Docker distribution source. A licence activation code is required, including for evaluation. The catalog entry is dated 2018; confirm a currently supported image tag and matching database/Java requirements before adopting it. Scope: Vendor commercial Docker distribution; current supported artifact version must be confirmed. Source: https://www.logicaldoc.com/download/docker-images (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/logicaldoc/logicaldoc/. Artifact reference: Select a vendor-supported immutable image; catalog entry date is not a current release.

- Minimum footprint / sizing: Documented. The current vendor matrix specifies a dedicated 64-bit 2.5-GHz eight-core server, 24 GB memory and 512 GB fast disk for application deployment. It lists JDK 25 and current OS baselines. Concurrency, repository data, configuration and HA require additional sizing; older installation guides show different minima. Scope: Current vendor commercial-server requirements; verify against selected release. Source: https://www.logicaldoc.com/resources/system-requirements (reviewed 2026-11-20).

- License pricing: Documented. The on-premises offer requires commercial licences and directs buyers to request a quote. No numeric price is established by the reviewed product page. Agree user counts, edition, term and maintenance separately from hosting and operating costs. Scope: Commercial on-premises offer; quoted licence terms, not Community pricing. Source: https://www.logicaldoc.com/product/on-premise-dms (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## M-Files On-Premises

Customer-operated document vault and information-governance platform with metadata-driven workflows.

- Listing: https://launchinyourcloud.com/directory/m-files-on-premises/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription software; on-premises and support entitlements follow the order
- Licensing model: commercial-only
- Installation: Licensed Windows Server installation; vendor implementation planning
- Architecture: Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.
- Operations: Customer maintains server infrastructure, vault backups and upgrades; review server requirements and the contracted support and licensing connections.
- Product website: https://www.m-files.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

Commercial M-Files server subscription software. The EULA covers ordered on-premises or cloud software and associated licenses/support; this entry selects on-premises operation.

Persistent customer-operated M-Files Server and vault/database infrastructure on Windows Server.


### Category fit

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

- records-management: Configurable records retention and disposition rules with document history and audit trails.

- policy-procedure-management: Configured SOP, compliance and training workflows supported by metadata, permissions and document lifecycle controls; not a separately verified turnkey policy module.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html (checked 2026-11-12). 


### Cloud deployment evidence

- M-Files self-managed cloud deployment (aws, azure, gcp): https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated deployment options: https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html

- Records retention and disposition: https://www.m-files.com/supplemental/records-management/

- SOP, training and governance application patterns: https://www.m-files.com/wp-content/uploads/2023/07/How-M-Files-Mitigates-Risks-for-Accounting-Firms.pdf

- Software subscription license agreement: https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ

### Licensing sources

- https://empower.m-files.com/sfc/servlet.shepherd/version/download/068QA00000Y5dQGYAZ

### Infrastructure sources

- https://userguide.m-files.com/user-guide/latest/eng/deployment_options.html


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 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 vault authentication guide explicitly links on-premises Microsoft Entra configuration and OAuth 2.0/OIDC providers for any environment. Client/web-add-in configuration and licensed implementation requirements remain separate. Scope: M-Files document-vault authentication; not Hubshare or automatic cloud login setup. Source: https://userguide.m-files.com/user-guide/latest/eng/document_vault_authentication.html (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. The guide documents subscription-level SCIM for on-premises servers joined to M-Files Manage. A separate vault-level Entra SCIM method requires Entra ID Premium and limits Entra authentication to Desktop; on-premises plugin-based synchronization is also documented. Scope: M-Files on-premises provisioning; Manage connection, method and client limitations differ. Source: https://userguide.m-files.com/user-guide/latest/eng/user_synchronization_entra_id.html (reviewed 2026-11-16).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies an installation package containing Server, Admin and optional desktop components. The guide links the latest package through the vendor download portal and documents advanced installation options. Package access and entitlements must be obtained; this is not a public infrastructure template. Scope: Current on-premises Windows installer distribution. Source: https://www.userguide.m-files.com/user-guide/latest/eng/Installing_the_software.html (reviewed 2026-11-20). Deployment artifact: https://product.m-files.com/downloads/. Artifact reference: Vendor latest-download portal; authenticated or entitled access may be required.

- Minimum footprint / sizing: Documented. The single-server guide lists 2 CPU cores, 1 GB RAM and 300 MB for M-Files Server itself. Its examples scale to 4 cores/4 GB for 50,000 objects and 8 cores/16 GB plus SQL Server for one million. File storage, database, backups and HA need separate sizing; these are object-count examples, not a 100-user guarantee. Scope: Vendor single-server guidelines; application storage and HA excluded. Source: https://userguide.m-files.com/user-guide/latest/eng/hardware_guidelines_for_single_server_environments.html (reviewed 2026-11-20).

- License pricing: Documented. The on-premises server is linked to a customer subscription using an initial licence from M-Files Manage. Automated renewal needs outbound licensing endpoints. This establishes subscription/licence delivery, not a published per-user price or infrastructure cost. Scope: On-premises server subscription and licence automation. Source: https://userguide.m-files.com/user-guide/latest/eng/?contextId=133304 (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Philter by Philterd (Self-Hosted / Cloud Marketplace)

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

- Listing: https://launchinyourcloud.com/directory/philter/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application.
- 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://www.philterd.ai
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

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

Philter REST service on customer EC2 through the vendor's supported AMI or separately installed upstream application. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

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

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

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.philterd.ai/philter/ (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy
  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.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Marketplace VM (azure): https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter
  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.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.

- Philter: Open Source, Self-Hosted PII & PHI Redaction API (gcp): https://www.philterd.ai/philter/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jzonthemtn, AzazelSensei, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/philterd/philter/graphs/contributors

- Upstream project: https://github.com/philterd/philter

### Sources

- AWS Marketplace AMI: https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy

- Azure Marketplace VM: https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter

- Philter: Open Source, Self-Hosted PII & PHI Redaction API: https://www.philterd.ai/philter/

- Apache-2.0 LICENSE.txt: https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt

- Philterd Pricing: https://philterd.ai/pricing/

- AWS Marketplace EULA PDF: https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs

- GitHub Releases: https://github.com/philterd/philter/releases

- Philter runtime and library corrections: https://github.com/philterd/philter/releases/tag/4.0.1

### Licensing sources

- https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt

- https://philterd.ai/pricing/

- https://d7umqicpi7263.cloudfront.net/eula/dKWyRA8OFGG7dZHQQ11-sVYBd8p0ZdR4ZLHVrytHdhs

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy

- https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter

- https://www.philterd.ai/philter/


### Buyer diligence


Research coverage: 7/12 fields (58%); 5 documented, 2 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: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from Philterd, LLC. The publisher package and upstream application have separate maintenance. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Philterd. Its package version is 4.0.1; verify the contained application and required entitlements separately. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace) selected Azure public offer. Source: https://catalogapi.azure.com/offers/philterdllc1687189098111.philter?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Supporting source: AWS delivery and package version — https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy. Offer philterdllc1687189098111.philter: Philterd, LLC; Virtual machine; https://marketplace.microsoft.com/en-us/product/philterdllc1687189098111.philter. Offer prodview-y32h6usoum7zy: Philterd; Amazon Machine Image (AMI); package 4.0.1; https://aws.amazon.com/marketplace/pp/prodview-y32h6usoum7zy.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: philterdllc1687189098111.philter public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/philterdllc1687189098111.philter?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. Philter documents API keys and optional password sign-in for its own users, while its separate UI is described as in development. The reviewed material does not establish an external SAML/OIDC user-federation path for the self-hosted redaction service. API bearer/session keys are not sufficient SSO evidence. Scope: Philter redaction API authentication; separate UI, cloud marketplace subscription and customer portal sign-in are distinct surfaces. Source: https://github.com/philterd/philter/blob/main/docs/docs/sign_in_security.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 upstream README publishes versioned philterd/philter Docker images, including 4.0.1, and a Compose recipe that builds the checked-out source. Use the released image for a release-specific deployment, configure API credentials and persistence/cache services, and distinguish source builds from the marketplace package. Scope: Philter 4.0.1 upstream runtime packaging; not a complete provider infrastructure or HA template. Source: https://github.com/philterd/philter/blob/4.0.1/README.md (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/philterd/philter. Artifact reference: philterd/philter:4.0.1; upstream documentation states there is no latest tag.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed runtime and configuration documentation does not establish a quantitative whole-host CPU/RAM/storage floor for the selected redaction workload. Document rendering, OCR/models, request concurrency, cache and durable data can change memory and storage needs; per-document limits are not host sizing. Scope: Self-hosted Philter application and selected processing/cache dependencies; marketplace VM size is not a universal minimum. Source: https://github.com/philterd/philter/blob/4.0.1/README.md (reviewed 2026-11-20). Supporting source: Runtime settings and processing limits — https://github.com/philterd/philter/blob/main/docs/docs/settings.md.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/philterd/philter/main/LICENSE.txt (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 4.0.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Philter by Philterd (Self-Hosted / Cloud Marketplace) upstream application; verify compatibility with the selected package. Source: https://github.com/philterd/philter/releases/tag/4.0.1 (reviewed 2026-11-19).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Philter runtime and library corrections (security-advisory): Philter 4.0.1 updates Brotli and Jackson-related dependencies. Scope: The Philter 4.0.1 release identifies corrected dependencies; no blanket affected range is inferred for independently patched systems. Conditions: Exposure depends on the actual Ubuntu/JVM libraries and configured document/API processing. Action: Check the installed runtime against Philter 4.0.1 dependency corrections and update the image or affected libraries through the documented process. Source: https://github.com/philterd/philter/releases/tag/4.0.1; reviewed 2026-11-19.



