Skip to content

AI FinOps for AWS Bedrock, OpenAI & Anthropic

Follow the money.
Every token of it.

Three providers flow in. Tokkara shows exactly which person, team and model every dollar ends up with, then tells you how to spend less.

No SDK · No proxy · No code changesSee exactly what we access →

Works with the providers you already pay

  • AWS Bedrock
  • OpenAI
  • Anthropic

The problem

The bill grows. The answer doesn't come.

Typical things we hear

The Bedrock line on the AWS bill doubled. Nobody could tell me which team did it.

Head of Platform

Finance wants AI cost per product. I have one invoice from OpenAI and three from AWS.

Finance lead

I'm fairly sure we run Opus on jobs Haiku could do. I just can't prove it.

Engineering manager

The product

One lens over every model you pay for.

One run rate across every provider

Bedrock, OpenAI and Anthropic land in one number, with the trend, the forecast and what moved it.

tokkara.emor.techSample data

Run rate

$48,210

+18.4%

Forecast

$52,900

month end

Requests

4.1M

30 days

Bedrock · 32%OpenAI · 29%Anthropic · 39%

Spend by model, down to the token

Input, output and cache tokens priced exactly, then reconciled against your AWS bill.

tokkara.emor.techSample data

Spend by model · last 30 days

claude-opus$12,402
gpt-5$9,118
claude-sonnet$7,301
nova-pro$4,204
gpt-5-mini$2,860
titan-embed$1,180
Input 61%Output 27%Cache 12%

Every dollar has an owner

Attribute cost to people, teams, API keys and projects, using the identities your providers already record. Bedrock traces each call to the IAM identity behind it.

tokkara.emor.techSample data

Top spenders · sample handles

1user_018team:search$3,880
2user_042team:support$2,910
3user_007team:growth$2,240
4user_113team:platform$1,630
5user_064team:search$1,210

Catch what shouldn't be in a prompt

Secrets and personal data flagged in Bedrock prompts during sync. Only the redacted match is kept.

tokkara.emor.techSample data

Open findings · sample

AWS access key in promptteam:platform · claude-sonnetCritical
Card number in a support promptteam:support · claude-haikuHigh
Customer email in a batch jobteam:growth · claude-sonnetMedium

Then price the fix

The Savings Engine ranks concrete changes by dollars per month and effort, and tracks what you rolled out.

tokkara.emor.techSample data

Ranked savings · sample account

-$14,930/mo

Move Sonnet 5 traffic to Sonnet 5.5Low$6,180
Stop idle prompt-cache rebuilds in coding sessionsLow$3,410
Route Claude through the global inference profileNone$2,940
Compact sessions that carry over 150k tokens of contextMedium$2,400

What a first report looks like

From a blurry invoice to a ranked list of fixes.

Illustrative sample account
Sample data
monthly AI spend analysed
$48,210
Sample data
addressable by newer models, routing and caching
31%
Sample data
projected savings
$14,930/mo
Sample data
first report after connecting
24h
Ranked savings actions for the sample account
ActionEffortSaving per month
Move Sonnet 5 traffic to Sonnet 5.5Low
$6,180
Stop idle prompt-cache rebuilds in coding sessionsLow
$3,410
Route Claude through the global inference profileNone
$2,940
Compact sessions that carry over 150k tokens of contextMedium
$2,400

Estimates use your actual usage. Validate quality on a sample before rolling out a model change.

How we estimate savings
What we use
Every Bedrock request from the last 30 days, with its exact input, output and cache tokens, priced at your current rates and projected to a month.
Newer model upgrades
The same tokens repriced at the successor model's rates. Successors are newer models in the same family, never a smaller one.
Global routing
Requests on in-region Claude inference profiles cost about 10% more than the global profile; the saving is that difference.
Idle cache rebuilds
Session turns that rewrote the prompt cache after a 5 to 60 minute pause, priced as the gap between cache-write and cache-read rates.
Long context
Cache-read tokens beyond 150k per turn: the spend you could avoid by compacting earlier.
Assumptions
Traffic stays at the same volume and mix. Opportunities worth $1 a month or less are dropped. After you mark a fix as rolled out, the saving is measured, not estimated.
See a full sample report

Savings estimate

What could you save?

Estimate only, based on the levers the Savings Engine checks: newer models, global routing, idle cache rebuilds and long context. Your real figure comes from your own usage in the first report.

Estimate

$2,000 – $6,000 a month

How it works

Connected in five minutes. Nothing in your request path.

  1. 01

    Connect

    Deploy a read-only IAM role for Bedrock and add usage admin keys for OpenAI and Anthropic. Takes about five minutes.

  2. 02

    We read your logs

    Invocation logs and usage APIs you already have. No proxy, no SDK, no code changes.

  3. 03

    Attribute the spend

    Usage is matched to people, teams, API keys and models, then priced to the cent.

  4. 04

    Act on it

    Budgets, spike alerts, security findings and ranked savings, all in one place.

Before you connect

AWS Bedrock

  • Model invocation logging turned on, delivering to an S3 bucket
  • Permission to deploy a CloudFormation stack that creates one read-only IAM role
  • Cost Explorer enabled, to reconcile against your AWS bill

OpenAI

  • An organization owner who can create an admin key

Anthropic

  • A Console admin who can create an admin key

Only need one provider? Connect just that one.See every permission

Why not a gateway?

Visibility without standing in the way.

Gateways and proxies see spend by routing every request through themselves. Tokkara reads the records your providers already keep.

How Tokkara compares with a gateway or proxy
AspectGateway or proxyTokkara
SetupSDK or base-URL change in every serviceConnect your accounts; about five minutes
Latency addedA network hop on every requestNone; logs are read after the fact
Code changesRequiredNone
If the vendor is downRequests can fail or queueYour traffic is never touched
Where prompts goThrough the vendor's serversNever routed through us; Bedrock logs are read after the fact with your permission, and only redacted findings are kept

Built for every seat

One source of truth, four ways to read it.

AI cost per team and product, every month

  • Monthly reports ready for the close
  • Budgets with 80% and 100% alerts
  • Forecasts before the invoice arrives

Capabilities

Everything between the invoice and the fix.

Cost attribution

Attribute cost to people, teams, API keys and projects, using the identities your providers already record.

Savings Engine

Ranked fixes priced in dollars per month.

Budgets & alerts

Thresholds and spikes to Slack or email.

Security findings

Secrets and personal data flagged in Bedrock prompts.

Monthly reports

Rollout tracking and proven savings.

SSO & teams

SAML/OIDC sign-in and role-based access.

Privacy controls

Choose what's stored; every admin change is audited.

Pricing

Start free. Pay when it pays for itself.

Starter

Free

for your first assessment

  • One connection per provider
  • Overview, spend and people views
  • First report and savings assessment
Start free

Enterprise

Custom

for regulated and multi-account orgs

  • Everything in Team
  • SSO, teams and audit log
  • Privacy controls
  • Priority support
Talk to us

FAQ

Questions, answered.

Do I need to change my application code?

No. Tokkara reads the logs and usage data your providers already produce. There's no SDK, proxy or gateway in the request path.

What access does Tokkara need?

A read-only IAM role for AWS Bedrock, plus admin keys for OpenAI and Anthropic. Those providers only expose usage data to admin keys; Tokkara only calls their usage and directory read endpoints. Every permission is listed on our Trust page, and you can revoke access at any time.

How is cost attributed to people for each provider?

Bedrock: to the IAM user or assumed-role session behind each call. OpenAI: to the user who owns the key, otherwise the API key or project. Anthropic: to the Console user for Console usage, otherwise the API key or workspace. Map any of these to teams.

Do you store prompts?

No prompt text by default. Prompt scanning reads Bedrock prompts during sync and keeps only redacted matches. First-prompt previews for Claude Code sessions are off by default for new organizations, and every admin change is recorded in the audit log.

Which regions are supported?

Bedrock sync reads invocation logs in whichever AWS region you enabled them. Our hosting region is available on request.

How long do you retain data?

90, 180, 365 or 730 days, or forever; you choose. Usage, sessions and findings older than that are deleted daily.

How do I revoke access?

Delete the CloudFormation stack for Bedrock and revoke the admin keys in the OpenAI and Anthropic consoles. Tokkara loses access immediately. Step-by-step instructions are on the Trust page.

What happens if a provider changes its log format?

Records we can't parse are skipped, never guessed. The provider card shows the sync error so you know, and we update the parser.

How accurate are the costs?

Tokens are priced per model, including cache reads and writes, and Bedrock totals are reconciled against your AWS bill.

Put your AI bill in focus.

No SDK, no proxy and no change to your application. First report within 24 hours of connecting.