What this page covers
Deployment Prerequisites lists what your institution and Smartflow need to prepare before a deployment starts.
Before you start
- Your deployment model is selected.
- Your IT owner is named.
- Your security review path is known.
- Your pilot or rollout scope is agreed.
What your institution provides
- Compute - Approved cloud subscription or bank-managed virtual machines / Kubernetes.
- Networking - Private access path, firewall rules, and approved egress where required.
- Storage - Bank-managed object, file, or equivalent storage.
- Identity - Approved identity provider.
- Certificates - Bank-managed certificates.
What Smartflow provides
- Application services for user access, workflow, extraction, review, and export.
- AI models for loan-specific extraction inside the approved environment.
- Configuration support for field mappings, workflow rules, and tenant setup.
- Health checks for deployment monitoring without document data exposure.
Minimum sizing guide
- CPU - Start with 8 vCPUs for pilot; plan 16 vCPUs or more for production.
- Memory - Start with 32 GB for pilot; plan 64 GB or more for production.
- Storage - Start with 500 GB SSD for pilot; plan 2 TB SSD or more for production.
- GPU - Optional for pilot; recommended for higher throughput.
Network checklist
- Confirm user access over HTTPS.
- Confirm identity-provider callback routing.
- Confirm approved outbound licensing heartbeat.
- Confirm integration routing only for systems in scope.
- Confirm firewall and certificate owners.
Tips
- Assign one IT owner and one business owner before kickoff.
- Confirm storage retention expectations before uploading pilot documents.
- Keep a written list of systems that are in scope and out of scope.
Troubleshooting
- Deployment cannot start -> Check whether compute, storage, network, and identity owners are assigned.
- SSO setup is blocked -> Confirm protocol and identity-provider metadata with IT.
- Export is blocked -> Confirm downstream system access and approval status.