Three editions, two pricing axes (edition + capacity band), no surprise true-ups from a noisy Tuesday. Paid POC that credits to year one, and a displacement credit if you are leaving Splunk. That is the whole model.
caver core: SPL engine, /ui web UI, splunkd-compatible REST peer, caver-scheduler with Slack / Teams / Telegram / webhook actions.
Everything in Standard, plus CAVERN (ES), ECHO (ITSI), UBA, SLAM (SOAR).
Enterprise modules with multi-tenant isolation and white-label.
One deployment = one production cluster, dev and staging environments included for the same customer entity. Multi-deployment discount kicks in at the second cluster.
Splunk charges by the gigabyte you ingest. A bad firewall day costs you money. A new logging source costs you a procurement cycle. We refuse to recreate that dynamic. Caver capacity is measured in two units a customer can actually control:
Servers, endpoints, network devices, cloud accounts, OT assets — anything that shows up in your data with an identifier. Count grows with your infrastructure, not with your luck.
Each integration sending data into caver counts once, no matter how chatty it is. Add a new SaaS audit log? +1 source, predictable line item, not a budget event.
$25K to $75K to stand up caver against your real data in a non-production environment for 60 days. If you convert, the full POC fee credits 100% toward your year-one license. If you do not, you walk with the deployment plan, sizing data, and a clean exit. Free POCs filter for tire-kickers; paid POCs filter for buyers.
Bring written proof of a terminated Splunk contract and we take a meaningful slice off year one. The bigger the Splunk bill you are killing, the bigger the credit. This is the cleanest signal we can give that we exist to replace Splunk, not to coexist with it.
Email [email protected] with the rough size of your Splunk bill, your renewal window, and the modules you most want to displace. We will come back within a business day with a sizing estimate and a POC plan.