Hosted browsers and devices
Official integrations with hosted browser and device services, one package per service.
An official integration is one package that gives a target its browser or
device from a hosted service, through the engine’s provider interface.
Only the target’s browser or device in the config changes.
Kernel
@e2e-dev/kernel: hosted Chromium for web targets, one browser per worker or per test.
Lightpanda
@e2e-dev/lightpanda: the open-source headless browser, started per worker slot on your own machine, no Chromium.
Expo Simulators
@e2e-dev/eas: hosted iOS simulators and Android emulators for mobile targets.
smol machines
@e2e-dev/smol: Chromium microVMs on your computer, each test in a branch of a warm browser.
Limrun
@e2e-dev/limrun: hosted iOS simulators and Android emulators, with app installation and device cleanup.
TestMu AI
@e2e-dev/testmu: hosted Android emulators, iOS simulators, and real devices for mobile targets, and Chrome and Edge for web targets.
BrowserStack
@e2e-dev/browserstack: BrowserStack App Automate real Android and iOS devices for mobile targets.
E2B
@e2e-dev/e2b: Android 16 sandboxes for mobile targets, and Chromium sandboxes for web targets.
Use a service with no integration
For any other service, write a small provider in your project: a
BrowserProvider for the web engine, or a
DeviceProvider for the mobile engine.
To run e2e on a CI service such as GitHub Actions, Expo Workflows, or Norrix, see Continuous integration.

