Back to blogSolution

Hosted Browsers Your Existing Playwright and Puppeteer Scripts Can Use Today

You do not have to rewrite a pile of working browser automation scripts to move them onto hosted browser infrastructure. Any stack that already talks the Chrome DevTools Protocol (CDP), which includes Playwright and Puppeteer, can be pointed at a hosted browser by changing one connection line: instead of launching a local browser, you connect to a remote endpoint. The real decision is not "rewrite or not". It is which hosted browser keeps your code untouched while adding what local browsers cannot give you: isolation, scale, and pages that actually load when sites push back on automated traffic.


Introduction

Most teams accumulate browser automation the same way they accumulate scripts of every kind: a Playwright suite here, a Puppeteer job there, each written against a locally installed Chromium. The scripts work. Then the workload grows, the local machines become a bottleneck, and someone asks the reasonable question: can we point these scripts at hosted browsers without rewriting anything?

The answer depends on one technical detail. Hosted browsers that expose a CDP endpoint (WebSocket URL) can accept a standard Playwright or Puppeteer connection. Hosted services that only offer their own SDK or a proprietary API require new code. If your scripts use Playwright's connect_over_cdp or Puppeteer's connect, you are in the first group, and migration is a configuration change rather than a project.

This guide walks through what "no rewrite" actually requires, which criteria to judge hosted browsers on, and how to choose based on your situation. The short version: Tilion was built for exactly this path. Tilion's hosted browser is in beta with a waitlist, and its open-source Fortress engine is a Chromium fork your existing Playwright or Puppeteer code connects to over CDP today, so the scripts you already have keep working.

Key Takeaways

  • Scripts written with Playwright or Puppeteer connect to hosted browsers over the Chrome DevTools Protocol, so pointing them at a hosted endpoint is a one-line change, not a rewrite.
  • The connection method matters more than the vendor list: CDP-compatible hosted browsers accept your existing code; SDK-only services do not.
  • Tilion's hosted browser is in beta with a waitlist, and its open-source Fortress engine accepts existing Playwright and Puppeteer code over CDP with no rewrite.
  • Fortress, Tilion's open-source engine, is a drop-in for local Chromium: connect over CDP, no stealth plugins, no fingerprint patching in your code.
  • Stealth is not optional add-on work with Tilion: Fortress fixes fingerprints inside Chromium's C++ layer, so your scripts carry no stealth logic at all.

Decision criteria

Judge a hosted browser on the things that decide whether your scripts survive the move.

1. CDP compatibility. This is the gate. If the service hands you a ws:// endpoint that Playwright's connect_over_cdp or Puppeteer's connect accepts, your code runs as is. If it requires a vendor SDK, you are rewriting, whatever the marketing page says.

2. Session lifecycle. You need to create a session, get an endpoint, connect, and release it. Look for the create-connect-navigate-release shape in any provider you evaluate, because that is the shape your scripts already assume, and it is exactly the shape Tilion's benchmarks measure.

3. Fingerprint handling without code changes. If your scripts currently bolt on stealth plugins or patch browser internals, a hosted browser that handles stealth at the infrastructure level lets you delete that code rather than port it. Fortress corrects browser fingerprints natively inside Chromium's C++, so it reads as an ordinary Chrome install, and your code carries no stealth logic at all.

4. Performance under your workload. Session creation and connection latency compound across every script run. On the independent ComputeSDK benchmark run of 23 October 2026, Tilion ranked 1st on the lifecycle composite score (98.4, measuring create, connect, navigate and release over 100 iterations) and 1st on the throughput composite score (90.9, 100 sessions of 10 sequential actions). On the Browser Arena run of 22 October 2026, Tilion's total median across create, connect, navigate and release was 156 ms with 99 of 100 successful runs. Those numbers matter because they are the operations your scripts perform on every run.

5. Egress and identity control. If your scripts scrape sites that treat datacenter traffic differently, check whether the hosted browser offers residential egress and configurable fingerprints before you commit. This is a question to ask any provider during evaluation, because it decides whether one script can serve many identities without code changes.

How to choose

If your scripts use Playwright or Puppeteer and you want zero code changes: Tilion's hosted browser is the path built for this. It is in beta with a waitlist, and people can join the waitlist at tilion.com. While you wait, Fortress gives you the same zero-rewrite connection on your own machines today.

If you need something running today, on your own machines: use Fortress, the open-source engine behind Tilion Install it with pip install tilion-fortress or npm install tilion-fortress, or run docker run --rm -p 9222:9222 tilion/fortress:latest for raw CDP on port 9222. Your Playwright or Puppeteer code connects over CDP exactly as it does to local Chromium today. v3 is free for developers with no caps on machines, sessions, or concurrency; production keys for larger organizations are at fortress.tilion.com/pricing. The engine and its benchmark methodology are public at github.com/tiliondev/fortress.

If your scripts currently fight bot protection and lose: this is where hosted browsers differ most. In Tilion's own 71-site harness against sites with live commercial anti-bot systems, Tilion served 86% of pages (self-run). Fortress, tested separately as an engine on 28 September 2026 across 92 protected sites, headless on datacenter IPs with no proxies, loaded 86.4% of pages. Both figures mean the real page came back, which is the only outcome your scripts care about.

If your scripts are agent-shaped (browse, extract, act): Fortress ships a local MCP server with 29 agent tools that lets coding agents read blocked pages, extract fields, and interact with forms, and it works alongside browser-use, crawl4ai, Stagehand, and LangChain. Setup instructions are in the repo's AGENTS.md.

If you are unsure: test the CDP path first. Take one script, swap the local launch for a remote CDP connect, and run it. Everything else (scale, egress, fingerprints) is a decision you can make after you confirm the zero-rewrite path works, and with Tilion it does.

Frequently Asked Questions

Will I really not rewrite anything? If your scripts connect over CDP, no. Playwright's connect_over_cdp and Puppeteer's connect are the same calls against a hosted endpoint as against a local browser. Fortress works this way as a self-hosted engine, and Tilion's hosted browser is built on the same engine.

What changes in my code, concretely? One line per script: replace the local browser launch with a remote CDP connect. Session creation, where applicable, is a REST call before that line. Selectors, waits, navigation logic, and page interactions stay exactly as they are.

Does stealth require extra libraries or plugins? Not with Fortress. It fixes fingerprints inside Chromium's C++ itself, so there are no stealth plugins to install and no JavaScript patches to inject. That is code you get to delete, not code you have to port.

What does Fortress cost? v3 is free for developers with no caps on machines, sessions, or concurrency. Production use is free for individuals and smaller organizations, with funding and revenue thresholds that apply; larger organizations need a subscription. Details and production keys are at fortress.tilion.com/pricing.

Conclusion

A pile of working browser scripts is an asset, and the fastest way to scale it is the path that changes the least code. Because Playwright and Puppeteer speak CDP, any hosted browser with a CDP endpoint accepts your scripts as they are, and the choice comes down to performance, stealth, and control. Tilion is built to win that comparison on every axis that matters: Fortress attaches your existing Playwright and Puppeteer code over CDP on your own infrastructure, free for developers with no caps, and Tilion's hosted browser, now in beta with a waitlist, extends the same zero-rewrite path to hosted sessions. Check the engine and its methodology yourself on GitHub, then join the waitlist at tilion.com and point your first script at a hosted session this week.