If you are a founder, a CTO, or a product strategist, your competitor's GitHub commits are the most expensive document in their company that you cannot read. The second most expensive is their tech stack — and that one you can read, because it ships in the response of every HTTPS request to their public site.
A competitor that swapped Mixpanel for PostHog, Heroku for Fly.io, Algolia for Typesense, or Segment for self-hosted RudderStack has just made a public infrastructure decision after weeks or months of internal evaluation. They paid the procurement cost, the migration cost, the engineering-time cost, and the integration cost, and they decided the new tool was worth it. That decision is information.
If you are evaluating the same swap, their decision is signal — they have already done the work you are about to do. If you are competing against them, their decision is intelligence — the new tool is better fit for at least one of you. If you are building a tool that targets users of either, their decision is pipeline — prospects who just migrated have an 18-month "we just chose this" honeymoon, and prospects who got migrated away from are in a renewal-anger window.
This post is the under-$100/month pipeline for tracking competitor tech-stack changes over time, at the cadence of a daily snapshot. The reference implementation uses the wappalyzer-replacement actor for the detection layer, plus ~120 lines of Python for the diff layer. BuiltWith and SimilarTech offer the same thing as a SaaS product — for $295–$995/month per seat, with seat-based licensing that makes it expensive to share with the eight people on your team who would actually use the data.
Why competitor stack data is structurally cheap to collect
Public web infrastructure is, by design, observable. Your competitor's site responds to HTTPS requests with HTTP headers, HTML, JavaScript, and resource URLs. Each of those carries fingerprints of the underlying technology:
- A
Server: cloudflareheader confirms Cloudflare is in front. - A `
Top comments (0)