@ryancarson @thinkshiv check us out as a comparison - may find better success metrics.
English
browserless
268 posts
browserless
@browserless
A managed fleet of headless browsers, ready to use with scraping, testing or other automations 🚀 https://t.co/BeqqzveUXb
加入时间 Şubat 2018
134 关注964 粉丝
@thinkshiv I was thinking about browserbase for this. So you’d recommend it?
English
Finally got the agent to reliably attach a video of it using the browser to demonstrate a passing acceptance test
One step closer to a real Code Factory
English
This is a big deal for browser automation infrastructure. ARM64 Chrome means lower compute costs, fewer Chromium edge cases, and way more flexibility in where you run headless browsers. We're already exploring what this unlocks for Browserless users.
Joel Griffith@joeldoesjs
Google is finally bringing Chrome to ARM64 Linux devices. Very exciting for two reasons: better automation capabilities — and much cheaper. It also means you’ll be able to do a lot more with @browserless and Raspberry Pi. Stuff like: - Being able to run on many different machines, like AWS arm64 instances. - Watch and record sites that have mp4 video files. - Run tests on a variety of new machine types if you’re unit-testing. Another big plus is that you won’t have to deal with Chromium-related edge cases and automation setbacks like fingerprint differences, missing codecs, etc. Raspberry Pi is already very popular with home automation tinkerers, so I expect to see some really cool use cases in the near future. Will definitely be keeping an eye out.
English
Thank you to everyone who contributed code, filed an issue, or answered a question in Discord.
These lessons came from you.
Now back to building.
English
The fastest way to learn is to let users tell you what you missed.
Most feature requests are noise. The ones that show up three times from three users are signal.
English
Browserless crossed 12,000 GitHub stars last month.
8 years of commits. 77 contributors. Almost 1,000 forks. Thousands of production environments we will never see.
Here is what open source taught us about building a company:
English
/8
Curious how your team could drop the ops overhead and just ship? Might be time to rethink how you run browser automation.
English
/7
Takeaway: If you’re fighting real-time data or transaction windows, stable browser automation isn’t optional-it’s your edge. Your ops shouldn’t hold you back from building the core product. Worth it.
English
Manifold Freight’s team ran 100s of browser automations every 5 minutes.
No ops headaches. No costly rewrites. No missed revenue.
Here’s how they pulled it off:
🧵
English
Most fintech teams bolt on security later and pay for it.
Atomic Fi built it into the foundation from day one.
Which one are you?
browserless.io/blog/atomic-fi…
English
The architecture that made it work:
→ Self-hosted Browserless enterprise images
→ One container per task (complete session isolation) → Custom endpoints built for their specific workflows → Direct access to our engineering team
Security and speed. Not a tradeoff.
English
Atomic Fi built their fintech platform on Browserless from day one.
Now they run thousands of secure automations daily across payroll systems and financial institutions.
Here's how 👇
English