LoanPro Resources and Uptime

General

Most LoanPro customers use our shared environment, which means LoanPro makes decisions on scaling the hardware and services used to make the software function. In order to scale hardware on-the-fly, LoanPro has implemented auto-scaling. Auto-scaling includes monitoring to detect the usage levels of current hardware and services, and then deploys new resources employing code to spin up and provision new hardware.

Each customer in the shared AWS environment has a database that is dedicated to their tenant, or tenants, if they have multiple LoanPro accounts. LoanPro is designed to operate optimally when a certain number of database connections, processing power, and AWS services are used per customer.

Some clients pay additional fees for dedicated hardware or a separate AWS environment.

LoanPro Uptime and Speed

In order for LoanPro to meet our stated uptime and provide the speed needed for our software to operate acceptably, customers should operate within the limits LoanPro is designed for. This means that if a client is responsible to follow LoanPro's recommendations to ensure their resources are appropriate to their usage. Excessive usage concerns include, but are not limited to:

  • API calls in both volume and frequency
  • Number of loans in their tenant (LoanPro account)
  • Database connections
  • Number of rules
  • Etc.

If client usage is high, based on their configuration, the client is responsible to authorize LoanPro's recommendatiosn for resources. Continuous usage at or near the design limits for hardware are a mitigating circumstance and LoanPro is not required to meet uptime or issue statement credits for those customers.

Security

Security is very important to LoanPro and its clients. LoanPro employs coding practices, software, and procedures to keep data within LoanPro secure. This includes measures to guard against:

  • DDOS attacks
  • Man-in-the-middle attacks
  • SQL injection
  • Unauthorized authentication
  • System intrusion
  • Etc.


How did we do?


Powered by HelpDocs (opens in a new tab)