Skip to main content

comparison / Checked 2026-11-02

Amazon Bedrock AgentCore Browser vs Tilion

Amazon Bedrock AgentCore Browser and Tilion compared on pricing, limits, features and measured performance, with every figure linked to the provider's documentation.

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 - 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). Tilion: Free plan: 10 concurrent sessions, 10 browser hours per month, 1 GB premium proxy egress, 30 minute longest session, hard stop at the allowance (no overage), no card. The launch post also says new accounts start with free credits worth a few hundred hours of browser time.[1][2]
  • Highest concurrency on self-serve plans: Amazon Bedrock AgentCore Browser 1000 (Consumption (pay as you go)); Tilion 250 (Team).[1][2]
  • Longest session on self-serve plans: Amazon Bedrock AgentCore Browser 8 hours (Consumption (pay as you go)); Tilion 12 hours (Team).[1][2]
  • Regions: Amazon Bedrock AgentCore Browser lists 22 regions (selectable); Tilion lists 3 regions (selectable).[3][4]

Sources: aws.amazon.com [1] ↗docs.tilion.dev [2] ↗docs.aws.amazon.com [3] ↗docs.tilion.dev [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.

ItemAmazon Bedrock AgentCore BrowserTilionNotte (publisher)
Billing unitPer 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.[1]Browser time is metered for each minute a session is alive (on credit-funded accounts 1 credit per minute, 60 credits per browser hour). The launch post states $0.03 per browser-hour. Developer and Team are card-billed against monthly browser-hour allowances with metered overage.[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 tierNo 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]Free plan: 10 concurrent sessions, 10 browser hours per month, 1 GB premium proxy egress, 30 minute longest session, hard stop at the allowance (no overage), no card. The launch post also says new accounts start with free credits worth a few hundred hours of browser time.[4]$10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required[3]
Entry paid planConsumption (pay as you go)[1]Developer[4]Developer ($20/mo)[3]
Browser-hour rate (self-serve plans)Not publishedNot published$0.01[3]
Rate as published (entry paid plan)$0.0895 per vCPU-hour (CPU); $0.00945 per GB-hour (memory)[1]metered overage; rate and monthly price not published in the pages read[4]$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 published250 hours[4]Not published
Proxy per GB (entry paid plan)Not publishedNot published$10[3]
Proxy pricingNot 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.[5]Residential, ISP and mobile exits are metered as premium egress against the plan's included GB (Free 1, Developer 2, Team 25). Past it, paid plans are invoiced per GB at graduated prices by exit type; Free is refused. The docs example response lists residential at $5.5/GB up to 5 GB, $4.5 up to 20 GB, $3.5 up to 1000 GB and $2.0 beyond; mobile $7.0/$6.17/$4.5/$3.0; datacenter $0.48 down to $0.32. Traffic through your own custom proxy does not count against the premium allowance.[2]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.[6]
CAPTCHA pricingNot publishedOn credit-funded accounts (Free and wallet-funded) a successful solve costs 20 credits and nothing is charged when there is nothing to solve. On the current Developer and Team plans CAPTCHA solves are uncapped and card billed without per-call debits.[2]Included on Free, Developer and Startup (no per-solve charge listed); Enterprise row says Targeted[3]
All plansConsumption (pay as you go) price not published[1]Free $0; Developer price not published; Team price not published; Enterprise custom[2]Free $0; Developer $20/mo; Startup $100/mo; Enterprise custom[3]

Sources: aws.amazon.com [1] ↗docs.tilion.dev [2] ↗notte.cc [3] ↗docs.tilion.dev [4] ↗docs.aws.amazon.com [5] ↗docs.notte.cc [6] ↗

Limits

ItemAmazon Bedrock AgentCore BrowserTilionNotte (publisher)
Max session duration8 hours (configurable timeout)[1]Plan dependent: Free 30 min, Developer 2 h, Team 12 h, Enterprise as agreed (unlimited). The ttl field accepts 5 to 604800 seconds subject to the plan cap.[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 timeout15 minutes (900 seconds)[4]Ephemeral sessions default to ttl 3600 seconds, lowered to the plan cap (1800 on Free)[5]15 minutes (max_duration_minutes default)[6]
Idle timeoutNot publishedidle_timeout defaults to 300 seconds; configurable from 1 to 3600 seconds[5]Default 3 minutes, configurable from 1 to 30 minutes; each operation resets it[6]
Max concurrency1000 concurrent active sessions per account by default, adjustable via support ticket[7]Per plan, counted across the whole account: Free 10, Developer 25, Team 250, Enterprise 250 and up[2]Browsers: 5 Free, 25 Developer, 100 Startup, Custom Enterprise. Agents and functions: 5, 25, 100, Custom.[3]
Highest concurrency on self-serve plans1000 (Consumption (pay as you go))[8]250 (Team)[2]100 (Startup)[3]
Session creation rate limitStartBrowserSession: 30 transactions per second per account, adjustable. CreateBrowser: 5 TPS.[7]A per-API-key creates-per-minute throttle (rate_limits.session_creates_per_minute in GET /v1/usage); an example Team response shows 60. Per-plan values are not published in the pages read.[2]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]
Regionsus-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)[10]us, de, sg (selectable)[5]Not published
Data retention (entry paid plan)30 days[8]7 days[2]Not published

Sources: docs.aws.amazon.com [1] ↗docs.tilion.dev [2] ↗notte.cc [3] ↗docs.aws.amazon.com [4] ↗docs.tilion.dev [5] ↗docs.notte.cc [6] ↗docs.aws.amazon.com [7] ↗aws.amazon.com [8] ↗docs.notte.cc [9] ↗docs.aws.amazon.com [10] ↗

Features

FeatureGroupAmazon Bedrock AgentCore BrowserTilionNotte (publisher)
Connect over CDPConnectYes[1]Yes[2]Yes[3]
PlaywrightConnectYes[4]Yes[5]Yes[3]
PuppeteerConnectUnknownYes[2]Yes[6]
SeleniumConnectUnknownUnknownYes[7]
Persistent profilesLogin and stateYes[8]Yes[9]Yes[10]
Credential vaultLogin and stateUnknownYes[11]Yes[12]
Managed loginLogin and stateUnknownYes[13]Yes[14]
TOTP and 2FA handlingLogin and stateUnknownYes[11]Yes[15]
CAPTCHA solvingAnti-bot and networkUnknownYes[16]Yes[17]
Stealth and fingerprintingAnti-bot and networkPreview[18]Yes[19]Yes[20]
Managed proxiesAnti-bot and networkUnknownYes[21]Yes[22]
Proxy geo-targetingAnti-bot and networkUnknownYes[19]Yes[22]
Bring your own proxyAnti-bot and networkYes[23]Yes[24]Yes[22]
Live viewObserve and controlYes[25]Yes[26]Yes[27]
Embeddable live viewObserve and controlYes[28]Yes[26]Yes[29]
Human takeoverObserve and controlYes[25]Yes[26]Yes[29]
Session recordingObserve and controlYes[25]Yes[26]Yes[30]
Network logsObserve and controlYes[31]UnknownYes[32]
File downloadsFiles and extensionsUnknownYes[33]Yes[34]
File uploadsFiles and extensionsUnknownYes[33]Yes[34]
Browser extensionsFiles and extensionsYes[35]UnknownNo[36]
Serverless functionsRun code and agentsYes[37]UnknownYes[38]
SchedulingRun code and agentsUnknownUnknownYes[39]
WebhooksRun code and agentsUnknownYes[9]Yes[40]
MCP serverRun code and agentsYes[41]Yes[13]Yes[42]
Hosted agent APIRun code and agentsYes[41]Yes[43]Yes[44]
Scrape and fetch APIRun code and agentsUnknownYes[45]Yes[46]
Self-hostingDeploymentUnknownYes[47]Enterprise[44]
Region selectionDeploymentYes[48]Yes[19]Unknown
Sources (48)

docs.aws.amazon.com [1] ↗docs.tilion.dev [2] ↗docs.notte.cc [3] ↗docs.aws.amazon.com [4] ↗docs.tilion.dev [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗docs.aws.amazon.com [8] ↗docs.tilion.dev [9] ↗docs.notte.cc [10] ↗docs.tilion.dev [11] ↗docs.notte.cc [12] ↗docs.tilion.dev [13] ↗docs.notte.cc [14] ↗docs.notte.cc [15] ↗docs.tilion.dev [16] ↗docs.notte.cc [17] ↗docs.aws.amazon.com [18] ↗docs.tilion.dev [19] ↗docs.notte.cc [20] ↗docs.tilion.dev [21] ↗docs.notte.cc [22] ↗docs.aws.amazon.com [23] ↗docs.tilion.dev [24] ↗docs.aws.amazon.com [25] ↗docs.tilion.dev [26] ↗docs.notte.cc [27] ↗docs.aws.amazon.com [28] ↗docs.notte.cc [29] ↗docs.notte.cc [30] ↗docs.aws.amazon.com [31] ↗docs.notte.cc [32] ↗docs.tilion.dev [33] ↗docs.notte.cc [34] ↗docs.aws.amazon.com [35] ↗docs.notte.cc [36] ↗aws.amazon.com [37] ↗docs.notte.cc [38] ↗docs.notte.cc [39] ↗docs.notte.cc [40] ↗docs.aws.amazon.com [41] ↗docs.notte.cc [42] ↗docs.tilion.dev [43] ↗notte.cc [44] ↗docs.tilion.dev [45] ↗docs.notte.cc [46] ↗github.com [47] ↗docs.aws.amazon.com [48] ↗

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.

ProviderLifecycle medianP95Success rateActions/sTest setupRun date
Amazon Bedrock AgentCore Browser2458 ms[1]3410 ms[1]100% of 100 runs[1]1.08[2]runner us-east-1 -> browsers us-east-12026-11-02 (lifecycle), 2026-11-01 (throughput)
Tilion206 ms[1]523 ms[1]99% of 100 runs[1]4.89[2]runner us-east-1 -> browsers us-east-12026-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-22026-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 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]
python From Amazon Bedrock AgentCore Browser docs
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] ↗

Get started with Tilion

SDK languages: python, typescript. The snippet below is the official python quickstart from docs.tilion.dev, trimmed.

  • python: tilion-fortress[2]
  • python: tilion[3]
  • typescript: tilion-fortress[4]
  • typescript: tilion-mcp[5]
python From Tilion docs
import os
import uuid
import requests
from playwright.sync_api import sync_playwright

base = "https://back.tilion.dev"
headers = {"Authorization": f"Bearer {os.environ['TILION_API_KEY']}"}
response = requests.post(
    f"{base}/v1/session",
    headers={**headers, "Idempotency-Key": str(uuid.uuid4())},
    json={}, timeout=200,
)
response.raise_for_status()
session = response.json()

try:
    with sync_playwright() as p:
        browser = p.chromium.connect_over_cdp(session["connect_url"], timeout=60000)
        try:
            context = browser.contexts[0]
            page = context.pages[0] if context.pages else context.new_page()
            page.goto("https://example.com/", wait_until="domcontentloaded")
            print(page.title())
        finally:
            browser.close()
finally:
    response = requests.delete(
        f"{base}/v1/session/{session['session_id']}", headers=headers, timeout=30
    )
    response.raise_for_status()

Sources: docs.tilion.dev [1] ↗pypi.org [2] ↗pypi.org [3] ↗npmjs.com [4] ↗npmjs.com [5] ↗

Keep comparing

Put the workflow to the test.

Try Notte Read the quickstart ↗