Vendor cost breakdown
AWS Bedrock & Kiro cost in 2026: what teams actually pay
AWS-billed AI is usage-based, not seat-based: Amazon Bedrock charges per token across on-demand, batch, and provisioned modes, and Kiro — AWS’s agentic IDE — sells per-developer credit plans from $20 to $200 per month. Because the spend lands inside the AWS bill next to everything else, it is the AI cost teams most often can’t attribute.
Prices verified against official vendor pages on 2026-06-12. All waste figures are estimates from your own inputs.
AWS Bedrock & Kiro plans and per-seat prices
| Plan | Price / seat / month | Best for | Usage notes |
|---|---|---|---|
| Bedrock on-demand | Usage-based | Usage-based (per token) | Pay per input/output token, priced per model. Standard, Flex (discounted, higher latency), and Priority tiers. |
| Bedrock batch | Usage-based | Asynchronous bulk jobs | 50% off on-demand pricing for non-urgent workloads. |
| Bedrock provisioned / reserved | Usage-based | Guaranteed-throughput workloads | Fixed price for reserved tokens-per-minute capacity (1- or 3-month terms). |
| Kiro Free | $0 | Individuals | 50 credits/month, perpetual. |
| Kiro Pro | $20 | Developers | Credit allowance; overage at $0.04/credit when enabled. |
| Kiro Pro+ | $40 | Developers | Larger credit allowance. |
| Kiro Power | $200 | Heaviest individual usage | Pro Max ($100) sits between Pro+ and Power. |
Sources: Amazon Bedrock pricing · Amazon Bedrock service tiers · Kiro pricing
Where teams waste money on AWS Bedrock & Kiro
- Bedrock has no permanent free tier — every API call bills from the first token, and the spend hides inside the broader AWS invoice unless it is tagged and broken out.
- Provisioned or reserved throughput keeps billing whether or not traffic arrives; capacity bought for a launch and forgotten is classic AWS-AI waste.
- Batch and Flex tiers cut token costs by up to 50% for non-urgent workloads — workloads left on Standard out of inertia pay double.
- Kiro credit overages at $0.04/credit add up silently once enabled; unused credits also don’t roll over, so plan tier should match each developer’s real usage.
- Without cost-allocation tags or separate accounts, Bedrock spend can’t be attributed to teams — making it impossible to know which product or team owns the cost.
Estimate your AWS Bedrock & Kiro spend
The calculator below is prefilled with a typical AWS Bedrock & Kiro setup — for example, this one runs $500/month. Swap in your own seats and prices — nothing is saved until you create a free workspace.
Tool inputs
Seats, price, active-user estimate, and usage/API spend. Nothing is saved yet.
AWS Bedrock & Kiro cost FAQ
How is AWS Bedrock priced?
Bedrock is usage-based: you pay per input and output token at rates set per model, with no permanent free tier. On-demand is the default; batch processing costs 50% less for asynchronous jobs; Flex trades latency for a discount; Priority pays a premium for faster responses; and provisioned/reserved capacity bills a fixed price for guaranteed throughput on 1- or 3-month terms.
How much does Kiro cost per developer?
Kiro offers a perpetual free tier with 50 credits per month, then paid plans at $20 (Pro), $40 (Pro+), $100 (Pro Max), and $200 (Power) per month with increasing credit allowances. Optional overage bills $0.04 per additional credit, and unused credits do not roll over.
Why is AWS-billed AI spend hard to track?
Because it is buried in the AWS bill: Bedrock token charges, Kiro subscriptions, and other AI services appear as line items among hundreds of others, often across multiple accounts. Unless teams tag resources or use Cost Explorer filters, total AI spend on AWS stays invisible to the people deciding on seats and tools.
How should a team budget for Bedrock?
Treat it like cloud infrastructure, not a subscription: estimate monthly token volume per workload, choose batch or Flex tiers for anything non-urgent, set AWS budget alerts on the Bedrock service, and review provisioned capacity monthly. Track the resulting monthly number alongside seat-based AI subscriptions — a DevSpend AI workspace keeps both in one view.
More vendor cost breakdowns
Or track every tool in one free workspace — up to 5 subscriptions, waste number always visible.