U.S.-Based
Amazon Bedrock agents for production workflows
We design, build and run Amazon Bedrock agents in your AWS account. New agents run on AgentCore, grounded in your documents, with a person approving risky steps.
$7,000
Starting price of an agent with 1 or 2 connected systems
40
AI projects delivered since 2020
5.0
Clutch rating from 40 reviews

How a Bedrock agent runs
We approach AI and machine learning as engineering disciplines, not experiments. Our process is designed to move from clear business goals to production-ready models that deliver measurable results.
An order exception arrives
A late shipment triggers an alert in your operations queue.
The agent checks the facts
It reads the ERP, carrier API and contract terms through approved tools.
Operations approves the fix
A coordinator accepts or edits the proposed change.
The order is updated
The change is written to the ERP with a full log.
Amazon Bedrock development, in short
- Kansas City metro software and AI company that builds AI agents on Amazon Bedrock
- Bedrock agents, document search and AI workflows for mid-market AWS customers
- AI inside your own AWS account
- Builds from $4,000, model usage billed at cost through your AWS account
Agents in your AWS account.
- 01Build priceIntegrations from $4,000, agents with 1 or 2 connected systems from $7,000
- 02Model usageBilled at cost on your own AWS account
- 03Already on Bedrock Agents?AWS no longer offers Bedrock Agents to new customers. We support existing agents or move them to AgentCore
- 04You keepAgent code, prompts and infrastructure templates
What is an Amazon Bedrock agent?
An Amazon Bedrock agent uses a foundation model's reasoning, your company's APIs and your data to break a request into steps and finish a task. It runs in your own AWS account, under your access rules. AWS now offers two ways to run one: the original Bedrock Agents, which AWS calls Agents Classic, are no longer available to new customers, and for new projects AWS points to Amazon Bedrock AgentCore.
What a Bedrock agent build includes
A model chosen on your tasks
A model chosen on your real tasks, from the hundreds of models AWS offers in Bedrock.
Tools through approved connections
Your APIs, Lambda functions and MCP servers, reached through approved connections.
A knowledge base
The agent answers from your documents and shows its sources.
Guardrails and approvals
Guardrails and approval steps before the agent changes a record or replies to a customer.
Tracing and code
Tracing, evaluations and cost alerts, switched on before release. Agent code and infrastructure templates in your own repository.
An agent, not a chatbot
A chatbot answers questions. An agent also acts: it calls a tool, checks the result and moves to the next step. A person approves the steps that carry risk.
Amazon Bedrock Knowledge Bases: which type fits
A knowledge base lets a Bedrock agent answer from your own data and cite the source. AWS offers several types, and the right one depends on where your data lives. Third-party connectors, document-level permissions and AgentCore Gateway integration are available only for Managed Knowledge Bases (Amazon Bedrock user guide).
What Bedrock agents connect to
Agents reach tools through approved connections: AWS services, MCP servers and your business systems.
When a Bedrock agent pays off
A Bedrock agent pays off when a task spans several systems in or around AWS. The task should repeat hundreds of times a month and follow rules a person can explain.
Signs we see before an AWS team asks for an agent:
- Your data already sits in Amazon S3, RDS or DynamoDB, and security wants AI inside the same account.
- Staff check three systems to resolve one exception, such as a late order or a billing dispute.
- Answers exist in documents, but people search for them by hand every day.
- A Bedrock Agents Classic prototype works, but it has no evaluations, tracing or approval steps.
- Your product team wants Claude or another model on the AWS bill you already have.
When to wait
If the task is a single question and answer over documents, RAG search may be all you need. If your data is scattered or unclear, start with an AI readiness assessment.
What to prepare before the first call
The AWS account and region you plan to use and any data rules, API documentation or read access for each system the agent must reach, about 50 real past cases with the outcome a person chose for each, and one owner on your side who decides which steps need approval.
What we build with Amazon Bedrock
Five builds for AWS teams, each running in your own account under your access rules.
New agents on AgentCore
AWS points new agent projects to AgentCore. It runs agents built with LangChain, the Claude Agent SDK, Strands or your own code. For example, a claims triage agent built with LangGraph and deployed on AgentCore Runtime in your account.
Amazon Bedrock Knowledge Bases
We connect your document stores so agents answer from your files, and reviewers see the source behind each answer. For example, support staff ask about a warranty term, and the answer cites the PDF in Amazon S3 it came from.
Bedrock Agents Classic support
We keep existing Bedrock agents running, fix failing actions and plan the move to AgentCore. For example, an existing agent whose order lookup fails, fixed now and mapped to AgentCore for a planned move.
Guardrails and approvals
We configure Bedrock Guardrails, then add approval steps before an agent changes a record or replies to a customer. For example, sensitive information filters mask account numbers, and a coordinator approves every refund the agent proposes.
Claude in your AWS account
Claude models are available in Amazon Bedrock, so usage stays on your AWS bill. For example, a contract summary feature that calls Claude through Bedrock, so usage lands on your AWS bill.
What you get when the Bedrock agent ships
You get a working agent in your AWS account and everything needed to run it without us: code, prompts, tests, infrastructure templates and documentation.
Bedrock agent ROI: a worked example
A Bedrock agent pays back when the hours it saves cost more than the build and the AWS usage. This example uses assumed numbers for order exceptions, not a client result: at these numbers, the agent pays for itself in under two months, before AWS usage. AWS bills model and AgentCore usage at cost on your account. Swap in your own exception volumes with the AI ROI calculator, and estimate the model usage per exception with the LLM cost calculator. After release we track accuracy and cost per case, so you can compare the real saving with this estimate.
How Amazon Bedrock consulting works
Four steps from your AWS setup to a monitored agent in production.
We review your AWS accounts, data stores and the models available in your region. You get a build plan and a fixed price.
We build the agent on sample tasks and measure accuracy before it touches live systems. You get a tested prototype on your data.
We deploy with authenticated tool access through AgentCore Gateway and approval steps. You get a production-ready agent in your account.
We trace each step and tool call, and run evaluations as real traffic grows. You get a production release and a runbook.
AI work in production
Two AI builds from our case studies, both in production. For the first, we also set up HIPAA-compliant infrastructure on AWS.
Risks in Bedrock agent projects, and how we handle them
Each risk gets a control in code or configuration before release, not a promise in a slide.
How Amazon Bedrock keeps your data safe
AWS commitments, plus our rules
AWS states that Bedrock never stores or uses your data to train models, and that model providers have no access to your prompts or completions. We add your own access, network and logging rules on top. On our side, IAM roles give the agent only the access it needs, keys stay in your secrets manager, and every tool call is logged. For models hosted entirely in your own AWS account, see private AI. For company-wide rules on agents and other AI tools, see AI governance and compliance. Health data has its own rules. Our guide to HIPAA-compliant AI explains what changes when a Bedrock agent touches patient records.
Provider isolation
Bedrock runs each model provider's software in deployment accounts that the Bedrock team owns and the providers cannot access.
Shared responsibility
AWS protects the infrastructure, and you control your content and configuration.
Private traffic
Traffic can stay private through Amazon VPC and AWS PrivateLink, and AWS requires TLS 1.2 or later.
Audit logs
AWS CloudTrail can log API and user activity for audits.
Guardrails
Guardrails filter harmful content, block denied topics and mask sensitive information in prompts and replies.
What Amazon Bedrock costs to run each month
Billed by usage on your account
AWS bills Bedrock by usage on your own account, and you choose how: per token on demand, discounted batch, or reserved capacity. AgentCore adds consumption-based charges with no upfront commitment or minimum fee.
We set cost alerts per agent before launch, so usage never surprises finance. Our agent build price is separate from AWS usage and fixed in writing before work starts.
Source: aws.amazon.com/bedrock/pricing and the AgentCore developer guide, read November 2026. Prices change, so we estimate yours during the review.
How AWS bills it
On-demand, Standard tier: per token, with no commitment. Fits most new agents and uneven traffic
Flex and Priority tiers: per token, Flex at a discount to Standard, Priority at a premium. Fits work that can wait longer, or replies that must be fast
Batch inference: per token, 50% below on-demand for select models. Fits large jobs that don't need an instant answer
Provisioned Throughput: per model unit per hour, with no commitment or a 1-month or 6-month term. Fits steady high volume that needs reserved capacity
Prompt caching: cache reads and writes billed per token at separate rates. Fits agents that resend the same long instructions or documents

How to choose an Amazon Bedrock consulting partner
Ask any Amazon Bedrock consulting partner these questions before you sign. Good answers come in writing.
Questions to ask, and what a good answer includes
- Will you build on AgentCore or Agents Classic? AgentCore for new agents, since AWS has closed Agents Classic to new customers.
- Which model will the agent use, and why? A test of two or three models on your real cases, with accuracy and cost per task.
- How will the agent reach our systems? Gateway tools with scoped IAM permissions, and approval steps for risky actions.
- How will you measure quality before launch? A written test set and a pass mark agreed before the build.
- What will it cost to run each month? An estimate of model and AgentCore usage, billed at cost on your AWS account.
- Where will the code live? In your repository and AWS account from day one, with infrastructure templates.
- What paperwork comes first? An NDA and a certificate of insurance before the first call.
Bedrock Agents vs AgentCore: what changed for new agents
Bedrock Agents Classic let you set up an agent inside Bedrock in a few steps. AgentCore runs agents from any framework and any model in production, with separate services for runtime, tools, memory, identity and monitoring. It works with frameworks such as LangGraph, CrewAI, LlamaIndex, Strands Agents and the OpenAI Agents SDK, and its services work together or on their own.
Source: AWS, What is Amazon Bedrock AgentCore? (developer guide), read November 2026. If you already run Bedrock Agents: the AWS notice we read closes Agents Classic to new customers and lists no end date for existing agents. We keep current agents working and plan a tested move to AgentCore when it suits your roadmap.
What an Amazon Bedrock build costs
A fixed price per build, agreed before work starts. We never resell usage: AWS bills models and hosting at cost on your account. Connecting the agent to 1 or 2 more systems adds $3,000, and 3 or more add $9,000. See AI agent development cost.
Custom integration or MCP server
One system
From $4,000
AI agent, 1 or 2 connected systems
With approval steps
From $7,000
AI agent, 3 or more connected systems
Across several systems
From $13,000
Maintenance and support
After launch
From $500 a month
Project Discovery
Credited to the build
$490
Why AWS teams build agents with SoftDoes
AWS teams build agents with SoftDoes because everything we write stays in their own AWS account and repositories. We have delivered 40 AI projects, and we build on Claude in Bedrock as a Claude Partner Network member.

- 01
40 AI projects delivered
About 80% of our projects now include AI, from document automation to agents.
- 02
Vendor documents first
Our NDA and certificate of insurance reach your procurement team before the first call.
- 03
You own the code
Agent code, prompts and infrastructure templates live in your repositories and AWS account.
- 04
Claude Partner Network member
Claude models run in Amazon Bedrock, and we build on Claude as a Claude Partner Network member.
- 05
Rated 5.0 on Clutch
5.0 from 40 client reviews. Clutch named SoftDoes a Top Artificial Intelligence Company and Top Machine Learning Company in Kansas City for 2026.
- 06
Kansas City headquarters
Headquartered in Mission, KS, in the Kansas City metro. Call 800-909-2345 to reach the team.
Amazon Bedrock agents by industry
The same agent patterns, built around each industry's systems, records and rules. Each industry page covers the agent use cases and compliance rules for that field.
Healthcare
Prior authorization, intake and records work on AWS, with HIPAA controls and a person approving each filing.
Insurance
Claims intake, document checks and status updates, with a person approving every payout decision.
Financial services
Document checks, dispute research and reporting, with an audit log for every agent step.
Logistics
Shipment exceptions, carrier updates and document checks across ERP and warehouse systems.
Legal
Intake, document review and drafting, written into the case management system.
Manufacturing
Supplier questions, quality reports and maintenance lookups across plant systems.
Questions about Amazon Bedrock agents
AgentCore, models, data and cost. Can't find your answer?
What is an Amazon Bedrock agent?
It is an AI agent on Amazon Bedrock that breaks a request into steps, calls your company's APIs and uses your data to finish a task. AWS no longer offers the original Bedrock Agents to new customers and points new projects to AgentCore. We build new agents on AgentCore and support existing ones.
Is Amazon Bedrock the same as ChatGPT?
No. ChatGPT is OpenAI's chat product for people. Amazon Bedrock is an AWS platform for building generative AI applications and agents, with hundreds of foundation models from leading AI companies. You build your own apps on it, inside your AWS account. AWS states that Bedrock never stores or uses your data to train models.
What are AWS Bedrock managed agents?
AWS uses the name Amazon Bedrock Managed Agents, powered by OpenAI, for agents that combine OpenAI frontier models and the OpenAI harness with AWS infrastructure. They are one option next to AgentCore, which runs agents from any framework. We compare both on your use case, cost and data rules before we build.
What is Amazon Bedrock AgentCore vs Bedrock?
Bedrock is the platform for building generative AI applications and agents with foundation models. AgentCore is AWS's platform for running agents in production, with any framework and any model. Its Gateway controls how agents reach tools such as MCP servers, APIs and Lambda functions, and its Evaluations show where an agent went off track.
Which models can a Bedrock agent use?
Bedrock offers hundreds of foundation models from leading AI companies, including Claude models from Anthropic. AgentCore can also deploy agents with any model. Model availability varies by AWS region, so we confirm the models you need in your region during the review step, before any build work starts.
How much does an Amazon Bedrock agent cost?
Our agent builds start at $7,000 with one or two connected systems and $13,000 with three or more. Integrations start at $4,000. AWS bills model and hosting usage separately, at cost, on your account. Maintenance starts at $500 a month. Any project can start with Project Discovery: $490, credited to the build.
What does Amazon Bedrock AgentCore do?
AgentCore runs AI agents in production on AWS. AWS describes it as a platform for building, deploying and operating agents at scale with any framework and any foundation model. Its services cover the runtime, tool access through Gateway, memory, identity, policy, observability and evaluations, and you can use them together or one at a time.
What is Amazon Bedrock AgentCore Identity?
AgentCore Identity manages how agents sign in and what they may access. AWS says it works with existing identity providers, such as Amazon Cognito, Okta, Microsoft Entra ID and Auth0. You don't migrate users or rebuild sign-in flows. We use it so agents act with scoped credentials, never a shared admin account.
What is the difference between Bedrock agents and Bedrock AgentCore?
Bedrock Agents, now called Agents Classic, let you set up an agent inside Bedrock in a few steps. AWS no longer offers them to new customers. AgentCore is the platform AWS points new projects to. It runs agents built with frameworks such as LangGraph or Strands, on models in or outside Bedrock.
What are Amazon Bedrock Knowledge Bases?
They let an agent or app answer from your own data. When a question comes in, the knowledge base searches your sources and passes the relevant passages to the model, and the answer can cite them. AWS offers a managed type with connectors and document permissions, and a customer-managed type where you run the vector store.
Can we keep using our existing Bedrock agents?
The AWS notice we read closes Agents Classic to new customers and lists no end date for existing agents. We keep current agents running, fix failing steps and add monitoring. When it suits your roadmap, we move each agent to AgentCore and rerun its test set before cutover, so its behavior stays the same.
Do we have to use Claude on Bedrock?
No. Bedrock offers hundreds of models from leading AI companies. AgentCore also runs agents on models in or outside Bedrock, including OpenAI, Gemini, Llama, Mistral and Amazon Nova. We test two or three models on your real tasks and pick by accuracy, cost and speed. Claude is one strong option, not a requirement.
How do you stop a Bedrock agent from taking the wrong action?
Every tool gets the narrowest access the task needs. AgentCore Policy checks each tool call through Gateway against rules we write with you, before it runs. Steps that change a record, move money or message a customer wait for a person to approve them. Every step is traced, so reviewers can see why the agent acted.
How long does a Bedrock agent project take?
It depends on the task, the systems and your release process. We set the agent's scope, price and schedule in a written plan before the build starts. Many teams begin with Project Discovery for $490, which is credited to the build. The plan lists what we need from you, such as AWS access and past cases.
Updated · Reviewed by Orest Andrusyshyn, Founder and CEO














































