jackienotchan
Joined 2 years ago
Joined 2 years ago
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...
The record/replay is definitely and interesting direction. The browser automation space is getting super crowded though (even within YC), so curious to hear how you differentiate from:
- BrowserUse
- Browserbase
- BrowserBook
- Skyvern
For scraping, how do you handle Cloudflare and Captchas? Do you respect robots.txt instructions of websites?
This comes with negative side effects for website owners (costs, downtime, etc.), as repeatedly reported here on HN (and experienced myself).
Does Webhound respect robots.txt directives and do you disclose the identity of your crawlers via user-agent header?
- BrowserUse - Founded 2024
- Greptile - Founded 2023
The third quote is from a VC who has never founded a startup himself and has a clear interest in pushing founders to trade work-life balance for his own quick returns.
So none of these people worked on anything longer than 2 years. I wonder what will happen if we check back in 5–10 years. Will they still be doing and promoting 996, or will they be burned out and have changed their minds? Make your bets.
YC seems to fund quite many document extraction companies, even within the same batch:
- Pulse (YC W24): https://www.ycombinator.com/companies/pulse-3
- OmniAI (YC W24): https://www.ycombinator.com/companies/omniai
- Extend (YC W23): https://www.ycombinator.com/companies/extend
How do you differentiate from these? And how do you see the space evolving as LLMs commoditize PDF extraction?
Do you have any built-in features that address these issues?
Do you have any built-in features that address these issues?
[0] https://www.ycombinator.com/launches/Lbx-simplex-on-demand-p...
This trend is creating a lot of headaches for developers responsible for maintaining heavily scraped sites.
related:
- "Dear AI Companies, instead of scraping OpenStreetMap, how about a $10k donation?" - https://news.ycombinator.com/item?id=41109926
- "Multiple AI companies bypassing web standard to scrape publisher sites" https://news.ycombinator.com/item?id=40750182
I also assume you don't check the robots.txt of websites?
I'm all for automating tedious work, but with all this (mostly AI-related) scraping, things are getting out of hand and creating a lot of headaches for developers maintaining heavily scraped sites.
related:
- "Dear AI Companies, instead of scraping OpenStreetMap, how about a $10k donation?" - https://news.ycombinator.com/item?id=41109926
- "Multiple AI companies bypassing web standard to scrape publisher sites" https://news.ycombinator.com/item?id=40750182
Even within YC, there are many competitors that do pretty much the same thing:
- Firecrawl
- BrowserUse
- Browserbase
- CloudCruise
- NotteLabs
- Intuned
- Expand.ai
- Reworkd
And then you have the extremely well-funded web retrieval players like Parallel and Exa.
How do you differentiate to all these?
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 Context respect robots.txt directives and do you disclose the identity of your crawlers via user-agent header?