Skip to main content

Deployment Overview

Smartflow deploys as an isolated, edge instance within your bank's environment. No document data leaves your infrastructure.

Deployment Model​

Smartflow supports two deployment models:

  • Azure private cloud - Deployed in the bank's Azure subscription. Best for banks with an existing Azure presence.
  • On-premise / edge - Deployed on bank-managed infrastructure. Best for banks with strict no-cloud policies.

Both models guarantee complete data isolation: each institution gets a dedicated instance with no shared infrastructure or cross-bank data commingling.

What the Bank Provides​

  • Compute - Azure subscription with resource group, or bank-managed VMs / Kubernetes for on-premise.
  • Networking - Private network path, firewall rules, and approved egress where required.
  • Storage - Bank-managed object, file, or NFS storage.
  • Identity - Azure AD, SAML, or OIDC identity provider.
  • TLS certificates - Bank-managed certificates or Azure Key Vault where applicable.

What Smartflow Provisions​

  • Application services for extraction, review, export, and monitoring workflows.
  • Loan-specific AI models deployed within the instance.
  • Configuration support for tenant setup, field mappings, and workflow rules.
  • Health monitoring without document data exposure.

Architecture Overview​

At a high level:

  1. Users access Smartflow through the approved browser and network path.
  2. The load balancer and TLS setup route traffic to Smartflow application services.
  3. Smartflow services run extraction, review, approval, export, and monitoring workflows.
  4. The data layer stores documents, extracted values, configuration, and workflow history.
  5. The identity provider handles sign-in.
  6. LoanIQ integration is enabled only when it is in deployment scope.

Network Requirements​

  • User browsers to Smartflow - HTTPS access for the application.
  • Identity provider to Smartflow - HTTPS callback path for SSO.
  • Smartflow to LoanIQ middleware - Configurable route for data export when enabled.
  • Smartflow to licensing service - HTTPS heartbeat for license validation only.
warning

No outbound connections carry document data. The only outbound traffic is licensing heartbeats and optional anonymised telemetry.

Sizing Guidelines​

info

Detailed sizing will be determined during the scoping session. The following are minimum recommendations.

  • CPU - Start with 8 vCPUs for pilot; plan 16 vCPUs for production.
  • Memory - Start with 32 GB for pilot; plan 64 GB for production.
  • Storage - Start with 500 GB SSD for pilot; plan 2 TB SSD for production.
  • GPU - Optional for pilot; recommended for higher production throughput.