Best Wappalyzer alternatives 2026.

Ten tools compared honestly. The free extension swaps (WhatRuns, BuiltWith trends), the FOSS forks of the pre-paywall Wappalyzer codebase (tunetheweb, enthec, wappalyzer-next), the paid depth alternatives (BuiltWith, SimilarTech, ful.io), programmatic options (W3Techs), and the wildcard most lists miss: hiring-signal intent.

Published 2026-05-27 · 13 min read

How to pick: the five categories

Free extension upgrade

Same shape as the old free Wappalyzer extension - click a tab, get a tech list. No login, no paywall, no API. The right swap when you only used Wappalyzer in-browser and never paid.

e.g. WhatRuns, BuiltWith trends

FOSS fork of old Wappalyzer

Community forks of the pre-2023 Wappalyzer codebase that kept the technologies ruleset open. Self-host, run on your own URLs, no rate limits. Requires you to be comfortable with Node or Python.

e.g. tunetheweb/wappalyzer, enthec/webappanalyzer, wappalyzer-next

Paid replacement (depth)

What you buy when free extensions aren't enough - bulk lookups, historical adoption data, contact enrichment. Different price points and data philosophies.

e.g. BuiltWith, SimilarTech, ful.io

Programmatic alternative

API-first tech detection for engineering and data teams. You pay per lookup or per dataset; you don't open a browser.

e.g. W3Techs, ful.io API

Hiring-signal wildcard

Not a Wappalyzer replacement - a different signal entirely. Tech in job postings reveals the team-side adoption that website scanners can't see.

e.g. JobsPipe, TheirStack

The 10 alternatives

1Free extension upgrade
WhatRuns

WhatRuns

whatruns.com

Best for: Developers who only ever used the free Wappalyzer extension and want the same in-browser UX without the paywall.

Pricing

Free. No paid tier, no account required.

Trial

Free forever

Pros
  • Closest UX clone to the old free Wappalyzer Chrome extension - click the icon, see the stack.
  • Genuinely free with no lookup limits, no signup gate.
  • Detects fonts, WordPress themes, and design-side tech better than most competitors.
Cons
  • Smaller technology set than legacy Wappalyzer - around 1,000 detections vs Wappalyzer's broader ruleset.
  • No web app, no bulk scanner, no API - browser-only.
  • Slower to add detections for new frameworks than the FOSS forks.
Verdict

The right swap if you were a free-Wappalyzer user who never logged in. If you need an API or bulk lookups, keep reading.

See WhatRuns's tech stack →
2FOSS fork of old Wappalyzer
tunetheweb/wappalyzer

tunetheweb/wappalyzer

github.com

Best for: Developers who want the original Wappalyzer codebase, self-hosted, with active community maintenance.

Pricing

Free, MIT-licensed. Self-host or run locally.

Trial

Free forever

Pros
  • Direct fork of the last open-source Wappalyzer commit before the 2023 paywall.
  • Most actively maintained of the community forks - PRs land regularly with new framework detections.
  • Run it as a CLI, a Node library, or a self-hosted scanner with no rate limits.
Cons
  • No browser extension build maintained alongside the fork - you install from source.
  • Detection ruleset is smaller than the closed-source post-2023 Wappalyzer database.
  • Self-hosting and update cadence are on you.
Verdict

The right pick if you want to keep the Wappalyzer engine and you're comfortable with a Node toolchain. Bonded to community contributions, so coverage tracks what the community cares about.

See tunetheweb/wappalyzer's tech stack →
3FOSS fork of old Wappalyzer
enthec/webappanalyzer

enthec/webappanalyzer

github.com

Best for: Teams that need a maintained technologies ruleset they can ship into their own scanner.

Pricing

Free, GPLv3-licensed. Bring your own runtime.

Trial

Free forever

Pros
  • Maintained by enthec as a continuation of the original Wappalyzer technologies ruleset.
  • Other tools (webanalyze, py-wappalyzer) already pull definitions from this fork - de-facto upstream.
  • Explicit commitment from the maintainer not to take the repo private.
Cons
  • Ruleset only - you supply the detection engine or use a wrapper.
  • GPLv3 has stricter redistribution requirements than MIT; check before bundling.
  • Smaller contributor base than tunetheweb fork; new framework support can lag a release cycle.
Verdict

Pick this when you're building your own scanner and want the rules without the original Wappalyzer codebase. Best paired with py-wappalyzer or webanalyze.

See enthec/webappanalyzer's tech stack →
4Paid replacement (depth)
BuiltWith

BuiltWith

builtwith.com

Best for: Sales and BD teams that need bulk lookups, historical adoption data, and contact enrichment.

Pricing

Free single-site lookups. Paid plans from $295/mo.

Trial

Free lookups; paid tier trial on request

Pros
  • Deepest technology dataset in the category - 100k+ tracked technologies with historical adoption back to 2008.
  • Bulk site lists with technology filters - the actual workflow Wappalyzer's paid tier targets.
  • Free in-browser lookups remain available without a login, which keeps it useful for ad-hoc checks.
Cons
  • Paid pricing is hostile compared to Wappalyzer's old free extension - $295/mo Basic is the entry point.
  • Stale detections in long-tail categories; review revenue estimates with skepticism.
  • No real free API; the value lives in the paid web app.
Verdict

Pick when your Wappalyzer use was sales-led and you need lists of sites running a given tech, not just one-off lookups. If you only used the free Chrome extension, BuiltWith is overkill.

See BuiltWith's tech stack →
5Paid replacement (depth)
SimilarTech

SimilarTech

similartech.com

Best for: Sales teams tracking technology-adoption trends and quarterly market-share shifts.

Pricing

Basic $200/mo (2 technology reports); Ultimate $490/mo; Enterprise custom.

Trial

Free Chrome extension; paid trial on request

Pros
  • Strong on adoption trends over time - which technologies are gaining or losing share.
  • Free Chrome extension covers per-site detection for individual lookups.
  • Bundled contact data on enterprise tiers cuts the round-trip to a separate prospecting tool.
Cons
  • Paid tiers are sales-led with limited transparency on overage pricing.
  • Smaller domain coverage than BuiltWith for long-tail and non-English sites.
  • The free extension is good but adds nothing over WhatRuns for one-off checks.
Verdict

Pick when adoption trends drive your motion - which is a narrow band of users. For most ex-Wappalyzer devs, the free extension is the only piece you'll touch.

See SimilarTech's tech stack →
6Programmatic alternative
ful.io

ful.io

ful.io

Best for: Teams that want a cheap technology-detection API without committing to BuiltWith pricing.

Pricing

Free trial credits; paid plans from $34/mo. API included.

Trial

25 free credits

Pros
  • Cheapest paid entry point in the category - $34/mo gets you a working API.
  • 75k+ technologies tracked, comparable surface to legacy Wappalyzer.
  • Chrome extension available if you also want the in-browser UX.
Cons
  • 25 free credits is a thin trial - you can't really evaluate at scale.
  • Smaller historical depth than BuiltWith; thinner adoption trends.
  • Newer player; integrations and ecosystem are limited vs incumbents.
Verdict

The pragmatic API pick when BuiltWith's pricing is offensive and the FOSS forks need too much wiring. Validate the credit math against your actual lookup volume before scaling.

See ful.io's tech stack →
7Programmatic alternative

Best for: Anyone researching web-wide market share for a specific technology category.

Pricing

Free daily surveys and lookups. API packs from EUR 100 per 1,000 requests.

Trial

Free web access

Pros
  • Single best free source for web-technology market-share data, updated daily.
  • No vendor bias - W3Techs publishes methodology and refuses to gate the macro numbers.
  • Per-site lookups remain free and don't require an account.
Cons
  • Not a per-site profiling tool - depth on any one URL is thinner than Wappalyzer's extension.
  • API pricing is pay-as-you-go and adds up fast at scale.
  • Coverage is top-1M sites; long-tail domains are not consistently indexed.
Verdict

Use it for trend research, not per-site detection. If your reason for searching Wappalyzer alternatives was 'how much of the web runs Next.js,' W3Techs is the answer.

See W3Techs's tech stack →
8FOSS fork of old Wappalyzer
wappalyzer-next

wappalyzer-next

github.com

Best for: Security researchers and pentesters who want a Python CLI for mass scanning.

Pricing

Free, MIT-licensed.

Trial

Free forever

Pros
  • Python-native, easy to drop into existing recon and CI pipelines.
  • Designed for mass scanning out of the box - reads URL lists, outputs JSON.
  • Pulls technologies from the enthec fork, so detections stay current.
Cons
  • CLI-only - no web UI, no browser extension.
  • Optimized for offensive security workflows; sales and marketing users will find it bare.
  • Smaller contributor base; expect occasional dependency-resolution friction.
Verdict

Pick when your Wappalyzer use was scripted recon, not in-browser checks. Pair with the enthec ruleset for the freshest detections.

See wappalyzer-next's tech stack →
9Free extension upgrade
BuiltWith trends (free)

BuiltWith trends (free)

trends.builtwith.com

Best for: Anyone who wants the BuiltWith depth without the $295/mo entry point - per-site only.

Pricing

Free for per-site lookups; no account required.

Trial

Free forever

Pros
  • Deepest free per-site lookup available - more detections than WhatRuns for a single URL.
  • Historical first-detected dates on individual technologies for free, which matters for sales research.
  • Same data backbone as paid BuiltWith, just gated to manual lookups.
Cons
  • No bulk export, no API, no list building - paid tier or nothing.
  • Web-only; no maintained browser extension that surfaces tech inline.
  • Free tier is bait for the paid product, so expect upsell prompts.
Verdict

The 'I just want to look up one site' answer that beats WhatRuns on depth. For workflow integration, you'll still need a different tool.

See BuiltWith trends (free)'s tech stack →
10Hiring-signal wildcard
JobsPipe

JobsPipe

jobspipe.dev

Best for: Sales and BD teams who use technographics to find buying triggers, not just to profile current stacks.

Pricing

Self-serve plans; transparent monthly pricing.

Trial

Free tier on signup

Pros
  • Detects technology adoption from job postings, which fires before a site update or DNS change can be scanned.
  • Captures backend and infrastructure tech that website scanners can't see - Snowflake, Databricks, Kubernetes, internal frameworks.
  • Hiring signals tie to a hiring manager and a team, not just a domain, which makes outreach concrete.
Cons
  • Not a Wappalyzer replacement - it answers a different question entirely.
  • Coverage depends on companies posting jobs with explicit tech names; quiet teams stay quiet.
  • Wrong tool if you only want to ID the CMS or analytics on a single URL.
Verdict

The wildcard. If your reason for using Wappalyzer was 'find companies adopting X,' JobsPipe surfaces that signal earlier and ties it to a person. If your reason was 'identify the stack on this URL,' use any of the nine tools above.

FAQ

Is Wappalyzer still free?+

The Chrome extension is still installable, but the useful surface got paywalled in 2023. The technologies ruleset went closed-source, and the paid web app starts at $250/mo. The free extension still works for per-site lookups, but it stopped getting community contributions, so detection quality has drifted relative to maintained forks.

Wappalyzer went closed-source - what's the FOSS fork?+

Two forks matter. tunetheweb/wappalyzer keeps the original codebase alive with active PRs - the right pick if you want the Wappalyzer engine. enthec/webappanalyzer maintains the technologies ruleset only - the right pick if you're embedding detections into your own scanner. Most modern tools (webanalyze, py-wappalyzer) pull from enthec.

Why isn't Wappalyzer detecting some technologies anymore?+

Because the public ruleset stopped updating after the 2023 closed-sourcing. Newer frameworks (anything that gained traction after mid-2023) often aren't in the free extension. The FOSS forks have caught up on most of them. If you're seeing missed detections on common stacks, that's the cause.

WhatRuns vs Wappalyzer - which is more accurate?+

WhatRuns detects fewer technologies overall (around 1,000 vs Wappalyzer's broader set) but stays current on common frameworks because it's still maintained. Wappalyzer's free tier is technically more comprehensive but increasingly stale. For day-to-day in-browser lookups on mainstream stacks, WhatRuns is the better default now.

Is there a free Wappalyzer API alternative?+

Not really a free hosted one. The closest is self-hosting tunetheweb/wappalyzer or wappalyzer-next as a CLI or service - free, unlimited, but you run the infrastructure. For a hosted API at a sane price, ful.io starts at $34/mo. W3Techs offers free per-site web lookups but charges per API call.

Why is JobsPipe on a Wappalyzer alternatives list?+

Because the most common Wappalyzer use case in B2B is 'find me companies running X' - and for the technologies that matter (data platforms, internal infrastructure, recent migrations), website scanners miss most of the signal. JobsPipe detects tech adoption from job postings, which fires earlier and surfaces tech that never touches the public web. It's not a replacement for Wappalyzer; it answers the same business question with a different signal.

Can I migrate my Wappalyzer paid plan to a cheaper tool?+

If you were on Wappalyzer paid for bulk lookups, the closest swap is ful.io at a fraction of the price, or BuiltWith if you need historical adoption depth. If you were on paid for the API only, self-hosting a FOSS fork is genuinely free and removes the rate limits. If you were paying for contact enrichment bundled on top, SimilarTech or a dedicated contacts tool is a cleaner separation of concerns.

Are the FOSS forks legally safe to use commercially?+

Yes, with caveats. tunetheweb/wappalyzer is MIT-licensed - use it anywhere. enthec/webappanalyzer is GPLv3, which has copyleft requirements if you redistribute - fine for internal tools and SaaS backends, check counsel before bundling into a sold product. The original Wappalyzer code pre-2023 was MIT, so the lineage is clean.

Methodology

Vendors evaluated on the same five axes. JobsPipe is the publisher; we’ve listed ourselves at #10, last, and called out that we’re not a tech-detection replacement.

  1. We ranked free-extension and FOSS options first because the primary intent behind 'Wappalyzer alternative' searches is replacing the free extension users lost when Wappalyzer paywalled itself in 2023, not upgrading to enterprise tooling.
  2. Verdicts are written from the position of a developer or technical BD user who installed Wappalyzer for free and wants the same shape - in-browser tech detection without a paywall or an account.
  3. FOSS forks are scored on maintenance signals (recent commits, open-issue throughput, contributor breadth), license clarity, and detection-rule freshness against current frameworks - not by raw star count.
  4. Pricing reflects publicly listed plans as of May 2026. Sales-led pricing (SimilarTech mid-tier, BuiltWith enterprise) is described as a range because actual negotiated rates vary widely with seat count and procurement leverage.
  5. JobsPipe sits at #10 with explicit wildcard framing because it is not a Wappalyzer replacement - it answers the 'find companies adopting X' question with a different signal (job-posting tech mentions) that fires earlier than any website scanner can. Included for honest scope, not parity.

Add hiring-signal intent alongside Wappalyzer. Free tier, 5,000 requests/month, no credit card.

Get a free API key