Skip to main content

comparison / Checked 2026-11-02

Notte vs Browserless

Notte and Browserless compared on pricing, limits, features and measured performance, with every figure linked to the provider's documentation.

Key differences

  • Browser-hour rate on self-serve plans: Notte $0.01; Browserless $0.18 (Scale) to $0.24 (Prototyping). The Pricing section shows each rate as published.[1][2]
  • Free tier - Notte: $10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required. Browserless: Free plan: 1,000 units per month, 2 concurrent browsers, 2 minute max session. Requests are rejected after the allowance is used (no overage billing on Free).[1][2]
  • Longest session on self-serve plans: Notte 5 hours (Startup); Browserless 1 hour (Scale).[1][2]
  • Serverless functions - Notte: Yes. Python scripts with a run() function, deployed as Functions that run on Notte infrastructure and can be invoked via API or scheduled. A maximum function runtime is not stated in the pages read. Browserless: Yes. POST /function runs your JavaScript (ESM, receives a Puppeteer page and optional context) per request on Browserless. The code is sent in the request body, as application/javascript or as application/json with code and context. The browser session closes automatically when execution completes.[3][4]
  • Self-hosting: Notte Enterprise; Browserless Yes.[1][5]
  • Open source: Notte lists SSPL-1.0 (Server Side Public License v1) at github.com/nottelabs/notte (The core library (local browser sessions and scraping) only; the hosted API service (stealth sessions, functions, vaults and personas) is not open source); Browserless lists SSPL-1.0 OR Browserless Commercial License (dual license) at github.com/browserless/browserless.[6][5]

Sources: notte.cc [1] ↗browserless.io [2] ↗docs.notte.cc [3] ↗docs.browserless.io [4] ↗raw.githubusercontent.com [5] ↗github.com [6] ↗

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.

ItemNotteBrowserless
Billing unitDollar-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[1]Units: 1 unit per 30 seconds of open browser session, partial 30 s increments rounded up. Proxy traffic (per MB), successful CAPTCHA solves and some APIs also draw from the same unit balance.[2]
Free tier$10 credits granted once with no expiry; 5 concurrent browsers; 15-minute sessions; no card required[1]Free plan: 1,000 units per month, 2 concurrent browsers, 2 minute max session. Requests are rejected after the allowance is used (no overage billing on Free).[3]
Entry paid planDeveloper ($20/mo)[1]Prototyping ($25/mo billed annually)[3]
Browser-hour rate (self-serve plans)$0.01[1]$0.18 (Scale) to $0.24 (Prototyping)[3]
Rate as published (entry paid plan)$20/mo including $20 credits per month; usage then $0.01 / hour of browser sessions from credits[1]$25/month billed annually ($35/month billed monthly); 20k units per month; $0.0020 per unit overages[3]
Included browser hours (entry paid plan)Not publishedNot published
Proxy per GB (entry paid plan)$10[1]Not published
Proxy pricingBuilt-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.[4]Built-in proxies are billed in units: residential 6 units per MB, datacenter 2 units per MB.[3]
CAPTCHA pricingIncluded on Free, Developer and Startup (no per-solve charge listed); Enterprise row says Targeted[1]10 units per successful CAPTCHA solve; unsuccessful attempts are not charged.[2]
All plansFree $0; Developer $20/mo; Startup $100/mo; Enterprise custom[1]Free $0; Prototyping $25/mo billed annually; Starter $140/mo billed annually; Scale $350/mo billed annually; Enterprise custom[3]

Sources: notte.cc [1] ↗docs.browserless.io [2] ↗browserless.io [3] ↗docs.notte.cc [4] ↗

Limits

ItemNotteBrowserless
Max session durationPer 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.[1]Per plan: Free 2 min, Prototyping 15 min, Starter 30 min, Scale 60 min; Enterprise custom[2]
Default session timeout15 minutes (max_duration_minutes default)[3]30 seconds (default connection timeout, raise it with the timeout parameter)[4]
Idle timeoutDefault 3 minutes, configurable from 1 to 30 minutes; each operation resets it[3]By default Browserless closes the browser process as soon as the client connection drops. After Browserless.reconnect, the server holds the browser open for a configurable timeout window. No general idle timeout for connected sessions was found.[5]
Max concurrencyBrowsers: 5 Free, 25 Developer, 100 Startup, Custom Enterprise. Agents and functions: 5, 25, 100, Custom.[1]Per plan: Free 2; Prototyping 10 annual / 5 monthly; Starter 40 / 30; Scale 100 / 80; Enterprise custom[6]
Highest concurrency on self-serve plans100 (Startup)[1]100 (Scale)[2]
Session creation rate limitRate 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.[7]Not published
RegionsNot publishedus-west (San Francisco, production-sfo), eu-uk (London, production-lon), eu-nl (Amsterdam, production-ams) (selectable)[2]
Data retention (entry paid plan)Not published7 days[2]

Sources: notte.cc [1] ↗browserless.io [2] ↗docs.notte.cc [3] ↗docs.browserless.io [4] ↗docs.browserless.io [5] ↗docs.browserless.io [6] ↗docs.notte.cc [7] ↗

Features

FeatureGroupNotteBrowserless
Connect over CDPConnectYes[1]Yes[2]
PlaywrightConnectYes[1]Yes[3]
PuppeteerConnectYes[4]Yes[3]
SeleniumConnectYes[5]No[3]
Persistent profilesLogin and stateYes[6]Yes[7]
Credential vaultLogin and stateYes[8]Yes[9]
Managed loginLogin and stateYes[10]Yes[11]
TOTP and 2FA handlingLogin and stateYes[12]Yes[11]
CAPTCHA solvingAnti-bot and networkYes[13]Yes[14]
Stealth and fingerprintingAnti-bot and networkYes[15]Yes[16]
Managed proxiesAnti-bot and networkYes[17]Yes[18]
Proxy geo-targetingAnti-bot and networkYes[17]Yes[18]
Bring your own proxyAnti-bot and networkYes[17]Yes[19]
Live viewObserve and controlYes[20]Yes[21]
Embeddable live viewObserve and controlYes[22]Yes[23]
Human takeoverObserve and controlYes[22]Yes[24]
Session recordingObserve and controlYes[25]Yes[26]
Network logsObserve and controlYes[27]Yes[26]
File downloadsFiles and extensionsYes[28]Yes[29]
File uploadsFiles and extensionsYes[28]Yes[29]
Browser extensionsFiles and extensionsNo[30]Yes[31]
Serverless functionsRun code and agentsYes[32]Yes[33]
SchedulingRun code and agentsYes[34]Unknown
WebhooksRun code and agentsYes[35]Beta[36]
MCP serverRun code and agentsYes[37]Yes[38]
Hosted agent APIRun code and agentsYes[39]Beta[36]
Scrape and fetch APIRun code and agentsYes[40]Yes[41]
Self-hostingDeploymentEnterprise[39]Yes[42]
Region selectionDeploymentUnknownYes[43]
Sources (43)

docs.notte.cc [1] ↗docs.browserless.io [2] ↗docs.browserless.io [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗docs.browserless.io [7] ↗docs.notte.cc [8] ↗docs.browserless.io [9] ↗docs.notte.cc [10] ↗docs.browserless.io [11] ↗docs.notte.cc [12] ↗docs.notte.cc [13] ↗docs.browserless.io [14] ↗docs.notte.cc [15] ↗docs.browserless.io [16] ↗docs.notte.cc [17] ↗docs.browserless.io [18] ↗browserless.io [19] ↗docs.notte.cc [20] ↗docs.browserless.io [21] ↗docs.notte.cc [22] ↗docs.browserless.io [23] ↗docs.browserless.io [24] ↗docs.notte.cc [25] ↗docs.browserless.io [26] ↗docs.notte.cc [27] ↗docs.notte.cc [28] ↗docs.browserless.io [29] ↗docs.notte.cc [30] ↗docs.browserless.io [31] ↗docs.notte.cc [32] ↗docs.browserless.io [33] ↗docs.notte.cc [34] ↗docs.notte.cc [35] ↗docs.browserless.io [36] ↗docs.notte.cc [37] ↗docs.browserless.io [38] ↗notte.cc [39] ↗docs.notte.cc [40] ↗docs.browserless.io [41] ↗raw.githubusercontent.com [42] ↗docs.browserless.io [43] ↗

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
Notte317 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)
BrowserlessAll 100 runs failed at the connect_over_cdp stage: browserType.connectOverCDP: WebSocket error: [redacted websocket url] 401 Unauthorized[1]Not measured0% of 100 runs[1]Not measuredrunner us-west-1 -> browsers us-west2026-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 Notte

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

  • python: notte-sdk[2]
  • typescript: notte-sdk[3]
  • python: notte (open-source core: local sessions and scraping)[4]
python From Notte docs
import os

from notte_sdk import NotteClient
from playwright.sync_api import sync_playwright

client = NotteClient()

with client.Session(idle_timeout_minutes=2) as session:
    cdp_url = session.cdp_url()

    with sync_playwright() as p:
        browser = p.chromium.connect_over_cdp(cdp_url)
        try:
            page = browser.contexts[0].pages[0]
            page.goto("https://www.google.com")
            page.screenshot(path=os.environ.get("NOTTE_SCREENSHOT_PATH", "screenshot.png"))
        finally:
            browser.close()

Sources: docs.notte.cc [1] ↗pypi.org [2] ↗npmjs.com [3] ↗pypi.org [4] ↗

Get started with Browserless

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

  • typescript: @browserless.io/bap-ts[2]
  • typescript: @browserless.io/cli[3]
  • python: bap-py (documented, not yet published to PyPI)[4]
python From Browserless docs
from playwright.sync_api import sync_playwright

TOKEN = "YOUR_API_TOKEN_HERE"  # Replace with your actual token

def get_page_title():
    with sync_playwright() as p:
        # Connect to Browserless using CDP (recommended method)
        browser = p.chromium.connect_over_cdp(
            f"wss://production-sfo.browserless.io?token={TOKEN}"
        )

        context = browser.new_context()
        page = context.new_page()

        # Navigate to the target website
        page.goto("https://www.example.com/")

        # Get the page title
        title = page.title()
        print(f"The page's title is: {title}")

        # Clean up resources
        browser.close()

if __name__ == "__main__":
    get_page_title()

Sources: docs.browserless.io [1] ↗npmjs.com [2] ↗npmjs.com [3] ↗docs.browserless.io [4] ↗

Keep comparing

Put the workflow to the test.

Try Notte Read the quickstart ↗