alex@yourcyberit.com: we are not sure on the actual size yet; but things we are looking at is how to manage the cost on this.

As you can imagine we cannot simply increase the size without placing restrictions on the way this is used.

To expand on this and explain, our system first connects over our hosted data centre, once this is done the devices then try to create a direct connection (peer-2-peer) cutting our data centres out of the picture; but if a direct connection is not possible it falls back to routing all traffic via our data centre.

The issue here is we like all SaaS applications have to pay for data coming in and out of the data centre. Due to this we are looking at possibly making it so that you have a larger if not unlimited size when directly connected, but limited when using our data centre for routing.

Robin: Hi Robin, I completely understand limiting routing traffic via your data centre if a file upload/download falls back to some fluke in being unable to make a peer-2-peer connection. However, the likelihood of such a failure should be minimal, especially if you're utilizing good stun/turn/ice servers with your webrtc. Not a single connection for my clients has shown anything other than a peer-2-peer connection, which means it is cutting out the middle man at that point (your data centre) and I should then not be limited in file uploads/downloads. As a quick turnaround fix, could you not change the programmatic logic that there is no cap on connections that succeed peer-2-peer connection, and maybe put your limit then only on the connections that fail such a connection and fall back to routing traffic via your data centre?