Browserbase Functions hosts the code controlling a browser alongside its managed browser service. Its design account addresses a remaining burden for automation teams: operating separate workers to run scripts, even after outsourcing the browser itself.
A function keeps a stable identity while each deployment stores an immutable code version. Publishing a new version leaves production traffic unchanged until an explicit promotion, so teams can test it first or restore an older version. Each execution is tied to its deployment and browser session, making failures traceable. State can persist during a run, but Functions does not preserve it between separate invocations.
