Neo4j Cost Optimization
OhChimp connects a read-only user to find Neo4j waste: oversized stores, indexes off ONLINE, a thin page cache, leaking transactions, verified on bill.
How does OhChimp connect to Neo4j?
OhChimp connects over the Bolt protocol with a read-only user, using the uri, username, and password you provide. It runs probe queries against catalog and statistics views (SHOW INDEXES, SHOW CONSTRAINTS, SHOW TRANSACTIONS, JMX store-size and page-cache metrics, and dbms.listQueries) and reads only metadata and runtime stats.
Does OhChimp need write access or see my data?
No. OhChimp uses a read-only user and reads index, constraint, store-size, and transaction metadata through probe queries. It never stores your nodes, relationships, properties, secrets, or workload contents.
What Neo4j costs can OhChimp actually reduce?
The ones a cloud bill never shows you: oversized graph stores you could archive or compact, indexes stuck off ONLINE, slow long-running queries holding memory, a page cache hit ratio below 95% that signals mis-sized memory, more than 50 open transactions that point to a leak, and labels missing a constraint that force full scans on MERGE.
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 the 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 not implemented. Pricing is flat monthly and OhChimp never takes a cut of your savings, with a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in the first 12 months on a paid plan.