comparison · LoupeKit vs Wappalyzer
LoupeKit vs Wappalyzer: which one should you install?
Wappalyzer defined this category and its detection is the reference the rest of us are measured against. What changed is the product around it: it is now a technographics and lead-generation platform, with the browser extension listed under a paid plan and free accounts capped at fifty lookups a month. If you are buying prospect lists filtered by tech stack, nothing here competes with it.
Prospect lists filtered by tech stack: Wappalyzer. Naming this page’s stack with the marker that matched: LoupeKit.
Wappalyzer
Paid plans · account required · lead-generation platform
A detection engine wrapped in a sales tool. Its own pricing page puts the browser extension among paid features and gives free accounts fifty lookups and five alerts a month; the plans above that are priced per seat with lookup and API credit budgets, and are aimed at building prospect lists rather than at inspecting one page.
LoupeKit
Free · no account · Chromium and Firefox
Detection as an inspector rather than as a funnel. 1700 technologies across seven detection sources, and every row opens on the literal thing that matched - a DOM marker, an asset URL, a generator tag, a page global, a namespaced custom property, or a header on the page’s own response - with its confidence and a link to the documentation.
Feature by feature
8 of 10 rows differ · they are the shaded onesWhere LoupeKit stops, and why
2 of the rows above · each one is a decision- Lead lists and CRM enrichment
- That product is built on sending the sites you visit to a server that keeps them. This one does not have the permission to do it and does not want the business — detection runs on the document already open, and no audit runs without being asked for by name.
- Bulk lookups and an API
- Looking up ten thousand domains means crawling them, which is a different product with a different cost. LoupeKit reads the page you are on, which is why the detection can show the marker it matched on rather than a name from a database.
The same jobs, side by side
See what one page is built with
WAPPALYZER Sign in, and it counts against a monthly lookup budget.
LOUPEKIT Open the panel. There is no account and nothing is counted.
Know why a technology was detected
WAPPALYZER The result is the name and a category.
LOUPEKIT Every row shows the marker, URL, header or global that matched, and its confidence.
Build a list of sites using a framework
WAPPALYZER This is the product. Filters, alerts, CRM enrichment, exports.
LOUPEKIT Not offered, and not planned. One page at a time, on request.
Compare two sites’ stacks
WAPPALYZER Two lookups against the budget, read side by side yourself.
LOUPEKIT Pin one page, open another: what each runs alone, what both share, where versions drifted.
Check a detected version against known CVEs
WAPPALYZER Not part of the extension.
LOUPEKIT The served version, dated against published advisories.
Keep the reading off a server
WAPPALYZER A lookup is an account action.
LOUPEKIT Detection runs in the page. Only the audit, probes and advisories call anything.
Pick Wappalyzer if
If detection is an input to sales. Filtering thousands of domains by the technologies they run, watching for a competitor’s customers to migrate, or enriching a CRM are real jobs, they are what that platform is built for, and this extension does none of them and never will.
Pick LoupeKit if
If you are looking at one page and want to know what it runs, why the tool thinks so, and whether the version it serves has a published advisory against it - without signing in, and without a counter.
Run both
Reasonable, and they barely overlap in practice: one answers a question about a market, the other about the tab in front of you.
On accounts
The difference that matters here is not a feature, it is a threshold. An account turns "what is this built with" into an identified, logged and budgeted action, and the answer arrives from somebody else’s server. LoupeKit mints a device id locally on first run, has nothing to sign in to, and runs detection inside the page - the panel can tell you what a site is built with while you are offline.
TWO BUILDS9 browsers
Chromelisting in reviewFirefoxlisting in reviewBravelisting in reviewOperalisting in reviewEdgelisting in review4 moreChromium browsers: Arc, Vivaldi, Chromium, Opera GXthe Chrome buildCHECKED 17 AUGUST 2026
Every figure about Wappalyzer on this page was checked on that day against wappalyzer.com, including its pricing page, and nothing here is quoted from a review. Where a fact is not published anywhere we can point at, the table says so rather than estimating it. Products change; if something above is out of date, write to [email protected] and it will be corrected.
Wappalyzer and every other product name on this site are the trademarks of their own owners. LoupeKit is not affiliated with, endorsed by or sponsored by any of them.