Skip to content
Browserberg Browserberg
Integrations

Bring the tools you already use

A session is a Chrome DevTools Protocol endpoint. Whatever already drives Chromium on your machine drives it here, with the connect URL changed and nothing else.

Why there is no Browserberg SDK to learn first

CDP is the interface

We did not invent a client library and then ask you to port to it. The endpoint speaks the protocol Chromium already speaks, so your existing driver works.

Leaving is as cheap as arriving

A migration that is one line in costs one line out. That is deliberate: an integration that locks you in is not a feature, and pretending otherwise would not survive contact with a technical evaluation.

Try it with a script you already have

Five browser hours, no card. The comparison that matters is your own suite, not ours.

Start free Book a call

  • Chrome DevTools Protocol on Browserberg

    Run Chrome DevTools Protocol against EU-hosted browser sessions. Connect over CDP with a one-line endpoint change, keep your existing scripts, and keep session...

  • LangChain on Browserberg

    Run LangChain against EU-hosted browser sessions. Connect over CDP with a one-line endpoint change, keep your existing scripts, and keep session data in the EU.

  • MCP on Browserberg

    Give Claude Code or any MCP client a hosted EU browser: one endpoint, tools for browsing, delegated tasks, workflows and the audit log, data kept in the EU.

  • Playwright on Browserberg

    Run Playwright against EU-hosted browser sessions. Connect over CDP with a one-line endpoint change, keep your existing scripts, and keep session data in the EU.

  • Puppeteer on Browserberg

    Run Puppeteer against EU-hosted browser sessions. Connect over CDP with a one-line endpoint change, keep your existing scripts, and keep session data in the EU.

  • Selenium on Browserberg

    Run Selenium against EU-hosted browser sessions. Connect over CDP with a one-line endpoint change, keep your existing scripts, and keep session data in the EU.