AgentBay vs AWS Bedrock AgentCore
Choose AgentBay for browser, desktop and mobile automation agents that need Chinese-cloud or Singapore-hosted environments; choose AWS Bedrock AgentCore for teams already on AWS that need IAM- and VPC-integrated code execution for agents. AgentBay uses Cloud environment instance isolation; AWS Bedrock AgentCore uses MicroVM (Runtime) isolation.
Key differences between AgentBay and AWS Bedrock AgentCore
- Isolation: AgentBay uses Cloud environment instance; AWS Bedrock AgentCore uses MicroVM (Runtime).
- Company headquarters: Alibaba Group is based in Hangzhou, China; Amazon Web Services is based in Seattle, United States.
- Session length: 30 min default; configurable (AgentBay) versus Up to 8 h (AWS Bedrock AgentCore).
- SDKs and interfaces: Only AgentBay lists JavaScript/TypeScript, Go, Java, CLI and MCP server. Only AWS Bedrock AgentCore lists AWS SDKs and AWS CLI.
What they have in common
- Both are cloud or model provider services.
- Neither is open source.
- Both list Python.
AgentBay vs AWS Bedrock AgentCore at a glance
| Attribute | AgentBay | AWS Bedrock AgentCore |
|---|---|---|
| What it is | Alibaba Cloud's on-demand cloud sandboxes for agents, offering browser, Windows/Linux desktop, Android cloud-phone and code-space environments through one SDK. | AWS’s managed agent platform: a Code Interpreter tool for running agent-generated code and a Runtime that hosts each agent session in its own microVM. |
| Type | Cloud or model provider service | Cloud or model provider service |
| Isolation | Cloud-hosted environment instances described as sandboxed with "safe isolation"; the virtualisation technology is not named | Runtime: a dedicated microVM per user session with isolated CPU, memory and filesystem, sanitized after the session. Code Interpreter: documented as a containerized environment within AgentCore |
| Open source | No | No |
| Self-host / BYOC | No / Not documented | No / Not documented |
| SDKs | Python, JavaScript/TypeScript, Go, Java, CLI, MCP server | Python (AgentCore SDK), AWS SDKs, AWS CLI |
| Cold start (vendor claim) | Not documented | No numeric claim; Runtime v2 restores from snapshots for consistent cold starts |
| Max session | Lifecycle policy per session: idle release timeout default 5 minutes (backend minimum 3), maximum runtime default 30 minutes from creation, or manual release only; keep_alive() resets the idle timer | Code Interpreter: 15 min default, up to 8 hours. Runtime microVMs: up to 8 hours, stop after 15 min idle |
| Persistence | Sessions are temporary and lose data when released; Contexts (AgentBay-managed OSS directories) persist across sessions via Context Sync at start/end or Context Mount (beta, aio-ubuntu-2404 image only); pause/resume is currently in whitelist-only access | State persists between executions within a session; Runtime can persist filesystem across stop/resume (managed session storage in preview). Large files via S3 |
| Snapshots / pause | Not documented / Not documented | Not documented / Not documented |
| GPU | Not documented | Not documented for Code Interpreter or Runtime microVMs; the separate Runtime “Instances” compute type is described for agents that need GPUs |
| Networking | Basic bandwidth of 10 Mbps on all plans; premium bandwidth on Pro and Ultra billed at $0.123 per GB inbound | Code Interpreter network modes: Sandbox (isolated) or Public; VPC connectivity supported |
| Pricing | Plans plus pay-as-you-go: Basic free, Pro $149/month, Ultra $225/month (+$1.5 per extra concurrent session per month); CPU $0.027 per core-hour, memory $0.0113 per GB-hour billed per second, storage overage $0.000045 per GiB-hour; built-in agents metered in Credits at $0.0267 each | Code Interpreter: $0.0895 per vCPU-hour + $0.00945 per GB-hour, billed per second; CPU billed on actual consumption (not during I/O wait), memory on peak |
| Free tier | Basic plan: free, 10 concurrent sessions, 100 GiB storage, system images only; one-time trial voucher of 100 points for compute | No product-specific free tier is listed; general AWS new-customer credits apply |
| Compliance | Not documented | HIPAA eligible and pursuing FedRAMP per the AWS FAQ; AWS reports an internal assessment against programmes including ISO, PCI and SOC, with third-party audits in upcoming cycles |
| Regions | Deployed in Singapore (international site); a separate China site exists | 15 AWS Regions across North America, South America, Europe and Asia Pacific |
| Company headquarters | Hangzhou, Zhejiang, China | Seattle, Washington, United States |
| Good fit for | Browser, desktop and mobile automation agents that need Chinese-cloud or Singapore-hosted environments | Teams already on AWS that need IAM- and VPC-integrated code execution for agents |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose AgentBay
- You need browser, Windows/Linux desktop and Android environments from a single provider and SDK
- You run on Alibaba Cloud or need a Singapore-hosted sandbox
- You want a free plan with 10 concurrent sessions to prototype on
- You want Playwright or Puppeteer scripts to drive the hosted browser unchanged
Reasons to choose AWS Bedrock AgentCore
- You are already on AWS and want IAM, VPC and CloudTrail integration
- You need long-running sessions (up to 8 hours)
- You want consumption-based CPU billing that skips I/O wait
Trade-offs to check first
- AgentBay: Isolation technology is not documented
- AgentBay: Sessions default to a 30-minute maximum and lose all data on release unless Contexts are configured
- AWS Bedrock AgentCore: AWS-only; no self-hosting or other clouds
- AWS Bedrock AgentCore: Code Interpreter isolation is documented only as “containerized”
Both are worth piloting with your own image and region. See the full AgentBay profile and AWS Bedrock AgentCore profile, or the complete comparison.
More comparisons
Frequently asked questions
Is AgentBay or AWS Bedrock AgentCore better for AI agents?
What is the difference between AgentBay and AWS Bedrock AgentCore?
Which is open source, AgentBay or AWS Bedrock AgentCore?
How do AgentBay and AWS Bedrock AgentCore isolate code?
How does AgentBay pricing compare with AWS Bedrock AgentCore?
Can you self-host AgentBay or AWS Bedrock AgentCore?
How long can sessions run on AgentBay and AWS Bedrock AgentCore?
keep_alive() resets the idle timer. AWS Bedrock AgentCore: Code Interpreter: 15 min default, up to 8 hours. Runtime microVMs: up to 8 hours, stop after 15 min idle.Sources
- alibabacloud.com/en/product/agentbay
- alibabacloud.com/help/en/agentbay/
- alibabacloud.com/help/en/agentbay/product-overview/agentbay-billing-instructions
- alibabacloud.com/help/en/agentbay/product-overview/new-user-trial-instructions
- docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-tool.html
- docs.aws.amazon.com/bedrock-agentcore/latest/devguide/code-interpreter-resource-session-management.html
- docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-how-it-works.html
- aws.amazon.com/bedrock/agentcore/pricing/
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). AgentBay vs AWS Bedrock AgentCore. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/alibaba-agentbay-vs-aws-agentcore/