Skip to main content

What this page covers

On-Premise Deployment helps IT teams prepare Smartflow for bank-managed infrastructure when cloud deployment is not preferred.

Before you start

  • Your IT team has approved the on-premise deployment path.
  • Compute, storage, network, identity, and certificate owners are named.
  • The pilot scope and expected document volume are agreed.
  • Any outbound connectivity limits are documented.

Recommended stack planning

  • Compute - Use bank-managed virtual machines or Kubernetes infrastructure.
  • Storage - Use bank-managed file or object storage.
  • Identity - Use the bank-approved identity provider.
  • Network - Keep user access and service access inside approved routes.
  • Certificates - Use bank-managed certificates.
  • Monitoring - Confirm operational health checks without document data exposure.

Steps

  1. Confirm the on-premise environment owner.
  2. Confirm minimum compute and storage sizing.
  3. Confirm network routes and firewall rules.
  4. Confirm identity-provider integration.
  5. Confirm certificate ownership.
  6. Confirm document storage location.
  7. Install Smartflow application services with the onboarding team.
  8. Configure users, roles, workflows, and document models.
  9. Test upload, extraction, review, approval, and export.
  10. Review the test result with IT and the business owner.
  11. Start the pilot only after acceptance.

Cost factors to plan

  • Document volume - Higher volume may require more compute and storage.
  • Extraction speed - Faster turnaround may require GPU capacity.
  • Network constraints - Restricted environments may need more setup time.
  • Support model - Bank-operated environments require clear operational owners.
  • Retention policy - Longer retention increases storage planning needs.

Tips

  • Confirm outbound restrictions early.
  • Use a small but representative pilot document set.
  • Keep deployment, security, and business acceptance in one checklist.

Troubleshooting

  • Installation is blocked -> Check whether compute, storage, and certificates are ready.
  • Users cannot sign in -> Check identity-provider metadata and callback access.
  • Extraction is slower than expected -> Review sizing and GPU availability.
  • Support questions are unclear -> Confirm the named bank owner for each environment component.

Related features