The three-way buying decision
This shortlist starts with Browserless and Lightpanda, then includes Notte as a third implementation path for bursty browser workers. A queue receives more browser jobs than the account can run at once. Workers must wait for capacity and recover slots after failed jobs.
Browser slots and session creation rate constrain the burst independently. Queue work before allocating a browser, and apply bounded retries to avoid a synchronized retry wave.
A proposed acceptance case
A queue receives more browser jobs than the account can run at once. Workers must wait for capacity and recover slots after failed jobs.
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 fixed burst of jobs, the account's documented concurrency entitlement and a bounded application queue. |
| Pass condition | The queue drains without exceeding the entitlement; every allocated browser is associated with one job and eventually released. |
| Negative case | Fail a job after browser allocation. Verify that the next queued job can acquire the recovered slot and that retries do not create untracked sessions. |
| Evidence to retain | Queue arrival and start times, allocated sessions, completion counts and recovered capacity. |
Documented mechanisms, side by side
These labels describe product mechanisms. The linked source and the acceptance case determine whether a mechanism meets this workflow's requirement.
| Requirement | Browserless | Lightpanda | Notte |
|---|---|---|---|
| Browser control | Documented | Compatibility-dependent | Documented |
| Saved browser state | Authenticated Profiles | Not established | Documented |
| Live view | Documented | Check engine support | Documented |
| Deployment choice | Documented | Engine available | Enterprise options |
Sources: docs.browserless.io [1] ↗docs.browserless.io [2] ↗docs.browserless.io [3] ↗docs.browserless.io [4] ↗lightpanda.io [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗docs.notte.cc [8] ↗docs.notte.cc [9] ↗
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.
Lightpanda: Use Lightpanda Cloud's limits and billing documentation for hosted capacity. Self-operated engine instances have a different capacity model and should not inherit cloud account assumptions.
Notte: The public plans list 5, 25 and 100 concurrent browser sessions, with custom limits on Enterprise. Session duration and concurrent capacity are separate plan limits; a larger technical API limit does not override the plan.
Sources: docs.browserless.io [1] ↗lightpanda.io [2] ↗notte.cc [3] ↗
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.
Lightpanda: Lightpanda Cloud supplies browser access for automation. Connect using the documented cloud path and evaluate compatibility with the control library and site behavior needed by the workflow.
Notte: Create an owned browser session, connect Playwright or Puppeteer over CDP, and stop the session when the work finishes. Browser lifecycle management remains necessary even when the control socket disconnects.
Sources: docs.browserless.io [1] ↗lightpanda.io [2] ↗docs.notte.cc [3] ↗
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.
Lightpanda: Compare hosted Lightpanda access with operating the engine yourself. The engine's supported APIs and website compatibility remain relevant in either deployment.
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.
Sources: docs.browserless.io [1] ↗lightpanda.io [2] ↗docs.notte.cc [3] ↗
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.
Lightpanda: Use the cloud billing unit and account limits for hosted access. A lower rate only helps if the target pages and required actions complete correctly on the selected engine.
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.
Sources: docs.browserless.io [1] ↗lightpanda.io [2] ↗notte.cc [3] ↗
What should change the choice?
Notte is a candidate when its published concurrency tiers fit the queue and the team wants browser and Python execution resources in one platform. Capacity must be checked separately from the hourly rate.
Browserless: 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.
Lightpanda: Lightpanda introduces a browser-engine decision. Keep it on the shortlist when its supported actions fit the real pages you use; a successful CDP connection or text task does not establish visual or full-browser equivalence with the proposed Notte workflow.
An existing pool or queue integration can outweigh a rate difference when it already handles the burst reliably. A single-session latency result does not establish fleet behavior for any provider.
Sources: docs.browserless.io [1] ↗docs.browserless.io [2] ↗docs.browserless.io [3] ↗docs.browserless.io [4] ↗lightpanda.io [5] ↗lightpanda.io [6] ↗notte.cc [7] ↗docs.notte.cc [8] ↗docs.notte.cc [9] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Browserless, Lightpanda and Notte: Queue arrival and start times, allocated sessions, completion counts and recovered capacity.
Remove a proposed configuration when its documented mechanism or a controlled pilot cannot meet the pass condition. Keep an undocumented feature as an unresolved question instead of inventing an equivalence. Do not select a provider solely because it appears in this shortlist.
- The queue drains without exceeding the entitlement; every allocated browser is associated with one job and eventually released.
- Fail a job after browser allocation. Verify that the next queued job can acquire the recovered slot and that retries do not create untracked sessions.
Sources: docs.browserless.io [1] ↗lightpanda.io [2] ↗notte.cc [3] ↗
Make a bounded pilot
Measure time to drain a fixed burst, total attempted starts, task success and the bill for both successful and failed work.
Use the same authorized account, input and final-state check in each configuration. Treat a missing product contract as an open question; do not turn an undocumented capability into an unsupported claim or a successful test result.
- Keep admission control in place while introducing the target provider.
- Move one queue partition and record allocation failures separately from task failures.
- Compare drained jobs, leaked slots and cost per completed job before raising concurrency.