On-premise deployment
On-premise deployment means running software on your own infrastructure rather than the provider's cloud. TruvaLI is deployed using this model, ensuring that customer data, including analysis and AI processes, never leaves your organization's boundaries.
Why on-premise?
Financial data is an asset for which regulators hold your institution accountable. When using a cloud-based provider, data processing responsibility is shared but compliance liability is not: during an audit, the questions are still directed to your institution.
Payment and electronic money information systems regulations in Turkey set clear expectations regarding where data is processed and who accesses it. On-premise deployment meets these expectations through architecture, not just contracts.
No cloud required for advanced analytics
A common assumption is that advanced analytics and AI capabilities can only run in the cloud. This is not the case with TruvaLI: the entire analysis layer, including open-source intelligence, case pre-analysis, and report generation, can run on your own servers, completely isolated from the internet.
Not a single byte of customer data leaves your environment.
Resource requirements and scale
A common concern with on-premise deployment is hardware cost. TruvaLI is designed to process high volumes with limited resources: transaction scoring across millions of records is completed in milliseconds using a modest server configuration.
Heavy reports run in the background without blocking user screens. Data that must be retained for legal retention periods is automatically archived to cold storage.
Deployment and implementation
Connection definitions (client and token) are established during the handoff phase.
TruvaLI can be positioned both as a pre-check before customer registration and as a final check at the time of transaction.
Before going live, your historical data is migrated: scenarios using lookback windows run with real data from day one.
You are not expected to adapt your workflow to the platform.
Continuity and security
Data is encrypted in transit and at rest. Server, network, and database metrics are monitored from a single dashboard. A disaster recovery plan aligned with recovery objectives is maintained with regular backups: periodic penetration testing and vulnerability screening are supported.
What it delivers to your organization
- Keeping data strictly within your organization's boundaries.
- Answering data residency audit questions through architecture.
- Advanced analytics without cloud dependency.
- Flexible positioning that adapts to your existing infrastructure.
Common questions
- Do AI features also run on-premise?
- Yes. The analysis layer, including case pre-analysis, open-source screening, and report generation, runs on your own servers: customer data is never sent to external services.
- Does on-premise deployment require significant hardware?
- The platform is designed to process high volumes with limited resources: scoring across millions of records is completed in milliseconds with a modest server configuration. Exact requirements are determined together based on your transaction volume.
- What happens to our historical data?
- It is migrated into the system before going live. This ensures that your scenarios using lookback windows, such as 'the last 6 months', run with your real data from day one.
- How are updates performed?
- Releases are applied to your own environment during scheduled maintenance windows. Running the deployment offline does not hinder the update process.