The three-way buying decision
This shortlist starts with Browserbase and Lightpanda, then includes Notte as a third implementation path for budgeted browser fleets. A team has a recurring browser budget and a target number of completed jobs. Plan capacity, billing rounding and failed attempts affect what the budget buys.
Choose a plan that can run the workload before calculating usage. Retry traffic, idle sessions and rounded minimum time can change the cost per completed job.
A proposed acceptance case
A team has a recurring browser budget and a target number of completed jobs. Plan capacity, billing rounding and failed attempts affect what the budget buys.
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 representative job volume, attempted session durations, concurrency requirement and network usage estimate. |
| Pass condition | The eligible configuration stays within the modeled budget while completing the required work, with each usage meter and plan credit applied once. |
| Negative case | Reprice the workload with additional failed attempts and idle time. The model must expose the higher cost instead of preserving an optimistic cost-per-success figure. |
| Evidence to retain | Attempted and completed jobs, rounded browser usage, separate meters, plan allowance and estimated invoice. |
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 | Browserbase | Lightpanda | Notte |
|---|---|---|---|
| Browser control | Documented | Compatibility-dependent | Documented |
| Saved browser state | Contexts | Not established | Documented |
| Live view | Documented | Check engine support | Documented |
| Deployment choice | Hosted service | Engine available | Enterprise options |
Sources: docs.browserbase.com [1] ↗docs.browserbase.com [2] ↗docs.browserbase.com [3] ↗docs.browserbase.com [4] ↗lightpanda.io [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗docs.notte.cc [8] ↗docs.notte.cc [9] ↗
Pricing model
Browserbase: Compare the public plan's included browser allowance and overage with the workflow's duration. Include proxy traffic and any separately priced services; an Arena browser-hour estimate does not describe the whole Browserbase bill.
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: browserbase.com [1] ↗lightpanda.io [2] ↗notte.cc [3] ↗
Browser control
Browserbase: Create a managed browser session and connect a supported browser library to its connection URL. The session API and the browser connection have separate lifecycles.
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.browserbase.com [1] ↗lightpanda.io [2] ↗docs.notte.cc [3] ↗
Deployment ownership
Browserbase: Publish TypeScript Functions through the supported deployment flow. The reviewed Function overview lists us-west-2 availability; this is narrower than assuming every browser region also hosts Functions.
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.browserbase.com [1] ↗lightpanda.io [2] ↗docs.notte.cc [3] ↗
A common browser-usage scenario
For an illustrative fleet of 10 browsers active eight hours a day over 30 days, browser usage is 2,400 hours. The table multiplies that same usage by the saved Arena rate. It excludes other providers' plan minimums, allowances and rounding, so it is not a total-invoice comparison.
Task completion below comes from the separate throughput workload. Preserve its date and failure context; a low usage rate or fast lifecycle does not establish that an authenticated business job completes. BrowserArena is maintained by Notte.
| Provider | Arena rate / browser-hour | Browser usage at 2,400 hours | Throughput task completion |
|---|---|---|---|
| Browserbase | $0.12 | $288.00 | 100% on 2026-10-17 |
| Lightpanda | $0.06 | $144.00 | 100% on 2026-10-18 |
| Notte | $0.01 | $24.00 | 91% on 2026-10-18 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗browserbase.com [3] ↗lightpanda.io [4] ↗notte.cc [5] ↗
What should change the choice?
Notte's public $0.01 browser-hour rate makes it a useful cost baseline. Apply its paid-plan minimum and any proxy, execution or identity usage before estimating the actual recurring bill.
Browserbase: Browserbase's TypeScript Function contract is a reason to retain it when that is the deployed language your team wants. A move to Notte Functions includes a Python execution decision; moving only the browser can leave your existing controller in place.
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.
Included allowances, a different billing minimum or an existing commercial commitment can make retaining another provider reasonable. Compare invoices for eligible configurations, not hourly labels alone.
Sources: browserbase.com [1] ↗docs.browserbase.com [2] ↗docs.browserbase.com [3] ↗lightpanda.io [4] ↗lightpanda.io [5] ↗notte.cc [6] ↗docs.notte.cc [7] ↗docs.notte.cc [8] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Browserbase, Lightpanda and Notte: Attempted and completed jobs, rounded browser usage, separate meters, plan allowance and estimated invoice.
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 eligible configuration stays within the modeled budget while completing the required work, with each usage meter and plan credit applied once.
- Reprice the workload with additional failed attempts and idle time. The model must expose the higher cost instead of preserving an optimistic cost-per-success figure.
Sources: browserbase.com [1] ↗lightpanda.io [2] ↗notte.cc [3] ↗
Make a bounded pilot
Price a representative week from attempted sessions and actual duration, then compare it with the plan's included credits and limits.
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.
- Capture source attempted usage and plan allowance for a representative period.
- Model the same work using the target plan, rounding rules and separate service meters.
- Canary a bounded budget before changing the full fleet's billing path.