Skip to content

SolutionsBrowser automationComing soon

Real browsers, driven from code

With Browser, each browser runs in a microVM of its own, driven by Playwright or Puppeteer, its logins kept. Until it opens, a sandbox runs one today.

The Browser page

TypeScript, today
import { chromium } from "playwright-core";
import { Sandbox, BROWSER_IMAGE } from "glac";

const sbx = await Sandbox.create({ image: BROWSER_IMAGE });
const browser = await chromium.connectOverCDP(sbx.url(9222));
const page = browser.contexts()[0].pages()[0];
await page.goto("https://example.com");

Chromium in a sandbox from our browser image, its DevTools on port 9222, reached by a signed link.

What is decided

Decided for when Browser opens, after the launch.

  • Planned

    Billed by what it uses: CPU while it computes, memory while awake, by the second.

  • Planned

    Beside its agent: the agent in a sandbox of its own, the browser beside it.

  • Planned

    One size, and larger: 1 vCPU and 2 GiB, or bigger, billed alike.

  • Planned

    Asleep, it keeps its state, at $0.02 a GB-month.

  • Planned

    Chrome or Lightpanda, headless or with a screen.

  • Planned

    Logins kept from one session to the next, in its profile.

Illustrative previews

The products it uses

Start with what is here

A sandbox from our browser image runs Chromium today, with Playwright connecting from outside.

SandboxThe TypeScript SDK