The three-way buying decision
This shortlist starts with Kernel and Anchor Browser, 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 | Kernel | Anchor Browser | Notte |
|---|---|---|---|
| Browser control | Documented | Documented | Documented |
| Saved browser state | Documented | Documented | Documented |
| Live view | Documented | Documented | Documented |
| Deployment choice | Check deployment offering | Check deployment offering | Enterprise options |
Sources: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗docs.anchorbrowser.io [5] ↗docs.anchorbrowser.io [6] ↗docs.anchorbrowser.io [7] ↗docs.anchorbrowser.io [8] ↗docs.notte.cc [9] ↗docs.notte.cc [10] ↗docs.notte.cc [11] ↗docs.notte.cc [12] ↗
Pricing model
Kernel: Use the plan and browser configuration in Kernel's pricing documentation. Managed networking, account allowances and app execution make a browser-hour comparison only one part of the decision.
Anchor Browser: Compare the selected browser and task offering using Anchor's current commercial terms. Include network usage and the execution path actually used; a batch API's capacity is not a price quote for that batch.
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: kernel.sh [1] ↗anchorbrowser.io [2] ↗notte.cc [3] ↗
Browser control
Kernel: Kernel exposes browser creation and control APIs. Its documentation distinguishes on-demand browsers from configured browser pools, so compare the acquisition path your application will actually use.
Anchor Browser: Anchor sessions can be controlled over CDP or REST. Its documentation separates direct browser control from natural-language tasks and versioned automation tasks.
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: kernel.sh [1] ↗docs.anchorbrowser.io [2] ↗docs.notte.cc [3] ↗
Deployment ownership
Kernel: Kernel Apps move the automation process next to the browser. Alternatively, an external process can control a browser through the browser API. Choose based on execution locality and deployment ownership.
Anchor Browser: Use a browser session from existing code or deploy a reusable Automation Task. The task path includes workflow editing and versioning; direct CDP leaves execution ownership with your application.
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: kernel.sh [1] ↗docs.anchorbrowser.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 |
|---|---|---|---|
| Kernel | $0.06 | $144.00 | 69% on 2026-10-17 |
| Anchor Browser | $0.05 | $120.00 | 100% on 2026-10-17 |
| Notte | $0.01 | $24.00 | 91% on 2026-10-18 |
Sources: browserarena.ai [1] ↗browserarena.ai [2] ↗kernel.sh [3] ↗anchorbrowser.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.
Kernel: Kernel's browser-local Apps make execution placement part of the decision. Compare the repeated action path with the proposed Notte controller or Function deployment before concluding that a lifecycle or hourly-rate difference decides the workflow.
Anchor Browser: Anchor's demonstration or prompt-authored Automation Tasks and Notte's Python Functions suit different authoring preferences. Both document website-authentication tooling, so a credible recommendation must address the actual login and workflow-editing path.
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: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗anchorbrowser.io [4] ↗docs.anchorbrowser.io [5] ↗docs.anchorbrowser.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 Kernel, Anchor Browser 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: kernel.sh [1] ↗anchorbrowser.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.