Book a Demo
Book a Demo
CubeAPM
CubeAPM CubeAPM

Splunk Pricing Calculator

Verified - April 2026

Splunk Observability Cloud Pricing Calculator

Adjust the inputs to match your environment. The right-hand panel updates instantly.

Profile

Splunk Observability Cloud Verified

Hosts (with bundle selection), RUM sessions, synthetic runs, database instances and Secure Application hosts. All list prices from splunk.com.

hosts
DBs
hosts
What's in the bundles: Infra ($15) = Infrastructure Monitoring; App+Infra ($60) = APM + Infrastructure Monitoring; End-to-End ($75) = APM + Infrastructure + RUM + Synthetics. Database Monitoring and Secure Application are always billed separately, on top of whichever bundle you pick.

CubeAPM ingestion estimate CubeAPM side only

CubeAPM bills on a single dimension: total GB ingested per month. Splunk Observability Cloud does not bill on log volume, so this slider does not affect the Splunk number on the right - it only shapes the CubeAPM estimate.

GB/day
How CubeAPM calculates: (log GB/day × 30) + (~2 GB/host/month for APM + Infra) + (~20 KB / RUM session), charged at $0.15/GB with a $1,000/month minimum.

What's included with CubeAPM - $0.15/GB

One platform. One bill. One per-GB rate that covers everything Splunk sells as separate observability SKUs.

  • APM with full-fidelity traces + profiling
  • Log management, unlimited retention
  • Infrastructure monitoring (hosts, containers, K8s)
  • Real User Monitoring (web + mobile)
  • Synthetic monitoring
  • Database monitoring
  • Unlimited users, no per-seat charges
  • Unlimited dashboards & alerts
  • No per-host, per-session or per-instance fees
  • Runs inside your own AWS / GCP / Azure account
What this calculator covers: Splunk Observability Cloud only (APM, Infrastructure, RUM, Synthetics, Database Monitoring, Secure Application). It does not include Splunk Platform / Cloud (log ingest), Enterprise Security, ITSI or SOAR - those are priced separately by Splunk and are out of scope for an observability-vs-observability comparison.
Runs entirely inside your own AWS, GCP or Azure account - your log, metric and trace data never leaves your infrastructure. One $0.15/GB covers APM, logs, infra, RUM, synthetics and database monitoring in a single bill: no per-host fees, no per-session meters, no per-instance DB fees.

Get a quote tailored to your environment

Most teams migrating off Splunk Observability Cloud cut their observability spend by 40-80%. We'll price your exact host + log + retention mix in a 15-minute call.

Book a Demo → View Pricing
How we calculate this - sources, assumptions, disclaimers

Scope: This calculator covers Splunk Observability Cloud only. Splunk Platform / Cloud (log ingest), Enterprise Security, ITSI and SOAR are out of scope - they are separately-licensed Splunk products and a CubeAPM-vs-Splunk-Observability comparison should not bundle them in.

Verified, from Splunk's public pages

Splunk Observability Cloud list: Infrastructure $15/host/mo, APM $55/host/mo, RUM $14 / 10,000 sessions, Synthetics $1 / 10,000 uptime runs (API and Browser meters share this rate), Database Monitoring $75/instance/mo, Secure Application $22/host/mo. Bundles: App+Infra $60/host/mo, End-to-End $75/host/mo.

Bundle inclusion rules used here

  • Infra only: hosts billed at $15. APM, RUM, Synthetics, DB and Secure App billed separately.
  • App+Infra: hosts billed at $60. RUM, Synthetics, DB and Secure App billed separately.
  • End-to-End: hosts billed at $75, RUM and Synthetics included. DB and Secure App still billed separately.
Note: Splunk's product page sometimes describes Database Monitoring as included in the bundles. In customer-published quotes it consistently appears as a separate $75/instance line item, which is the behavior modelled here.

CubeAPM side

Estimated log GB/day × 30 = baseline monthly GB. Plus ~2 GB/host/month for APM + Infra (typical microservices), and ~20 KB per RUM session. Charged at $0.15/GB. $1,000/mo minimum. Cloud infra overhead ~$0.02/GB paid to your cloud provider.

Savings display

Capped at "up to 90%" regardless of computed value.

Sources

Splunk Observability Pricing · Observability FAQ.

Estimates based on Splunk Observability Cloud list pricing published at splunk.com, verified April 2026. Splunk is a registered trademark of Splunk LLC. This calculator is not affiliated with or endorsed by Splunk LLC or Cisco Systems, Inc.

Splunk $4,047/mo
CubeAPM $767/mo
Book Demo

Why use this Splunk Observability Cloud pricing calculator

All Inputs in One Place

Combine hosts, RUM sessions, uptime requests, and On-Call seats instead of estimating each separately.

Compare packages vs products

Model the Infrastructure, App & Infrastructure, and End-to-End packages against a standalone product mix.

Real estimates

Starter pricing doesn’t show what you’ll actually spend. This ties rates to real usage for a practical projection.

Catch cost gaps early

Spot areas often missed: AWS infrastructure overhead, support upgrades, and gaps between list and commercial pricing.

Model rollout in phases

Start with infra, layer in APM, RUM, Synthetics, and On-Call as coverage expands, and see cost at each stage.

Build a budget faster

Create a working estimate for engineering, SRE, and finance teams before procurement starts.

What makes Splunk Observability Cloud costs grow at scale

Starting with one package is straightforward. Costs grow as more products are adopted, more teams join, and environments expand across multiple independent billing dimensions at once.

Additional modules stack on top of the base package

Adding APM at $55/host/month, RUM at $14 per 10,000 sessions, and On-Call at $5/user/month introduces three new billing dimensions. For 250 hosts with 1M monthly sessions and 25 On-Call users, the monthly estimate moves from $3,750 to over $19,000.

As more engineering teams adopt On-Call, seats accumulate. Going from 10 to 50 users raises that line item from $50 to $250/month, adding to a total that is already growing across other dimensions.

Most teams don’t adopt every product on day one. Once APM and RUM are added, session-based and user-based charges sit on top of the package. Adding Database monitoring at $75/instance adds yet another dimension on top of APM.

New clusters, nodes, and services can expand the monitored host count faster than initial estimates suggest, pushing both package costs and APM costs upward at the same time.

AWS Marketplace materials for Splunk note that additional AWS infrastructure costs may apply. Total spend can include both the Splunk software estimate and cloud runtime overhead that needs to be budgeted separately.

What makes Splunk Observability Cloud costs hard to estimate

The final cost is shaped by more than one pricing unit and more than one deployment path, which is why the total gets harder to model as teams grow and add products.

Multiple billing units across products

Infrastructure Monitoring and APM are per host. RUM is per 10,000 sessions. Synthetic Monitoring is per 10,000 uptime requests. On-Call is per user. Each scales independently.

Packages and standalone products don't map cleanly

Teams may end up using a package, standalone products, or a mix. The pricing page doesn’t show which route is cheaper for a specific setup without manual calculation.

The per-host rate jumps 4x across tiers

Moving from Infrastructure ($15) to App & Infrastructure ($60) is a 4x jump. Tier selection drives cost far more than small changes in host count.

Session and request volumes are harder to predict

RUM and Synthetic Monitoring costs are tied to user traffic and test frequency, which can grow faster than expected as applications scale and more tests are added.

How to reduce Splunk Observability Cloud costs

Audit unused hosts before renewal
Unused hosts quietly inflate the annual bill. Reviewing what is still actively monitored is the fastest way to find savings at the package level.
Removing 30 unused hosts from App & Infrastructure saves 30 x $60 = $1,800/month ($21,600/year)
Dev, QA, and staging rarely need the full package mix. Moving them to the Infrastructure package keeps higher-cost tiers focused on workloads that justify the spend.
50 non-production hosts from App & Infrastructure ($60) to Infrastructure ($15) saves 50 x $45 = $2,250/month
Not every host needs APM visibility. Limiting higher-cost tiers to critical services can cut costs significantly since the per-host rate jumps from $15 to $60 between tiers.
100 critical hosts on App & Infra + 150 on Infrastructure = $8,250/month vs $15,000/month for all 250 on App & Infra. Monthly saving: $6,750.
Not every page needs RUM, and not every engineer needs an On-Call seat. Scoping both to where they’re genuinely needed prevents stacking costs across teams and environments.
Cutting RUM from 5M to 2M sessions saves $4,200/month. Reducing On-Call from 50 to 25 seats saves $125/month.
 

Kubernetes environments can increase monitored host counts quickly. Running a cost estimate before adding new clusters avoids surprises on the next invoice.

How CubeAPM approaches pricing differently

The final cost is shaped by more than one pricing unit and more than one deployment path, which is why the total gets harder to model as teams grow and add products.

Predictable pricing of $0.15/GB

Covers logs, metrics, and traces. No per-host fees, no per-user charges, no session billing.

Runs in your cloud

Deploys inside your AWS, GCP, or Azure account. Data never leaves your infrastructure.

Unlimited users

No per-seat licensing. Invite your entire engineering and SRE org without a new billing dimension.

Unlimited retention

Keep data as long as you need. No vendor-imposed expiry or tiered retention pricing.

×
×