Browser UseFrom the builder
A Production Architecture for the Browser Use Open-Source Library
Browser Use described the architecture it uses to run the open-source browser-use library in production, built from a FastAPI service on ECS Fargate, a single standard SQS queue and AWS Lambda workers, which the team says took more than 4,000 commits to get right. The API returns HTTP 202 in under 50 milliseconds, step checkpoints and screenshots go to S3, and to work around Lambda's 15-minute limit a task saves state two minutes before the deadline and re-queues itself, up to 12 continuations or about three hours. Failed messages go to a dead-letter queue after three attempts, and each invocation wipes its /tmp workspace to keep data from leaking between sessions.
AWS Lambda has a 15-minute hard limit, but browser agents don't. A task that takes 20 minutes shouldn't fail because of a runtime constraint.
Saved . A shortened excerpt from the official blog; the original publisher retains authorship.