See Claude Code on Bedrock cost by engineer and team

Per-session cost for Bedrock-routed Claude Code, without building a telemetry pipeline

Start free for up to 5 engineers. Team views come with Pro.

If your team runs Claude Code through Amazon Bedrock, the AWS bill shows model usage for the account, not which engineer or kind of work it went to. VibeCheck, Maestro AI's coding agent visibility product, captures each Claude Code session on the engineer's machine, so Bedrock-routed sessions are counted like any other and estimated cost rolls up by person, team, model and kind of work.

The Problem

Teams pick Bedrock to keep model traffic inside their AWS account and commitments. The tradeoff is visibility. Corvane Freight, a fictional logistics company, routed 60 engineers' Claude Code through one Bedrock account. Finance could see the line item grow each month. The platform team could not say which teams, repos or kinds of work were behind it without tagging credentials per person and building a metrics pipeline.

How It Cascades

Usage is attributed to the account or role, not the engineer who ran the session.

The common workaround, per-user telemetry exported into dashboards, is a project the platform team has to build and maintain.

Codex or Cursor usage elsewhere in the company never lands in the same view.

Budget conversations start from a single growing line item.

The Insight

The engineer's machine already knows everything the bill doesn't: who ran the session, in which repo, with which model, and what it was for. Capture there, and the provider route stops mattering.

The Solution

Each engineer runs one install command. A stop hook in Claude Code nudges a small background sync service and returns at once; the service uploads each finished session, retries when offline, and never makes the agent wait. It works the same whether Claude Code talks to Bedrock or to Anthropic directly. VibeCheck prices every session from its own tokens, cache included, at current published reference prices and labels the result as an estimate. Usage then breaks spend down by person, team, model, kind of work and skill, and Sessions sorts by cost.

The Outcome

Corvane's platform lead can show which teams and kinds of work drive the Bedrock line, with an estimate the finance partner can compare month to month, and no telemetry pipeline to run.

Questions

Yes. VibeCheck reads each finished Claude Code session on the engineer's machine, so sessions routed through Amazon Bedrock are captured like any other. You don't change how Claude Code connects to Bedrock, and there's no telemetry pipeline to build.

No. They're estimates at current published reference prices, labeled that way. Negotiated rates and AWS commitments aren't applied. They're built for comparing people, teams, models and kinds of work.

No. VibeCheck shows where the spend goes, by person, team, model and kind of work. It doesn't enforce limits or change what engineers can run.

See who your Bedrock Claude Code spend belongs to

Capture sessions from the laptop, whatever the provider route.

Start free for up to 5 engineers. Team views come with Pro.

After you sign up

  1. 1InstallThrough your MDM, or one command per laptop.
  2. 2SessionsEach one appears as it finishes, priced and read.
  3. 3Weekly RewindOn Pro, the Monday after an engineer’s first week.