
# Records management on AWS

Compare documented Records management deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/records-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: AWS account
- 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.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

8 listings.


## Alfresco Content Services + Governance Services

Customer-operated content and records management with retention and record-declaration workflows.

- Listing: https://launchinyourcloud.com/directory/alfresco-governance/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Community and commercial editions; capabilities and support differ
- Licensing model: open-source
- Installation: Distribution ZIP/module installation; underlying platform container/Helm options
- Architecture: Customer-operated content repository, search and database
- Operations: Customer operates repository, search, database, backups and upgrades. Enterprise container access requires vendor credentials.
- Product website: https://www.hyland.com/en/products/alfresco
- Source review: 2026-11-14; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-14

### Scope and qualifications

Governance Services adds records management to Alfresco Content Services. Select the exact edition and supported production installation. Storage connectors do not establish provider-specific deployment support, and the documented development Docker Compose configuration is not a recommended production topology. Hyland’s current supported-platform documentation lists Governance Services 26.2. The retained 25.2 installation page is version-specific, so verify the selected Content Services and Governance Services versions against the current compatibility matrix.

This broad combined Content Services/Governance listing spans LGPL-3.0 Community software and commercially licensed Enterprise software with additional enterprise extensions. Community-only deployments and Enterprise deployments have different rights/features.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- records-management: Records lifecycle management with file plans, retention schedules, declaration and auditing. Community and commercial editions differ. Docker Compose examples are for development/testing; review a supported production topology.

- document-management: Content Services provides the content repository and document management; Governance Services adds records lifecycle capabilities.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/Alfresco/acs-deployment/blob/master/docs/helm/eks-deployment.md (checked 2026-11-12). Source: https://github.com/Alfresco/docs-alfresco/blob/master/governance-services/7.4/install/index.md (checked 2026-11-12). 


### Cloud deployment evidence

- Alfresco Content Services deployment on Amazon EKS (aws): https://github.com/Alfresco/acs-deployment/blob/master/docs/helm/eks-deployment.md
  The vendor documents customer-operated ACS Enterprise and Community deployments on EKS, including persistent storage and customized repository/Share images. Evidence covers the ACS platform on which Governance Services is installed. Add the compatible Governance Services images or modules, required entitlements and production configuration; the separate development-only Compose example is not a production recommendation.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Alfresco Governance Services 7.4 add-on installation (aws): https://github.com/Alfresco/docs-alfresco/blob/master/governance-services/7.4/install/index.md
  The vendor versioned 7.4 manual documents Governance Services distribution ZIP/AMP installation on the compatible ACS platform and a development/test-only Compose option. Pair the add-on documentation with the ACS EKS deployment evidence and confirm the supported ACS/Governance release combination and commercial entitlements. This is not a claim that the development Compose file is a production topology.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Versions: Governance Services 7.4; confirm compatible ACS release.


### Sources

- Current Alfresco documentation: https://docs.hyland.com/p/alfresco

- Governance Services 25.2 installation options: https://support.hyland.com/r/Alfresco/Alfresco-Governance-Services/25.2/Alfresco-Governance-Services/Install

- Official container installation source and limitations: https://github.com/alfresco/docs-alfresco/blob/master/governance-services/7.2/install/docker.md

- Licensing and edition terms: https://github.com/Alfresco/alfresco-community-repo

- Licensing and edition terms: https://docs.alfresco.com/governance-services/community/

- Licensing and edition terms: https://pages.alfresco.com/rs/alfresco/images/en-enterprise-community-edition-comparison.pdf

- Licensing and edition terms: https://connect.hyland.com/t5/alfresco-blog/open-source-licensing/ba-p/173240

- Current Alfresco supported platforms and Governance Services releases: https://docs.hyland.com/r/Current/Alfresco-Supported-Platforms

### Licensing sources

- https://github.com/Alfresco/alfresco-community-repo

- https://docs.alfresco.com/governance-services/community/

- https://pages.alfresco.com/rs/alfresco/images/en-enterprise-community-edition-comparison.pdf

- https://connect.hyland.com/t5/alfresco-blog/open-source-licensing/ba-p/173240

### Infrastructure sources

- https://support.hyland.com/r/Alfresco/Alfresco-Governance-Services/25.2/Alfresco-Governance-Services/Install

- https://github.com/alfresco/docs-alfresco/blob/master/governance-services/7.2/install/docker.md

- https://docs.hyland.com/r/Current/Alfresco-Supported-Platforms


### Buyer diligence


Research coverage: 4/12 fields (33%); 1 documented, 3 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: Sources checked — unresolved. The official Identity Service source describes SAML federation for Alfresco Content Services, the parent platform. It does not establish the current Governance Services/ACS/Identity Service supported-version combination or commercial entitlement. Confirm that matrix for the selected governance installation. Scope: Parent-platform federation documented; current Governance Services combination unresolved. Source: https://raw.githubusercontent.com/Alfresco/docs-alfresco/master/identity-service/latest/index.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 archived 7.2 Docker Compose instructions are explicitly for development and test. Enterprise images require Quay credentials through Alfresco Support; do not treat this recipe as a supported production architecture. Scope: Alfresco Governance Services 7.2 Enterprise container recipe; historical, not current-release certification. Source: https://github.com/alfresco/docs-alfresco/blob/master/governance-services/7.2/install/docker.md (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The version-7.2 Compose source cites a 16-GB required memory setting while describing lower troubleshooting allocations. It explicitly limits Compose to development/test. This does not establish a current production or HA footprint for ACS plus Governance Services and supporting search/database components. Scope: Legacy development/test container recipe; current production sizing unresolved. Source: https://raw.githubusercontent.com/Alfresco/docs-alfresco/master/governance-services/7.2/install/docker.md (reviewed 2026-11-20).

- License pricing: Sources checked — unresolved. The reviewed installation source requires customer-issued Quay credentials for Enterprise Governance images. Community source licensing does not establish those commercial entitlements, supported ACS/AGS combinations or pricing. Obtain a current subscription and module quote for the selected deployment. Scope: Enterprise distribution access; current licence/pricing terms unresolved. Source: https://raw.githubusercontent.com/Alfresco/docs-alfresco/master/governance-services/7.2/install/docker.md (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## FormKiQ Records Management

Implement retention, legal hold, defensible disposition, and compliant lifecycle policies for governed records.

- Listing: https://launchinyourcloud.com/directory/formkiq-records-management/
- Publisher listing: Yes — FormKiQ publishes this directory.
- Entry kind: solution; configured solution on formkiq
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: serverless
- License: Commercial FormKiQ Advanced or Enterprise; confirm required extensions
- Licensing model: commercial-only
- Installation: Configure the solution in a FormKiQ deployment; CloudFormation installs the platform.
- Architecture: Application on the FormKiQ document and workflow platform
- Operations: Customer-managed AWS deployment option; agree solution configuration, modules and support with FormKiQ.
- Product website: https://formkiq.com/solutions/records-management/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This is a business solution built on FormKiQ, not a separate infrastructure product. Its application configuration and available capabilities depend on the agreed edition and extension modules. This listing covers the customer-managed AWS option; vendor-managed deployments are outside this entry.

This listing describes the packaged Business Solution available through commercial Advanced/Enterprise deployments. The separate open-source Core platform does not by itself include this packaged solution.

Serverless baseline for this business solution; no required OpenSearch dependency is identified. Optional OpenSearch add-ons are evaluated separately and do not add a Hybrid label to this listing.


OpenSearch required for this solution: No

### Category fit

- records-management: Retention, legal hold and disposition of business records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq (checked 2026-11-12). 


### Cloud deployment evidence

- FormKiQ commercial AWS installation (aws): https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq
  The publisher documents customer-specific CloudFormation installation for Essentials, Advanced and Enterprise, including target AWS regions and licensed modules. Business solutions are configurations of this same AWS platform; their solution scope and entitlements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed. Edition: FormKiQ platform; solution configuration and entitlement must be agreed separately.


### Sources

- Records Management solution: https://formkiq.com/solutions/records-management/

- Business solution editions and platform relationship: https://formkiq.com/solutions/

- Commercial deployment notes: https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq

- Platform infrastructure and optional components: https://docs.formkiq.com/docs/platform/overview

- Licensing and edition terms: https://formkiq.com/pricing/

### Licensing sources

- https://formkiq.com/solutions/

- https://formkiq.com/pricing/

### Infrastructure sources

- https://formkiq.com/solutions/records-management/

- https://docs.formkiq.com/docs/platform/overview


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 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.

This is a configured solution. Parent platform buyer facts: https://launchinyourcloud.com/directory/formkiq/#buyer-diligence. Parent entitlements, sizing and release versions are not automatically established for this solution.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The solution overview describes configurable access and workflows but does not establish its actual end-user SAML/OIDC integration, identity provider or account mapping. FormKiQ platform Cognito/JWT and IAM/API authentication are separate evidence; obtain the solution-specific login design and included commercial modules. Scope: FormKiQ Records Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/records-management/ (reviewed 2026-11-21). Supporting source: Underlying platform architecture — https://docs.formkiq.com/docs/platform/overview.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Record-level access, retention, legal holds and disposition controls are described; approved policies and authorised staff remain prerequisites. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Records Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/records-management/ (reviewed 2026-11-16).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Commercial installations use customer-specific CloudFormation templates supplied during onboarding. Request the template for this solution, licensed modules and AWS region; the public Core template does not include the configured solution. Scope: FormKiQ Records Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/records-management/ (reviewed 2026-11-16). Supporting source: Commercial deployment and customer-specific templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- Minimum footprint / sizing: Sources checked — unresolved. The configured solution uses customer-specific deployment and optional processing/search/integration modules. No quantitative solution-specific CPU/RAM/concurrency/storage baseline was established. Serverless platform architecture and a document-import benchmark do not size the complete business workflow, external services or HA/recovery requirements. Scope: FormKiQ Records Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/records-management/ (reviewed 2026-11-21). Supporting source: Platform architecture and optional components — https://docs.formkiq.com/docs/platform/overview. Supporting source: Commercial deployment templates — https://docs.formkiq.com/docs/formkiq-modules/installation/formkiq.

- License pricing: Documented. The solution requires agreed commercial scope. The solution page identifies Enterprise; confirm the edition, modules, implementation and support in a solution quote. Published base-platform prices are not the total solution price; AWS usage and connected services are additional. Scope: FormKiQ Records Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/records-management/ (reviewed 2026-11-16). Supporting source: Edition pricing and separately quoted modules/services — https://formkiq.com/pricing/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







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







## Laserfiche Self-Hosted

Self-hosted document and records platform with forms and configurable business process automation.

- Listing: https://launchinyourcloud.com/directory/laserfiche-self-hosted/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial self-hosted software; license and module entitlements apply
- Licensing model: commercial-only
- Installation: Licensed Laserfiche 12 Windows installers
- Architecture: Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.
- Operations: Customer operates supported Windows servers, repository/database backups and product updates; follow the chosen modules installation requirements.
- Product website: https://www.laserfiche.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 the self-hosted product. Use-case pages describe platform workflows; confirm availability and licensing for the chosen version and modules. The current support matrix requires Windows Server Desktop Experience and explicitly excludes Docker and Kubernetes deployment for self-hosted applications.

This record covers the commercial self-hosted Laserfiche product. Installation and activation require licensed application entitlements; marketplace templates do not confer a license to the underlying platform.

Persistent Windows Server applications, repository storage and database; current support guidance excludes containerized self-hosted applications.


### Category fit

- document-management: Repository, capture, search and document process automation on customer-operated servers.

- records-management: Document lifecycle, retention, access controls and disposition; configure schedules for the organization.

- contract-management: Configurable contract creation, approval and records workflows; confirm the selected self-hosted modules.

- financial-application-management: Document routing and automation for loan applications, illustrated by the vendor banking case study.

- case-management: Forms, repository content and process workflows for service case management; implementation is configured to the case process.

- hr-employee-records-management: Employee records, onboarding approvals and access controls for HR processes.

- claims-management: Low-code claims review and approval workflows; does not establish an insurance policy or adjudication core.

- workflow-automation: Forms and document workflows for routing, approvals and task automation.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf (checked 2026-11-12). 


### Cloud deployment evidence

- Laserfiche reseller installation terms for customer AWS and Azure environments (aws, azure): https://mccmeetings.blob.core.usgovcloudapi.net/nwpraguemn-pubu/MEET-Packet-7ead60072b1d4ae485774089b3fea95c.pdf
  Cities Digital installation terms, published in the municipal meeting packet on PDF page 40, explicitly cover new Azure or AWS environments and exclude Laserfiche Cloud from that section. The client supplies Windows, SQL Server and network configuration and validates workflows. This documents a reseller-assisted self-hosted path; confirm the current server version, license, support scope and implementation fees.
  Source type: public-procurement-record; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosted installation overview: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- Current operating system and deployment support: https://support.laserfiche.com/kb/1012418/raw

- Business process solutions: https://www.laserfiche.com/solutions/

- Document and records capabilities: https://www.laserfiche.com/products/document-and-records-management/

- Loan application automation case study: https://www.laserfiche.com/resources/customer-stories/growin-bank-expedites-loan/

- Insurance claims workflows: https://www.laserfiche.com/solutions/financial-services/insurance/

- Software license agreement and legal resources: https://www.laserfiche.com/legal/

### Licensing sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://www.laserfiche.com/legal/

### Infrastructure sources

- https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm

- https://support.laserfiche.com/kb/1012418/raw


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 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: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Laserfiche 12 Directory Server accepts SAML 2.0 identity providers using imported metadata and claim mappings. Configure the licensing site, client integrations and local-account policy; this does not establish every optional module or Cloud entitlement. Scope: Laserfiche 12 self-hosted Directory Server federation. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/admin-lfds-saml-identity-provider.htm (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. Laserfiche 12 uses a product installer that selects applications, detects installed versions and offers updates. Follow new-installation, repository and system-specification instructions; this page is not a public IaC package. Scope: Laserfiche self-hosted version 12 installer and initial configuration. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/install-overview.htm (reviewed 2026-11-16).

- Minimum footprint / sizing: Sources checked — unresolved. The current supported-platforms list establishes Windows Server and database compatibility, but does not supply a complete Laserfiche 12 CPU/RAM topology. Public numeric checklists found cover version 11 or older. Obtain a version-12 component and HA sizing design rather than applying those legacy minima. Scope: Laserfiche 12 self-hosted hardware sizing unresolved. Source: https://support.laserfiche.com/kb/1012418/pdf (reviewed 2026-11-20). Supporting source: Older version-11 server minimum is not a version-12 sizing recommendation — https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Subsystems/LFAdmin/Content/Installation/Laserfiche_Server_%28United%29_pre_check.htm.

- License pricing: Sources checked — unresolved. The self-hosted Directory Server workflow requires a licensing site registering the repository server. The reviewed integration documentation does not establish current licence prices, user metrics or maintenance terms; obtain an on-premises quote rather than applying Laserfiche Cloud prices. Scope: Self-hosted licence delivery established; commercial pricing and terms unresolved. Source: https://doc.laserfiche.com/laserfiche.documentation/12/userguide/en-us/content/config-lfm-configuration-page-connection.htm (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.







## MailStore Service Provider Edition (SPE)

Commercial multitenant email archive operated by service providers in their own cloud accounts.

- Listing: https://launchinyourcloud.com/directory/mailstore-spe/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage.
- Operations: The service provider operates SPE in its own cloud account and serves its customers; this is not an end-customer-owned mailbox archive.
- Product website: https://help.mailstore.com/en/spe/Frequently_Asked_Questions
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The buyer/operator is the service provider. Its end customers do not thereby own the provider's cloud account. SPE licensing and tenant operations are separate from MailStore Server and from a vendor-hosted archive subscription; account for the documented storage and I/O demands.

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

MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- records-management: Commercial multitenant email archive operated by service providers in their own cloud accounts.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.mailstore.com/en/spe/Frequently_Asked_Questions (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.mailstore.com/en/spe/Frequently_Asked_Questions (checked 2026-11-19). 


### Cloud deployment evidence

- MailStore SPE FAQ (aws, azure): https://help.mailstore.com/en/spe/Frequently_Asked_Questions
  MailStore Service Provider Edition services on supported Windows IaaS instances and high-throughput persistent storage. The buyer/operator is the service provider. Its end customers do not thereby own the provider's cloud account. SPE licensing and tenant operations are separate from MailStore Server and from a vendor-hosted archive subscription; account for the documented storage and I/O demands.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- MailStore SPE FAQ: https://help.mailstore.com/en/spe/Frequently_Asked_Questions

- MailStore SPE Product: https://www.mailstore.com/en/products/mailstore-spe/

- SPE Changelog (v26.4): https://www.mailstore.com/en/products/mailstore-spe/changelog/

### Licensing sources

- https://www.mailstore.com/en/products/mailstore-spe/

### Infrastructure sources

- https://help.mailstore.com/en/spe/Frequently_Asked_Questions


### 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. SPE end-user access documents redirecting synchronised Microsoft 365 or Google Workspace users to the provider for authentication, including client and web access. Configure the tenant instance and directory integration. This does not establish the same mechanism for the service-provider management console. Scope: MailStore SPE tenant archive-user federated login; infrastructure administrators separate. Source: https://help.mailstore.com/en/spe/End_User_Access (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. SPE supplies a Windows installer through its partner portal that installs binaries for any server role; initial configuration assigns single-server or distributed roles. Obtain partner access and licence, then configure instances, TLS, firewall, persistent storage and updates. Scope: MailStore SPE partner-delivered role installer; operational configuration separate. Source: https://help.mailstore.com/en/spe/Installing_MailStore_Service_Provider_Edition (reviewed 2026-11-21). Deployment artifact: https://help.mailstore.com/en/spe/Installing_MailStore_Service_Provider_Edition. Artifact reference: Current vendor SPE installation instructions.

- Minimum footprint / sizing: Documented. The SPE requirements give each standalone Management Server and Client Access Server 2 GB RAM and 150 MB installation disk, with x64 CPU; archive Instance Hosts have separate workload-dependent requirements. These role baselines exclude stored mail/indexes, database working sets, replicas and HA capacity. Scope: MailStore SPE management/access role minimums; not a whole archive host or HA footprint. Source: https://help.mailstore.com/en/spe/System_Requirements (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: MailStore Service Provider Edition (SPE); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.mailstore.com/en/products/mailstore-spe/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Piler Enterprise

Commercial self-hosted email archive with retention, search and compliance-policy controls.

- Listing: https://launchinyourcloud.com/directory/piler-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Docker / Compose
- Architecture: Persistent Linux or Docker application, database, search and archive storage in customer AWS infrastructure.
- 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://docs.mailpiler.com/piler-ee/installation/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Use the current Piler Enterprise 2.x installation and supported-version guidance. The older cloud-installation page names AWS; its recipe must not be mistaken for a current version pin. A commercial server licence and per-deployment capacity planning remain required.

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

Persistent Linux or Docker application, database, search and archive storage in customer AWS infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- records-management: Commercial self-hosted email archive with retention, search and compliance-policy controls.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.mailpiler.com/piler-ee/installation/ (checked 2026-11-19). 


### Cloud deployment evidence

- Piler EE Install (aws): https://docs.mailpiler.com/piler-ee/installation/
  Persistent Linux or Docker application, database, search and archive storage in customer AWS infrastructure. Use the current Piler Enterprise 2.x installation and supported-version guidance. The older cloud-installation page names AWS; its recipe must not be mistaken for a current version pin. A commercial server licence and per-deployment capacity planning remain required.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Piler EE Install: https://docs.mailpiler.com/piler-ee/installation/

- Piler EE 2.1.0+ Docs (2026-11-02): https://docs.mailpiler.com/piler-ee-fiber/setup/

- Compliance Docs: https://docs.mailpiler.com/piler-ee-fiber/

- Piler Pricing: https://mailpiler.com/pricing/

### Licensing sources

- https://mailpiler.com/pricing/

### Infrastructure sources

- https://docs.mailpiler.com/piler-ee/installation/


### 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. Piler Enterprise 2.x documents Entra user login using an app registration, client secret, tenant and callback, returning users to the archive UI with group assignments. Configure the selected single/multi-tenant licence and identity mapping; mailbox collection credentials are distinct. Scope: Piler Enterprise 2.x archive-user Entra federation. Source: https://docs.mailpiler.com/piler-ee-fiber/azure-ad-auth/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The 2.x guide supplies a single-host Compose installation and a separate Linux installer, with licence file, persistent archive data and backup guidance. Match current packages and architecture, configure hostname/TLS/secrets and review security settings before production. Scope: Piler Enterprise 2.1+ installation paths; current package and licence selection. Source: https://docs.mailpiler.com/piler-ee-fiber/setup/ (reviewed 2026-11-21). Deployment artifact: https://docs.mailpiler.com/piler-ee-fiber/install-single-host/. Artifact reference: Current Piler Enterprise 2.x single-host guide.

- Minimum footprint / sizing: Documented. The 2.x single-host guide starts at 2 vCPU, 4 GB RAM and 200 GB disk, noting roughly 0.7 GB idle memory before ingest/search load. This is a starting point for an empty/small archive; mail volume, attachment extraction, search index, retention, replicas and backups require additional capacity. Scope: Piler Enterprise 2.x single-host starting baseline, not complete HA archive sizing. Source: https://docs.mailpiler.com/piler-ee-fiber/install-single-host/ (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Piler Enterprise; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://mailpiler.com/pricing/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Rocket Content Services - Mobius

Commercial content-services and archive platform delivered to customer AWS through a negotiated offer.

- Listing: https://launchinyourcloud.com/directory/rocket-mobius/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Licensed Mobius Kubernetes application delivered through AWS Marketplace Helm packaging.
- 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://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Procurement is by private offer rather than self-service list pricing. The vendor identifies older 12.0-12.4 releases as out of support; confirm the contracted supported version and migration path rather than treating the offer as a version guarantee.

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

Licensed Mobius Kubernetes application delivered through AWS Marketplace Helm packaging. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- legacy-system-archive-access: Commercial content-services and archive platform delivered to customer AWS through a negotiated offer.

- records-management: Commercial content-services and archive platform delivered to customer AWS through a negotiated offer.

### Deployment boundaries


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


### Cloud deployment evidence

- AWS Marketplace Helm Offer (aws): https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw
  Licensed Mobius Kubernetes application delivered through AWS Marketplace Helm packaging. Procurement is by private offer rather than self-service list pricing. The vendor identifies older 12.0-12.4 releases as out of support; confirm the contracted supported version and migration path rather than treating the offer as a version guarantee.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Marketplace Terms: https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw

- Mobius 12.6.1 Advisory: https://community.rocketsoftware.com/rocket-contentedge-114/guidance-regarding-mobius-releases-12-0-12-1-12-2-12-3-and-12-4-out-of-support-advisory-28488

### Licensing sources

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

### Infrastructure sources

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


### 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: Documented. The reviewed AWS offer delivers Helm chart from Rocket Software, Inc.. Its package version is Mobius View 12.5.2; verify the contained application and required entitlements separately. Scope: Rocket Content Services - Mobius selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw (reviewed 2026-11-19). Offer prodview-vbbdpfvvaqhqw: Rocket Software, Inc.; Helm chart; package Mobius View 12.5.2; https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Rocket documents Mobius View SAML through Apache HTTPD/mod_auth_mellon and Keycloak, plus a separate OAuth2-proxy/Entra integration. Configure the selected supported Mobius/View release, trusted proxy and identity mapping; the published examples do not certify every Marketplace chart version. Scope: Vendor Mobius View user-federation design; application/chart compatibility must be selected. Source: https://docs.rocketsoftware.com/bundle/configuring_sso_applications_for_mobius/page/mobius_12_5/hnf1736175733763.html (reviewed 2026-11-21). Supporting source: Entra/OAuth2-proxy integration — https://docs.rocketsoftware.com/bundle/configuring_sso_applications_for_mobius/page/topics/integrating_oauth2-proxy_with_microsoft_entra_id_identity_pr.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Rocket-published AWS offer delivers Mobius using a Helm chart. Obtain the selected chart/images, contract and vendor configuration instructions, and provision compatible Kubernetes/storage/database services; this delivery route does not establish a complete one-click HA environment. Scope: Vendor Marketplace Helm delivery for Rocket Mobius; exact supported configuration and licence required. Source: https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw (reviewed 2026-11-21). Deployment artifact: https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw. Artifact reference: Current vendor offer reviewed on this date.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed Marketplace and identity material do not establish a quantitative full production resource baseline. Obtain chart/node/component CPU/RAM, repository/index storage and HA requirements for a supported release; older out-of-support deployments are not a sizing reference. Scope: Rocket Mobius current production sizing remains unconfirmed. Source: https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Rocket Content Services - Mobius; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://aws.amazon.com/marketplace/pp/prodview-vbbdpfvvaqhqw (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






