All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Building Scalable Agent Infrastructure: From AWS Lambda to Unikraft Micro-VMs

By

gregpr07

3mo ago· 9 min readenInsight

Summary

Browser Use shares their technical journey from running web agents on AWS Lambda to developing a more robust infrastructure using Unikraft micro-VMs with a control plane architecture. The article details their evolution from browser-only agents to adding code execution capabilities, addressing challenges with agent isolation, scalability, and security. They explain how moving from a Lambda-based approach to micro-VMs solved problems with agent reliability during deployments and performance issues when memory-hungry agents affected API performance.

Key quotes

· 4 pulled
We run millions of web agents at Browser Use. We started with browser-only agents on AWS Lambda, where each invocation is isolated, scaling is instant, and there are no secrets to worry about.
Then we added code execution. Agents could write and run Python, execute shell commands, create files. We built this as an isolated sandbox the agent called as a tool.
But the agent loop still ran on the same backend as our REST API. Redeploy? All running agents die. Memory-hungry agent? The API slows down.
Security was fine: the code ran in the sandbox, not on the backend.
Snippet from the RSS feed
From AWS Lambda to Unikraft micro-VMs with a control plane architecture.

You might also wanna read