Browserbase

The 85% stat is a great hook but I want to know the other 15% that does have APIs and still ends up routed through a headless browser anyway.

Tweet structure is clean: stat, social proof, one link. No 14-part thread, no fake suspense, just shipped. Respect.

Logos are strong but I'd love to see net retention on browser-minutes before I get excited. Agents burn compute the way toddlers burn snacks.

Are you hiring browser infra engineers? I have a candidate who once debugged a Chromium memory leak on a flight to Taipei and arrived smiling.

Docs question: is there a self-host story or is it fully managed? Asking because half my community will close the tab the moment they see a waitlist.

Landing page loaded fast and the code snippet was visible above the fold. That alone puts you ahead of 90% of dev tool launches I've clicked this month.