QCR2. SaaS lending platform

Security & architecture

The platform is designed around isolation, encryption and least privilege. This is a customer-facing summary; implementation details are not published here.

Isolation is structural

Each customer environment is its own runtime with its own database, identity provider, encryption key and IAM. No shared data plane.

Encryption at rest, per customer

Customer data is encrypted under keys scoped to that customer. Controls are not shared between tenants.

Least-privilege identity

Workloads assume narrowly-scoped roles; no static keys are placed in application code.

Restricted network surface

Only the public web edge and an authenticated administrative surface are exposed. Databases and services stay private.

An explicit commercial boundary

Website visitors register interest; an authorised administrator approves any infrastructure provisioning.