The three-way buying decision
This shortlist starts with Browserless and AWS AgentCore Browser, then includes Notte as a third implementation path for webhook-triggered browser Functions. An application event causes a browser operation. Delivery can be repeated, while the browser may finish after the original HTTP caller stops waiting.
The event can be delivered more than once. An asynchronous invocation needs a run identifier and completion handling rather than an assumption that the first HTTP response contains the result.
A proposed acceptance case
An application event causes a browser operation. Delivery can be repeated, while the browser may finish after the original HTTP caller stops waiting.
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 test event with a stable application event ID and an operation whose resulting object can be counted. |
| Pass condition | The application tracks a terminal run and the intended number of website changes for that event, including after duplicate delivery. |
| Negative case | Send the same event twice and interrupt the first caller. Verify that run tracking and idempotency still describe the intended outcome. |
| Evidence to retain | Event ID, invocation acknowledgement, execution ID, terminal state and resulting website object. |
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 | AWS AgentCore Browser | Notte |
|---|---|---|---|
| Code execution | Product-dependent execution | External AWS compute | Python Functions |
| Scheduled execution | External scheduler | External scheduler | Native |
| Recordings / replay | Product-dependent | Custom browser + S3 | Documented |
Sources: docs.browserless.io [1] ↗docs.browserless.io [2] ↗docs.aws.amazon.com [3] ↗docs.notte.cc [4] ↗docs.notte.cc [5] ↗
Where the code runs
Browserless: Browserless supports several code and control surfaces. Compare the exact runtime endpoint or external runner you intend to use, including its language, deployment, versioning and invocation contract.
AWS AgentCore Browser: The Browser Tool supplies the browser environment. An external process or another AWS execution service runs the application code that controls it. Identify that service and its runtime before comparing it with a deployed browser Function.
Notte: Functions deploy Python code with a run() entry point. Invoke them over HTTP or with an SDK, inspect run history, and roll back code by redeploying an earlier version as the latest version.
Sources: docs.browserless.io [1] ↗docs.aws.amazon.com [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.
AWS AgentCore Browser: Use an AWS-managed Browser Tool or configure a custom browser with recording, networking and an execution role. Keep the controller's deployment separate in the architecture and operational estimate.
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] ↗docs.aws.amazon.com [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.
AWS AgentCore Browser: A complete AWS workflow may include browser use, the controlling compute service, storage and other metered services. Price the selected architecture and region instead of treating a browser benchmark rate as the final invoice.
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] ↗aws.amazon.com [2] ↗notte.cc [3] ↗
What should change the choice?
Consider Notte when an HTTP-invoked Python Function can own the browser task and expose its run history. Your application still needs its own event identity and duplicate-delivery policy.
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.
AWS AgentCore Browser: AgentCore Browser's AWS integration can matter more than moving a browser endpoint. Retain AWS identity and observability requirements in the evaluation, and separately account for the code runner and website login before comparing Notte's integrated workflow.
A TypeScript Function, browser-local action or existing external worker may be the better fit when it already integrates with the event system. Moving the browser does not require moving every webhook handler.
Sources: docs.browserless.io [1] ↗docs.browserless.io [2] ↗docs.browserless.io [3] ↗docs.aws.amazon.com [4] ↗aws.amazon.com [5] ↗docs.notte.cc [6] ↗docs.notte.cc [7] ↗notte.cc [8] ↗
How to remove an option from the shortlist
For this workflow, require the following evidence from Browserless, AWS AgentCore Browser and Notte: Event ID, invocation acknowledgement, execution ID, terminal state and resulting website object.
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 application tracks a terminal run and the intended number of website changes for that event, including after duplicate delivery.
- Send the same event twice and interrupt the first caller. Verify that run tracking and idempotency still describe the intended outcome.
Sources: docs.browserless.io [1] ↗docs.aws.amazon.com [2] ↗docs.notte.cc [3] ↗
Make a bounded pilot
Send a test event twice, keep a stable job identifier and verify the intended number of website changes and terminal run records.
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 the application's event ID when replacing invocation plumbing.
- Invoke the target from a test event and track its terminal result separately from the initial response.
- Route one event partition to the target and keep duplicate handling enabled during cutover.