Base44 SDK Adds a Browser Module for Remote Browser Automation

Base44Nov 4, 2026View original changelog

The Base44 SDK gained a browser module that lets backend functions start remote browser sessions with getSession(). The sessions are controlled over the Chrome DevTools Protocol using Playwright or Puppeteer. Sessions are billed per minute against workspace credits.

Key Takeaways

The SDK's new browser module lets backend functions run browser automation.
getSession() starts a remote browser session that is driven over the Chrome DevTools Protocol.
Developers can use Playwright or Puppeteer, so existing automation code carries over.
Sessions are billed per minute from workspace credits until they end, so code should call endSession().
Base44 stores no browser state, which makes every session independent.
The module needs service role mode and SDK 0.8.56 or later, which keeps it out of frontend code.

Remote browsers from backend functions

Base44 added a browser module to its SDK. Calling getSession() from a backend function starts a remote browser session. The function then controls that browser over the Chrome DevTools Protocol, using either Playwright or Puppeteer. This allows scraping, screenshots, form filling and other browser automation to run inside a Base44 app's backend.

How sessions work

Base44 does not store browser state, so each session is independent. Sessions use credits from the workspace that owns the app and are billed by the minute until they end. The SDK reference documents getSession() and endSession(), along with session options and error codes. Because billing runs until a session ends, backend code should end sessions once the work is finished.

Requirements

The module is only available in service role authentication mode, so it is meant for backend functions rather than frontend code. It requires SDK version 0.8.56 or later.