CTA background image

Learning Pool Fair Usage Policy


To make Learning Pool software as customizable as possible, we have given you access to many of the underlying functions that power it. Giving you access to these underlying functions allows you to build powerful integrations and add-ons using the full capabilities of Learning Pool platforms. Unfortunately, this also allows for these underlying products to be misused or abused.

This policy exists to ensure that Learning Pool platforms and our customers are protected from misuse and abuse. Our goal with this policy is not to restrict you from building your learning delivery on top of Learning Pool’s software or put you in a position where you have to worry about additional fees. Learning Pool software is designed and packaged in such a way that the vast majority of our customers, big or small, will not run into the edge cases described in this policy.

A very small number of customers use an excessive amount of resources at peak times, to the extent that it can impair the service of others. The Learning Pool fair usage policy is designed so that we are able to provide the most effective service to all our customers.

The fair usage policy will identify the very small number of very heavy-use customers. We will communicate with these customers to try and establish what is driving their specific high usage and how individual usage patterns and habits can be modified to the benefit of all. In extreme cases, Learning Pool may be required to apply management techniques to reduce the impact the heavy use customers have of the service delivery of others.


Customers shall ensure that any applications that access Learning Pool’s services do not place unreasonable burden on, or intentionally overuse said service, and that such use shall comply with any fair usage limits outlined in this policy.

The use or launch of any automated system that accesses the Stream Suite services in a manner that sends more request messages to said service in a given period of time than exceeds our policy in the same period, is prohibited.

Storage space

Within the Learning Pool SaaS environment you can store documents, website resources, data and transactions in the database. To ensure that there is enough storage space for everyone, the amount of data you can store per user is limited. The amount of storage depends on your contract and agreed number of users. All users can have sufficient disk space if the SaaS solutions are used normally. The actual size of the data storage can be found by contacting our service desk. More storage space can be freed up by deleting data yourself or by asking Learning Pool to do this for you. If your organisation structurally stores more data than is reasonable and normal, Learning Pool will contact you to discuss the situation. It is possible to expand the storage.

The maximum amount of data you can store per organisation is limited as follows:

Storage Type Limit
Relational database 20GB
Mongo DB 25GB – 10 million statements
File Storage 150GB
Individual max upload size 1GB


Network traffic and bandwidth

To avoid a negative effect of excessive network traffic, Learning Pool checks the traffic. We compare your usage with the average usage of all SaaS customers with the same contract. With normal use, you don’t have to worry about the network bandwidth which is available. If you cause a situation that could lead to a decline in service, we will contact you to discuss the situation.

Limiting data traffic

Under normal circumstances, there is no excessive use of data traffic. However, individual users can use larger amounts of data traffic than the average of comparable users. They can cause a lot of network overload and nuisance for other customers.

We reserve the right to monitor the amount of data traffic and to filter excesses. If the amount of data traffic deviates too much from the average, we will contact you and see how we can normalise the usage. If you do not normalise your consumption as a result of this contact, we can block (temporarily) the data traffic or charge extra costs.

The below table sets out the maximum amount of data traffic per organisation for our SaaS applications:

Application Requests

Service Reporting period Limit (LXP) Limit (LMS)
Outbound load balancer bandwidth Quarterly 450GB

300 concurrent connections


400 Concurrent connections

Yearly 1.8TB 3.7TB
Inbound API requests (not generated by the frontend application) Daily average 200,000

(300 per minute at peak)


(150 per minute at peak)


The below table sets out the maximum amount of CDN traffic per organisation:


Service Reporting period Limit
Outbound CDN bandwidth Quarterly 4TB
Yearly 12TB


Computing power

To prevent a negative effect of excessive use of computing power, Learning Pool keeps an eye on server usage. Usage is compared with the average usage of all users with the same contract. With normal use, you do not have to worry about the servers available to you. The cause of increased usage is usually the normal growth of users and customers. This is one reason to scale up computing power. Learning Pool can intervene in case of excessive use. We will discuss this with you in advance.

The below table sets out the maximum amount of computing resource per organisation:


Service Limit (per service, other than Stream Data Cloud ) Limit (Stream Data Cloud)
AWS Load Balancer 1 (shared) 1
AWS EC2 instances (vCPUs average per month) 4 8
AWS RDS/Aurora (vCPUs average per month) 2 N/A


Fair Use Policy in urgent and extreme cases

In an urgent or extreme case, for example if the system is attacked (DDoS denial of service attack) the service may be stopped or your access may be temporarily blocked. Another reason for this could be if your system has been compromised. For example, a hacker or a potential security hole has been found. In urgent situations, we immediately shut down the system and contact you afterwards to discuss possible solutions.


Last updated 14 September 2022