The three-way buying decision
This shortlist starts with Kernel and Browserless, then includes Notte as a third implementation path for debugging recorded browser runs. A support engineer investigates a failed job after the browser has ended. The recording must be connected to the input, execution version and final result.
The recording mode, retention and session identifiers determine what can be reconstructed. Some artifacts become available only after the browser stops or processing finishes.
A proposed acceptance case
A support engineer investigates a failed job after the browser has ended. The recording must be connected to the input, execution version and final result.
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 harmless workflow with one deliberately failing step and recording enabled through the documented mechanism. |
| Pass condition | An investigator can find the correct run, identify the failing step and reconcile the recording with the application's terminal status. |
| Negative case | Create a run with the wrong recording configuration in a test environment. The system must expose the missing artifact rather than linking a different run as evidence. |
| Evidence to retain | Job input reference, code version, session ID, recording reference and terminal result. |
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 | Browserless | Notte |
|---|---|---|---|
| Browser control | Documented | Documented | Documented |
| Saved browser state | Documented | Authenticated Profiles | Documented |
| Live view | Documented | Documented | Documented |
| Deployment choice | Check deployment offering | Documented | Enterprise options |
Sources: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗docs.browserless.io [5] ↗docs.browserless.io [6] ↗docs.browserless.io [7] ↗docs.browserless.io [8] ↗docs.notte.cc [9] ↗docs.notte.cc [10] ↗docs.notte.cc [11] ↗docs.notte.cc [12] ↗
Inspecting a run
Kernel: Live browser URLs support an embedded view and a read-only option. Replays and browser telemetry are separate observability surfaces; app invocation logs add execution context.
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.
Notte: Live view shows an active browser and can be embedded in an application. Recordings let you review a finished session. Function runs have their own history and results, so keep the run ID alongside the browser session ID.
Sources: kernel.sh [1] ↗docs.browserless.io [2] ↗docs.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.
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.
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.browserless.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.
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.
Sources: kernel.sh [1] ↗docs.browserless.io [2] ↗docs.notte.cc [3] ↗
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.
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.
Sources: kernel.sh [1] ↗docs.browserless.io [2] ↗notte.cc [3] ↗
What should change the choice?
Notte is relevant when browser recordings and Python run history need to support the same investigation. Confirm artifact availability and retention for the selected account before relying on it for support.
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.
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.
Keep a provider whose existing replay integration already meets the team's investigation needs if the new system would lose necessary artifacts or history. A green feature label does not establish equivalent retention.
Sources: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗docs.browserless.io [5] ↗docs.browserless.io [6] ↗docs.browserless.io [7] ↗docs.browserless.io [8] ↗docs.notte.cc [9] ↗docs.notte.cc [10] ↗docs.notte.cc [11] ↗notte.cc [12] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Kernel, Browserless and Notte: Job input reference, code version, session ID, recording reference and terminal result.
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.
- An investigator can find the correct run, identify the failing step and reconcile the recording with the application's terminal status.
- Create a run with the wrong recording configuration in a test environment. The system must expose the missing artifact rather than linking a different run as evidence.
Sources: kernel.sh [1] ↗docs.browserless.io [2] ↗docs.notte.cc [3] ↗
Make a bounded pilot
Create a controlled failure, stop the browser correctly, and retrieve the expected replay, logs and application result using the stored run identifiers.
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.
- Preserve source run and replay references for historical jobs.
- Add target session and Function references to newly canaried jobs.
- Have an investigator reconstruct a controlled failure before moving the support workflow.