Elasticsearch Cost Optimization
Cut your Elasticsearch bill: reduce over-replicated indices, add ILM delete phases, fix over-sharding, right-size nodes. Savings verified on the real bill.
How does OhChimp connect to Elasticsearch?
It connects to your cluster using either your hosts list or a cloud_id, authenticated with an API key or a monitor-role user. It runs read-only calls against cluster health, index and node stats, settings, mappings, ILM policies, and snapshot repositories. It works with self-managed clusters and Elastic Cloud.
Does OhChimp need write access or see my data?
No. OhChimp uses a read-only monitor-role connection and reads metadata and statistics only: index sizes, shard counts, replica settings, node heap and CPU, ILM policies, and snapshot repositories. It never stores your documents, secrets, or workload contents.
What Elasticsearch costs can OhChimp actually reduce?
The main ones are over-replicated indices wasting storage, ILM policies with no delete phase that let data grow unbounded, over-sharded nodes burning heap, oversized nodes with idle heap and CPU, bloated read-only indices that need a force-merge, and snapshot retention running up storage and egress.
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. You are always the one who clicks.
How are Elasticsearch savings verified, and what does it cost?
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. Until then it stays flagged as not implemented. Pricing is a flat monthly fee with no cut of your savings, and paid plans carry a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in the first 12 months.