Redis Cost Estimator

Enter your own rates and the shape of the deployment. Compute, egress and backup are separated, because egress is frequently the surprise.

Paste below, or drop a file anywhere on this panel

Or drop a file anywhere on this panel. Nothing is uploaded: the analysis runs in this tab.

The answer appears here

Paste on the left and press Calculate. Nothing leaves this tab.

Examples

Real input you can load into the tool above. Each one shows a different thing going wrong, because that is what the tool is for.

A six node cluster

With realistic egress, which is often a large share of the bill

nodes: 6
node-hourly: 0.25
egress-gib-month: 2000
egress-per-gib: 0.09

Compute only

The same cluster with no cross-zone traffic, for comparison

nodes: 6
node-hourly: 0.25
egress-gib-month: 0

Common mistakes

These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.

  1. Costing instances and stopping there

    Cross-zone replication, consumer egress, backups and snapshots are all billed separately and frequently exceed compute.

    Instead:Include every line. Egress in particular surprises people.

  2. Provisioning memory as though all of it is usable

    Only 60 to 70% is available for data once buffers and fork headroom are accounted for.

    Instead:Cost the usable capacity, not the provisioned figure.

  3. Committing to reserved capacity before rightsizing

    A commitment on capacity you did not need locks the waste in for a year.

    Instead:Rightsize first, then commit to what remains.