Pay for the deployment. Not for every gigabyte you happen to ingest.

Per-GB is the pain Caver exists to retire. A bad firewall day, a new logging source, a noisy DNS resolver: under volume pricing, every one of those is a budget event. A Caver license is flat per deployment, so you ingest what you need to ingest. Capacity bands measure the two things you actually control, hosts monitored and data sources connected, and both scale predictably with your infrastructure.

One production Caver cluster, plus the development and staging environments that pair with it for the same customer entity. Multi-region failover under the same customer counts as one deployment. A second business unit or a second legal entity with its own data isolation counts as a second deployment, and multi-deployment discounting starts at the second cluster.

No. Every tier licenses the whole platform: the SIEM core, CAVERN detection engineering, ECHO service intelligence, UBA behavioral analytics, SLAM automation and response, Dashboard Studio, and the lake underneath. There is no single-layer edition and no collector-only SKU. Adoption is one of two paths: migrate fully off the legacy SIEM, or run Caver in parallel and cut over when the numbers convince you. Tiers move on capacity, deployment, tenancy, and support.

Nothing breaks. Caver surfaces a UI banner and writes an audit-log entry when usage runs past the band, visible on the customer side and on ours. There are no hard lockouts. At renewal we true up: you pay the next band up, matching actual usage during the prior term. We collect what we are owed at renewal, not by bricking a production SOC.

Both, from Enterprise up. Standard runs Caver-hosted. Enterprise and MSSP run Caver-hosted or on your own infrastructure, and the license includes installer access: Helm charts, Terraform modules, and cloud templates, plus the App Store subscription pipeline that keeps collectors current. Same license model either way. The SLA differs slightly: 99.9% uptime when Caver-hosted, mutually agreed when self-hosted, because you control the operating environment.

Not for the commercial product. The fastest way in is the paid 60-day POC, which credits 100% toward year one if you convert. Free POCs filter for tire-kickers; paid POCs filter for buyers, and the credit removes the cost objection.

Show us written proof of an active Splunk contract you are terminating in order to land on Caver (a redacted order form is fine). Based on the Splunk annual spend, you get 25%, 35%, or 50% off year one. The credit is year-one only and non-stackable with other promotional credits. Every accepted credit becomes a published displacement case study, with your approval.

No. Caver is closed-source proprietary software, delivered as binaries plus a commercial license, the same shape as every other commercial SIEM in this market. The full MIT-to-commercial story is at /caver/transition/. Contact matt@redeyesecurity.com for evaluation access and license terms.

Caver ships with a standard EULA that handles the bulk of the relationship. Larger enterprise customers typically prefer an MSA with Caver-specific order forms attached. We work with either. Tennessee is the default governing law; we have negotiated alternative law and venue for larger deals.