I'm always genuinely curious on how startups navigate the founder maze as it helps to break the myth of an overnight success story.
Based on your YC page, you went through a couple of pivots over the last years:
- 4 years ago: Intuned - The data assistant for engineering leaders [0]
- 2 years ago: Intuned - The browser automation platform for developers and product teams [1]
- 1 year ago: Intuned Auth Sessions - Build authenticated scrapers and RPA [2]
What was kind of the evolution from YC S22 4 years ago till you arrived at today's launch? How did you find your differentiation in a highly commoditized space? Even within YC, there are many competitors like Firecrawl, Reworkd, BrowserUse, NotteLabs, Browserbase, etc.
Another thing that might interest HN: AI crawlers come with negative side effects for website owners (costs, downtime, etc.), as repeatedly reported here on HN (and experienced myself).
Does Intuned respect robots.txt directives and do you disclose the identity of your crawlers via user-agent header?
We actually went through 1 hard pivot only, the reset is more about framing the problem as we dug deeper and understood the customers and issue more. As an example, "Intuned Auth Sessions" is just a feature that we still support today!
But you are right, being a founder is not easy and the hardest part is figuring out what to build, does it make sense to keep going or should you stop - those are questions I still struggle with until today.
For your question about how is this different - I think if you dig into those product you will see that our focus is different, many of the companies mentioned are focused on powering agents via APIs, some are focused on enabling users to use AI at runtime, we do feel that our product is somewhat differentiated - the closest one is possibly Reworkd and I would still say the product is somewhat different. Now, the hardest part is actually commenting this with customers and the market in general - and there, we have a lot to figure out!
For robots.txt and user-agents question, we think of ourselves as providing infrastructure and flexibility for our customers to do what they want - we do encourage in our docs that they respect robots.txt but we don't enforce it on a platform level.
Appreciate you taking the time to leave this comment - very thoughtful
Biggest question I have is how this will overcome sites that implement aggressive anti-automation security. I can easily automate websites with existing tools until I slam into that wall.
Congrats on launch. I have experienced these issues first hand with `Open Finance` a few years ago.
I feel that you'll end up being an automation agency (you mentioned UiPath), companies who have the skills and capacity to build, will not need your service. But those who want the full service, you might fill a gap.
If you think about "price", "speed" and "accuracy (reliability/quality)", our bet is that models won't hit those 3 together. So you won't get a model that is very fast, very cheap and very accurate anytime soon.
Also, imagine that you have a case where you want to scrape 10,000 records from a website, why have AI navigate to every page to do this? why not write the code, run it, and get consistent and fast result? its also predictable, if it messes up, you know what happened and you can trace it to the exact line of code.
Yes, we we did our YC and social launches, we had few companies sign up and we have been building with them sense. For some of them, we have enabled them to run 1000+ scrapers which would have been very hard without Intuned. Some of these have been with us for 2+ years!
What our users love is the agent and the idea that we are not using AI at runtime which improves reliability.
this is not meant as personal assistant to do a task like this - the idea is that if you want to build a travel assistant and you want to do an integration with a travel booking service using browser automation - you can use Intuned to build this integration and expose an API to do search and one to do a booking, etc.
Does this make sense?
We actually do support CDP directly as well. As for why playwright, playwright provides a lot of benefits that we like in terms of being code - like auto-waiting, good syntax for a lot of operations, agents can use playwright pretty well and playwright is generally like by the community we target.
If a customer, doesn't want to use playwright, they don't have to given CDP but we most of our templates use playwright.
Based on your YC page, you went through a couple of pivots over the last years:
- 4 years ago: Intuned - The data assistant for engineering leaders [0]
- 2 years ago: Intuned - The browser automation platform for developers and product teams [1]
- 1 year ago: Intuned Auth Sessions - Build authenticated scrapers and RPA [2]
What was kind of the evolution from YC S22 4 years ago till you arrived at today's launch? How did you find your differentiation in a highly commoditized space? Even within YC, there are many competitors like Firecrawl, Reworkd, BrowserUse, NotteLabs, Browserbase, etc.
Another thing that might interest HN: AI crawlers come with negative side effects for website owners (costs, downtime, etc.), as repeatedly reported here on HN (and experienced myself).
Does Intuned respect robots.txt directives and do you disclose the identity of your crawlers via user-agent header?
[0] https://www.ycombinator.com/launches/Gqr-intuned-the-data-as...
[1]https://www.ycombinator.com/launches/LGE-intuned-the-browser...
[2] https://www.ycombinator.com/launches/Lpq-intuned-auth-sessio...
For your question about how is this different - I think if you dig into those product you will see that our focus is different, many of the companies mentioned are focused on powering agents via APIs, some are focused on enabling users to use AI at runtime, we do feel that our product is somewhat differentiated - the closest one is possibly Reworkd and I would still say the product is somewhat different. Now, the hardest part is actually commenting this with customers and the market in general - and there, we have a lot to figure out!
For robots.txt and user-agents question, we think of ourselves as providing infrastructure and flexibility for our customers to do what they want - we do encourage in our docs that they respect robots.txt but we don't enforce it on a platform level.
Appreciate you taking the time to leave this comment - very thoughtful
Also, one of our engineers did a write up on bot detection systems and how they work - https://intunedhq.com/blog/how-bot-detection-works
I feel that you'll end up being an automation agency (you mentioned UiPath), companies who have the skills and capacity to build, will not need your service. But those who want the full service, you might fill a gap.
I wish you all the best.
Also, imagine that you have a case where you want to scrape 10,000 records from a website, why have AI navigate to every page to do this? why not write the code, run it, and get consistent and fast result? its also predictable, if it messes up, you know what happened and you can trace it to the exact line of code.
If a customer, doesn't want to use playwright, they don't have to given CDP but we most of our templates use playwright.