What is Velocity Governance?

Velocity Governance is the discipline of observing whether engineering practices keep pace with development velocity. As teams adopt AI and ship faster, Concordance monitors 50 protocols across 6 SDLC phases to ensure quality, security, and compliance don't degrade.

How does Concordance help with CRA compliance?

Concordance maps 50 engineering protocols to all 21 CRA Annex I essential requirements, generating continuous audit-ready evidence from your actual engineering toolchain — GitHub, GitLab, Jira, Linear, and more. No manual documentation required.

How does Concordance help with NIS2 compliance?

Concordance maps 50 engineering protocols to all 10 NIS2 Article 21(2) essential measures, providing continuous compliance evidence from your SDLC. It covers supply chain security, incident handling, risk assessment, and secure development practices.

The Foundation Scan is completely free — scan any public GitHub repository and get engineering practice scores across 50 protocols in under 60 seconds. No sign-up required. Pro plans start at $49/month for continuous monitoring.

How is Concordance different from DORA metrics?

DORA metrics measure deployment frequency, lead time, change failure rate, and recovery time — they tell you how fast you ship. Concordance measures 50 engineering practices across 6 SDLC phases — it tells you if your processes can keep up with that speed. They're complementary: DORA measures velocity, Concordance governs it.

What does Concordance access?

Concordance reads only metadata — PR configurations, CI pipeline configs, branch protection rules, dependency manifests, and workflow signals. It never accesses source code, secrets, or credentials.

Scoring Engine Diagnostics

50/50 protocols scored · Running real engine against fixture data

Overall

4.8

Strong (4+)

49

Moderate

1

Weak (<2.5)

0

Avg Confidence

81%

Pass Rate

100%

Drifted

0

Requirements

5.0

8 stds

Design

4.8

6 stds

Development

4.9

11 stds

Testing

5.0

9 stds

Release

4.5

8 stds

Operations

4.5

8 stds

🛡 AI SENTINELNOT DETECTED

Requirementsavg 5.0

IDStandardExpActualSource

1.1Issue Tracking Linkage 5

590%

linear+scm

1.2Acceptance Criteria 5

585%

linear

1.3Ticket Description Quality 5

585%

linear

1.4Estimation Practice 5

590%

linear

1.5Backlog Health 5

585%

linear

1.6Priority Classification 5

585%

linear

1.7Sprint Discipline 5

590%

linear

1.8Requirement Traceability 5

590%

linear+scm

Designavg 4.8

IDStandardExpActualSource

2.1Design Discussion 5

580%

linear

2.2Architecture Decision Records 5

580%

linear

2.3Technical Documentation 5

580%

scm

2.4API Contract Definition 5

570%

linear

2.6Dependency Management 4

480%

scm

2.7Design Review Workflow 5

575%

linear

Developmentavg 4.9

IDStandardExpActualSource

3.11Technical Debt Management 5

585%

linear+scm

3.1Branch Protection 5

595%

scm

3.2PR Review Quality 5

585%

scm

3.3PR Size Discipline 5

585%

scm

3.4Review Turnaround 4

490%

scm

3.5Approval Rigor 5

590%

scm

3.6Code Ownership 5

590%

scm

3.7Commit Convention 5

585%

scm

3.8Linting Enforcement 5

570%

scm

3.9Secrets Management 5

565%

scm

3.10Repository Documentation 5

580%

scm

Testingavg 5.0

IDStandardExpActualSource

4.1CI Pipeline Exists 5

595%

scm

4.2CI Gating 5

590%

scm

4.3Test Coverage 5

580%

scm

4.4Test Reliability 5

580%

scm

4.5Test Categorization 5

570%

scm

4.6Security Analysis 5

575%

scm

4.7Dependency Scanning 5

575%

scm

4.8Build Reproducibility 5

570%

scm

4.9Environment Parity 5

565%

scm

Releaseavg 4.5

IDStandardExpActualSource

5.1Build Artifacts 5

575%

scm

5.2Release Cadence 5

585%

scm

5.3Lead Time 3

385%

scm

5.4Release Approval 5

565%

scm

5.5Changelog Practice 5

575%

scm

5.6Semantic Versioning 5

590%

scm

5.7Rollback Capability 4

460%

scm

5.8Feature Flagging 4

470%

scm

Operationsavg 4.5

IDStandardExpActualSource

6.1Incident Response 4

495%

scm+tracker

6.2Postmortem Practice 4

495%

scm+tracker

6.3Runbooks 5

565%

scm+tracker

6.4SLO Definition 5

565%

scm+tracker

6.5On-Call Practice 4

485%

scm+tracker

6.6Monitoring & Alerting 5

570%

scm+tracker

6.7Change Failure Tracking 4

480%

scm+tracker

6.8Operational Review 5

580%

scm+tracker

Fixture Summary

SCM Data
Repos: 2
PRs: 60
Reviews: 60
Commits: 200
Releases: 16
Issues: 60
Workflows: 8
Tracker Data
Issues: 40
Cycles: 6
Documents: 14
Estimation: fibonacci
Engine Output
Results returned: 50
Standards defined: 50
Missing: 0
Avg confidence: 81%
Overall score: 4.8

Concordance Scoring Engine · 50/50 protocols · Real engine, fixture data · v2