CircleCI monitoring
CircleCI monitoring beyond Insights
Workflows, DORA metrics, and flaky tests across every organisation, with credits translated to dollars on every row. The cross-project, cross-provider view Insights stops at.
Projects across 4 orgs · sorted by last workflow
Works across every major CI/CD provider
Workflows · DORA · Flaky tests
Beyond the Projects page (and Insights)
Three capabilities every CI/CD Watch tenant uses, each wired into how CircleCI reports data. Insights is solid for a single project; CI/CD Watch is the cross-project, cross-provider view with credits translated to dollars throughout.
Workflows, every org, one feed
The Projects page works for one project. Insights stops there too.
Every workflow and every job across every CircleCI organisation, in one live feed. Resource class and credit cost shown per job, translated to dollars at your plan's rate. Drill back to the CircleCI pipeline page when you need the raw logs.
- Credits-to-dollar translation built in: every run shows actual spend, not abstract units
- Resource class visible on every job: medium, xlarge, macos.medium, arm.large
- Each row links straight to app.circleci.com/pipelines/<vcs>/<org>/<project>/<num>
Outcome: one view across every CircleCI org, with cost in real dollars on every row.
What's needed: CircleCI API token. Nothing in your .circleci/config.yml changes.
Workflows across 4 orgs · live
DORA, calculated from CircleCI workflow runs
Five DORA metrics, across every project Insights can't span.
DORA metrics calculated from real workflow run data, including 2024's Rework Rate. Insights gives you DORA per project; we aggregate across the entire CircleCI estate, and across the rest of your tooling alongside. Deployments auto-detect on main and master.
- Workflow-filter rules target deploy jobs by name across every org
- Orb-emitted deploy jobs (aws-s3/sync, circleci/heroku, etc.) recognised by orb name
- Trend over 7 / 30 / 90 days, per-project or aggregated, with period-over-period regression alerts
Outcome: a DORA view Insights can't deliver, with cost attached.
What's needed: API token. Auto-detection covers the simple cases.
DORA by project · 30 days · ranked by deploy frequency
Flaky tests, surfaced via store_test_results
CircleCI already parses your test results. We surface the flakes.
If your job already runs store_test_results, the data is there. Each test gets a flip rate, failure rate, and current status so the most disruptive ones surface first across every project in your CircleCI estate.
Native CircleCI step, no extra config
- store_test_results:
path: test-results- Per-test flip rate scored across branches over a rolling 30-day window
- Failure rate and current status per test, sortable in the table
- Test splitting (parallelism: N) merged per logical test, not duplicated per shard
Outcome: fix the disruptive tests first, with real flip-rate data to triage them.
What's needed: store_test_resultsstep. CircleCI's native, nothing custom.
Flaky tests, last 30 days, sorted by flip rate
Same connect, more depth
How we work with CircleCI
Three more capabilities the same connect unlocks. None of them are CircleCI-only, but each pays off particularly well on CircleCI estates where credit accounting, resource-class drift, and orb consumption all shape the bill.
Cost
Cost-optimization opportunities ranked by potential saving
Right-sizing recommendations, redundant-step detection, and waste categorisation. Each opportunity translates the saving from credits to dollars at your plan's rate.
Audit
Audit rules catch CI/CD hygiene gaps across the estate
Built-in rules check for missing lint, no unit tests, absent SAST, secrets-in-config patterns, and more. Findings ranked by severity; each one names the project and the fix.
Strategy
Branching strategy auto-detected per project
Trunk-based, GitFlow, GitHub-flow detected from your real branch and merge patterns. DORA metrics get a per-strategy lens so trunk-based projects aren't penalised for not having long-lived release branches.
All from one connect
Plus the rest of the toolkit
The three capabilities above are what you'll use most. Same connect also gives you cost tracking, PR health, stability classification, performance ratings, security insights, Slack, CLI, and an MCP server. No extra integrations.
Cost tracking →
Credit-translated spend plus developer wait time. Waste auto-categorised by type. Team tier.
PR health →
Per-project CI failure rates, reviewer wait time, and PR-to-deploy latency. Team tier.
Stability classification →
Every pipeline auto-classified healthy, flaky, or broken. Trend detection on each.
Performance ratings →
Per-pipeline performance scoring across the estate. Spot the slow outliers.
Security insights →
Per-project security-scan detection rolled up across the estate. Business tier.
Slack notifications →
Pipeline failures, regressions, and degradation alerts in your team channel. Team tier.
CLI →
Query pipeline status, costs, and DORA from your terminal. Pipe it anywhere.
MCP server →
Hook Claude, Cursor, or any AI agent into live pipeline state.
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 projects.
- 3 projects
- 1 team member
- Workflow runs, DORA, flaky tests
- Credit-translated cost view (last 30 days)
- Email support
Team
Flat rate per tenant. Up to 20 projects and 10 team members.
- 20 projects
- 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 projects and 50 team members.
- 100 projects
- 50 team members
- Everything in Team
- Audit findings and cost-optimization opportunities
- Priority support
Comparison
How CI/CD Watch compares
A 10-person team running CircleCI across ~20 projects. Headline pricing only; deeper feature comparisons live on the linked pages.
CI/CD Watch$29 / mo flat (Team) | CircleCI InsightsIncluded in CircleCI plan | |||
|---|---|---|---|---|
| Cross-project workflow feed | Yes, with cost per row | Per-project only | Yes | Limited |
| Credit-to-dollar translation | On every spend figure | Credits only | Compute only | No |
| DORA across CircleCI + other providers | Yes, aggregated | CircleCI only | Add-on | Yes |
| Flaky test surfacing | Flip rate, failure rate | Limited | Test count | No |
| Pricing model | Flat per tenant | Bundled with CI | Per committer + spans | Per contributor |
| Setup time | ~2 min API token | Already there | Agent install per repo | OAuth + config |
Competitor pricing reflects each vendor's published headline rate. CircleCI Insights ships with the CircleCI plan; we compare on coverage not price. See the linked comparison pages for fuller feature matrices.
~2 min
to connect via API token
0
agents to install in your runners
5
DORA metrics from day one
Flat
per-tenant pricing
FAQ
CircleCI specifics
- How is this different from CircleCI Insights?
- Insights is excellent per project: queue time, throughput, success rate, test trends. It stops at the project boundary. CI/CD Watch is the cross-project (and cross-provider) lens: which projects burn the most credits, which orbs you depend on, which org is regressing on DORA, and how CircleCI fits alongside GitHub Actions or GitLab if you run a mixed estate.
- How does credit-to-dollar translation work?
- We multiply the credits each job consumes by your plan's per-credit rate, factoring in resource-class multipliers (medium = 5 credits/min, xlarge = 20 credits/min, macos.medium = 200 credits/min, and so on). Every spend figure on every page is shown in dollars so cost comparisons across resource classes don't need mental maths.
- Will it eat into our credit pack?
- No. CI/CD Watch reads from CircleCI's v2 API after pipelines complete. It does not run jobs, install runners, or consume credits. The polling is rate-limit-aware and stays under the 200 req/min v2 ceiling using conditional requests.
- How does CI/CD Watch get our pipeline data?
- Via the standard CircleCI v2 REST API using an API token you generate at connect time (read-only on pipelines, workflows, jobs, and project metadata). No webhooks, no app install, no runners modified.
- Does it support orb-emitted deploys?
- Yes. Deployments that fire through orbs (aws-s3/sync, circleci/heroku, slack/notify-deploy, custom org orbs) are auto-detected by orb name and command. The deployment-classification model handles the indirection so DORA counts the logical deploy once, not the orb invocation N times.
- How long does setup take?
- Around two minutes. Create a personal API token in CircleCI, paste it into CI/CD Watch, pick which projects to include. The first workflow feed populates within minutes.
- Is pricing tied to credits or seats?
- Neither. CI/CD Watch is flat per tenant: $0 Free, $29 Team, $99 Business per month. Project and team-member caps differ per tier; consumption inside those caps is unmetered.
- Can we get DORA across CircleCI and GitHub Actions or Jenkins?
- Yes. Connect each provider separately; DORA metrics include runs from every connection. Useful for mixed estates mid-migration.
- Server (self-hosted) or Cloud only?
- Cloud only today. CircleCI Server connections sit behind your firewall and require additional networking config that's not yet in scope. If you're running Server, get in touch.
More on CI/CD monitoring
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 for orb-emitted deploys 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
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.
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
CI/CD monitoring: beyond watching pipelines go green
What estate-level CI/CD monitoring should actually surface, and where most dashboards stop short.
One view across every CircleCI org.
Connect CircleCI in two minutes. Workflows, DORA, and flaky tests across every project, with credits translated to dollars throughout.