Cubbit Next Generation Cloud

<!--HTML-->In the last year Cubbit has delivered many Cubbit cells in Italy. A cubbit cell is a very simple device that provides encrypted block storage service. These cubbit cells connect to each other from different datacenters of different Italian companies. Each cell relies on a different data link and is powered by a different power line. Even cubbit cells hosted in a specific company do not contain data blocks of that company but mainly data blocks of others and vice versa, data blocks of a specific company are mostly stored in cubbit cells hosted elsewhere. This design combines hardware redundancy and hyper-distribution of risk and thus ensures that data stored in a Cubbit swarm (i.e. the p2p network made up of all Cubbit cells) is strongly defended against accidental and catastrophic loss, at a fraction of the cost that companies typically spend for that level of service. But this, good as it is, is just the basic idea of ​​Cubbit. To convince a BTB customer to join the Cubbit swarm, Cubbit had to change some of the basic assumptions that made up its initial proposal to the customer: today Cubbit is no longer a Sync and Share solution, but an S3 compatible Object Storage service. This means that the Customer can continue to store data via the Cubbit web interface and can continue to share it with other Cubbit users, but can also activate the versioning service on the files or prevent them from being modified for a certain period of time. And it can do much more: it can connect Cubbit to a third-party solution designed for the S3 protocol. Data uploaded from widely used clients (Cyberduck, Nextcloud, CloudBerry, Veeam…) are visible to each other and also from the Cubbit web interface, giving the client complete control over the data flow and a variety of data cases . use, which was previously not possible. By adopting a de facto industry standard such as the AWS S3 protocol, Cubbit can synchronize its cloud object storage with third-party cloud object storage and allows the customer, for example, to synchronize data from Azure to Cubbit with minimal effort . Adding more protocols (as we did with S3) will multiply the use cases, but a key step in the integration will be making the Cubbit cell available in the form of a virtual machine or container, allowing the customer to implement their own portion of a cubbit swarm in a virtualized data center or even create a private cubbit swarm from scratch, and deploy it in a private wide area network.