Cassandra Cost Optimization
OhChimp probes Cassandra for over-replicated keyspaces, oversized partitions, and MV overhead. You press apply, savings verified on your real bill.
How does OhChimp find Cassandra cost savings the node bill can't show?
OhChimp connects a read-only user and runs probe queries against Cassandra's system catalog and size estimates. That lets it see over-replicated keyspaces, oversized partitions, tombstone and GC pressure, mismatched compaction strategies, materialized view overhead, and blocking read repair, which are sources of waste a cloud billing dashboard never exposes.
Does OhChimp need write access or see my data?
No. OhChimp uses a read-only user and reads schema metadata and size estimates through probe queries against system_schema and system tables. It never stores your application rows, secrets, or workload contents.
What Cassandra costs does it actually reduce?
Storage and node footprint, mostly. It targets replication factors above 3 that multiply storage, partitions over 100MB and STCS-on-read-heavy tables that drive compaction and GC load, tombstone-prone tables, materialized views that double writes, and BLOCKING read repair that adds cross-node I/O.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and OhChimp applies the matching code and infrastructure changes together.
How are Cassandra savings verified, and what does it cost?
Savings are checked against your real bill. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10%, and 3 consecutive positive checks, and stays flagged not implemented until then. Pricing is a flat monthly fee with no cut of your savings, backed by a year-one ROI guarantee that refunds your subscription if it doesn't pay for itself in the first 12 months.