What Browserless supplies
Browserless provides hosted browser access and self-hosted options. Its documentation separates BaaS, BrowserQL and BAP, with different ways to control sessions, preserve state and use credentials.
You need a browser service that fits existing automation libraries or a self-hosted deployment, and can select the appropriate Browserless product.
This is a source-based buying guide, not a claim of hands-on testing across every documented feature. Follow the source for the product and plan you would actually use.
Sources: docs.browserless.io ↗
Browser control
Browserless: Create a browser through the selected Browserless connection path. The product documentation distinguishes browser-library connections from BrowserQL and BAP workflows, so retain the product name in configuration and comparisons.
Sources: docs.browserless.io ↗
What survives a session
Browserless: Browserless documents authenticated profiles and reconnect flows. A retained profile and a reconnectable live browser preserve different state; choose the mechanism based on whether the running page must continue.
Sources: docs.browserless.io ↗
Website login
Browserless: BAP documents loadSecret() with a configured 1Password integration. Profiles provide another way to reuse authenticated state. Check the selected product's prerequisites before treating these as interchangeable login options.
Sources: docs.browserless.io ↗
Where the code runs
Browserless: Browserless supports several code and control surfaces. Compare the exact runtime endpoint or external runner you intend to use, including its language, deployment, versioning and invocation contract.
Sources: docs.browserless.io ↗
Deployment ownership
Browserless: Browserless has cloud and self-hosted deployment paths. Managed dedicated deployments expose some account APIs that a fully self-hosted installation does not, so document the actual deployment rather than a generic feature list.
Sources: docs.browserless.io ↗
Capacity and limits
Browserless: Account concurrency and session routing affect a Browserless deployment. Use its concurrent-session guidance, and distinguish shared cloud, managed dedicated and self-hosted capacity.
Sources: docs.browserless.io ↗
Inspecting a run
Browserless: BAP live URLs stream an active session and support human interaction. Browserless also documents video recording and session replay. Availability and connection parameters depend on the selected product.
Sources: docs.browserless.io ↗
Pricing model
Browserless: Browserless Cloud uses units. Browser time consumes one unit per 30-second increment, rounding partial increments upward; proxy traffic and other services also consume units. Included units and overage depend on the plan.
Sources: docs.browserless.io ↗
Where Notte is worth evaluating
Choose the Browserless product and deployment before drawing a conclusion from its documentation. BAP, shared browser access and a self-hosted service can have different features; Notte's session and Function resources should be compared with the specific path you would purchase.
Notte combines cloud browser sessions with deployed Python automations and website authentication tools. You can control the browser over CDP or use Notte's actions, then deploy repeated work as a Function.
Retaining Browserless can be the right outcome when its documented model already fits the application. Compare Notte only against a concrete missing capability, operating responsibility or cost constraint.
Sources: docs.browserless.io [1] ↗docs.browserless.io [2] ↗docs.notte.cc [3] ↗docs.notte.cc [4] ↗
Questions to settle before buying
The connection route and product matter. A feature documented for BAP or a managed dedicated deployment should not be assumed to exist on every shared BaaS endpoint.
Ask for the exact session, state and execution contract of the proposed account. A published browser observation does not establish feature availability, supported websites or production access.
- Which workload must pass before purchase?
- Who owns the running code, stored browser state and website connection?
- Which browser and handler limits apply to the selected plan?
- What does the invoice include beyond browser usage?
- What would have to be rebuilt to leave this provider?