Live data from Hacker News

Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

intunedhq.com

51–60 of 76 posts

Re: Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

#53
Who are your primary customers/usecases?

What do you think of just reverse engineering the network requests and writing scripts to hit the underlying APIs that the browser is making instead of tackling at the browser automation layer?

Re: Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

#54

Who are your primary customers/usecases? What do you think of just reverse engineering the network requests and writing scripts to hit the underlying APIs that the browser is making instead of tackling at the browser automation layer?

[dead]

Re: Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

#56

Salam. I'm currently working on a very similar idea but through a no code UX perspective https://usetwobytwo.com . Nice to see you guys see the same issue exist.

Salam, very interesting. curious why abstracting the code? For us, exposing code gives the user way more control and visibility about what's happening with their automations.

Re: Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

#57

Who are your primary customers/usecases? What do you think of just reverse engineering the network requests and writing scripts to hit the underlying APIs that the browser is making instead of tackling at the browser automation layer?

Hi Arjun, our customers use Intuned for a wide range of use cases, the main ones being: govtech and insurance tech. In addition, agencies that specialize in scraping for their customers.

Our Intuned agent and Web Task API always use reverse engineering when possible — the underlying agents have access to the network layer and can reverse engineer APIs when needed. At the end of the day, this comes down to what the user needs. We have seen cases where users need data from the network, and in these cases we skip the browser layer. In some other cases, we saw that users need to authenticate via the browser but then all the automation can be done via the network. We have also seen customers who want to get markdown of the pages in addition to hitting the APIs so a browser layer is a must.

Post reply on HN