Decide whether this move earns its cost
A queue receives more browser jobs than the account can run at once. Workers must wait for capacity and recover slots after failed jobs.
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.
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.
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.
Keep the result contract stable
A fixed burst of jobs, the account's documented concurrency entitlement and a bounded application queue.
The queue drains without exceeding the entitlement; every allocated browser is associated with one job and eventually released.
Preserve the evidence contract across the move: Queue arrival and start times, allocated sessions, completion counts and recovered capacity.
Map the workflow's resources
| Requirement | Kernel | Notte |
|---|---|---|
| Browser control | Documented | Documented |
| Saved browser state | Documented | Documented |
| Live view | Documented | Documented |
| Deployment choice | Check deployment offering | Enterprise options |
Sources: kernel.sh [1] ↗kernel.sh [2] ↗kernel.sh [3] ↗kernel.sh [4] ↗docs.notte.cc [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗docs.notte.cc [8] ↗
Capacity and limits
Kernel: Kernel documents concurrent browsers, browser creation rate and per-browser resources separately. Standby browsers can still consume concurrency. Pools change how browsers are acquired; they do not erase account limits.
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: kernel.sh [1] ↗notte.cc [2] ↗
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.
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.notte.cc [2] ↗
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.
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.notte.cc [2] ↗
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.
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] ↗notte.cc [2] ↗
Cut over one responsibility at a time
For this Kernel-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.
- 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.
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 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. |
A reason to delay or keep the source
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.
Kernel: Browser-local code changes the deployment model. Check app action behavior, account limits and persistent-state ownership before moving an external worker into it.
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.
Sources: kernel.sh [1] ↗notte.cc [2] ↗