About this workload
Published by Notte, which competes with the products on this page. Every figure links to the provider's own documentation, checked on 2026-11-02.
An event from another system triggers a browser operation and the application tracks its result.
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.
Acceptance test: Send a test event twice, keep a stable job identifier and verify the intended number of website changes and terminal run records.
Provider support
Statuses and limits for the features this workload depends on, as stated in each provider's documentation.
| Provider | Serverless functions | Webhooks | Hosted agent API |
|---|---|---|---|
| Notte | Yes[1] | Yes[2] | Yes[3] |
| Browserbase | Yes[4] | Yes[5] | Yes[6] |
| Kernel | Yes[7] | Unknown | No[8] |
| Steel | Unknown | Unknown | Unknown |
| Hyperbrowser | Unknown | Unknown | Yes[9] |
| Anchor Browser | Yes[10] | Yes[11] | Yes[12] |
| Browser Use Cloud | Unknown | Yes[13] | Yes[14] |
| Browserless | Yes[15] | Beta[16] | Beta[16] |
| Cloudflare Browser Run | Unknown | Beta[17] | Unknown |
| Amazon Bedrock AgentCore Browser | Yes[18] | Unknown | Yes[19] |
| Lightpanda | Unknown | Unknown | No[20] |
| Tilion | Unknown | Yes[21] | Yes[22] |
Sources (22)
docs.notte.cc [1] ↗docs.notte.cc [2] ↗notte.cc [3] ↗docs.browserbase.com [4] ↗docs.browserbase.com [5] ↗docs.browserbase.com [6] ↗kernel.sh [7] ↗kernel.sh [8] ↗hyperbrowser.ai [9] ↗docs.anchorbrowser.io [10] ↗docs.anchorbrowser.io [11] ↗docs.anchorbrowser.io [12] ↗docs.browser-use.com [13] ↗docs.browser-use.com [14] ↗docs.browserless.io [15] ↗docs.browserless.io [16] ↗developers.cloudflare.com [17] ↗aws.amazon.com [18] ↗docs.aws.amazon.com [19] ↗lightpanda.io [20] ↗docs.tilion.dev [21] ↗docs.tilion.dev [22] ↗