Swami Sivasubramanian's re:Invent 2025 keynote on December 3 was the clearest sales pitch yet for treating Amazon Bedrock AgentCore as the production layer for agentic AI. Two of the headline announcements — AgentCore Identity (agents act on behalf of real users in Salesforce or Slack) and AgentCore Memory (agents learn from past episodes) — close gaps that until last week forced you to bolt together identity, memory, and observability yourself. So: should an Indian SMB now buy AgentCore or keep building agents on n8n+OpenAI, or graduate to self-hosted LangGraph? We ran a side-by-side this week on a real client workload. The answer surprised us.
TL;DR — what we'd recommend today
Bedrock AgentCore is a real buy choice for Indian SMBs IF (a) you're already on AWS for compute/storage, (b) your workload involves multiple tool integrations across SaaS apps, and (c) you need audit trails for regulatory reasons. Stay on n8n+OpenAI if your workload is mostly chat with light tool use and your monthly LLM spend is modest. Build on self-hosted LangGraph only if you need fine-grained control over the agent loop or need to run on-prem for data-residency reasons. The headline: AgentCore is now competitive on cost AND time-to-production for the right workloads.
Why Swami's keynote moved the needle
Two announcements in Caylent's keynote recap actually matter for production:
Identity lets an agent act on behalf of an authenticated user when it calls Salesforce, Slack, or any OAuth-protected SaaS. Until December 3, you wired this yourself with delegated tokens and a creative interpretation of OAuth scopes. AgentCore Identity provides a managed primitive — your agent gets a per-user token, you stop maintaining auth infrastructure.
Memory stores structured episodes (context + reasoning + actions + outcomes) and uses a reflection agent to extract patterns. The practical effect: your agent stops asking the user "what was your customer ID again?" three turns into a conversation. This is the feature most teams hand-rolled with vector stores + Postgres in 2025.
Combined with the AgentCore Policy primitive (natural-language guardrails enforced by formal verification), AWS now offers a production-grade agent stack that matches what teams were building from scratch.
The workload we benchmarked
Real client: a Pune logistics SMB (40 staff, ₹14 cr revenue) that wanted an internal agent to handle three workflows: customer dispatch queries (incoming WhatsApp/email), invoice reconciliation (matching freight bills to deliveries), and weekly leadership digest (summary of operations from 6 systems). Roughly 4,200 agent invocations per month projected.
We built the same agent on three stacks and measured cost, time-to-production, and operational overhead.
The 3 stacks compared
The cost comparison
One month of running the same workflow on each stack, December 2025.
| Cost line | Bedrock AgentCore | n8n + OpenAI | Self-hosted LangGraph |
|---|---|---|---|
| LLM inference (4,200 calls) | Lowest | Highest | Low |
| Compute / orchestration | Highest (Lambda) | Lowest (Hetzner) | Low (EC2) |
| Memory / vector store | Higher (AgentCore) | Lower (Postgres) | Lower (Postgres) |
| Identity / OAuth management | Paid (managed) | None (DIY) | None (DIY) |
| Observability | Highest (CloudWatch) | None (n8n logs) | Low (Langfuse) |
| Engineering ops time (4 wks) | Low | Medium | High |
| Total monthly | Lowest | Higher | Higher |
Two surprises. First, Bedrock AgentCore was actually CHEAPER than the n8n+OpenAI default — the ops-time savings more than offset the higher compute charges. Second, self-hosted LangGraph was the most expensive in total when you factor in engineering hours; it only wins on raw compute.
Time-to-production (the unexpected winner)
We measured how long it took our team to get a production-ready agent shipped on each stack. Same engineer, same scope, same QA bar.
AgentCore wins because Identity, Memory, and observability all come pre-wired. n8n is fast for the orchestration but slow on OAuth integration with enterprise SaaS. LangGraph gives you the most control but you build everything from scratch.
When each stack actually wins
Pick Bedrock AgentCore if...
Pick n8n + OpenAI if...
Pick self-hosted LangGraph if...
The DIY walkthrough — building a thin AgentCore agent
This is the trimmed reference we shipped to the Pune logistics client. About 80 lines of Python plus the AWS configuration.
When NOT to use Bedrock AgentCore
Three legitimate reasons to skip it.
You're not on AWS. AgentCore is AWS-native. If your stack is GCP-first, the integration tax outweighs the savings — Vertex AI Agent Builder is your equivalent.
You need real-time voice agents. AgentCore is built for tool-use and reasoning workflows; it doesn't have a streaming voice primitive. For voice AI, you still want LiveKit or Twilio + your own orchestrator.
You need on-prem deployment. AWS won't ship AgentCore as a self-hosted product. If your data can't leave your data center, build with LangGraph or BeeAI.
Pre-decision checklist
- Inventory current AI workload — call volume, tool count, OAuth complexity
- Estimate monthly LLM spend at current quality bar
- Map regulatory requirements (RBI/SEBI/IRDAI audit trail needs)
- Confirm AWS region availability (ap-south-1 preview as of Dec 2025)
- Check existing AWS spend vs threshold for committed-use discounts
- Run cost calc on YOUR workload — don't trust marketing benchmarks
- Build a 100-call shadow eval comparing two stacks before commit
- Time-to-production estimate including OAuth setup + observability
- Engineering ops capacity — how many hours/week can you afford
- Exit-strategy plan if you outgrow or under-grow the choice
Real outcome — Pune logistics client (3 weeks in)
We shipped on Bedrock AgentCore. After 3 weeks of production:
The client renewed for a 12-month commit and added two more workflow agents (HR onboarding query handling, supplier-payment status). The unit-economics math improved further with each new agent — fixed AWS costs amortized.
What the broader market reaction looks like
Not everyone is excited. The DEV community piece My Takeaways from Swami's re:Invent 2025 Keynote is positive but flags a real concern: vendor lock-in. Once your agent's identity, memory, and policy live in AWS-managed services, you're not migrating to GCP for free. The counter-view from Cloudelligent is that AgentCore's framework-agnosticism (LangGraph, AutoGen, custom — all welcome) limits the lock-in to identity and memory, not the agent logic itself.
We agree with the second view, with one caveat: if you bet on AgentCore Memory and AgentCore Identity, you'll need to rewrite both layers if you migrate off AWS. For most Indian SMBs, that's an acceptable trade. For larger orgs with multi-cloud strategy, build your own abstraction layer over the AWS primitives.
Where this fits in the work we do
Our AI automation team ships agents on all three stacks depending on client constraints. The Pune logistics build is on AgentCore. Our work for Radiant Finance uses n8n + OpenAI for the lighter-weight workflows. Our internal tooling (the code-review bot, release-notes generator) is on self-hosted LangGraph because we wanted to learn the framework deeply.
Founder Vivek Kumar writes more on the strategic view of AWS's AI play on his personal site. For the deeper engineering perspective on building agents from scratch, see our WhatsApp + OpenAI bot walkthrough from earlier this month.
Reddit threads worth following: r/aws for community sentiment on the AgentCore preview, r/LangChain for the build-vs-buy debates, and Hacker News re:Invent threads for the cloud-cost critiques.
FAQ
Is AgentCore generally available or still preview?
As of December 3, 2025, AgentCore Identity, Memory, and Policy are in preview in ap-south-1 (Mumbai). General availability expected Q1 2026. Pricing today is preview-tier; expect a small bump at GA.
Can I use Claude on AgentCore in India?
Yes. Claude Sonnet 4.5 is available via Bedrock in ap-south-1. Claude Opus 4.5 (released Nov 24) is rolling out to Bedrock regions over December — confirm in your console before assuming availability.
How does AgentCore Memory differ from a vector database?
AgentCore Memory stores structured episodes (context + reasoning + action + outcome) and runs a reflection agent nightly to extract patterns. A vector DB just stores embeddings. The reflection agent is the differentiator — it gives you "the agent learned that this customer prefers email" without you having to build the learning loop.
What's the AgentCore lock-in story?
Real but bounded. Your agent logic is portable (Bedrock supports LangGraph, AutoGen, custom frameworks). Your tool-use action groups are portable (just OpenAPI specs + Lambdas). Identity and Memory are AWS-native — migrating off them requires a rewrite of those layers. For a typical SMB, the cost of migration is ~3-5 weeks of engineering.
How does this compare to OpenAI's GPT-5 Agents?
OpenAI's agent platform has comparable orchestration features but lacks AgentCore Identity's per-user OAuth depth. For workflows that need to act on behalf of authenticated users in enterprise SaaS, AgentCore is currently more mature. For simpler single-tenant agents, OpenAI's offering is fine.
Can I run AgentCore on a hybrid (some on-prem, some cloud) setup?
No. AgentCore is fully managed. You can mix AgentCore agents with on-prem agents in the same product, but each agent runs entirely in its chosen home. Hybrid orchestration across the two requires your own glue layer.
What does AWS support look like for Indian SMBs adopting AgentCore?
Surprisingly good. AWS India has invested heavily in solutions architects for the AgentCore preview — most SMBs we've worked with this quarter got 4-6 hours of free SA time on architecture review. Worth asking your AWS account manager; they're trying to drive adoption and the SA hours are genuinely useful.
Want Help Picking the Right Agent Platform for Your Stack?
We run a 90-minute architecture review comparing Bedrock AgentCore, n8n+OpenAI, and self-hosted LangGraph for your specific workload. You walk away with a cost projection, a time-to-production estimate, and a fixed-scope quote if you want us to build the first agent. Suitable for Indian SMBs with meaningful monthly AI spend. First call is free.
Book a 90-min Architecture Review
