Reference total cost of ownership
Model usage is identical on every option and is measured separately.
The workload
Agent sessions a year
That is about 274,000 sessions a day and 5.0 trillion tokens a year.
One session
Model usage
The same models on every option
Akka on your AWS calls the same models as the two AWS options, so model usage is the same on all three. It is handled separately from the platform.
Akka Optimize
Akka Optimize searches production traffic for avoidable token spend. Effective optimizations lower token use by up to 70%.
Platform costs
Choose a cost to see how it is worked out
Akka. 205 service cores and 40 platform cores on EKS at $510 a core-year. A session needs 25% of 90 CPU-seconds, sized for a peak of 2.8 times the average, plus 5 for development.
AgentCore. 100 million sessions, each billed 90 seconds on 2 vCPU at $0.0895 a vCPU-hour and 300 seconds on 4 GiB at $0.00945 a GiB-hour.
EKS. 805 cores on EKS at $510 a core-year. A session needs 90 CPU-seconds, sized for a peak of 2.8 times the average, plus 5 for development.
aws.amazon.com/bedrock/agentcore/pricing; AWS Price List, Amazon EKS
Included services
These functions run on the service cores the tier already covers.
Runtime
Agents on Amazon EKS: 805 cores
Akka: 205 service cores
Each dot is 5 cores, sized for a peak of 2.8 times the average load.
Akka runs each session as a small actor, so a session waiting on a model holds no thread. Manulife reported up to 300% more concurrency after porting agents to Akka. Fox reports 150,000 cores reduced to 22,000.
Akka compute on EKS nodes
Agent compute on EKS nodes
AgentCore, at 2.2 times the node price
People
Akka site reliability engineers run the platform around the clock, and Akka support is part of the tier.
Crossover
Akka is below Agents on Bedrock AgentCore from 25 million sessions a year, about 68,000 a day.
Akka is below Agents on Amazon EKS from 43 million sessions a year, about 118,000 a day.
The Akka fee is fixed for the year and steps up with each core pack. Drag the chart to move the volume.
Next step
Platform cost a year at 100 million sessions, before model usage.
Outside the figures
Sources
Assumptions
The agent profile and the workload mix are the Base case of the Akka cost calculator. A session's history is 200 kilobytes. Agents on EKS need the same CPU-seconds a session as agents on AgentCore. A core on EKS is one vCPU and 4 GiB at the AWS Fargate price on EKS, $510 a year. The Akka Day 2 Ops tier is $175K a year with 25 service cores, one development and one production region, and 40 platform cores on your nodes; service cores beyond those are licensed in packs of 25 and 100. 5 service cores serve development. One AgentCore Policy decision runs for each tool call. Each session's history is retrieved once. Guardrails apply content filters only. Metric data is priced as log data. Bedrock Guardrails screens 15% of tokens: the model's output and the user's input. Logs are the session history, and a session writes 1 KiB of metric data. A token is four characters. The support plan is charged on platform charges alone. A full-time engineer costs $300K a year. Prices are list prices, on demand, with one production region.
Sources, read on 21 November 2026
AgentCore Runtime, Memory, Gateway and Policy: aws.amazon.com/bedrock/agentcore/pricing. Bedrock Guardrails: aws.amazon.com/bedrock/pricing. EKS cluster fee and Fargate on EKS, us-east-1: AWS Price List, Amazon EKS. RDS for PostgreSQL Multi-AZ gp3 storage, us-east-1: AWS Price List, Amazon RDS. CloudWatch logs and X-Ray spans, us-east-1: AWS Price List, Amazon CloudWatch. Enterprise Support: aws.amazon.com/premiumsupport/pricing. Akka customer figures: akka.io/blog/go-slow-to-go-fast and akka.io/customer-stories/tubi.