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 cost of Wasabi’s Reserve Capacity Storage (RCS) model is determined by both the storage capacity purchased and the contract term length.
For example, a 100 TB, one-year RCS contract entitles you to utilize up to 100 TB billable storage per month without incurring additional charges. Should consumption exceed this threshold, overage fees will apply at the prevailing then-current list rate plus premium support.
Under the RCS model, charges consist of three main components:
Reserved Capacity Storage – the total purchased storage amount, which can be used for both active and deleted data.
Premium Support – a mandatory technical support subscription included with all RCS plans.
Reserved Capacity Overage Fees – applied if your billable storage exceeds the purchased capacity.
Yes. All stored objects must remain in the system for at least 30 days. Deleting data before this minimum retention period will result in the data being moved to deleted storage which makes up an accounts billable storage.
We’ll notify you several times before your term ends. If neither you nor your reseller cancels at least 30 days before the end date, your plan will automatically renew for another year at the then-current price.
You’ll be billed monthly for any excess usage at the then-current rate, plus premium support. For instance, using 110 TB in a month when you’ve reserved 100 TB means billing for 10 TB overage plus support. RCS usage is calculated on the first of each month.
You may also add capacity on to your current RCS contract (Minimum purchase of 25TB), any storage added to your RCS contract will be prorated to your contract’s current term at the same rate as your original RCS purchase.
Unused capacity does not roll over to subsequent months.
No—RCS purchases are non-refundable and non-cancellable.
No. A Wasabi account may only operate under a single pricing model at a time. To utilize both Pay-as-You-Go and RCS, separate accounts must be established. Existing Pay-as-You-Go accounts can, however, be converted to RCS by working with your Wasabi Sales Rep.
Yes. Authorized Managed Service Providers (MSPs) and Value-Added Resellers (VARs) are permitted to resell RCS. Program details are available through the Partner Portal or via direct engagement with Wasabi.
Yes. The RCS allocation is managed at the account and sub-account level, allowing providers to partition storage across multiple end customers as required.
No. Standard Reserve Capacity Storage subscriptions are not geographically restricted. Data may be stored in any Wasabi region selected by the account owner.
Yes. Standard RCS contracts are available in a capped version. Usage thresholds can be enforced at 100% of the purchased storage amount, at which point further uploads are blocked. Automated notifications are provided as utilization approaches the limit.
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).