Cloudnado is a secure, high performance object storage built to store and retrieve any amount of data from anywhere on the Internet. It is highly scalable and highly available at very low costs. The total volume of data you can store is unlimited; however, individual objects have a maximum size of 5 TiB for Multipart uploads, and 5 GiB for single part uploads. For objects larger than 100 MiB, users should use the Multipart Upload capability.
You can sign up for a no-committment, no credit card required, free trial with this link. Free trial accounts have 5 GiB of free storage for 30 days. Once the trial period is over, you can add your credit card to qualify for our free tier, where you can receive 5 GiB of free storage for up to 1 year.
After signing up, please refer to our documentations to begin using Cloudnado.
Cool-ST offers a general purpose storage for any cool or cold data. Cool-ST is designed for high availability and high durability. It stores objects redundantly across multiple zones that are separated by at least 100 miles. As a result, Cool-ST is geo-redundant, and any two availability zone can be impacted, and data in Cool-ST will still be safe and available.
Cool-OZ offers a low cost alternative for those that do not need the data resilience model of Cool-ST. In Cool-OZ, objects are stored redundantly, but only within an availability zone. If that availability zone becomes impacted, the data in Cool-OZ may be impacted as well. As a result, it is recommended to store objects in Cool-OZ that can be recreatable, such as secondary storage or backup data.
Cool-MC is a managed multicloud service offered by Cloudnado. When data is uploaded to Cool-MC, Cloudnado divides the data in shards, and manages the distribution of shards to various cloud providers in order to optimize on performance, durability, and cost. The cloud providers chosen in Cool-MC are a combination of trusted cloud vendors, and a whitelist of vendors that Cloudnado have vetted through an application process.
Cool-MC provides a simplified inteface to multi-cloud storage, as Cloudnado fully manages the multi-cloud infrastructure. Additionally, Cool-MC has vendor-redundancy, which means that you do not have to rely on any single cloud vendor in Cool-MC. For example, if in 10 years one of the major storage vendor (or even Cloudnado) ceases to exist, data will still be in tact and retrievable.
Another benefit of Cool-MC is the increased level of redundancy, as data is stored geo-redundantly across multiple available zones. If 4 availability zones are impacted, data in Cool-MC is still safe and available.
With Cloudnado, you pay only for what you use. There is no minimum fee. The standard way to enter payment information is to access your account's billing page and enter your credit card. However, if you wish to use a different method of payment, please contact the support email listed in your account dashboard.
The price for each usage is described in the product feature comparison chart. Taxes are not included in the chart.
Free trial accounts offer a way for users to try Cloudnado Cool-ST without any commitment. No credit card is required to create a free trial account. They have full account functionality for 30 days; however, they have a maximum storage limitation of 5 GiB, and an egress and retrieval limitation of 5 GiB.
For those that wish to extend the 5 GiB free period to 1 year, users can upgrade their free trial into a base account with free tier.
The free tier provides non-trial accounts with the ability to try Cloudnado services free of charge for a limited time. Free tier is only offered for eligible products, and lasts for 1 year from account creation. To find out which products are eligible, please refer to the product feature comparison chart. The billing works as follows:
Each month, if the total storage amount across all eligible products is 5 GiB or less, then the storage costs for those products are waived for that month.
Each month, if the total egress amount across all eligible products is 5 GiB or less, then the egress costs for those products are waived for that month.
Each month, if the total retrieval amount across all eligible products (that has retrieval costs) is 5 GiB or less, then the retrieval costs for those products are waived for that month.
Products are otherwise charged at their normal rates.
The volume of storage that we bill you for each month is based on the average amount of storage you used throughout the month. We measure this by calculating the total TimeStorage-ByteHours, which are totaled up at the end of the month, then converted to TimedStorage-GigabyteMonth, to generate your monthly charges.
For example, if you storage 1 GiB (1,073,741,824 bytes) for the first 15 days in January, and 0 bytes of storage for the rest of the month, you will have a total of 1 GiB x 15 days = 1,073,741,824 bytes x 360 hours = 386,547,056,640 TimedStorage-ByteHours = 0.48387096774 TimedStorage-GigabyteMonth. Multiply the TimedStorage-GigabyteMonth by the storage price of the product you are using, and the result will be your storage cost for that product.
For our products with minimum object size, your storage usage will be calculated as normal, except that if an object falls below the minimum object size, we bill you as if the object's size is equal to the minimum object size. Minimum object size is applied to products where there is large overhead in storing your objects, and is designed to protect Cloudnado from operating at a loss.
For our products with minimum object duration, your storage usage will be calculated as normal, except that if an object is deleted earlier than the minimum object duration, we bill you as if the object's duration is equal to the minimum object duration. Note that if an object is instead modified, and there is no versioning involved for the bucket, then the old version of the object will be implicitly deleted in order for the new object to take its place. The old version will still be subject to the minimum object duration requirement. Minimum object duration is applied to products where there is large overhead in storing your objects, and is designed to protect Cloudnado from operating at a loss.
The volume of egress that we bill you for each month is based on the total number of bytes that is transferred out of Cloudnado servers. Transferring bytes between Cloudnado servers incurs no egress costs.
For products that have retrieval costs, the volume of retrieval that we bill you for each month is based on the total number of bytes that is read by the Cloudnado servers holding the data. Note that unlike egress, retrieval volume will still be counted even if the data transfer is between Cloudnado servers.
Cloudnado is secure by default. All objects and buckets are private by default upon creation, and only the resource own has full control of the permissions. Cloudnado supports user authentication to control access to data with policies such as Access Control List (ACL) and Bucket Policies, which allows the resource owner to selectively grant permissions to users and groups of users.
All communication requires SSL endpoints via HTTPS and are therefore encrypted. If you need extra security, you can specify the Server-Side Encrpytion (SSE) option to encrypt data stored at rest. You can configure your buckets to automatically encrypt objects before storing them if the incoming storage requests do not have any encryption information. Additionally, you can encrypt your data client-side with your own encryption libraries before storing it in Cloudnado.
Cloudnado accounts have the ability to create subaccounts, and manage the access of these subaccounts. Organizations with multiple employees only need a single Cloudnado account, and can issue a subaccount for each employee. The permission management of accounts and subaccounts is done through two mechanisms: Access Control Lists (ACLs) and Bucket Policies. ACLs allow the resource owner to grant specific permissions (e.g. READ, WRITE, FULL_CONTROL) to specific users for an individual object or bucket. Bucket Policies allows the resource owner to specify rules on a bucket which apply broadly across all requests to that bucket, such as making all objects readable to a specific user by default.
Because Cloudnado has an S3-compliant interface, Cloudnado follows Amazon S3's Server-Side Encryption options. As a result, Cloudnado offers SSE-S3 and SSE-C as server-side encryption options. Additionally, users can encrypt their data client-side with their own encryption library before sending the data to Cloudnado. All of these options allow you to store sensitive data encrypted at rest in Cloudnado.
SSE-S3 provides an integrated solution where Cloudnado handles the key management, key protection, and encryption process using multiple layers of security. You should chood SSE-S3 if you prefer to have Cloudnado manage your keys and encryption process.
SSE-C allows you to provde your own encrpytion keys, and have Cloudnado use the provided keys to encrypt and decrypt your data server-side. With SSE-C, you don't need to implement or use an encryption library to perform the encryption and decryption, but you do need to manage your own keys that you send to Cloudnado. Use SSE-C if you want to maintain your own encryption keys, but don't want to implement a client-side encryption library.
Using a client-side encryption library to encrypt your data before sending to Cloudnado would allow you to retain control of your encryption keys, the encryption algorithm, as well as exeuction of the encryption and decryption itself. Some customers prefer the full end-to-end control of the encryption and decryption of objects. Use client-side encryption if you want to maintain full control of your encryption process, are able to implement such a process with an encryption library, and need to have your objects encrypted before they are sent to Cloudnado for storage.
Cloudnado Cool-ST is designed to provide 99.99999999999999% (16 9's) durability of objects over a given year. This durability level corresponds to an average annual expected loss of 0.00000000000001% of objects. For example, if you store 100,000,000,000 objects with Cloudnado Cool-ST, you can on average expect to incur a loss of a single object once every 100,000 years. In addition, Cool-ST is designed to sustain data in the event of two entire availability zone loss, as well as in the event of geographical catastrophes because Cool-ST is geo-redundant.
Likewise, Cloudnado Cool-OZ and Cool-MC is designed to provide 99.999999999% (11 9's) duraiblity of objects over a given year. Cool-OZ cannot sustain data over a single availability zone loss, nor is it geo-redundant. Cool-MC can sustain data in the event of four entire availability zone loss, and is geo-redundant. Additionally, it is vendor redundant, and does not rely on any single cloud vendor (including Cloudnado) in order to continue operating.
As with any environment, the best practice is to have a backup and to put in place safeguards against malicious or accidental deletion. For Cloudnado, the best practice includes secure access permissions, geo-redundancy, versioning, and regularly tested backups.
Cloudnado stores your objects redundantly across multiple devices in a highly secure availability zone. The objects are routinely checked for data integrity and can be repaired from data corruption. In additional, for Cool-ST and Cool-MC, Cloudnado redundantly stores your objects across multiple availability zones as well, and the availability zones are separated by at least 100 miles. As a result, two availability zone can be impacted, and data within Cool-ST will be safe. Likewise, four availability zones can be impacted, and data within Cool-MC will still be safe.
Cloudnado uses a combination of Content-MD5 checksums and cyclic redudancy checks (CRCs) to detect data corruption. Cloudnado performs these checksums on data at rest and repairs any corruption using redundant data. In addition, we caluclate checksums on all network traffic to detect corruption of data packets when storing or retrieving data.