Plan your cluster.

Get radically simple storage.

This calculator is designed as a self-service tool to match your storage and performance requirements to the most cost efficient EC2 instance based on your application needs.
WekaIO’s storage services can share the same EC2 instances as your applications (termed Shared) or you can deploy on dedicated servers (termed Dedicated).
If you have any questions or need further assistance feel free to contact us directly.

What’s your level of expertise?

I am a Standard user

Heck I'm an Expert user

Start with

Your requirements


This section lets you specify the capacity requirements for your applications.

Capacity: This field specifies the total file system usable capacity which is shared by all instances. You can specify the capacity in Terabytes or Gigabytes.

Tiering: Your AWS cluster can be based on SSD exclusively, or you can store files on a combination of local SSDs and S3 buckets. All files on SSD and S3 are available to the applications.
Data is tiered to the S3 bucket based on a tiering policy.
All recently written and accessed files will reside on SSDs.
The calculator will provide the cost of a fully populated S3 tier, however costs will depend on actual usage over time.

SSD Capacity: For tiered clusters, you can specify what percentage of the total capacity you would like to keep on local SSDs. The physical capacity will be calculated for you based on the percentage you specified.


Total capacity
SSD only

Deployment Model

This section specifies the resources required for Weka's cluster and your applications.

Shared vs. dedicated this control whether Weka processes are running on the same instances as your applications (hyper converged mode), or whether dedicated instances are used for Weka.

CPU cores required: This field specifies how many compute cores you require to run your applications, when running on shared instances to Weka and to the applications.

Expert - SSDs reserved for user applications: WekaIO requires a minimum of one SSD per instance and by default, all local SSDs are used by the WekaIO file system. If you would like to reserve some SSDs per instance for your applications, you can specify it here. This feature will limit your instance types to those that support sufficient SSDs for both the application and WekaIO.

Deployment Model

(to WekaIO)
(with WekaIO)


This section is optional and lets you specify your application performance requirements. Performance can be specified in either IOPS (I/O operations per seconds) or bandwidth (GBytes per second).

R/W: Specify the percentage of IO operations that are read operations vs. the total number of operations.

IOPS: Specify the number of IO operations in 1000s per second required for the whole cluster. This option will be hidden if bandwidth performance is chosen.

Bandwidth: Specify the Gigabytes/second required for the whole cluster. This option will be hidden if IOPS performance is chosen.

Expert - Low latency: Check this box if you would like the cluster to maintain a consistent low latency (latency target is specified to the right of the checkbox). A low latency target is valid only for IOPS performance and will change depending on the number of availability zone configurations.

Expert - Bursty vs. Sustained this controls whether the performance requirements above are defining a burst, or whether the cluster is required to sustained them for a long period of hours or more. This is controlled by AWS network rate limiting.



Region: You can specify the region to run the cluster, different regions have different Amazon instance and S3 pricing.

Expert - Multi-AZ mode: Weka can be deployed within a single AZ or a multi AZ setting. Multi AZ clusters are resilient to a single AZ failure, but have higher latency and are more costly due to a less efficient protection scheme and charges due to cross-AZ traffic

AZ config

View all

Your instance options