Automation

Your workflow. Your code.Our browser infrastructure.

Put repetitive web tasks into repeatable workflows. Run your Playwright and Puppeteer scripts on real browsers with native graphics, human-like mouse and keyboard input, and the visibility to understand every run.

  • Playwright & Puppeteer
  • GPU in every instance
  • Physical mobile devices
Your workflow, connectedAutomation
  1. 01Your application or job
  2. 02Playwright / Puppeteer
  3. 03CDT firewall + system input
  4. 04Real browser workflow
Open → interact → verifyYour application triggers the job. The platform runs the browser environment.

Built for Automation

Automate the work between web pages.

Use browser code for tasks that require navigation, interaction, or a visual page rather than a single API request.

01

Forms and operational tasks

Move through multi-step forms and routine data entry in the web applications your team uses. Keep business rules and completion checks in your code.

02

Reports and dashboard workflows

Navigate dashboards and gather the information your workflow needs. Review the recording when a layout change or unexpected page state interrupts a run.

03

Repeatable mobile workflows

Run mobile web tasks on physical devices. Exercise the real mobile browser environment when a desktop profile does not match the workflow.

The Cloud Dev Tools difference

Real hardware.
Every browser layer covered.

Browser access is more than an endpoint. These capabilities work together underneath your code, across AI agents, scraping, automation, and testing.

01 / Automation

A firewall for Puppeteer and Playwright

Automation libraries can leak objects that a website’s web application firewall detects. Our own firewall sits between libraries such as Puppeteer and Playwright and the browser to prevent those detectable object leaks.

Your library → CDT firewall → Browser

02 / Graphics

A GPU in every instance

Every browser instance has a native GPU for hardware rendering. WebGL, canvas, video, and page composition use real graphics hardware, with actual consumer CPU and RAM values reported in JavaScript.

Consumer CPU · Real RAM · Native GPU

03 / Devices

Physical mobile devices

Run desktop browsers on consumer hardware or choose physical mobile devices. Mobile sessions use an actual mobile browser environment rather than desktop emulation with a smaller viewport.

Real desktop hardware · Physical mobile

04 / Network

The right route for the destination

Choose datacenter, residential, or mobile proxies, city-level targeting, or bring your own proxy. The API’s domain-based routing keyword helps automatically select an appropriate proxy for your target website.

Domain-based routing · Flexible proxies

05 / Browser

Current browsers. Native handshakes.

We run regular browsers and keep them up to date. TLS and protocol handshake parameters come from the browser itself, without tying your workflow to an older browser binary bundled with an automation library.

Up-to-date browsers · Native protocols

06 / Interaction

Input through the human path

Mouse and keyboard events execute at the system level, through the same input path as real peripherals. Movements and keystrokes mimic human behavior instead of relying only on synthetic page events.

System-level mouse · System-level keyboard

From code to browser

Keep the familiar.
Connect to something better.

Use Playwright or Puppeteer with a managed browser endpoint. Start with the connection details in the API documentation.

Read the integration documentation
  1. 01

    Keep your workflow logic

    Run your application or scheduled job wherever you already host it. Connect to a remote browser instead of maintaining browser hardware yourself.

  2. 02

    Choose the browser environment

    Use current desktop browsers or physical mobile devices, with a GPU in every instance and proxy options for the destination.

  3. 03

    Run, watch, and improve

    Follow a live session and inspect searchable history and recordings. Develop and try supported-language code directly in the portal.

From development to investigation

See the run.
Understand the result.

The browser is only half the workflow. Develop in the portal, follow active sessions, and return to the evidence when something needs a closer look.

Cloud Dev Tools session history with searchable logs, browser recordings, proxy details, and CAPTCHA solver status
Session history, network details, and recordings in one view.

Live session views

Let people and AI agents follow the browser as a workflow runs.

Searchable logs and replay

Find past sessions, inspect detailed logs, and review clear recordings.

A portal for development

Write and run tests in supported languages without local IDE or environment setup.

Locally run AI CAPTCHA assistance

Use local AI models to help resolve difficult CAPTCHA challenges during a session.

Common questions

Automation,
explained.

Where does my automation code run?

Your application can run the Playwright or Puppeteer client in your own environment and connect to a Cloud Dev Tools browser endpoint. The portal also lets you write and run tests in supported languages.

How are clicks and typing handled?

Mouse and keyboard events execute through system-level input paths, with movement and keystrokes designed to mimic human interaction.

How can I debug a broken workflow?

Watch the live session, search past runs, inspect detailed logs, and replay the recording to see which page or action needs attention.

A complete browser foundation

Put your browser workflows to work.