CDviz

Appearance

CDviz vs Middleware ​

Both CDviz and Middleware are open-source, Apache 2.0 platforms targeting SDLC observability and DORA metrics. The core difference is the data model: Middleware polls your tools (GitHub, GitLab, Jira) on a schedule; CDviz ingests a real-time event stream from your pipeline using the CDEvents standard.

Last updated July 2026. Corrections welcome.

At a glance ​

CDvizMiddleware
LicenseApache 2.0Apache 2.0
Self-hostedYesYes
SaaS optionCloud (€20/mo, 14-day free trial)Yes
Commercial supportYesYes (paid tiers only)
Data ownershipfullself-hosted / SaaS cloud
CDEvents standardYesNo
Data modelEvent-driven (push, real-time)Pull-based (polling)
DORA metricsYesYes
Sprint / project flow insightsNoYes
PR review analytics⏳ plannedYes
AI-powered reportsNoYes (Standard+)
Beyond monitoring: trigger workflowsYesNo
Jira integration¹Yes
Slack integration²Yes (Standard+)
Customizable storage backendsYes (PostgreSQL, ClickHouse…)No
VisualizationGrafana, BI, AI agents, MCP, IDPbuilt-in dashboards
Cost (self-hosted)Free (Community) · Pro €200/mo per orgFree community
Cost (SaaS)Cloud €20/month per org$39/user/month (Standard)

¹ Jira issue/version webhooks are mapped to CDEvents by a beta transformer, open source and free to self-host on any plan (see Jira integration), or via a custom webhook mapping.
² Slack notifications work through the HTTP sink plus a workflow tool (n8n, Make, Zapier…) or a custom webhook. There is no ready-made Slack app.

Key differences ​

  • Data model: Middleware polls GitHub, GitLab, and Jira APIs on a schedule into a proprietary model. CDviz receives events pushed from your pipeline tools in real time using the CDEvents open standard, so live data has no polling delay. It can still poll for backfill or webhook-less systems, and normalizes everything to CDEvents.
  • DORA calculation: Middleware derives DORA metrics from PR merge history and deployment annotations pulled from your VCS. CDviz derives DORA metrics from CDEvents emitted directly by your CI/CD toolchain at the moment they happen.
  • Scope: Middleware extends beyond CI/CD into sprint health: blocked work, spilled stories, Jira flow metrics, and AI-generated sprint summaries. CDviz focuses on the full SDLC event stream (build, test, artifact, deploy, incident) with less emphasis on issue-tracker analytics.
  • Event standard: CDviz is built on the CDEvents specification, a CD Foundation project for interoperable CI/CD events. Middleware uses a proprietary data model tied to its own integrations.
  • Observe and act: The CDviz event stream that drives observability can also trigger downstream workflows. Middleware is monitoring and reporting only.
  • Visualization: CDviz integrates with Grafana, BI tools, AI agents, and IDP frameworks, giving teams full flexibility. Middleware ships its own built-in dashboard UI, optimised for DORA and sprint metrics.
  • Cost model: CDviz commercial support is priced per organization per month, not per seat, so cost does not scale with team size. Middleware's Standard SaaS tier is $39 per user per month, which grows linearly with headcount.

When to choose CDviz ​

  • You want real-time metrics from a push-first event stream, not schedule-bound polling.
  • Data ownership or privacy regulations make vendor-hosted SaaS unacceptable.
  • You are adopting the CDEvents open standard for interoperability across your toolchain.
  • You need events to trigger downstream workflows, not only to observe them.
  • You want flexible storage, reporting, or integration with BI tools, AI agents, or IDPs.
  • Team size makes per-seat pricing expensive; you prefer a flat per-org cost (Cloud €20/mo, Pro €200/mo).

When to choose Middleware ​

  • Your primary workflow is sprint-centric: you want Jira flow metrics, sprint reports, and blocked-work detection alongside DORA.
  • You want AI-generated sprint summaries and automated Slack reports out of the box.
  • Your team is small and the free community tier covers your needs.
  • You prefer a built-in dashboard UI rather than operating Grafana separately.

Summary ​

Middleware and CDviz are both open-source Apache 2.0 tools, but they solve adjacent problems. Middleware is a strong choice for engineering managers who want sprint health, Jira flow, and AI-assisted reporting alongside DORA metrics. It has a polished built-in UI and a free self-hosted tier. CDviz is the right choice when you need a real-time event-push model, CDEvents interoperability, event-driven automation, and flexible visualization. Flat per-organization commercial support is available to reduce operational risk.

Get started with CDviz

Self-host CDviz: free, Apache 2.0. Or try CDviz Cloud: €20/mo, 14-day free trial, no credit card.

FAQ ​

Is Middleware open-source? Yes. Middleware is Apache 2.0 licensed and available at github.com/middlewarehq/middleware.

Does Middleware support CDEvents? No. Middleware uses a proprietary data model based on polling GitHub/GitLab/Jira APIs. CDEvents integration is not supported.

Does CDviz support Jira? Yes. A Jira webhook transformer (beta) maps issue and version events to CDEvents (ticket.*, artifact.published). It is open source and free to self-host on any plan, or you can ingest Jira webhooks via a custom mapping. Sprint-level flow metrics are not a current focus.

Is CDviz free? Yes. The Community plan is free forever (Apache 2.0, infrastructure costs only). Cloud (€20/month) adds managed hosting; Pro (€200/month) adds extra integrations and support. Both are billed per organization, not per seat.