kForge fits if…
- You present delivery metrics to management or to a client.
- Some of your deployments happen outside a pipeline.
- You need to demonstrate the traceability of your production releases.
kForge use case
Measuring DORA metrics from actual deployments
The delivery metrics presented to management are often rebuilt in a spreadsheet, from only part of the deployments.
The short answer
kForge calculates the four DORA metrics — deployment frequency, lead time for changes, time to restore, change failure rate — from your actual runs. It counts deployments started by a pipeline and those started from the command line.
Complete figures
A metric that saw only half the deployments would look credible while being wrong. kForge counts both paths.
- Automatic ranking by performance level
- Composable charts, from ready-made templates
- Runs and deployments tracked over time
A traceable chain
From a commit to the ticket it resolves, from the ticket to the deployment, from the deployment to the metric: the chain can be consulted without manual reconstruction.
- A commit linked to its ticket, and the ticket to its commits
- Each client’s metrics isolated from the others
Is it the right tool for you?
Limits to know
- Metrics cover the deployments known to kForge.
- Code review and merging stay on your forge.
- Pricing is still being defined.