Get The Tech Stack
Paste a website URL and get a public-evidence tech stack estimate from headers, HTML, scripts, cookies, and public web search.
What this proves
A useful stack critic has to start with evidence. This build turns one public URL into a sourced, confidence-labeled stack estimate before any scale advice.
How it works
What This Proves
Stack advice is easy to fake.
The first version of Stack Scale Critic tried to judge whether a founder's stack fit the current scale and next 10x. The problem was simpler and more basic: most users do not know the stack yet. They know the website URL.
This build makes the first step explicit.
Paste a public website. The tool fetches the site, reads public clues, searches for supporting web evidence, and returns a stack estimate with confidence labels.
What I Built
The live pass uses three evidence lanes:
- response headers, including hosting and CDN clues
- public HTML, scripts, assets, cookies, and framework markers
- public web search, using Gemini Google Search when configured and a no-key DuckDuckGo fallback otherwise
Every detected technology is labeled:
- Strong when the fetched site exposes a direct signal or public web evidence supports a visible clue
- Likely when a public marker strongly points to a technology
- Possible when the evidence comes from snippets, embeds, jobs, or indirect mentions
- Unknown when the public evidence does not prove the claim
The report also lists what not to overclaim. Backend, database, internal services, and private infrastructure stay unknown unless public evidence names them.
The endpoint caches each normalized URL for 15 minutes and has both per-browser and global 1-hour caps. If public search is unavailable, the report says so and falls back to fetched-site evidence only.
Why It Fits ShipWithTez
This is a clean SWT proof because it turns a vague founder question into an operator workflow:
What can we actually know about this website's stack from public evidence?
That output can later feed a sharper Stack Scale Critic, but it is valuable on its own. A founder, operator, investor, engineer, or agency can paste a URL and get the evidence trail behind the visible stack.
What I Would Add Next
- Open and inspect the top public-web source pages, not just snippets.
- Add a saveable result URL so the stack estimate can become a shareable artifact.
- Let users edit the stack estimate and mark their own verified tools.
- Feed the edited stack into Stack Scale Critic for scale-fit analysis.
- Add a source freshness check for job posts and engineering blogs.
Get new builds, breakdowns, and useful AI updates.