
# Financial application management

Financing and leasing applications, supporting evidence and retail agreements.

Canonical page: https://launchinyourcloud.com/categories/financial-application-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.


Financing and leasing applications, supporting evidence and retail agreements.

7 listings.


## FormKiQ Financial Application Management

API-first financial application and retail agreement workflows with customer data ownership, residency controls, packaged applications, and Bedrock AI.

- Listing: https://launchinyourcloud.com/directory/formkiq-financial-application-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/financial-application-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

- financial-application-management: Financing and leasing applications, supporting evidence and retail agreements.

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

- Financial Application Management solution: https://formkiq.com/solutions/financial-application-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/financial-application-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 Financial Application Management; configured commercial AWS solution, not the public Core deployment; solution-user federation remains unconfirmed. Source: https://formkiq.com/solutions/financial-application-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. Application evidence retains document-specific permissions and history; connected credit and signing services have separate processing boundaries. This is a vendor-described configurable control, not an independent attestation or a tested implementation. Scope: FormKiQ Financial Application Management; customer-managed AWS deployment; configured commercial solution, not Core; agreed application configuration and modules. Source: https://formkiq.com/solutions/financial-application-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 Financial Application Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/financial-application-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 Financial Application Management; configured commercial AWS solution, not the public Core deployment; complete workload sizing remains unconfirmed. Source: https://formkiq.com/solutions/financial-application-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. 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 Financial Application Management; customer-managed AWS deployment; configured commercial solution, not Core. Source: https://formkiq.com/solutions/financial-application-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.







## Frappe Lending Self-Hosted

Loan application and servicing software with borrower records, supporting documents and approval workflows.

- Listing: https://launchinyourcloud.com/directory/frappe-lending/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source GPL-3.0; implementation and support separately arranged
- Licensing model: open-source
- Installation: Frappe/ERPNext installation scripts
- Architecture: Customer-operated Frappe application and database
- Operations: Customer or implementation partner operates the server, applies updates and maintains backups.
- Product website: https://frappe.io/lending
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

A loan-focused application and servicing product. Applications capture borrower documents, co-applicants and proposed collateral before loan creation. A complete retail agreement or eSignature workflow is not established by the reviewed sources.

The listed Frappe Lending application is GPLv3 in the official repository and is offered for self-hosting. Paid hosting, implementation and support do not by themselves make this an open-core application.

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

- financial-application-management: Loan-focused application and servicing comparator with borrower documents and approval workflows; a complete retail agreement or eSignature workflow is not established.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.cloudimg.co.uk/guides/frappe-lending-on-ubuntu-24-04-azure/ (checked 2026-11-12). 


### Cloud deployment evidence

- Frappe Lending v16 Azure VM deployment guide by cloudimg (azure): https://www.cloudimg.co.uk/guides/frappe-lending-on-ubuntu-24-04-azure/
  Third-party image publisher cloudimg documents a complete Frappe Lending v16.4.0/ERPNext v16 Azure VM deployment in the customer subscription, including database, workers, loan workflows, HTTPS and backups. This is a packaged distribution, not an upstream-endorsed image. Check image charges, component versions and publisher support separately from upstream GPLv3 terms; this review inspected the guide and did not deploy or audit the image.
  Source type: third-party-package; reviewed: 2026-11-12; vendor support: not-assessed. Versions: Frappe Lending 16.4.0 / ERPNext 16.


### Sources

- Self-hosting and licensing: https://frappe.io/lending/pricing

- Loan application workflow: https://docs.frappe.io/lending/loan-application

- Product scope: https://docs.frappe.io/lending/introduction

- Licensing and edition terms: https://raw.githubusercontent.com/frappe/lending/develop/license.txt

### Licensing sources

- https://raw.githubusercontent.com/frappe/lending/develop/license.txt

- https://frappe.io/lending/pricing

### Infrastructure sources

- https://frappe.io/lending/pricing


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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The shared Frappe login system accepts external OAuth/OpenID logins configured with Social Login Key, including Google and Office 365. Configure the provider and permitted users for the installed Frappe version; this is framework login, not a separate application-specific SAML implementation. Scope: Self-hosted Frappe-based application login; provider configuration and matching framework/app versions required. Source: https://docs.frappe.io/framework/user/en/guides/integration/social_login_key (reviewed 2026-11-20). Supporting source: Frappe login handlers — https://github.com/frappe/frappe/blob/develop/frappe/integrations/oauth2_logins.py. Supporting source: Application framework dependency — https://github.com/frappe/lending/blob/develop/README.md.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Frappe publishes production Compose bases and custom-app image guidance, but this pass did not establish a complete, release-matched Lending deployment artifact. Confirm the Lending image, required apps and database migration sequence. Scope: Framework deployment checked; Lending-specific production packaging unresolved. Source: https://github.com/frappe/frappe_docker (reviewed 2026-11-14). Supporting source: Frappe Lending upstream — https://github.com/frappe/lending.

- Minimum footprint / sizing: Sources checked — unresolved. The underlying Frappe Docker ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD for a small single bench. It does not size this additional application or establish its whole-stack production/HA minimum; application jobs, database, attachments and replicas still require sizing. Scope: Platform recipe only, not an application-specific Frappe HR/Lending benchmark or Frappe Cloud hosting allocation. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20). Supporting source: Application dependencies — https://github.com/frappe/lending/blob/develop/README.md.

- License pricing: Documented. The reviewed Lending source is GPLv3. The pricing page offers self-hosting separately from paid Frappe Cloud hosting and implementation. Cloud site/server prices do not establish a self-hosted software subscription or an infrastructure estimate. Scope: Frappe Lending open-source application; ERPNext/Frappe dependencies and services must be evaluated separately. Source: https://github.com/frappe/lending/blob/develop/license.txt (reviewed 2026-11-20). Supporting source: Hosting and self-hosting options — https://frappe.io/lending/pricing.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v16.8.1, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream frappe/lending release record; commercial editions and deployment packages may differ. Source: https://github.com/frappe/lending/releases/tag/v16.8.1 (reviewed 2026-11-14).







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







## Lerian Lender (BYOC)

Commercial customer-operated lending service for credit origination, contracts and servicing.

- Listing: https://launchinyourcloud.com/directory/lerian-lender/
- 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: Terraform
- Architecture: Lender application container with product-specific AWS RDS, cache, object storage and vault identity resources.
- 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://github.com/LerianStudio/lerian-terraform-foundation
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The product-specific foundation module is AWS-only in the reviewed matrix; generic Lerian BYOC provider examples do not establish other Lender deployments. The operator deploys and runs this product; infrastructure-module releases and commercial Lender application releases are separate.

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

Lender application container with product-specific AWS RDS, cache, object storage and vault identity resources. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- financial-application-management: Commercial customer-operated lending service for credit origination, contracts and servicing.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/LerianStudio/lerian-terraform-foundation/tree/main/examples/aws/products/lender (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Lender TF (aws): https://github.com/LerianStudio/lerian-terraform-foundation/tree/main/examples/aws/products/lender
  Lender application container with product-specific AWS RDS, cache, object storage and vault identity resources. The product-specific foundation module is AWS-only in the reviewed matrix; generic Lerian BYOC provider examples do not establish other Lender deployments. The operator deploys and runs this product; infrastructure-module releases and commercial Lender application releases are separate.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS Lender TF: https://github.com/LerianStudio/lerian-terraform-foundation/tree/main/examples/aws/products/lender

- BYOC Models: https://docs.lerian.studio/en/start-here/evaluate-and-deploy/deployment-models.md

- Lender Deploy: https://docs.lerian.studio/en/products/lender/configuration-and-deploy.md

- TF Foundation: https://github.com/LerianStudio/lerian-terraform-foundation

- Lerian License: https://docs.lerian.studio/en/start-here/evaluate-and-deploy/lerians-license.md

- Licensed Institutions: https://docs.lerian.studio/en/products/lender/what-is-lender.md

- Prerequisites: https://docs.lerian.studio/en/products/lender/lender-prerequisites.md

- 2026-11 Release News: https://docs.lerian.studio/en/news/2026/2026-11.md

- TF Commits: https://github.com/LerianStudio/lerian-terraform-foundation/commits/main

### Licensing sources

- https://docs.lerian.studio/en/start-here/evaluate-and-deploy/lerians-license.md

- https://docs.lerian.studio/en/products/lender/what-is-lender.md

- https://docs.lerian.studio/en/products/lender/lender-prerequisites.md

### Infrastructure sources

- https://github.com/LerianStudio/lerian-terraform-foundation/tree/main/examples/aws/products/lender


### 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: Sources checked — unresolved. The guides require a bearer-token identity provider and route authorisation through Access Manager/Caradhras, with separate machine-to-machine credentials. This confirms API/service identity, not a selected lender-operator browser SSO integration. Identify the consuming UI and end-user account/role flow before asserting application SSO. Scope: Lerian Lender BYOC API/service identity versus consuming-application user SSO. Source: https://docs.lerian.studio/en/products/lender/configuration-and-deploy.md (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 reviewed source supplies deployment configuration for Lender application container with product-specific AWS RDS, cache, object storage and vault identity resources. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: Lerian Lender (BYOC) deployment example; review the full linked installation instructions. Source: https://github.com/LerianStudio/lerian-terraform-foundation/tree/main/examples/aws/products/lender (reviewed 2026-11-19). Deployment artifact: https://github.com/LerianStudio/lerian-terraform-foundation/tree/main/examples/aws/products/lender. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The prerequisites identify PostgreSQL, Valkey, Midaz, Redpanda, identity/licensing services and migration requirements, but do not publish quantitative whole-deployment CPU/RAM/storage sizing. Define origination/posting rates, tenant count, retention, event volume and HA before costing the platform. Scope: Lerian Lender BYOC complete production footprint remains unconfirmed. Source: https://docs.lerian.studio/en/products/lender/lender-prerequisites.md (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Lerian Lender (BYOC); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.lerian.studio/en/start-here/evaluate-and-deploy/lerians-license.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle FLEXCUBE Universal Banking

Commercial universal-banking software with retail/corporate lending and customer OCI deployment architecture.

- Listing: https://launchinyourcloud.com/directory/oracle-flexcube/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- 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: Licensed FLEXCUBE application, database and networking tiers in customer OCI.
- 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.oracle.com/en/solutions/flexcube-oci/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The architecture covers the customer's deployed banking system, not a hosted banking subscription. Match application, database, Java/runtime and third-party licensing and validate the bank-specific production design.

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

Licensed FLEXCUBE application, database and networking tiers in customer OCI. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- financial-application-management: Commercial universal-banking software with retail/corporate lending and customer OCI deployment architecture.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/flexcube-oci/ (checked 2026-11-19). 


### Cloud deployment evidence

- OCI Reference Architecture (oci): https://docs.oracle.com/en/solutions/flexcube-oci/
  Licensed FLEXCUBE application, database and networking tiers in customer OCI. The architecture covers the customer's deployed banking system, not a hosted banking subscription. Match application, database, Java/runtime and third-party licensing and validate the bank-specific production design.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI Reference Architecture: https://docs.oracle.com/en/solutions/flexcube-oci/

- Oracle Software Contracts: https://www.oracle.com/contracts/software/

- OMA A-Z: https://www.oracle.com/contracts/a-z/oma/

- FLEXCUBE Docs: https://docs.oracle.com/en/industries/financial-services/flexcube/index.html

### Licensing sources

- https://www.oracle.com/contracts/software/

- https://www.oracle.com/contracts/a-z/oma/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/flexcube-oci/


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 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 vendor FLEXCUBE UBS 14.7.2 security guide explicitly supports SAML SSO and distinguishes it from LDAP/MSAD password authentication. Select a currently supported compatible release, IdP and installation properties; OCI administrator login and every bundled banking component are separate identity surfaces. Scope: Versioned FLEXCUBE UBS 14.7.2 documented SAML capability; current deployment compatibility required. Source: https://docs.oracle.com/cd/F87755_01/PDF/Installation/Environment%20Setup/Security_Guide.pdf (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. The OCI guide provides a FLEXCUBE reference infrastructure architecture and recommendations, but does not establish the complete entitled application installer or a release-matched turnkey deployment artifact. Obtain the vendor package and supported WebLogic/database/application installation procedure. Scope: FLEXCUBE application delivery artifact remains unconfirmed; OCI architecture is separate. Source: https://docs.oracle.com/en/solutions/flexcube-oci/ (reviewed 2026-11-21).

- Minimum footprint / sizing: Documented. The OCI reference architecture names VM.Standard2.2 as a starting minimum shape and at least 256 GB ASM storage for its described database, with separate redundant application/database tiers. It uses older Oracle Linux 7.7-era assumptions. Revalidate current OS/shapes, licences, banking workload and HA sizing rather than treating it as a current universal minimum. Scope: Historical vendor FLEXCUBE OCI architecture sizing reference; current workload/releases require validation. Source: https://docs.oracle.com/en/solutions/flexcube-oci/ (reviewed 2026-11-21).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## PaygOps Community Edition

Open-source PAYGO loan, asset-finance, customer and payment operations platform.

- Listing: https://launchinyourcloud.com/directory/paygops/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec.
- 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.paygops.com/community-edition
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- financial-application-management: Open-source PAYGO loan, asset-finance, customer and payment operations platform.

- erp-crm: Open-source PAYGO loan, asset-finance, customer and payment operations platform.

### Deployment boundaries


- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml (checked 2026-11-19). 


### Cloud deployment evidence

- DigitalOcean App Spec (digitalocean): https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml
  PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The institutional source identifies actual use, public governance or a named community-support program. The linked application source separately establishes installation and licensing.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://www.paygops.com/post/masunga-releases-paygops-community-edition-as-open-source-with-support-from-global-energy-alliance

- Upstream project: https://github.com/MasungaTech/PaygOps-Community

### Sources

- DigitalOcean App Spec: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml

- Deploy README: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/README.md

- AGPL-3.0: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md

- Commits: https://github.com/MasungaTech/PaygOps-Community/commits/main

### Licensing sources

- https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md

### Infrastructure sources

- https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 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: Sources checked — unresolved. The Community documentation describes application authentication and API tokens, but does not establish an external SAML/OIDC identity-provider login path for customer-hosted Community users. Token-based API access alone is not enterprise user SSO. Scope: PaygOps Community user sign-in; commercial or hosted product capabilities are not transferred. Source: https://github.com/MasungaTech/PaygOps-Community/blob/main/README.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 reviewed source supplies deployment configuration for PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: PaygOps Community Edition deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The DigitalOcean template allocates two 1-vCPU/2-GB web instances, two API instances of the same size, two 1-vCPU/2-GB workers, and 1-vCPU/1-GB OpenPAYGO and Redis instances. Its three PostgreSQL entries are marked production:false. This is a documented recipe, not an HA or production minimum. Scope: Reviewed Community App Platform template; database capacity, persistent storage and production hardening remain separate. Source: https://github.com/MasungaTech/PaygOps-Community/blob/main/.do/deploy.template.yaml (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: PaygOps Community Edition; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






