Scrapium

Scrapium is Scrapfly's proprietary stealth browser, built on Chromium. Chromium is the open-source codebase that Google Chrome itself is built on: same engine, same rendering, same wire format. Chrome adds proprietary Google services on top; Scrapium adds stealth patches and agentic features instead. It patches 4,000+ signals at the C++ engine level (not in JavaScript) across WebGL, Canvas, AudioContext, Navigator, Screen, WebRTC, DRM, font rendering, and sensors. Values are seeded deterministically per profile so every session is internally coherent.

Yes. Scrapium runs behind the Scrapfly Web Scraping API at 5B+ scrapes per month against protected websites. Every Scrapfly customer hitting a target that needs a full browser is running through Scrapium without ever configuring it directly. Production workload, production detection vendors, production pass rates.

Scrapium is tuned for agent workflows (Playwright, Puppeteer, Selenium, Stagehand). We patch, fix, and extend Chrome capabilities specifically for automated and AI-driven use: programmable permission handling, popup and dialog control, tab-switching prevention, download handling, session resumption, and an enriched Chrome DevTools Protocol (extra CDP domains that genuine Chrome does not expose). Your agent framework sees a compliant Chrome, plus the hooks agents actually need.

Yes. Scrapium runs as an authentic Chrome build for Windows, macOS, and Linux. Windows Chrome renders with Windows fonts, Windows system colors, and the exact Blink build Chrome ships on that platform. The proxy chain guarantees OS-to-exit-peer alignment: a Windows browser always exits through a Windows peer, 100% coherent end to end. Same for macOS and Linux.

No. Scrapium is part of the Scrapfly infrastructure and is selected automatically when the Scrapfly protection system determines it is the right tool for a given target. You call the standard Scrapfly scrape API. Browser selection, fingerprint profile assignment, and patch seeding all happen server-side.

Our browser-engineering team auto-tracks every Chrome release. When a new Chrome stable ships, Scrapium ships the same patch target into the browser pool within days, maximum 3-day lag from GA, fully automated. No customer config, no version-lag fingerprint signal. Most stealth browsers run two or three versions behind, which is itself a detection signal: real users update Chrome automatically.

Detection systems time the sequence of DNS resolution, TLS handshake, and HTTP/2 negotiation. Real browsers on a return visit are fast because DNS is cached and TLS session tickets let 0-RTT resume. Most automated browsers re-resolve and re-handshake every request, which is a tell. Scrapium uses localized DNS resolvers geo-aligned to the proxy exit region, caches resolved IPs per session, and replays TLS session tickets when the server allows.