The Tardigrade Platform provides secure, private and reliable cloud object storage at a much lower cost than the cost of the big cloud providers. Billing is simple. We charge for three things, each of which we will call a “metered service type.” They are: static object storage, download bandwidth, and an object fee.
Static object storage is charged at $10 per terabyte per month, or $0.01 per gigabyte. Static object 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 of data for 30 days, two terabytes of data for 15 days, or three terabytes of data for 10 days, would each be the equivalent of one terabyte month.
Download bandwidth is charged at $45 per terabyte, or $0.045 per gigabyte of bandwidth consumed. There is no charge for ingress bandwidth, so uploading files to the network doesn’t incur any cost.
Each object stored on the network incurs a nominal object fee. The object fee is $0.0000022 Per Object Per Month. Distributed object storage is optimized for large files (several MB or larger in size - the larger the better). Very small objects generate more overhead due to storage of the metadata for the file. This matters more than the actual size of the object stored when it comes to overhead. Consequently, we charge a nominal object fee to account for that overhead. If a user is storing even large numbers of big files, the per object fee will be inconsequential. If a user streams millions of small files, the per object fee will offset the cost associated with the greater metadata overhead and may significantly increase the overall fees charged.
Project limits allow us to set boundaries on the amount of data users can upload to the Storj network and the amount of download bandwidth available to users. We have separate limits for storage and egress bandwidth per project on all Tardigrade Satellites. All limits are set to zero until a method of payment is added. Once a method of payment is added, the usage and egress limits will default to 50 GB. If you would like to increase your limits to higher values, you can always contact our support team through the Tardigrade support portal.
Storage and bandwidth limits are imposed by most cloud infrastructure providers as a normal part of capacity planning and to ensure achievement of SLAs. In distributed and decentralized storage systems they are equally important, if not more so. Just like any provider, the aggregate amount of available storage and bandwidth must be shared across all users. With a distributed and decentralized storage system like Storj, the storage and bandwidth are provided by a network of third parties running storage node software. One of the key drivers of the success of the Tardigrade service is the balance of supply and demand. If there are too many users overutilizing available resources, the user experience will be poor.
Similarly, if there are too many storage nodes, there won’t be enough use to provide a meaningful ROI for Storage Node Operators. This can lead to storage node churn, increasing load on the network, and potentially impacting durability. Usage limits are one part of the toolkit that allows us to maintain the balance.
We introduced rate limits between the uplink and the satellite to ensure a good quality of service for all uplink users. Without the rate limit it would be possible for users to inadvertently consume most of the database resources available on the satellite and cause issues for other users. The intention was to pick a default limit that would remain mostly unnoticed by end users (as the typical use case shouldn’t hit the limit). The current default limit is 100 requests per second for all meta info calls: list, get, delete, put. Customers can request a rate limit increase when needed by filling out the limit increase request form on our Tardigrade support portal. Please only make such requests if your use case really requires more than the current default limits. Requests will be evaluated taking into account the intended use case and availability on the network.