Pricing

Reserve Capacity Pricing FAQ

Below are the Frequently Asked Questions (FAQs) pertaining to Wasabi’s Reserved Capacity Storage (RCS) pricing model. Additional information on Wasabi’s pricing, billing, and payment policies may be found in this section of the Wasabi Knowledge Base.

The price associated with Wasabi’s RCS pricing model is based on the capacity and term associated with your RCS purchase. For customers using the Wasabi RCS pricing model, Wasabi service charges are based on the following criteria:

  • If you have purchased a 100 TB / 1 year term RCS package (for example), then on a monthly basis you can utilize up to 100 TB of Timed Active or Timed Deleted Storage without incurring any overage charges.

  • If in this example, the Timed Active Storage + Timed Deleted Storage exceeds 100 TB per month, then you will incur overage charges based on the pay-as-you-go price.

For customers using the Wasabi RCS pricing model, Wasabi service charges are calculated in accordance with the terms described below. For additional details and an invoice example, please refer to this knowledge base article.

  • Reserved Capacity Storage: This item is the amount of RCS storage you have purchased in TB. This storage capacity can be used for Timed Active Storage as well as Timed Deleted Storage purposes.

  • Reserved Capacity Overage Fee: This item is the amount of excess Timed Active and/or Timed Deleted Storage that is consumed above the initial or add-on RCS purchased storage capacity. This item only applies in the event you exceed the purchased storage capacity.

  • Premium Support:This item is the required Wasabi Premium Technical Support.

Wasabi has a minimum storage duration policy that means if stored objects are deleted before they have been stored with Wasabi for a certain number of days (30 days when using the Wasabi RCS pricing model), a Timed Deleted Storage charge equal to the storage charge for the remaining days will apply. This policy is comparable to the minimum storage duration policies that exist with some AWS and other hyperscaler storage services. For more details on this policy, please refer to this article.

The Wasabi Renewal Team will contact the email address listed on your account or the reseller you purchased from 120, 90, 60, and 30-days before your contract expires to discuss your renewal options. At this time, you will be able to adjust your contract to better fit your storage usage or terminate the contract. Your RCS package will automatically renew for subsequent one (1) year terms unless either party provides the other with notice of its intent not to renew at least ninety (90) days prior to the end of the then-current term. Any such renewal shall be at Wasabi’s then-current list price.

When you use more capacity in any given month that you have an active contract, Wasabi will invoice you monthly at the then list price of the product you use for any overages you may incur. For example, if you purchased a 100 TB RCS package and you use 110 TB in a given month, you will be invoiced for the additional 10 TB (plus 7% for premium support). RCS usage is calculated on the first of every month.

If you are planning to add more data to your Wasabi account over the course of the RCS term, we suggest adding a block of storage to your current Wasabi account plan. When you add a block of storage, Wasabi will make the contract end date of the new block of storage coterminous with the current storage plan. Add-on plans can be purchased in increments of 25 TBs and will receive the same RCS discounts as the current plan. Add-on plans will be prorated based on the number of months left on the current plan.

When you use less capacity in any given month than what you originally purchased, there is no rollover of that unused capacity to the next month. For example, if you purchased a 100 TB RCS package and you only use 80 TB of capacity in a given month, the remaining 20 TB does not carry over to future months.

A Wasabi RCS purchase is non-refundable and non-cancellable.

You can convert your existing pay-as-you-go Wasabi account into a Reserved Capacity Billing plan. However, it is not possible for a single Wasabi account to have both the pay-as-you-go and RCS pricing model. If you wish to have both, you would need to create separate accounts. If you are a Wasabi customer and wish to convert from the pay-as-you-go pricing model to the RCS pricing model, you can contact Wasabi make this change.

Yes, Wasabi RCS can be purchased through authorized Wasabi partners including MSPs and VARs who have signed up to sell the service. If you are already a member of the Wasabi Partner Network, you can find more detailed information by logging into the Wasabi Partner Portal. If you are not yet a partner, contact Wasabi for more info.

As the Wasabi account owner, you are free to decide how best to partition your Wasabi RCS purchase amongst your end customers.

RCS subscriptions are not associated with a particular region. You are free to choose whichever region suits your data storage needs best.

Yes. Wasabi provides a purchasing option that protects you from exceeding the capacity that you choose. If you are a control or standalone account, you will receive notifications as you approach 100% of your contracted capacity. Once at 100%, the standalone or control account, including all sub-accounts if applicable, are flagged, and can no longer upload data to Wasabi. For more information, see the knowledge base article here.

Pricing FAQs for all Wasabi Pricing Models

Below are the frequently asked questions (FAQs) associated with all Wasabi pricing models.

Wasabi’s free egress policy is designed for use cases where you store your data with Wasabi, you access this data at a reasonable rate, and your use case does not impose an unreasonable burden on our service. To better understand the definition of ‘reasonable rate’ and ‘unreasonable burden’ in this context, please consider these guidelines.

  • If your monthly egress data transfer is less than or equal to your active storage volume, then your storage use case is a good fit for Wasabi’s free egress policy

  • If your monthly egress data transfer is greater than your active storage volume, then your storage use case is not a good fit for Wasabi’s free egress policy

For example, if you store 100 TB with Wasabi and download (egress) 100 TB or less within a monthly billing cycle, then your storage use case is a good fit for our policy. If your monthly downloads exceed 100 TB, then your use case is not a good fit.

If your use case exceeds the guidelines of our free egress policy on a regular basis, we reserve the right to limit or suspend your service.

Wasabi’s free egress API request policy is designed for use cases where you store your data with Wasabi, you access this data at a reasonable rate, and your use case does not impose an unreasonable burden on our service. To better understand the definition of ‘reasonable rate’ and ‘unreasonable burden’ in this context, please consider these guidelines.

  • If you are using a commercial application that has been validated by Wasabi, then can generally expect to be in compliance with Wasabi free API request policy

  • If you are using a non-validated application that imposes an inefficient and unreasonable load on the Wasabi service, we reserve the right to limit or suspend your service

If your use case exceeds the guidelines of our free API request policy on a regular basis, we reserve the right to limit or suspend your service.

Versioning is an object storage feature that is available from Wasabi as well as AWS S3. Any time you enable versioning, you are essentially creating new versions of the objects you are storing. This will result in an increase in storage charges. Bucket logging is another object storage feature that is available from Wasabi and AWS S3. As the feature name implies, when this feature is enabled, you will be creating log files for all bucket activity. These log files are treated just like any other type of billable storage.

As a means of answering this question, let’s consider an example where on day 1, you store a file called ‘foo.pdf’. On day 2, you then overwrite foo.pdf with a new copy of foo.pdf but do not change the file name or use versioning. As part of this overwrite action, the original copy of foo.pdf will transition from active storage to deleted storage. This will result in a charge for this particular object of 1 day of active storage and 29 or 89 days of deleted storage (depending on the minimum storage retention policy applicable to your account). In addition, you will be charged for storage of the new copy of foo.pdf.

Immutability means the stored objects cannot be deleted by the user or by Wasabi until the specified retention period has expired (this is a security feature for data protection). Any storage (immutable or not) will be charged as active storage.

If you use Wasabi to store files that are less than 4 kilobytes (KB) in size, you should be aware that Wasabi’s minimum file size from a charging perspective is 4 KB. You can store files smaller than 4 KB with Wasabi but (for example), if you store a 2 KB file with Wasabi, you will be charged as if it were a 4 KB file. This policy is comparable to minimum capacity charge per object policies in use by some AWS storage classes (for example, AWS S3 IA has a minimum capacity charge of 128 KB).