NewIntroducing a new category: Spatial ObservabilityRead it
Immersive FusionImmersive Fusion
DeepCube vs Splunk

Add a live map of your traces and logs next to Splunk.

DeepCube runs next to Splunk on your existing OpenTelemetry, with logs and AI in the node price.

$60-75

/host/month starting list price for the App & Infra and End-to-End bundles, billed annually, with logs priced separately (see Log Analytics in the pricing table). DeepCube is one per-node price with logs included.

Source: splunk.com/en_us/products/pricing.html, verified 2026-11-06

Two APM products

Splunk APM for cloud-native. AppDynamics for hybrid, on-prem and three-tier.

Built exclusively on OpenTelemetry

Your instrumentation stays yours. Change one endpoint and its API key header to leave.

The short answer

Is DeepCube a Splunk alternative?

For tracing a failure across your services and seeing what it depends on, yes. For alerting, on-call paging and infrastructure monitoring, no. Keep Splunk for those and run DeepCube next to it. Visualize takes 200 traces and logs per second for the whole grid, so check that against your volume. DeepCube (3D) is a Windows app today, with an alpha on macOS. It shows a quiet consumer or an unanswered call as a gap, but it does not yet flag a service that stops reporting.

A lone figure at the bottom of a dark canyon between two towering lattices of nodes and connections, one broad and one tall, neither reaching the other
Modern observability, purpose-built on OpenTelemetry

A managed live map next to Splunk

Your system is a live 3D map you investigate in, next to Splunk. That's spatial observability.

Side by side

DeepCube and Splunk, row by row

 DeepCubeSplunk
Architecture: How We Differ
InstrumentationStandard OpenTelemetry SDKs onlySplunk distribution of OTel Collector; upstream Collector at best-effort support
Data IngestionOTLP over gRPC onlyOTel Collector; SignalFlow analyzes incoming data
Visualization3D spatial topologyDashboards, the APM service map and Tag Spotlight
TracingDistributed tracing with spatial contextFull-fidelity tracing (100% of traces stored)
Log AnalyticsIntegrated log managementLog Observer Connect: Observability Cloud queries logs stored in the Splunk Platform, searched with SPL (source, verified 2026-11-09)
Vendor Lock-inLow. Change one endpoint and its API key header to leave.OpenTelemetry-native per Splunk
AI: Tessa vs Splunk AI SRE
Codebase AccessShipped. In DeepCube (3D), your local checkout: read, search, propose editsIn Alpha (2026-09-17): AI SRE code remediation on Claude Managed Agents reasons over source code in a sandbox and opens a pull request for review.
Spatial ContextIn DeepCube (3D): 3D topology + traces + metricsDashboards, the APM service map and Tag Spotlight
Code FixesShipped and available on every paid plan. You own the outcome.Code remediation in Alpha (2026-09-17): proposes a targeted fix in the codebase and opens a pull request for an engineer to review. Generally available AI SRE delivers step-by-step remediation plans
Focus AreaApplication topology, traces, metrics and code Cross-signal RCA (metrics, events, logs, traces) + remediation plans (AI SRE, generally available since June 2026); code remediation in Alpha
PricingIncluded in the price of every paid plan. No AI seat required, no per-query AI meter. Optional Tessa Personal seats (Tessa E5, E25 and E50 on the pricing page) add capacity.AI SRE is generally available since June 2026 and included in the Observability Essentials edition, which Splunk says is planned to be generally available in early November 2026
Accountability ModelIn DeepCube (3D), Tessa works through your traces, logs and code on her own, then brings you the answer. You own the outcomeHuman-in-the-loop by design: your team will "review, approve, and execute the final steps"
What you would pay, and for what
Bills onPer application instance (a node)"host-based entity pricing", per host per month, billed annually. MTS-based subscriptions are also documented
List rateVisualize: $20 per node, with a volume discount$15/host/mo Infrastructure, $60/host/mo App & Infra, $75/host/mo End-to-End, each a starting list price. A separate Free Edition "supports up to 15 hosts"
In the priceLogs and TessaAll bundles: Infrastructure Monitoring, Log Observer Connect, Network Explorer, Synthetic Uptime Monitoring. App & Infra adds APM and Synthetic API Monitoring. End-to-End adds Real User Monitoring and Synthetic Browser Monitoring
Not in the priceInfrastructure monitoring, alerting and paging. Optional: Tessa Personal seats (Tessa E5, E25 and E50), support hours. A $99.99 fee applies when you change plan.Database Monitoring and Secure Application are "Optional add-on. Contact us to learn more."
Log AnalyticsIncludedObservability Logs at "$0.60 per GB per day for 15 days of retention" (Splunk list price), or separate Splunk Platform pricing
On-CallNot in the price$5/user/mo (up to 10 seats)
AI AssistantIncluded (Tessa)Included in Observability Essentials (Splunk: "planned to be generally available in early November 2026")
Plan limitsVisualize: up to 5 users, 200 traces and logs per second for the whole grid, 30-day retention, shared infrastructure. Start: 3 users, 50 per second, 7-day retention. Telemetry above the limit can be dropped, and your collector will not show an error. DeepCube (3D) is a Windows app today, with an alpha on macOS.See its pricing page
What it is forRuns next to your current tool for tracing failures. No self-serve plan is meant to stand in for it today. Analyze and Fuse are available now through sales, with node minimums of 25 and 50."All your metrics, traces, and logs automatically monitored and correlated in one place."
Your numberCount your application instances, then see deepcube.ai/pricingSplunk's pricing page
Sources and full notes

Headline statistic. List pricing starts at $60-75/host/month for App & Infra and End-to-End, billed annually (source, verified 2026-11-06), with logs priced separately (see Log Analytics in the pricing table).

Introduction. Since Cisco acquired Splunk in March 2024 (source, verified 2026-11-07), the observability landscape inside Cisco has two APM products, both kept active and sold under one Splunk Observability portfolio: Splunk APM (positioned for cloud-native workloads) and AppDynamics (positioned for on-prem, 3-tier, and hybrid) (appdynamics.com now redirects to a Splunk page titled "AppDynamics joins the Splunk Observability portfolio"; source: splunk.com, verified 2026-11-06). Splunk says "Integration throughout the portfolio is underway", with identity and administration among its focus areas, and deep linking between AppDynamics and the Splunk platform is already delivered. Splunk calls the portfolio "complementary" and says "no migration needed", so today you pick the product that fits each workload (source: splunk.com, verified 2026-11-06). List pricing starts at $60/host/month for App & Infra and $75/host/month for End-to-End, billed annually (source, verified 2026-11-06). Logs are priced separately, through Observability Logs or the Splunk Platform.

DeepCube is the product; spatial observability is the category. We are not an APM company, we are a spatial observability company.

Where Splunk Excels. Log analytics and SIEM, which DeepCube does not try to replace.

  • Log analytics and SIEM: if your primary need is security operations or SIEM, keep Splunk for it. DeepCube does not try to replace it.
  • Working with organizations since 2003, and the depth of platform maturity that comes with it (source, verified 2026-11-06).
  • Full-fidelity tracing stores 100% of traces. Splunk's Trace Analyzer page says "With 100% of traces stored" (source, verified 2026-11-06), which helps when debugging rare issues.

Two APM Products. Splunk APM and AppDynamics. Two products, one portfolio, integration underway.

  • Two active APM products inside Cisco with different positioning: Splunk APM for cloud-native, AppDynamics for on-prem and hybrid. Both are kept active and sold under one Splunk Observability portfolio, and Splunk says "Integration throughout the portfolio is underway" (deep linking between AppDynamics and the Splunk platform is delivered). Splunk's guidance is to "Use the products that meet your requirements" (appdynamics.com now redirects to a Splunk page titled "AppDynamics joins the Splunk Observability portfolio"; source: splunk.com, verified 2026-11-06).
  • The practical question: a new cloud-native workload that may later go hybrid sits across two product lines, each with its own list prices on Splunk's pricing page.
  • List pricing starts at $60-75/host/month for App & Infra and End-to-End, billed annually, with logs priced separately (see Log Analytics in the pricing table).

What If You Could Choose Clarity Instead? Modern observability, purpose-built on OpenTelemetry.

  • One managed product for traces, logs and the 3D map.
  • Your system rendered spatially in 3D: an investigation surface you move through, where phantoms draw the missing side when a call never reports back, and Tessa, included in every paid plan, works from that topology into your connected codebase in DeepCube (3D).
  • Built exclusively on OpenTelemetry, so your instrumentation stays yours.

Architecture: How We Differ. OpenTelemetry only vs OpenTelemetry-native with a Splunk distribution.

DeepCube is built exclusively on OpenTelemetry with no vendor-specific distribution. Standard OTel SDKs and Collectors work out of the box. No vendor distribution needed.

Splunk's full-fidelity tracing stores 100% of traces (Splunk's APM page: "With 100% of traces stored"; source, verified 2026-11-06), which helps when debugging rare issues.

Architecture table.

  • Visualization, Splunk: Dashboards, the APM service map and Tag Spotlight (service map, Tag Spotlight, verified 2026-11-06)
  • Tracing, Splunk: Full-fidelity tracing (100% of traces stored) (source, verified 2026-11-06)

AI: Tessa vs Splunk AI SRE. A spatial investigation surface, with AI included in every paid plan.

In DeepCube (3D), Tessa connects the telemetry of the environment you are viewing to your connected codebase. In DeepCube (3D), add your repositories as workspaces, and Tessa can help you follow a production issue from the 3D topology to the source file and propose the fix in your workspace. You own the outcome.

Splunk's AI is not limited to logs. Its AI SRE, generally available since June 2026, does cross-signal root-cause analysis and delivers a "probable root cause ... along with a remediation plan that provides a step-by-step guide", and Splunk says it is "designed with a "human-in-the-loop" approach" (source, verified 2026-11-06). On 2026-09-17 Splunk extended AI SRE to code-level remediation on Claude Managed Agents, in Alpha: it works in "a disposable, network-isolated sandbox where Claude reasons over real source code" and opens a pull request for an engineer to review (source, Splunk blog 2026-09-17, verified 2026-11-06). A Splunk MCP Server also exposes observability data to external AI clients. It is genuinely capable, and AI that works in your code is now table stakes: Tessa's code fixes ship today on every paid plan in DeepCube (3D), where Splunk's code remediation is in Alpha. The durable difference is where the investigation happens. Splunk's investigation surfaces include dashboards, the APM service map and Tag Spotlight (Splunk docs, verified 2026-11-06); In DeepCube (3D), Tessa starts from where you stand in the 3D model (a node, a trace, or the core for the whole system), and in DeepCube (3D), phantoms show you, in place, a quiet consumer or a call with no reply.

AI table, full cells.

  • Codebase Access, Splunk: In Alpha (2026-09-17): AI SRE code remediation on Claude Managed Agents reasons over source code in a sandbox and opens a pull request for review (source, verified 2026-11-06). A Splunk MCP Server exposes observability data to external AI clients
  • Spatial Context, Splunk: Dashboards, the APM service map and Tag Spotlight (Splunk docs, verified 2026-11-06)
  • Code Fixes, DeepCube: Shipped and available on every paid plan. In DeepCube (3D), Tessa helps you follow the issue to the source file in your connected workspace and proposes the change. You own the outcome.
  • Code Fixes, Splunk: Code remediation in Alpha (2026-09-17): proposes a targeted fix in the codebase and opens a pull request for an engineer to review. Generally available AI SRE delivers step-by-step remediation plans (source, source, verified 2026-11-06)
  • Focus Area, Splunk: Cross-signal RCA (metrics, events, logs, traces) + remediation plans (AI SRE, generally available since June 2026); code remediation in Alpha (source, verified 2026-11-06)
  • Pricing, DeepCube: Included in the price of every paid plan. No AI seat required, no per-query AI meter. Optional Tessa Personal seats (Tessa E5, E25 and E50 on the pricing page) add capacity. Model quality scales with the plan.
  • Pricing, Splunk: AI SRE is generally available since June 2026 and included in the Observability Essentials edition, which Splunk says is "planned to be generally available in early November 2026" (GA, verified 2026-11-10; Essentials, verified 2026-11-14)
  • Accountability Model, Splunk: Human-in-the-loop by design: your team will "review, approve, and execute the final steps" (source, verified 2026-11-06)

What you would pay, and for what. Splunk Observability Cloud prices by per-host bundles, and also documents MTS-based subscriptions.

  • No bundle confusion: DeepCube includes traces, logs and Tessa in one per-node price. Splunk sells App & Infra and End-to-End bundles at different list prices, with logs priced separately (source, verified 2026-11-06).
  • Logs in the node price: Splunk offers Observability Logs in Observability Cloud, or log analytics on the Splunk Platform, where Splunk says to "Choose from activity-based, workload, or ingest pricing" (source, verified 2026-11-14). DeepCube includes log management.
  • No per-metric billing: Splunk offers MTS/usage-based billing alongside host-based billing, and draws the distinction itself: "In MTS-based subscriptions, all MTS are considered custom and charged", where host-based plans instead bundle host and container metrics into the subscription and meter only custom MTS against a per-host entitlement of 200 MTS on Enterprise and 100 on Standard (source: help.splunk.com, "Infrastructure subscription usage (Host and metrics plans)", page last updated 2026-07-13, verified 2026-11-06). Additional custom MTS are charged separately per MTS. DeepCube bills per node.
  • Predictable math: Node count sets the bill, with a volume discount on Visualize.

Pricing table, full cells. Bills on, List rate, In the price, Not in the price, On-Call and What it is for, Splunk: from Splunk's pricing page (source, verified 2026-11-06). Free Edition, Splunk: "supports up to 15 hosts" (source, verified 2026-11-06). Log Analytics, Splunk: Observability Logs at "$0.60 per GB per day for 15 days of retention" (Splunk list price), or separate Splunk Platform pricing (source, verified 2026-11-06)

Splunk pricing verified 2026-11-06 against splunk.com/en_us/products/pricing.html (the former observability pricing URL now redirects there). Actual costs vary by bundle selection and usage. DeepCube pricing from deepcube.ai/pricing. All prices USD.

Run DeepCube next to your current tool. Traces and metrics to two destinations, no re-instrumentation if you already run OTel.

  • Dual-destination: Splunk Observability already uses OpenTelemetry for data collection. Your OTel Collector can fan out telemetry to both Splunk and DeepCube simultaneously.
  • No code changes: Keep Splunk for alerting and paging. Send OTel data to DeepCube as well. Compare the experience side by side with the same production data.
  • Keep Splunk for logs and security: Use DeepCube for traces and spatial visualization alongside Splunk for log analytics, security and SIEM.
  • Monthly billing: Visualize is a monthly subscription. Start free.
  • Easy exit: If DeepCube is not right for you, change one endpoint and its API key header. Your instrumentation stays exactly the same.
It runs next to what you have

Run DeepCube next to your current tool.

Traces and metrics to two destinations, no re-instrumentation if you already run OTel.

Dual destination

Your OTel Collector can fan out telemetry to both Splunk and DeepCube simultaneously.

Keep Splunk for logs and security

Use DeepCube for traces and spatial visualization alongside Splunk for security.

Easy exit

If DeepCube is not right for you, change one endpoint and its API key header.

Dual-Destination Collector Config

receivers:
  otlp:
    protocols:
      grpc:
      http:

exporters:
  otlp/deepcube:
    endpoint: "https://otlp.deepcube.ai"
    headers:
      API-Key: "YOUR-API-KEY"
  otlphttp/splunk:
    traces_endpoint: "https://ingest.YOUR-REALM.observability.splunkcloud.com/v2/trace/otlp"
    metrics_endpoint: "https://ingest.YOUR-REALM.observability.splunkcloud.com/v2/datapoint/otlp"
    headers:
      X-SF-Token: "YOUR-SPLUNK-TOKEN"

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [otlp/deepcube, otlphttp/splunk]
    metrics:
      receivers: [otlp]
      exporters: [otlp/deepcube, otlphttp/splunk]
    logs:
      receivers: [otlp]
      exporters: [otlp/deepcube]

Standard OTel Collector config. Traces and metrics go to both destinations. Logs go to DeepCube only, so leave your existing log route in place. No code changes required if you already run OTel.

deepcube.ai

Ready to get going?

Plans, pricing, the demo grids and free sign-up live on deepcube.ai.