Estimate the Real Cost of Running MongoDB on KubErnEtEs

See how much you can save while gaining control, flexibility, and transparency by comparing public DBaaS costs to running cloud-native MongoDB from Percona on your own infrastructure.

Where are you running MongoDB?

Your MongoDB estate

Atlas instance sizeReplica sets

Each replica set is 3 nodes (primary + 2 secondaries). Add a row per instance size in your estate.

Percona Expert Support

Estimated Savings vs MongoDB Atlas

-

lower cost

-

MongoDB Atlas 100%

Percona self-managed -

Talk to us about self-managed MongoDB →

How this works. Savings are the modelled difference between MongoDB Atlas and the same estate self-managed with Percona Server for MongoDB, whether on your own cloud VMs or on Kubernetes with the Percona Operator for MongoDB (infrastructure, plus optional Percona support). Every replica set is 3 nodes; storage and backup follow each tier’s disk (storage per node, backup per replica set). Percona support is priced once on the total vCPUs across your whole estate, so it amortises as the estate grows.

i

*Any calculation, figures or pricing are estimates only, based on the data input and certain assumptions. These estimates are intended for informational purposes only and should not be relied upon in any manner - any actual savings will vary and are not guaranteed.

i

Estimates compare infrastructure (and optional Percona support) only; not a quote. Excludes data-transfer, operational labour, and commitment discounts. Actual results vary by region and workload.

i

Calculated in your browser. MongoDB is a trademark of MongoDB, Inc.

Resources