CI/CD monitoring
CI/CD pipeline monitoring across every provider
Pipeline runs, DORA metrics, cost, and flaky tests across GitHub Actions, GitLab CI, Bitbucket Pipelines, CircleCI, Azure DevOps, and Jenkins. Two-minute setup per provider. Connect what you've got.
Pipeline runs across 5 providers · live
Six providers, one view
Pick your CI to get started
Each provider gets its own page covering the specifics: vocabulary, native page links, deploy-detection conventions, and the patterns that swing the bill on that platform.
GitHub Actions
Workflow runs, DORA, and flaky tests across every repo. macOS cost concentration, third-party action pinning, reusable-workflow DORA attribution.
See GitHub Actions monitoring →
GitLab CI
Pipelines, DORA, and flaky tests across every project. Works the same on gitlab.com and self-managed. Native artifacts:reports:junit: support.
See GitLab CI monitoring →
Bitbucket Pipelines
Pipelines, DORA, and flaky tests across every workspace. Build-minute burn-down per workspace. Atlassian-stack friendly: Jira keys parsed from branches.
See Bitbucket Pipelines monitoring →
CircleCI
Workflows, DORA, and flaky tests across every CircleCI org. Credits translated to dollars on every row. The cross-project view Insights stops at.
See CircleCI monitoring →
Azure DevOps
Pipelines, DORA, and flaky tests across every project. YAML and Classic Release pipelines in one feed with dedup. Parallel-slot utilisation per row.
See Azure DevOps monitoring →
Jenkins
Jenkins jobs alongside your modern CI in one feed. DORA aggregated across both. No plugin install, API token only. Mixed-estate ready.
See Jenkins monitoring →
What you get on every connect
Six signals on every pipeline
Same capabilities regardless of which provider you connect. Pick the providers you run; the data shape is consistent across them all.
Status & duration
Every run, every repo, every provider. Live status plus duration trends over 7, 30, and 90 days.
DORA metrics →
All five DORA metrics, derived from pipeline data with configurable deployment-detection rules.
Pipeline stability →
Healthy, flaky, or broken classification per pipeline. Spot ones that pass on rerun more than first time.
Cost & waste →
Compute spend plus developer wait time. Waste categories for failed, cancelled, duplicate, and flaky runs.
Flaky tests →
JUnit XML parsed automatically. Flip rate and failure rate per test, sortable across the whole estate.
PR health →
CI success rate per PR, time-to-first-green, and the PRs blocked longest by failing or queued pipelines.
Audit →
Built-in rules check for missing tests, missing lint, absent SAST, secrets-in-config, and more.
Security insights →
Per-repo security-scan detection rolled up across the estate. Business tier.
Pricing
Flat per tenant
Start free for one team. Team and Business tiers are flat monthly rates per tenant. Enterprise is custom for organisations needing SSO, audit logging, and security review.
Free
For one team getting started with up to 3 repos.
- 3 repos
- 1 team member
- Any provider, or multiple
- DORA, flaky tests, stability
- Cost view (last 30 days)
- Email support
Team
Flat rate per tenant. Up to 20 repos and 10 team members.
- 20 repos
- 10 team members
- Everything in Free
- Cost tracking with full history
- PR health, performance ratings
- Slack notifications, CLI, MCP server
Business
Flat rate per tenant. Up to 100 repos and 50 team members.
- 100 repos
- 50 team members
- Everything in Team
- Audit findings and cost-optimization opportunities
- Security insights, audit log export
- Priority support
6
providers supported
~2 min
to connect each provider
0
agents to install anywhere
Flat
per-tenant pricing
FAQ
CI/CD pipeline monitoring
- What is CI/CD pipeline monitoring?
- CI/CD pipeline monitoring tracks the execution of continuous integration and continuous delivery pipelines across one or more providers. Beyond the green/red status, it covers duration, stability, cost, test results, and delivery metrics such as DORA. Good monitoring answers three questions on one screen: what is running right now, what is failing or slow, and how has delivery performance trended.
- Why not just use the provider's native UI?
- Provider-native UIs (the GitHub Actions tab, the GitLab Pipelines view, the Jenkins dashboard) work well for one repository or one project. They stop scaling once you have 20 or 30 repos, two providers, and a release train that touches all of them. Each UI wants its own tab and its own refresh cycle, and none of them speak to each other. Teams with mixed CI estates end up rebuilding cross-provider views in BI tools or bespoke scripts.
- Which CI/CD providers does CI/CD Watch support?
- Six: GitHub Actions, GitLab CI, Bitbucket Pipelines, CircleCI, Azure DevOps, and Jenkins. Connections are read-only and use each provider's official API. CI/CD Watch never reads source code or writes to repositories.
- Does CI/CD Watch require agents or CI configuration changes?
- No. CI/CD Watch connects via each provider's API only. No agent to install, no YAML to add. Most providers connect via OAuth; Jenkins uses an API token; GitLab uses a personal or group access token; Azure DevOps uses a PAT.
- How does CI/CD Watch stay live without hammering provider APIs?
- Efficient API polling with conditional requests: where a provider supports them (most do), we send conditional requests and get back a tiny 'nothing changed' response that costs almost nothing against the rate-limit budget. A rate-limit-aware scheduler backs off when a provider is close to its quota.
- What is included on the free plan?
- Monitoring is free for one team on up to 3 repos: pipeline runs, workflow status, duration, DORA, and flaky tests. Analytical insights (cost tracking with full history, PR health, performance ratings, security insights) are on paid plans. Slack alerts are available from the Team plan upwards.
Dig deeper
Read, compare, or get started
Blog
What are DORA metrics and why should you track them?
The four (now five) signals from DORA Research that measure how well a software team delivers. What each one means and how to read them.
Guide
Deployment detection
Auto-detection on main and master. Configure named rules per provider for reusable workflows, parent-child pipelines, or non-default branches.
Guide
Audit
How CI/CD Watch audits your pipelines for missing tests, missing lint, and other CI/CD hygiene gaps.
Blog
CI/CD monitoring: beyond watching pipelines go green
What estate-level CI/CD monitoring should actually surface, and where most dashboards stop short.
Blog
The true cost of CI/CD: compute, wait time, and waste
Compute is half the bill. Developer wait time is usually the bigger half. The taxonomy of CI/CD cost and where the waste lives.
Blog
Flaky tests: what they are, why they happen, how to fix them
Practical patterns for catching flaky tests early, ranking them by impact, and clearing them without halting feature work.
One view across every provider you run.
Connect what you've got in two minutes per provider. DORA, flaky tests, cost, and stability across them all.