Decide whether this move earns its cost
A controller loses its connection midway through a safe task and attempts to continue. Starting a fresh browser is not always equivalent to reconnecting to a live page.
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.
Evaluate Notte when browser ownership can be tracked independently of a transient controller socket. Confirm the supported reconnection path and distinguish it from loading a saved profile.
A provider's documented reconnect product can be decisive for a workflow that depends on a live page. Do not replace it with profile persistence without changing the task's continuation design.
Keep the result contract stable
A page with unsaved in-memory state, a stored provider session reference and a controlled controller interruption.
The application determines whether the original browser is still alive and either resumes the expected state or explicitly restarts the task.
Preserve the evidence contract across the move: Original session reference, page-state marker, connection interruption and resume-or-restart decision.
Map the workflow's resources
| Requirement | Browserless | Notte |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Authenticated Profiles | Documented |
| Live view | Documented | Documented |
| Deployment choice | Documented | Enterprise options |
Sources: docs.browserless.io [1] ↗docs.browserless.io [2] ↗docs.browserless.io [3] ↗docs.browserless.io [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗docs.notte.cc [8] ↗
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.
Notte: Profiles save cookies, local storage and session storage. Sessions start with fresh state by default. Persisting a profile writes state back when the session ends; a running session can also save its state explicitly.
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.
Notte: Vaults substitute credential placeholders in supported browser actions outside the model context. Managed Auth checks requested saved connections before automation. Personas supply an inbox and optional phone number for verification workflows.
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.
Notte: Use a remote browser from your existing process or deploy the browser automation as a Notte Function. These choices put lifecycle, scheduling and monitoring responsibilities in different places.
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.
Notte: The public usage rates are $0.01 per browser-hour, $0.05 per Function-hour and $10 per GB of managed proxy traffic. Paid plans return their price as usage credits. Price the relevant meters and plan eligibility for the workload.
Cut over one responsibility at a time
For this Browserless-to-Notte migration, keep the business assertion outside provider resource management. Source profile, connection, file and execution IDs are not valid target IDs; use a documented transfer path or establish the corresponding resource in Notte.
Retain source job history and a rollback route until the target pilot passes. A migration checklist is not evidence that saved state or runtime behavior is automatically portable.
- Inventory which steps depend on unsaved page state.
- Test the target session's documented connection path before moving continuation logic.
- Retain a restart path for ended sessions and verify that cleanup still occurs.
Sources: docs.browserless.io [1] ↗docs.notte.cc [2] ↗docs.notte.cc [3] ↗
A proposed acceptance case
This is an evaluation design, not a claim that this workflow has been executed successfully on every provider.
| Part of the test | Required observation |
|---|---|
| Controlled input | A page with unsaved in-memory state, a stored provider session reference and a controlled controller interruption. |
| Pass condition | The application determines whether the original browser is still alive and either resumes the expected state or explicitly restarts the task. |
| Negative case | Repeat the reconnect after the browser has ended. The application must not treat a new session or restored profile as the original live page. |
| Evidence to retain | Original session reference, page-state marker, connection interruption and resume-or-restart decision. |
A reason to delay or keep the source
Repeat the reconnect after the browser has ended. The application must not treat a new session or restored profile as the original live page.
Browserless: 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.
Delay cutover when the target's selected plan, required artifact path or supported website-account flow is not established. Resolve that gap before moving real jobs, even if the rate comparison favors the target.