Scalebrowser
Scalebrowser provides self-hosted browser infrastructure for AI agents. Its signed desktop client and Chromium-based engine run on a customer's own machine, giving each agent an isolated, persistent browser identity for signed-in work, challenging websites and browser tasks that lack APIs.
At a Glance
- AI-agent developers and automation engineers
- Teams running authenticated browser workflows
- Social media and marketplace operators
- Advertising and marketing operations
- +2 more
AI Tools by Scalebrowser
(1)
Scalebrowser
Self Hosted Browser for AI Agents
Discussions
No discussions yet
Be the first to start a discussion about Scalebrowser
Latest News
Browser agents: the 4 layers sites detect and how to get past them
AI agent login: 4 walls between an agent and a signed-in session
Behavioral biometrics: 11 mouse measures against 120 people
Bot detection in 2026: the 4 layers that flag an agent's browser
Products & Services
A licensed desktop client and signed Chromium fork that run on the customer's own machine. The daemon manages profiles, credentials, sessions, interfaces and engine verification; each profile has persistent identity, cookies, storage and device characteristics.
An interface for AI agents to read and operate pages through a compact tool set, including snapshots, clicks, typing, keyboard input, scrolling, downloads and artifacts.
MIT-licensed typed client for the REST API plus a direct-CDP driver; installable with pip and supporting profile management and browser driving.
MIT-licensed typed client for the REST API plus a direct-CDP driver, shipped with ESM and CommonJS support.
Market Position
Scalebrowser positions itself as a self-hosted alternative to cloud browser infrastructure and to stock Chromium driven through Playwright or Puppeteer stealth plugins. Its differentiators are a customer-controlled browser and network environment, a signed Chromium fork rather than only in-page patches, persistent seeded identities, isolated profiles, built-in login and secret handling, and agent input routed through a human-input layer. Its own comparisons discuss Browserbase, Playwright MCP, Chrome DevTools MCP, Camoufox, CloakBrowser, nodriver, Patchright, puppeteer-extra-plugin-stealth and browser-use.
Leadership
Founders
Davide Grasböck
Founder of Scalebrowser. The official author bio says he builds Scalebrowser, measures changes that web pages can observe against a real browser before shipping them, and writes about the results.
Executive Team
Davide Grasböck
Founder
Official Scalebrowser author bio identifies him as the founder and says he builds the browser layer, measures observable browser behavior and documents the findings.
Founding Story
Scalebrowser was created around the problem that AI agents often fail at the browser layer: sites can detect automation, credentials and second factors are difficult to handle safely, and cloud browsers move the browser and its network identity off the user's machine. Its stated initial vision is a browser layer that runs on customer-controlled hardware, keeps one persistent identity per profile, and routes agent actions through a human-input layer.
Business Model
Revenue Model
Paid subscriptions for licensed software and account entitlements. The software runs on the customer's hardware; plans are billed monthly or yearly and differ mainly by concurrent browsers and machines, while profiles and core capabilities are unlimited across plans.
Pricing Tiers
1 browser at once and 1 machine; unlimited profiles and the full product feature set.
5 browsers at once and 1 machine; unlimited profiles and the full product feature set.
20 browsers at once and 3 machines; unlimited profiles and the full product feature set.
50 browsers at once and 10 machines; additional units add 5 browsers for €40/month and 1 machine for €25/month.
Target Markets
- AI-agent developers and automation engineers
- Teams running authenticated browser workflows
- Social media and marketplace operators
- Advertising and marketing operations
- Businesses using supplier portals, SaaS tools and internal systems without APIs
- Organizations needing many isolated account identities on customer-controlled machines
- AI agents operating websites that require login, passwords, second factors, emailed codes or passkeys
- Operating tools and supplier/ad-management portals that have no usable API
- Running many separate social-media, marketplace, messaging and business accounts
- Repeating scheduled browser workflows across multiple portals
- Browser automation where persistent sessions, isolated identities and customer-controlled hardware are required
- Agents using MCP, direct CDP, REST, Python or Node automation