Splunk RUM (Observability Cloud) Pricing 2026: Quote-Only, What We Can Infer
Splunk RUM is quote-only. Splunk does not publish a RUM-specific per-session or per-beacon rate. RUM is bundled into Splunk Observability Cloud, which uses workload, ingest, entity, or activity-based pricing, all enterprise-negotiated.
The fast facts
| Pricing model | Quote only |
| Cheapest paid | Quote only |
| Per 1,000 sessions | , |
| Per GB ingest | , |
| Per 1,000 replays | , |
| Free tier | No |
| Session replay | unknown |
| Retention | Not published |
| Annual discount | Not published |
| Source | www.splunk.com/en_us/products/pricing.html |
The pricing model
Part of Splunk Observability Cloud. No published RUM-specific rate. Splunk lists generic observability pricing models (workload, ingest, entity, activity-based) but no specific RUM line item.
Inside Observability Cloud
Splunk RUM is one product line inside Splunk Observability Cloud, which also includes Splunk APM, Infrastructure Monitoring, Log Observer, Synthetic Monitoring, and IT Service Intelligence. Splunk Observability Cloud is itself one part of the broader Splunk platform (which centres on log analytics and SIEM). Pricing for RUM specifically is not published; pricing for Observability Cloud as a whole is itself opaque, with four named billing dimensions (workload, ingest, entity, activity) that map to different product mixes.
In practice, Splunk RUM is rarely bought standalone. It typically appears as a line item in a wider Splunk Observability Cloud contract that bundles APM, logs, and infrastructure. The bundle economics make standalone RUM pricing comparison against per-session vendors largely irrelevant for actual Splunk procurement.
The four pricing dimensions
- Workload-based, pay for the volume of metric data ingested, typically attached to APM and infrastructure use.
- Ingest-based, pay per GB of raw event data ingested, typically attached to logs and traces.
- Entity-based, pay per monitored entity (host, container, service). Common for infrastructure-heavy customers.
- Activity-based, pay per discrete monitoring activity (RUM session, synthetic check, APM trace). The closest analog to per-session RUM pricing, but Splunk does not publish the activity unit rate.
What we can infer
Splunk Observability Cloud contracts typically land in the $50,000-$500,000/year range based on customer scale. The RUM-specific portion of that bill is usually a minor fraction of the total, the dominant cost drivers are log ingest and APM. For a customer not already on Splunk, the RUM-only conversation rarely makes sense; for a customer already on Splunk APM at $100K+/year, adding RUM is often a 5-15% incremental line item rather than a separate procurement.
We do not publish a verified per-session rate for Splunk RUM. The numbers above are inference from broader Splunk Observability Cloud commercial patterns; treat as directional only, not a binding quote.
How Splunk RUM compares
- Versus Datadog RUM, both are enterprise-positioned platforms. Datadog publishes $4.50/1K sessions; Splunk does not publish a comparable rate. At similar scale, Splunk Observability Cloud contracts can be larger than equivalent Datadog spend due to log ingest dominance.
- Versus Akamai mPulse, both are fully quote-only. Splunk is at least published as a four-dimension pricing structure; Akamai publishes nothing concrete beyond mPulse Lite.
- Versus Dynatrace RUM, Dynatrace publishes $2.25-$4.50/1K and is more procurement-transparent. Splunk wins if log analytics is the bigger pain point; Dynatrace wins for pure observability with published rates.
- Versus AWS CloudWatch RUM, radically different procurement: AWS bills per-event at $1/100K, transparently published. Splunk bills are negotiated and opaque.
When Splunk RUM is the right choice
- You already run Splunk Observability Cloud and want to add RUM under the same contract.
- Your team prefers Splunk's SPL query language and dashboard ergonomics.
- You need RUM data flowing into the same query layer as logs and traces for cross-product investigations.
- You operate at enterprise scale where bundled procurement is preferable to multiple standalone vendor contracts.
When Splunk RUM is the wrong choice
- You are not on Splunk for any other product, the bundle rationale disappears and standalone Splunk RUM has no obvious cost advantage.
- You need transparent, published per-session pricing for procurement compliance.
- You operate at mid-market scale where per-session vendors (Datadog, Dynatrace, Sentry) offer cleaner pricing.
For Splunk on the APM and log management side, see our sister site's Splunk Observability pricing breakdown. For the operational consequences of quote-only vendors generally, see quote-only vendors.
Try it in the calculator
The RUM cost calculator includes Splunk alongside 17 other vendors. Enter your monthly page views, session replay coverage, retention, and sampling rate to see how Splunk's pricing compares head-to-head against the alternatives.
Where to go next
- Multi-vendor calculator — estimate Splunk's cost against 17 alternatives at your specific workload.
- Per-session pricing models — how Splunk's pricing model compares structurally to Datadog, Dynatrace, and Raygun.
- Quote-only vendors — the five RUM vendors that don't publish prices and the operational consequences.
- Hidden RUM costs — sampling, retention storage, replay storage, and overage gotchas across the category.
- Methodology — how we verified the Splunk pricing data shown above (verified 2026-06-16).