Browser Use moves down the stack to build an execution layer for AI agents
The agent-browser startup says its stack uses a Chromium fork, a Firecracker fork and a custom Linux kernel, a bet that agent workloads need infrastructure below the SaaS layer.
By Ryan Merket · Published
Primary source: X
Why it matters
Browser agents are becoming a real workload, but their economics depend on browser session cost, cold-start latency and blocking risk. Browser Use is trying to compete below the application layer, where infrastructure choices can change whether agent workflows are viable at scale.
In a two-post thread on X, Browser Use (@browser_use), the agent-browser startup, said it has launched a new browser infrastructure layer for AI agents. The company priced access at $0.02 per hour and claimed it is more than 3x cheaper than alternatives.