In case you missed it, we recently were on Starter Story talking about growing a developer-focused business. Some of their questions were tough, and we hope the answers can shed some light on your journey! Plus, you'll get see sneak peak at the futon that "bootstrapped" browserless into what it is now.
Our new post on SourceSort is now live! Being an open-source project has many benefits, but also some drawbacks, and we dive deep into how to get the best of both worlds.
Feel free to check out our interview here: https://sourcesort.com/interview/joel-griffith-browserless.
We recently did an interview with our friends over at brandfetch.io. Some great talking points including
Check it out here: https://blog.brandfetch.io/automating-browsers-with-browserless/
After two years of running the business we have now hit 500 paying users! This an incredible accomplishment, and we couldn't have done it without the support and help from this community.
If you're on IndieHackers, and wondering how to get started, we were in your same shoes not so long ago. Please reach out and we'd be more than happy to share our insights!
How do you answer the question of "it works locally, but not in prod?" for headless workloads?
This is a question we've often asked ourselves, and the only answer is a better toolset. With that in mind, our latest docker release now includes a "live" debugger! You can now drop-in on active Puppeteer/REST API sessions and see what the browser is doing + have access to the entirety of Chrome's developer tools!
Our README has more information on how this all works, and it's now a part of our Dedicated plans, so go forth and conquer headless Chrome!
We're happy to announce that our usage-based accounts are now live! Pay only $0.00008/second for running your headless browser work, and no ongoing costs or fees.
We're extremely excited about this release as we encountered many challenges, great and small, in getting this out to production. Expect more write-ups from us on how we went about them!
Full blog post here: https://docs.browserless.io/blog/2019/04/01/usage-accounts.html
We've, once again, decided to expose our learnings after over a year of running headless Chrome in production. Check out our blog post and see how you can be improving your headless work regardless of where you run it: https://docs.browserless.io/blog/2019/03/13/more-observations.html
Running a headless browser in production is fraught with frustration and downtime. browserless solves these issues by providing a rich set of developer tools, hosting, and reliability.