I built a website tech stack detector that gives every site a health score, here's why
Hey Indie Hackers,
I am Jayesh, founder of TrueTechFinder. I want to share what I have been building and get honest feedback from this community. The problem I kept running into every time I wanted to understand what technology a competitor or prospect was using, I would run it through existing tools and get a wall of technology names with zero context. I knew WordPress was listed, but what did that mean for their architecture? Was their stack modern or outdated? Secure or not?
I wanted answers, not lists. What I built (TrueTechFinder) detects 700+ technologies and does two things no other tool does:
-
Stack Health Score - Every site gets a 0–100 score based on six measurable pillars: infrastructure, security, modernity, performance, observability, and stack coherence. Fully documented methodology.
-
AI insights - a plain-English explanation of what the detected stack means. Not just "uses React" but "React frontend with Vercel deployment signals a PLG-focused team optimising for developer experience and fast iteration.
Where I am right now? Have got 1,000+ websites scanned using the tool by real users which are spread in 20+ countries. $0 MRR (working on the paid tier).
I have just redesigned the Homepage and website layout to make it user-friendly and easy to use.
I would love feedback on The "Stack Health Score" which is the feature I am most uncertain about. Does a numerical score add value to you when researching a site's stack, or does it feel arbitrary?
Would love honest takes from this community.
Try it here: https://www.truetechfinder.com
Happy to answer any questions about how I built it or where I am taking it next.
The strongest part here is the shift from “tech lookup” to “tech interpretation.”
That’s the real value.
Most tools dump components.
Yours is trying to answer what those components actually imply.
Where I’d be careful is the name.
“TrueTechFinder” explains the category, but it also makes the product feel more like a utility than something opinionated enough to own a trust-based score.
That matters because “Stack Health Score” is only useful if people believe the product behind it has judgment, not just detection.
Right now the feature is stronger than the brand framing.
Curious if the long-term play is staying a lookup tool, or turning this into a more opinionated product around stack trust / due diligence?
This is one of the sharpest observations I have received since launching and honestly something I have been sitting with myself.
You have identified the exact tension. "TrueTechFinder" is descriptive and searchable, which helped with early SEO and discoverability. But you are right that it does not carry the weight of a product that has judgment.
The Stack Health Score was the moment the product stopped being a lookup tool and started being something more opinionated. When you assign a number to a website's infrastructure choices, you are making a claim that some stacks are healthier than others, that security headers matter, that duplicate analytics tools are a signal worth flagging. That is a fundamentally different product from Wappalyzer or BuiltWith.
To answer your question directly, the long-term play is absolutely the opinionated direction. Agencies using it for client audits, sales teams qualifying prospects, investors doing technical due diligence on companies, these are the use cases where judgment matters more than detection.
The brand question is a real one I don't have a clean answer to yet. Changing a name post-launch has real costs around SEO, brand recognition, user confusion. But you have articulated clearly why the current name might cap the product's perceived authority at a certain level.
Curious what you think does the brand need to change to match the product's ambition, or can positioning and messaging do that work without a rename?
Positioning can stretch a weak name.
It usually cannot compound one.
That’s the tradeoff.
TrueTechFinder is useful for discoverability.
It is weak for authority.
And in your case that matters because the product is no longer selling detection.
It is selling judgment.
The moment you assign a score, rank stack quality, or imply trust risk, the product stops behaving like a lookup tool and starts behaving like an opinionated system.
That is usually where descriptive names start capping perceived authority.
You can absolutely buy time with positioning.
But if the long-term product is trust-weighted judgment, the name eventually has to carry more authority than “finder.”