80 karma · joined April 28, 2016
browserbase.com
It's called Stagehand (https://github.com/browserbase/stagehand) and we just released v3, which is a total rewrite.
We're building infrastructure that enables developers and LLMs to programmatically interact with the web using our hosted headless browsers.
A headless browser is just like the browser you're using right now, but running on a server. Running a single one isn't too bad, but running many of them becomes a complex exercise in stateful, distributed systems. We handle that, as well as provide great observability and other helpful features (like cookies management) to make developer's lives easier.
While the infrastructure product is how we make money, we also maintain Stagehand (https://github.com/browserbase/stagehand), the AI-powered successor to Playwright. We built it to show how you can use LLMs to build dynamic web automations that don't depend on deterministic code.
We're looking for developers who are interested in working on products that cater to other developers. You're an especially good fit if you're experienced in cloud infrastructure or distributed systems. We're a team of 10, full time in-person in-SF. You can learn more about our work culture here: https://x.com/pk_iv/status/1860762063490158642. We have product-market-fit, and have raised $27M from Kleiner Perkins, CRV, and Okta Ventures.
I've hired several people from HN and I'm excited to continue meeting great people like yourself!
Open roles are here: https://browserbase.com/careers You can also email at jobs@browserbase.com
(I am one of the authors!)
We even have an iFrame-able live view of the browser, so your users can get real-time feedback on the XPaths they're generating: https://docs.browserbase.com/features/session-live-view#give...
Happy to answer any questions!
Feel free to shoot me an email if you're interested in trying it out! paul@browserbase.com
That's actually one of the reasons why I started https://browserbase.com/. Maintaining headless browser infrastructure can be such a pain. I've spent a lot of time managing headless chrome fleets at scale, so happy to answer any questions.
I’ve always described this as “selling features vs selling solutions”. As a startup grows, the buying persona changes. Startups that sell to developers do best when they’re selling features, whereas a product manager/CEO is shopping for a solution (like increasing customer engagement). A neat thing I’ve noticed is that at one point, almost every B2B company will add a “Solutions” page to their website to highlight that.
Wrote about it more here: https://memos.hawkhill.ventures/p/selling-features-then-solu...)
Have you considered adding some operating templates for startups? I imagine your user is signing up because they need new process, and giving them some inspiration to play with may accelerate onboarding. (I signed up hoping to get that template you used in your demo video)
I'm not a fan of the superhuman interface, I've found that it create a big learning curve for what is could be a simple interface. At the same time I'm glad you guys drew inspiration from Linear, they have some great design too. I feel like they balance the hotkeys + clickable elements really well.
Slack integration is great. I think Loom would be big in my workflow too.
Happy to do a user interview etc to help out. email is in my profile.
https://www.loom.com/share/5358fbecd222474a93dd83abbe6ed755
Technologies we love: Javascript, Typescript, React, Next.js, Express, Postgres, TypeORM, Puppeteer, Heroku, AWS, Github.
If you're interested, say hi by emailing me paul@stream.club.
We're actually have all the features of their Professional plan ($50/month) at half the cost.
The on-screen participants per live stream is something we've capped at six for usability reasons (livestreams just don't look good with 10 faces on a stream).