Cost Optimization

How to architect an efficient application that minimizes costs

Cost Levers

  1. Storage - Charged at $10 per terabyte per month, or $.01 per gigabyte. Storage is calculated in “terabyte months,” which is a prorated calculation of how much storage is used throughout the month, broken down by hour. Storing one terabyte for 30 days, two terabytes of data for 15 days, or three terabytes for 10 days, would each be the equivalent of one terabyte month.

  2. Bandwidth - Charged at $45 per terabyte, or $.045 per gigabyte, of bandwidth consumed. Users are not charged for upload bandwidth, so uploading files to the network doesn’t incur any cost. Download bandwidth measures the transfer of data from a Storage Node Operator (or Host) to an Uplink.

  3. Per Object Fee - Charged at $0.0000022 per file stored. This charge ensures that users are incentivized to store data that is larger that is optimized for storage on the network. Decentralized cloud storage is best suited to the storage of large static objects.

Avoiding Double Bandwidth Fee

When running a gateway in a cloud environment a double bandwidth fee will be incurred (as data goes from Tardigrade to Legacy Cloud to User). If you are planning on integrating the gateway into your use case, it is best to host in a self-owned environment (on premise, or at edge).

Note That:

Our default configuration is an expansion factor of 275%, meaning that for every TB that’s uploaded to the network, we store 2.75 TB. Users are not charged for the expansion factor when storing data they are only charged for the actual size of the file and nominal overhead related to encrypting it.

When an object is downloaded, the download process includes requests for more than the minimum number of storage nodes required. While only 29 pieces out of 80 are required, in order to avoid potential long-tail performance lag from a single storage node, an Uplink will try to retrieve an object from 39 storage nodes. The Uplink will terminate all incomplete downloads in process once 29 pieces are downloaded and the object can be re-encoded.

This function of the network ensures a balance of performance and cost optimization, but does include some additional egress bandwidth overhead. For every downloaded object, this can include up to an additional 10% of bandwidth.