We just built AWS Lambda with a browser built-in. Introducing Functions, a new compute paradigm that co-locates your code and browsers to build faster browser agents. Functions lets your team focus on the product, while we handle the infrastructure.

Here's a quick walkthrough on deploying and invoking your first Browserbase Function:

Read more about Functions:

I have been waiting YEARS for this one !

can vouch as the first Functions user

I have used ALL the browser as a service options and even built my own, can safely say BB is 1. the best, 2. most reliable, 3. most future oriented of them all!

func browser() { // lets fkn go }

"The files are in the computer?!?"

she’s live!!! Hot damn @ajmcquilkin what a ship

looks slick

truly the biggest and most spectacular labor of love from @ajmcquilkin @walkergriggs and team to make this happen. So so so proud of this!! Core team ships!

Oh shit! Let's goo BB team! this is dope

This is a big step forward in our product lineup — Browserbase code execution opens up exciting things ahead

let’s gooo @ajmcquilkin 👨‍🍳

BB team back at it

crazy work by @ajmcquilkin

@ajmcquilkin cooked on the functions DX

🔥🔥

Hot start to the year of browser agents!

🔥🔥🔥

the future of browsers is this!

edit: the fastest browser agents

This announcement overlooks a crucial consideration while co-locating code and browsers sounds innovative, it raises questions about security and performance trade-offs. Prioritizing speed shouldnt come at the expense of robustness.

Please fix the stealth for base plan we re getting blocked all the way @Stagehanddev @pk_iv @ajmcquilkin

ya'll are absolutely cooking!

Is this able to upload/download files from a website? My current system does business automation with headless browsers on lambda. This looks super slick! I'm not sure if I should switch to BrowserBase or if I should come work for you.

great visuals!!

curious how this impacts cold start times for lambda functions

This is basically what we've needed for agent reliability. The co-location piece is huge — latency between your logic and the browser kills so many workflows. What's the cold start time looking like? That's usually the tradeoff with these managed browser setups.

this is fire

the agent is also co-located with the browser, definitely makes a difference, well done!

lambda with built-in browser? that's a win for serverless browser agents without the spin-up lag. does it support playwright scripts directly?