June 17, 2026
VMs, vibes, and a tiny scandal
How we run Firecracker VMs inside EC2 and start browsers in less than 1s
They made cloud browsers way cheaper and faster, and the comments instantly got messy
TLDR: The company says it rebuilt its cloud browser system so sessions start in under a second and cost a third as much, which matters because speed and privacy are everything here. Commenters were split between impressed, confused, and amused — especially over a possible AI editing slip and the question of why Google never launched this first.
A startup says it pulled off a neat little magic trick: browser sessions that used to cost 6 cents an hour now cost 2 cents, while also launching in under a second. The basic promise is simple even if the plumbing is not: every user gets their own isolated browser so nobody’s tabs, cookies, downloads, or logins can leak into somebody else’s session. To make that happen, they rebuilt their system so each browser runs in its own tiny virtual computer on Amazon’s cloud. Translation: safer, faster, cheaper — the holy trinity of internet infrastructure bragging rights.
But the real entertainment was in the replies. One commenter immediately spotted what looked like a hilarious publishing faceplant, joking that the post accidentally left in the AI’s own instructions — a classic “you can see the wizard behind the curtain” moment. Another dropped the big spicy question: if Google makes Chrome and runs giant cloud services, why hasn’t Google already made this exact product? That hot take gave the thread an instant conspiracy-lite energy, like the crowd was half impressed and half side-eyeing Silicon Valley for somehow leaving money on the table.
Then came the mini nerd-fight over whether Amazon already offers special server options that make this easier, while another reader skipped the drama entirely to geek out over a memory-loading trick called userfaultfd like they’d found the secret seasoning in the sauce. So yes, the company announced a faster, cheaper browser cloud — but the comment section turned it into a mix of gotcha humor, big-platform shade, and delightful technical nitpicking. As always, the product shipped, and the community shipped opinions.
Key Points
- •Browser Use says it reduced browser session cost from $0.06 to $0.02 per hour and lowered startup time to under one second by rebuilding its cloud browser infrastructure.
- •The new design runs every browser session inside its own Firecracker VM on regular Amazon EC2 instances to provide isolation between sessions.
- •The article describes this as an unusual nested virtualization setup because Firecracker is typically run on bare-metal servers, while EC2 instances are already virtualized.
- •Browser Use previously used Unikraft unikernels, which provided fast startup and low idle cost but lacked effective built-in autoscaling during traffic spikes.
- •To handle scaling, Browser Use built a custom control plane that monitors browser fleet state in real time and makes placement and scale-up or scale-down decisions faster than relying on AWS CloudWatch windows.