For engineering leaders

Your velocity tools count commits.
We read the code.

NRD Insight uses AI to review every pull request your team merges — grading real engineering craft across 12 dimensions, tying it to business impact, and turning what it finds into growth plans for every developer. Every score backed by a quote from the actual diff.

14 days free · up to 5 repos · nothing analyzed until you say so.
Your code never leaves AWS and is never used to train models.

Why teams switch

Velocity dashboards tell you how fast the wheels spin. Not whether the car is any good.

Velocity & DORA tools

  • Cycle time, deploy frequency, PR throughput
  • Treat a brilliant refactor and a copy-paste hack the same
  • Can't tell you who your strongest engineers actually are
  • Coaching advice: "merge smaller PRs"

NRD Insight

  • Reads every diff — grades correctness, security, testing, API design and 8 more
  • Every score cites the exact lines of code as evidence
  • Skill inventory and growth trend per developer, per team
  • Coaching advice: a training program built from that engineer's own PRs
How it works

Connected in minutes. Insight by tomorrow morning.

STEP 1

Connect GitHub — read-only

Install our GitHub App and pick exactly which repos to analyze. Nothing is analyzed until you enable it, repo by repo. Revoke access anytime with one click. Optionally connect Linear to tie code to the roadmap.

STEP 2

AI reviews every meaningful change

Each night, every merged PR and commit is graded against a fixed 12-dimension rubric and 24 engineering principles — inside AWS, with the evidence for every score preserved and auditable.

STEP 3

See people, not just pipelines

Dashboards for every developer, team, and repo: strengths, gaps, trajectory, business impact. Plus interactive training programs generated from your team's own code.

What we measure

Twelve dimensions of engineering craft. Zero vibes.

The rubric is fixed, versioned, and public to your team — the same bar for everyone. Trivial changes (lockfiles, typos) are filtered out before they cost you anything.

CorrectnessDoes it actually work, including the edges
TestingCoverage where it counts, not vanity %
SecurityInjection, authz, secrets, unsafe patterns
Error handlingFailures contained, propagated, logged
MaintainabilityWill the next person thank or curse them
ReadabilityNames, structure, intent on the page
PerformanceHot paths, N+1s, needless allocation
API designContracts a consumer can trust
Idiomatic masteryFluency in the language & framework
DocumentationThe why, written down where it lives
Scope disciplineOne change, done well, nothing smuggled
Review responsivenessHow feedback lands and gets absorbed
+ 24 principles checked on every PRSOLIDDRYKISSYAGNILaw of DemeterFail fastImmutabilityLow couplingTwelve-factorNo magic values…and 14 more
Business impact

Great code that ships the wrong thing is still the wrong thing.

Connect Linear and NRD Insight links every PR to the issue it served — even when nobody remembered to tag it.

  • Delivery alignment: AI judges whether the PR actually fulfilled what the ticket asked for.
  • Impact scoring: work on critical, high-priority projects counts for more than drive-by chores.
  • The full picture per developer: quality × impact × volume — so quiet force-multipliers finally show up.
Grow your people

Feedback with receipts. Training from their own code.

Every weakness the analysis finds becomes a concrete, personalized training program — with exercises generated from that developer's actual pull requests, runnable in a sandboxed editor.

  • 1:1s and reviews write themselves: evidence-linked strengths, gaps, and trendlines.
  • Growth events: see the moment a skill turns the corner — and celebrate it with badges.
  • No gaming it: we never rank on lines of code. Quality and significance, only.
Security & trust

Built like we expect your code to be built.

We ask for a lot of trust — read access to your code. Here is exactly how we honor it.

Your code never leaves AWS

Analysis runs on Amazon Bedrock inside our AWS environment. Diffs are stored encrypted (KMS) in S3, transit is TLS everywhere, and your code is never used to train any model.

Read-only, revocable, minimal

The GitHub App requests read-only access to contents, pull requests, and metadata — nothing else. You choose the repos. Uninstall revokes everything instantly.

Hard tenant isolation

Every row of your data is isolated with Postgres row-level security enforced at the database layer — not just application filters. Your data is invisible to any other customer, by construction.

Auditable, not oracular

Every score traces to a stored model response and a quoted diff. When a number surprises you, click through to the exact evidence — no black boxes.

Certified foundations

Runs entirely on AWS infrastructure holding SOC 2, ISO 27001, and PCI DSS attestations. Payments are handled by Stripe — card data never touches our servers.

You stay in control

Hard monthly AI-spend caps you configure. Export or delete your data on request. A DPA is available for teams that need one.

Pricing

Priced per analyzed developer. Dashboards free for everyone.

A seat is a developer whose code we analyzed that month — viewers, managers, and stakeholders are always free. Every plan includes AI-analysis credits; heavy months can opt in to overage at $0.05/credit, and you can cap spend so an invoice never surprises you.

Starter

$99/mo
+ $19 per analyzed developer
  • Unlimited repos & viewers
  • 500 + 250/dev AI credits included
  • All 12 dimensions + principles
  • Linear business-impact linking
  • Training programs
Start free

Scale

$999/mo
+ $13 per analyzed developer
  • Everything in Team
  • 6,000 + 250/dev AI credits included
  • Best per-developer economics
  • DPA & security review support
  • Onboarding assistance
Start free
Every plan starts with 14 days free: up to 5 repos and 10 developers analyzed, card required, cancel in one click. Nothing is analyzed until you explicitly enable a repo.
Questions leaders ask us

The straight answers.

Is our code used to train AI models?

No. Never. Analysis runs on Amazon Bedrock inside AWS, whose terms prohibit using your inputs to train models. Diffs are processed to produce your scores, stored encrypted for your own audit trail, and used for nothing else.

Will my engineers hate this?

The fastest way to make engineers hate measurement is to measure motion — commit counts, LOC. We deliberately never rank on volume. Engineers get the same evidence leaders see, their own growth view, and training built from their own code. The rubric is fixed and visible: the same bar for everyone, with receipts.

What exactly can you access?

Read-only: repository contents, pull requests, and metadata on only the repositories you enable. No write access of any kind. Uninstalling the GitHub App severs access immediately.

What counts as a paid seat?

Only a developer whose code we analyzed in that billing month. Everyone who just views dashboards is free, and your invoice lists exactly which developers were counted.

Which languages do you support?

All of them. The rubric measures engineering judgment — correctness, testing, error handling, design — which the AI evaluates in any language or framework, informed by each repo's own conventions.

How do you keep AI costs from running away?

Trivial changes are filtered before any AI runs, every plan includes a generous credit allowance, and when it's exhausted analysis pauses (cheap git metrics keep flowing) until you opt in to overage or your period renews. You are structurally protected from surprise bills.

Ready when you are

Know your engineering org the way you wish you always had.

Start your 14-day free trial

Connected in minutes · first insights by tomorrow morning