Key differences
Published by Notte, which competes with the products on this page. Every figure links to the provider's own documentation, checked on 2026-11-02.
- Free tier - Steel: Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days. Amazon Bedrock AgentCore Browser: No Browser-specific free tier is stated on the pricing page. It says new AWS customers receive up to $200 in Free Tier credits (not stated whether these apply to Browser).[1][2]
- Highest concurrency on self-serve plans: Steel 100 (Scale); Amazon Bedrock AgentCore Browser 1000 (Consumption (pay as you go)).[1][2]
- Longest session on self-serve plans: Steel 1 hour (Scale); Amazon Bedrock AgentCore Browser 8 hours (Consumption (pay as you go)).[1][2]
- Regions: Steel lists 1 region; Amazon Bedrock AgentCore Browser lists 22 regions (selectable).[3][4]
Sources: docs.steel.dev [1] ↗aws.amazon.com [2] ↗docs.steel.dev [3] ↗docs.aws.amazon.com [4] ↗
Pricing
Entry paid plan is the cheapest listed plan with a monthly price, or the first usage-only plan; Enterprise and contact-sales plans are excluded. Browser-hour rates span the lowest to highest rate across self-serve paid plans, normalized to one browser-hour.
| Item | Steel | Amazon Bedrock AgentCore Browser | Notte (publisher) |
|---|---|---|---|
| Billing unit | per browser hour, billed by the minute and rounded up[1] | Per second of consumed CPU (priced per vCPU-hour) plus peak memory (priced per GB-hour), 1-second minimum, 128 MB minimum memory; session spans microVM boot to termination. I/O wait and idle time are free if no background process runs.[2] | Dollar-denominated credits spent per hour of browser session ($0.01 per hour); the page says usage is rounded by a billing policy without stating the increment[3] |
| Free tier | Launch plan: $0 per month plus usage, with $30 in one-time free usage credits valid for 90 days[1] | No Browser-specific free tier is stated on the pricing page. It says new AWS customers receive up to $200 in Free Tier credits (not stated whether these apply to Browser).[2] | $10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required[3] |
| Entry paid plan | Scale ($250/mo)[1] | Consumption (pay as you go)[2] | Developer ($20/mo)[3] |
| Browser-hour rate (self-serve plans) | $0.08 (Scale) to $0.10 (Launch)[1] | Not published | $0.01[3] |
| Rate as published (entry paid plan) | $0.08/hour[1] | $0.0895 per vCPU-hour (CPU); $0.00945 per GB-hour (memory)[2] | $20/mo including $20 credits per month; usage then $0.01 / hour of browser sessions from credits[3] |
| Included browser hours (entry paid plan) | Not published | Not published | Not published |
| Proxy per GB (entry paid plan) | $6[1] | Not published | $10[3] |
| Proxy pricing | Steel-managed residential proxies: $10 per GB on Launch, $6 per GB on Scale, custom on Enterprise. On Launch, Steel-provided proxies require a $10 paid-balance deposit.[1] | Not applicable as a provider meter: only customer-supplied external HTTP/HTTPS proxies are supported, so proxy cost is whatever your proxy provider charges. Browser traffic is billed as network data transfer at standard EC2 rates.[4] | Built-in residential proxies $10 per GB. Custom proxies on the Startup plan $0.20 per GB, on top of what the proxy provider charges. Bandwidth is counted as request plus response bytes, rounded up to the next MB per session.[5] |
| CAPTCHA pricing | $3 per 1,000 solves on Launch, $1 per 1,000 solves on Scale, custom on Enterprise[1] | Not published | Included on Free, Developer and Startup (no per-solve charge listed); Enterprise row says Targeted[3] |
| All plans | Launch $0; Scale $250/mo; Enterprise custom[1] | Consumption (pay as you go) price not published[2] | Free $0; Developer $20/mo; Startup $100/mo; Enterprise custom[3] |
Sources: docs.steel.dev [1] ↗aws.amazon.com [2] ↗notte.cc [3] ↗docs.aws.amazon.com [4] ↗docs.notte.cc [5] ↗
Limits
| Item | Steel | Amazon Bedrock AgentCore Browser | Notte (publisher) |
|---|---|---|---|
| Max session duration | 15 minutes on Launch, 1 hour on Scale, up to 24 hours on Enterprise[1] | 8 hours (configurable timeout)[2] | Per plan: 15 min Free, 120 min Developer, 300 min Startup, custom on Enterprise. The API parameter max_duration_minutes documents a schema maximum of 1440 minutes, which exceeds the self-serve plan limits.[3] |
| Default session timeout | 5 minutes[1] | 15 minutes (900 seconds)[4] | 15 minutes (max_duration_minutes default)[5] |
| Idle timeout | Optional inactivityTimeout (milliseconds): releases the session early once it sees no CDP command or remote input for that long. Off by default; it has no effect if it is greater than or equal to timeout.[1] | Not published | Default 3 minutes, configurable from 1 to 30 minutes; each operation resets it[5] |
| Max concurrency | 10 on Launch, 100 on Scale, 1,000+ on Enterprise[6] | 1000 concurrent active sessions per account by default, adjustable via support ticket[7] | Browsers: 5 Free, 25 Developer, 100 Startup, Custom Enterprise. Agents and functions: 5, 25, 100, Custom.[3] |
| Highest concurrency on self-serve plans | 100 (Scale)[6] | 1000 (Consumption (pay as you go))[8] | 100 (Startup)[3] |
| Session creation rate limit | Not published | StartBrowserSession: 30 transactions per second per account, adjustable. CreateBrowser: 5 TPS.[7] | Rate limited per API key with a separate budget for session starts (POST /sessions/start): per minute 50 (Free), 50 (Developer), 100 (Startup); per hour 200, 200, 1,000; per day 600, 600, 10,000; Enterprise custom. Requests over the limit return 429.[9] |
| Regions | us-east[10] | us-east-1, us-east-2, us-west-1, us-west-2, eu-central-1, eu-west-1, eu-west-2, eu-south-1, eu-west-3, eu-south-2, eu-north-1, ap-southeast-5, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ap-southeast-7, ap-northeast-1, ap-northeast-2, ca-central-1, sa-east-1, us-gov-west-1 (selectable)[11] | Not published |
| Data retention (entry paid plan) | 14 days[6] | 30 days[8] | Not published |
Sources: docs.steel.dev [1] ↗docs.aws.amazon.com [2] ↗notte.cc [3] ↗docs.aws.amazon.com [4] ↗docs.notte.cc [5] ↗docs.steel.dev [6] ↗docs.aws.amazon.com [7] ↗aws.amazon.com [8] ↗docs.notte.cc [9] ↗docs.steel.dev [10] ↗docs.aws.amazon.com [11] ↗
Features
| Feature | Group | Steel | Amazon Bedrock AgentCore Browser | Notte (publisher) |
|---|---|---|---|---|
| Connect over CDP | Connect | Yes[1] | Yes[2] | Yes[3] |
| Playwright | Connect | Yes[4] | Yes[5] | Yes[3] |
| Puppeteer | Connect | Yes[6] | Unknown | Yes[7] |
| Selenium | Connect | Yes[8] | Unknown | Yes[9] |
| Persistent profiles | Login and state | Yes[10] | Yes[11] | Yes[12] |
| Credential vault | Login and state | Beta[13] | Unknown | Yes[14] |
| Managed login | Login and state | Beta[13] | Unknown | Yes[15] |
| TOTP and 2FA handling | Login and state | Beta[13] | Unknown | Yes[16] |
| CAPTCHA solving | Anti-bot and network | Yes[17] | Unknown | Yes[18] |
| Stealth and fingerprinting | Anti-bot and network | Yes[19] | Preview[20] | Yes[21] |
| Managed proxies | Anti-bot and network | Yes[22] | Unknown | Yes[23] |
| Proxy geo-targeting | Anti-bot and network | Yes[22] | Unknown | Yes[23] |
| Bring your own proxy | Anti-bot and network | Yes[22] | Yes[24] | Yes[23] |
| Live view | Observe and control | Yes[25] | Yes[26] | Yes[27] |
| Embeddable live view | Observe and control | Yes[25] | Yes[28] | Yes[29] |
| Human takeover | Observe and control | Yes[30] | Yes[26] | Yes[29] |
| Session recording | Observe and control | Yes[31] | Yes[26] | Yes[32] |
| Network logs | Observe and control | Yes[33] | Yes[34] | Yes[35] |
| File downloads | Files and extensions | Yes[36] | Unknown | Yes[37] |
| File uploads | Files and extensions | Yes[36] | Unknown | Yes[37] |
| Browser extensions | Files and extensions | Beta[38] | Yes[39] | No[40] |
| Serverless functions | Run code and agents | Unknown | Yes[41] | Yes[42] |
| Scheduling | Run code and agents | Unknown | Unknown | Yes[43] |
| Webhooks | Run code and agents | Unknown | Unknown | Yes[44] |
| MCP server | Run code and agents | Yes[45] | Yes[46] | Yes[47] |
| Hosted agent API | Run code and agents | Unknown | Yes[46] | Yes[48] |
| Scrape and fetch API | Run code and agents | Yes[49] | Unknown | Yes[50] |
| Self-hosting | Deployment | Yes[51] | Unknown | Enterprise[48] |
| Region selection | Deployment | Unknown | Yes[52] | Unknown |
Sources (52)
steel.dev [1] ↗docs.aws.amazon.com [2] ↗docs.notte.cc [3] ↗docs.steel.dev [4] ↗docs.aws.amazon.com [5] ↗docs.steel.dev [6] ↗docs.notte.cc [7] ↗docs.steel.dev [8] ↗docs.notte.cc [9] ↗docs.steel.dev [10] ↗docs.aws.amazon.com [11] ↗docs.notte.cc [12] ↗docs.steel.dev [13] ↗docs.notte.cc [14] ↗docs.notte.cc [15] ↗docs.notte.cc [16] ↗docs.steel.dev [17] ↗docs.notte.cc [18] ↗docs.steel.dev [19] ↗docs.aws.amazon.com [20] ↗docs.notte.cc [21] ↗docs.steel.dev [22] ↗docs.notte.cc [23] ↗docs.aws.amazon.com [24] ↗docs.steel.dev [25] ↗docs.aws.amazon.com [26] ↗docs.notte.cc [27] ↗docs.aws.amazon.com [28] ↗docs.notte.cc [29] ↗docs.steel.dev [30] ↗docs.steel.dev [31] ↗docs.notte.cc [32] ↗docs.steel.dev [33] ↗docs.aws.amazon.com [34] ↗docs.notte.cc [35] ↗docs.steel.dev [36] ↗docs.notte.cc [37] ↗docs.steel.dev [38] ↗docs.aws.amazon.com [39] ↗docs.notte.cc [40] ↗aws.amazon.com [41] ↗docs.notte.cc [42] ↗docs.notte.cc [43] ↗docs.notte.cc [44] ↗raw.githubusercontent.com [45] ↗docs.aws.amazon.com [46] ↗docs.notte.cc [47] ↗notte.cc [48] ↗docs.steel.dev [49] ↗docs.notte.cc [50] ↗docs.steel.dev [51] ↗docs.aws.amazon.com [52] ↗
Measured performance
BrowserArena is run by Notte, which competes with the providers it measures. Lifecycle covers creating a session, connecting, navigating and releasing it; actions per second comes from a separate throughput test. Each row is the latest run for that provider.
| Provider | Lifecycle median | P95 | Success rate | Actions/s | Test setup | Run date |
|---|---|---|---|---|---|---|
| Steel | 1192 ms[1] | 2111 ms[1] | 97% of 100 runs[1] | 3.35[2] | runner us-east-1 -> browsers us-east-1 | 2026-11-02 (lifecycle), 2026-11-01 (throughput) |
| Amazon Bedrock AgentCore Browser | 2458 ms[1] | 3410 ms[1] | 100% of 100 runs[1] | 1.08[2] | runner us-east-1 -> browsers us-east-1 | 2026-11-02 (lifecycle), 2026-11-01 (throughput) |
| Notte (for reference) | 317 ms[1] | 442 ms[1] | 100% of 100 runs[1] | 2.65[2] | runner us-west-1 -> browsers us-west-2 | 2026-11-02 (lifecycle), 2026-11-01 (throughput) |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗browserarena.ai [3] ↗browserarena.ai [4] ↗github.com [5] ↗
Get started with Steel
SDK languages: python, typescript, go, rust. The snippet below is the official python quickstart from github.com, trimmed.
import os
from playwright.sync_api import sync_playwright
from steel import Steel
STEEL_API_KEY = os.getenv('STEEL_API_KEY')
client = Steel(steel_api_key=STEEL_API_KEY)
session = None
try:
session = client.sessions.create()
playwright = sync_playwright().start()
browser = playwright.chromium.connect_over_cdp(
f"{session.websocket_url}&apiKey={STEEL_API_KEY}"
)
currentContext = browser.contexts[0]
page = currentContext.new_page()
page.goto("https://news.ycombinator.com", wait_until="networkidle")
finally:
if session:
client.sessions.release(session.id)
Sources: github.com [1] ↗pypi.org [2] ↗npmjs.com [3] ↗github.com [4] ↗github.com [5] ↗
Get started with Amazon Bedrock AgentCore Browser
SDK languages: python, typescript. The snippet below is the official python quickstart from docs.aws.amazon.com, trimmed.
- python: bedrock-agentcore[2]
- typescript: bedrock-agentcore[3]
- python: boto3 (clients bedrock-agentcore and bedrock-agentcore-control)[4]
from playwright.async_api import async_playwright, Playwright, BrowserType
from bedrock_agentcore.tools.browser_client import browser_session
import asyncio
async def run(playwright: Playwright):
# Create and maintain a browser session
with browser_session('us-west-2') as client:
# Get WebSocket URL and authentication headers
ws_url, headers = client.generate_ws_headers()
# Connect to the remote browser
chromium: BrowserType = playwright.chromium
browser = await chromium.connect_over_cdp(
ws_url,
headers=headers
)
context = browser.contexts[0]
page = context.pages[0]
try:
await page.goto("https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/what-is-bedrock-agentcore.html")
print(await page.title())
finally:
# Clean up resources
await page.close()
await browser.close()
async def main():
async with async_playwright() as playwright:
await run(playwright)
if __name__ == "__main__":
asyncio.run(main())Sources: docs.aws.amazon.com [1] ↗pypi.org [2] ↗npmjs.com [3] ↗pypi.org [4] ↗