Follow a failure through a live map of your system.
See which service a failure reached and what it depends on. DeepCube runs next to your Grafana stack, on the same OpenTelemetry.
projects if you self-host: Grafana, Loki, Tempo, Mimir, Pyroscope, Alloy, each shipped separately.
Source: grafana.com/oss, verified 2026-11-06If you self-host
Self-hosted, that is six projects to configure. Grafana Cloud manages them for you.
Managed
No stack to run for the map. Pair it with Grafana for alerting and dashboards.
Is DeepCube a Grafana alternative?
For a managed live map of your traces and logs, with no stack to run, yes. For custom dashboards, alerting, paging and infrastructure monitoring, no. Keep Grafana 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.
No stack to run for the map
Traces, metrics, logs and AI around a live 3D map you move through, in one managed product, not a stack you run yourself. That's spatial observability.
DeepCube and Grafana, row by row
| DeepCube | Grafana | |
|---|---|---|
| Architecture: How We Differ | ||
| Platform Model | Unified managed platform | LGTM stack (Loki + Grafana + Tempo + Mimir) plus Pyroscope and Alloy |
| Instrumentation | Standard OpenTelemetry SDKs only | OpenTelemetry-native (Alloy, plus Beyla, now Grafana's distribution of upstream OpenTelemetry eBPF Instrumentation) |
| Visualization | 3D spatial topology | Flexible dashboards over data wherever it is stored |
| Vendor Lock-in | Low. Change one endpoint and its API key header to leave. | Open-source components |
| Operational Burden | Fully managed SaaS | Self-managed (OSS or Enterprise) or Grafana Cloud (managed) |
| Community | Early | 77,000+ GitHub stars, massive ecosystem |
| AI: Tessa vs Grafana Assistant | ||
| Codebase Access | In DeepCube (3D), your local checkout: read, search, propose edits | Indirect on the generally available surfaces. The MCP server "lets external AI agents connect directly to your Grafana Cloud data". Two exceptions are preview-only: Managed Sandboxes (public preview since 2026-10-19) works in GitHub repositories you connect, and the Assistant desktop app (private preview since 2026-07-31) "can work with your local file system, your code, and your other tools" |
| Production Context | In DeepCube (3D): 3D topology + traces + metrics | Metrics, logs, traces, and profiles across Grafana Cloud, with cross-signal correlation and hypothesis testing via Assistant Investigations (GA 2026-07-29) |
| Code Fixes | Available on every paid plan. In DeepCube (3D), Tessa proposes the change in your connected workspace. You own the outcome. | First-party code fixes are in public preview: Managed Sandboxes, since 2026-10-19, has a coding agent edit your repository and prepare a pull request for you to review. Assistant Skills (GA 2026-03-17) plus auto-approve let users build runbooks that connect to external tools |
| Pricing | 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. | $20.00/active AI user/month at 1-25 users, $18.25 at 26-50, $17.00 at 51+, each seat including 40M tokens with overage at $2 per 1M; Enterprise is custom with a "Minimum commit of $25,000 per year". |
| Spatial Context | In DeepCube (3D): 3D topology-aware diagnosis | Grafana Cloud Knowledge Graph "automatically discovers your services from OpenTelemetry data" and renders an entity graph of dependencies plus an RCA workbench. It is an entity graph you filter and click through; DeepCube puts the same services, dependencies and telemetry in a space you move through |
| Accountability | In DeepCube (3D), Tessa works through your traces, logs and code on her own, then brings you the answer. You own the outcome | An investigation ends in a report, by Grafana's own definition. In Managed Sandboxes (public preview) an agent prepares a code change for review, and "Grafana never merges or deploys" |
| What you would pay, and for what | ||
| Bills on | Per application instance (a node) | Grafana Cloud Pro: a $19/month platform fee plus usage, on each product's own unit: active series, GB, host hour, active user and more |
| List rate | Visualize: $20 per node, with a volume discount | $19/month platform fee, plus usage at the rates in the rows below |
| Application Observability | In the node price | $0.025/host-hr, which Grafana prints as "$18/host"; Grafana notes "Automatic volume discounts" without publishing breakpoints |
| Logs | Included | $0.05/GB process + $0.40/GB write + $0.10/GB retain, after the free 50 GB |
| Visualization | Per node, up to 5 users on Visualize | $8.00/active user/mo at 1-25 users ($7.25 at 26-50, $6.80 at 51+), first 3 free |
| AI Assistant | Included (Tessa) | $20.00/active AI user/mo at 1-25 users, first 3 free |
| In the price | Logs and Tessa | The $19 platform fee includes allowances, then pay as you go: for example 10k active series, 50 GB of logs, 3 active AI users and 8x5 email support |
| Not in the price | Infrastructure monitoring, alerting and paging. Optional: Tessa Personal seats (Tessa E5, E25 and E50), support hours. A $99.99 fee applies when you change plan. | On Application Observability, "metrics, logs, traces, and profiles are billed separately" |
| Plan limits | Visualize: 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. | 13 months retention for metrics; 30 days for logs, traces and profiles |
| What it is for | Runs 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. | "Ready for scaling with more retention, basic support, and usage-based pricing." |
| Your number | Count your application instances, then see deepcube.ai/pricing | grafana.com/pricing |
Sources and full notes
Headline statistic. Self-hosted, that is six projects to configure. Grafana Cloud manages them for you. Source: grafana.com/oss, verified 2026-11-06 (Grafana, Loki, Tempo, Mimir, Pyroscope, Alloy shipped as separate projects).
Introduction. Grafana Labs was named a Leader in the 2026 Gartner Magic Quadrant for Observability Platforms, its third consecutive year, and placed furthest for Completeness of Vision for the second year running (source, verified 2026-11-06), with 77,000+ GitHub stars (source, verified 2026-11-06: 77,733 stars) and a large open-source ecosystem. We respect that. This page is an honest look at where DeepCube takes a different approach, where Grafana excels, and how you can evaluate both with the same production data.
DeepCube is the product; spatial observability is the category. We are not an APM company, we are a spatial observability company.
If you self-host. Self-hosted, that is six projects to configure. Grafana Cloud manages them for you.
- Loki, Tempo, Mimir, Pyroscope, Alloy, Grafana: Grafana ships these as six separate open-source projects, each with its own repository and release train. If you self-host, running them is your job.
- Assembly tax: configuration, upgrades, scaling, cross-signal correlation, and on-call for the monitoring system itself.
- Platform engineering bandwidth: for teams that need to ship features, not manage observability infrastructure, the assembly tax is real.
- Self-hosting also reduces the AI, and Grafana says so: "Core chat, dashboarding, querying, and navigation workflows remain available, while Grafana Cloud-dependent features such as investigations, Knowledge Graph memory, and Grafana Cloud MCP connections are hidden" (source, verified 2026-11-06). The open-source path and the full Assistant are not the same product.
No stack to run for the map Fully managed. Still OTel-native.
- Same commitment to open standards: no vendor-specific agents, and your instrumentation stays portable. Your OTel instrumentation works with any compatible backend.
- Single, managed platform: traces, metrics, logs, AI, and 3D topology in one product, not a stack you run yourself.
- What a dashboard does not give you: an investigation surface you move through in DeepCube (3D), and Tessa, an AI assistant included in the per-node price that, in DeepCube (3D), works from that view into your code.
- Phantoms: when a call goes out and nothing ever reports back from the other side, or a consumer goes quiet while messages keep arriving, DeepCube (3D) draws the missing side where it should be, so what is missing shows up in the space. It does not yet flag a service that stops reporting.
Architecture: How We Differ. No stack to run for the map. Pair it with Grafana for alerting and dashboards.
DeepCube and Grafana share the same commitment to open standards and OpenTelemetry. The difference is what happens after data ingestion. Grafana gives you deep, flexible dashboards. DeepCube gives you a 3D spatial environment where your services, relationships, and telemetry live together, plus an AI assistant that, in DeepCube (3D), can diagnose issues and propose a code fix.
Grafana Cloud is fully managed, and we will not pretend otherwise. The assembly does not disappear, it moves to the invoice: Grafana Cloud's pricing page lists 17 products, most with their own meter and free-tier limit, and you decide which ones to turn on (source, verified 2026-11-06). Many meters carry their own free limit, for example, on the free tier, 50 GB of logs per month, 2,232 Application Observability host hours, 3 active visualization users and 3 active AI users. DeepCube is managed, so there is no stack to run for the map. Pair it with Grafana for alerting and dashboards.
Architecture table. Community, Grafana: 77,000+ GitHub stars, massive ecosystem (source, verified 2026-11-06: 77,733 stars).
AI: Tessa vs Grafana Assistant. In DeepCube (3D), Tessa works through your traces, logs and code on her own, then brings you the answer.
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 helps you follow a production issue from the 3D topology to the source file, then proposes the fix.
In DeepCube (3D), Tessa works in your workspace, in your developer's local checkout. You own the outcome.
Grafana's equivalent surface holds a different set of things. "Grafana Assistant Workspace is a full-page Assistant experience", and its context picker takes "data sources, labels, metrics, dashboards, entities, skills, and notebooks" (source, verified 2026-11-06). Repositories connect separately, through a GitHub connector. Grafana is moving toward your code on two preview surfaces. Managed Sandboxes, in public preview since 2026-10-19, is where "the agent reads your repository, edits the code, runs tests and builds" (source, verified 2026-11-06). The Grafana Assistant desktop app, in private preview since 2026-07-31, "can work with your local file system, your code, and your other tools alongside all your data in Grafana Cloud", and Grafana says "features may change before GA" (source, verified 2026-11-06). The older Assistant CLI that reached local files is being retired: "Grafana Assistant CLI is deprecated and will be removed in a future release. Use gcx instead", and its filesystem tool is read-only by default, "Run the tunnel so Assistant can read local project files and, optionally, run approved shell commands on your machine" (source, verified 2026-11-06).
Grafana Assistant helps you write queries, understand anomalies, and investigate incidents, in Grafana and from Slack, your terminal or its mobile app. Valuable for teams who live in Grafana, and Grafana scopes it themselves: "Grafana Assistant brings a purpose-built LLM to Grafana so operators, developers, and SREs can troubleshoot issues, manage dashboards, and answer product questions in minutes" (source, verified 2026-11-06). It does reach a codebase, through the gcx CLI and an MCP server, but Grafana's own pricing FAQ puts the reasoning on your side of the line: when your own coding agent uses gcx or the Cloud MCP server to query Grafana, "the reasoning happens in your agent's model, and no Grafana AI tokens are consumed" (source, verified 2026-11-06). Grafana's first-party routes to a fix are previews: Managed Sandboxes in public preview and the desktop app in private preview. Through gcx and the MCP server, the fix happens in a coding agent you bring. On Cloud Pro it costs $20/active AI user/month on top of your existing Grafana costs, with the first 3 users free, and it is included on Grafana Cloud's free plan. Tessa is in the price of every paid DeepCube plan with no AI seat required (optional Tessa Personal seats, Tessa E5, E25 and E50, add capacity) and, in DeepCube (3D), goes from diagnosis to a proposed code fix in one conversation.
AI table, full cells.
- Codebase Access, Grafana: Indirect on the generally available surfaces, and Grafana describes both that way. gcx: "gcx is a single CLI that allows you and your AI coding agent structured access to both Grafana (dashboards, folders, alert rules, data sources) and Grafana Cloud products" (source, verified 2026-11-06). The MCP server: "The Grafana Cloud MCP server is a remotely hosted Model Context Protocol (MCP) server that lets external AI agents connect directly to your Grafana Cloud data" (source, verified 2026-11-06). Both let an agent you already own query Grafana, and gcx also reaches Assistant itself (gcx GA 2026-07-28, source, verified 2026-11-06). Two exceptions are preview-only: Managed Sandboxes (public preview since 2026-10-19) works in GitHub repositories you connect, and the Assistant desktop app (private preview since 2026-07-31) "can work with your local file system, your code, and your other tools" (source, verified 2026-11-06)
- Production Context, Grafana: Metrics, logs, traces, and profiles across Grafana Cloud, with cross-signal correlation and hypothesis testing via Assistant Investigations (GA 2026-07-29) (source, verified 2026-11-06). Grafana defines the deliverable itself: an investigation "forms hypotheses, dispatches sub-agents to prove or disprove them against your telemetry, and produces a structured report with findings, supporting evidence, and recommended next steps" (pricing FAQ, verified 2026-11-06)
- Code Fixes, DeepCube: 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, Grafana: First-party code fixes are in public preview. Assistant Skills (GA 2026-03-17) plus auto-approve let users build runbooks that connect to external tools; Grafana's own example is "raising a PR in GitHub or GitLab" via a user-configured pipeline calling GitHub (source, verified 2026-11-06). The surface to watch is Managed Sandboxes, in public preview since 2026-10-19: "the agent reads your repository, edits the code, runs tests and builds" (source, verified 2026-11-06). The desktop app preview also works with "your code"; Grafana says "features may change before GA" (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, Grafana: $20.00/active AI user/month at 1-25 users, $18.25 at 26-50, $17.00 at 51+, each seat including 40M tokens with overage at $2 per 1M; Enterprise is custom with a "Minimum commit of $25,000 per year". Note what counts as a seat: "Connecting through the Cloud MCP server also counts as active use", so pointing your own coding agent at Grafana bills an AI user (source, verified 2026-11-06)
- Spatial Context, Grafana: Grafana Cloud Knowledge Graph "automatically discovers your services from OpenTelemetry data" (source, verified 2026-11-06) and renders an entity graph of dependencies plus an RCA workbench (source, verified 2026-11-06). It is now the default: "New Grafana Cloud organizations get Grafana Application Observability powered by the Grafana Cloud Knowledge Graph automatically" (source, verified 2026-11-06), and its "Show all entities" search, added 2026-09-24, displays "a connected view of every entity in your environment", with "results are truncated for performance" in large environments (source, verified 2026-11-06). It is an entity graph you filter and click through; DeepCube puts the same services, dependencies and telemetry in a space you move through
- Accountability, Grafana: An investigation ends in a report, by Grafana's own definition: an investigation "produces a structured report with findings, supporting evidence, and recommended next steps" (pricing FAQ, verified 2026-11-06). In Managed Sandboxes (public preview) an agent prepares a code change for review, and "Grafana never merges or deploys" (source, verified 2026-11-06)
What you would pay, and for what. Grafana Cloud bills per signal, per user and per feature (source, verified 2026-11-06). This table shows how each one bills and what each price covers.
- What the price covers: On Visualize, within its limits, the node price covers a 3D spatial investigation surface, phantoms in DeepCube (3D) for a quiet consumer or a call with no reply, and Tessa's allowance with no per-token billing.
- No per-user platform fees: DeepCube's platform and its built-in AI assistant are priced per node, not per user, with no AI seat required (optional Tessa Personal seats, Tessa E5, E25 and E50, add capacity). Grafana charges $8/user for visualization and $20/user for AI separately, each with the first 3 active users free (source, verified 2026-11-06).
- Predictable billing: DeepCube's per-node pricing means data volume does not set your bill, within your plan's throughput limit. Grafana Cloud bills per GB across logs, traces, and profiles.
- No operational burden: DeepCube is fully managed with the same OTel portability. Grafana Cloud is Grafana's managed option; self-hosted Grafana runs on infrastructure you operate.
- Investigations add a token meter: "Investigations are billed by the tokens they consume - there is no per-investigation or per-seat charge." The ones you start count toward each AI user's 40M-token monthly allowance, the ones alerts and incidents trigger count toward a 25M-token monthly system pool, and "Beyond your included allowances, additional tokens are billed at $2 per 1M" (source, verified 2026-11-06). Tessa's allowance is part of DeepCube's node price, with no per-token billing.
- One more meter, not one more subscription: Grafana sells Investigations with "No separate subscription - pay only for the tokens investigations consume" (source, verified 2026-11-06). The AI bill is seats plus tokens; DeepCube's bundled AI is in the node price.
- Connecting your own agent bills a seat: "Connecting through the Cloud MCP server also counts as active use", so the integration that keeps the reasoning in your model still consumes a $20 AI user (source, verified 2026-11-06).
- Bills on, Grafana: Grafana Cloud Pro: a $19/month platform fee plus usage, on each product's own unit: active series, GB, host hour, active user and more (source, verified 2026-11-06)
- List rate, Grafana: $19/month platform fee, plus usage at the rates in the rows below (source, verified 2026-11-06)
- Application Observability, Grafana: $0.025/host-hr, which Grafana prints as "$18/host"; Grafana's Pro card notes "Automatic volume discounts" without publishing breakpoints, and does not say whether the 2,232 free host hours apply. That is the current published rate, and it applies to customers who started on or after 2026-02-13, who "pay for host hours plus telemetry, with no telemetry credits", so telemetry bills on top. Customers who started earlier "pay a higher host hour rate that includes telemetry credits"; Grafana does not print that rate (pricing, Application Observability pricing, verified 2026-11-06)
- Logs, Grafana: $0.05/GB process + $0.40/GB write + $0.10/GB retain, after the free 50 GB (source, verified 2026-11-06)
- Visualization, Grafana: $8.00/active user/mo at 1-25 users ($7.25 at 26-50, $6.80 at 51+), first 3 free (source, verified 2026-11-06)
- AI Assistant, Grafana: $20.00/active AI user/mo at 1-25 users, first 3 free (source, verified 2026-11-06)
- In the price, Grafana: The $19 platform fee includes allowances, then pay as you go: for example 10k active series, 50 GB of logs, 3 active AI users and 8x5 email support (source, verified 2026-11-06)
- Not in the price, Grafana: On Application Observability, "metrics, logs, traces, and profiles are billed separately" (source, verified 2026-11-06)
- Plan limits, Grafana: 13 months retention for metrics; 30 days for logs, traces and profiles (source, verified 2026-11-06)
- What it is for, Grafana: "Ready for scaling with more retention, basic support, and usage-based pricing." (source, verified 2026-11-06)
Grafana Cloud pricing based on Pro tier rates from grafana.com/pricing, verified as of 2026-11-06. Actual costs vary by data volume and active users. Self-hosted Grafana is free but excludes operational costs. 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: Your OTel Collector fans out traces and metrics to both DeepCube and Grafana simultaneously.
- Both platforms are OTel-native: Add an exporter, see your data in DeepCube's 3D topology, and decide which experience your team prefers.
- Keep your Grafana dashboards: DeepCube adds spatial topology and AI on top. You do not have to abandon existing dashboards.
- Easy exit: If DeepCube is not right for you, change one endpoint and its API key header. Your instrumentation stays exactly the same.
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 fans out traces and metrics to both DeepCube and Grafana.
Keep your Grafana dashboards
You do not have to abandon existing dashboards.
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/grafana:
# Your stack's OTLP endpoint, e.g. https://otlp-gateway-prod-us-central-0.grafana.net/otlp
endpoint: "${env:GRAFANA_CLOUD_OTLP_ENDPOINT}"
auth:
authenticator: basicauth/grafana
extensions:
basicauth/grafana:
client_auth:
username: "${env:GRAFANA_CLOUD_INSTANCE_ID}"
password: "${env:GRAFANA_CLOUD_API_KEY}"
service:
extensions: [basicauth/grafana]
pipelines:
traces:
receivers: [otlp]
exporters: [otlp/deepcube, otlphttp/grafana]
metrics:
receivers: [otlp]
exporters: [otlp/deepcube, otlphttp/grafana]
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.
Ready to get going?
Plans, pricing, the demo grids and free sign-up live on deepcube.ai.
