237K+ AI events recorded on our own fleet · last 30 days AI events on our own fleet · 30d

Leadership

Understand your engineering AI rollout.

One view of adoption, policy findings and coverage, plus what the spend bought and which vendor it rests on.

Answers for the next rollout review.

Measured on enrolled machines, not surveyed. Each team agrees its own benchmark. Values shown are illustrative.

  1. Which teams are using AI coding tools?

    Share of enrolled machines with recorded AI activity, by team.

  2. What did policy find?

    Findings from the last 28 days, broken down by severity.

  3. How much of the fleet is covered?

    Machines enrolled and reporting, against the target you set.

Vendor strategy

Who does the rollout depend on?

See how much AI spend sits with one vendor, what a price change would cost and where alternatives exist. Go into the next vendor conversation with numbers.

  • Lower vendor riskKnow when you depend too much on one provider.
  • Cut spend safelyFind routine work that can move to a cheaper tier.
TraceletLeadership / Spend & ROI

Spend & ROI

Where the AI budget goes: spend, return, forecast and vendor exposure.

38Diversification71% top vendorSingle-vendor

$41.0K platform spend · 4 providers

Spend by provider

Frontier models Primary vendor$29.1K · 71%
Frontier models Second vendor$6.6K · 16%
Open-weight models Self-hosted$3.3K · 8%
Embeddings and small models Two vendors$2.0K · 5%

Leverage

Blended rate

$6.40/M

Weighted across every provider and tier in use

Tiering opportunity

$7.2K

if routine workloads moved to the standard tier

Portable spend

58%

$23.8K has an active same-tier alternative today

Price-shock scenario

Top vendor

Primary

$29.1K · 71% of spend

Spend under scenario

$48.3K

+$7.3K vs today

Exposure

71%

of spend tied to one vendor

Scenario applies the price increase to the top vendor's slice only; the rest of the mix is held constant. Illustrative, not a forecast.

ConcentrationExposureLeverageOne vendor view

Spend forecast

Where are spend and return heading?

Project spend, hours saved and net return from today's run-rate. Test headcount and pricing before the budget round.

  • No budget surprisesKnow where spend lands before the month ends.
  • Usage vs budgetSee whether adoption grows with the spend.
TraceletLeadership / Spend & ROI

Spend & ROI

Where the AI budget goes: spend, return, forecast and vendor exposure.

Projected monthly spend

$44.2K

$1.47K a day run-rate

Spend to date

$26.5K

12 days left in the cycle

Projected net ROI

$198K

1,540 hours saved, projected

Active developers

186 / 300

62% adoption

Spend forecast

solid = actual · dashed = projected run-rate
$0$10K$20K$30K$40K$50KDay 1Day 5Day 10Day 15Day 20Day 25Day 30Today · day 18$44.2K projected
$0$25K$50KDay 1Day 10Day 20Day 30
Actual, days 1–18 Projected, days 19–30 Today

Scenario planner

Move a lever and both figures move with it
Headcount
Unit price
Scenario monthly spend
$44.2K
= baseline
Scenario net ROI
$198K
= baseline

Assumes linear run-rate, current keep rate held constant, and value scaling proportionally with headcount. A planning scenario, not a commitment.

Run-rateScenariosReturnOne planning view

Fleet risk

What is the fleet exposed to?

Findings, secrets and destinations rolled into one fleet risk score, with the enforcement mode beside it.

  • Know if risk is improvingTrack exposure over time, by severity.
  • Elevated access in viewSee emergency access across the fleet.
  • Numbers you can defendReal counts, never guessed dollar figures.
TraceletLeadership / Risk & assurance

Risk & compliance

Findings, violations, compliance coverage, break-glass activity and assurance.

42Fleet scoresecurity postureAt risk

Enforcement: mixed · 3 of 8 teams in allow_all (recorded, not blocked)

Open critical

4

of 34 critical + high

High severity

23

29 medium

Secrets detected

6

across the 30d window

Unapproved destinations

9

of 138 distinct domains contacted

Weighted risk trend

30d
04080Sep 3Sep 10Sep 17Sep 24Oct 3

Findings by severity

  • Critical11
  • High23
  • Medium29
  • Low28
  • Open31
  • Resolved60

Break-glass activity

Requests18
Granted72%
Pending2

Time-boxed elevated access. The same keycards engineering approves on the governance side, rolled up for the board. Median window 30 minutes.

Prevented loss

Secrets caught6
Egress blocked12
Dangerous actions blocked5
Break-glass denied3

Counts only, deliberately no dollar figure. A fabricated "avoided breach cost" would undermine every honest number next to it.

ExposureFindingsBreak-glassOne risk view

Give AI room to work. Keep your business in control.

Tell us about your team, the tools you use, and the work you want to protect.

Let’s talk