Wappalyzer API Pricing 2026: After Going Closed Source

Wappalyzer is one of the names that comes up first whenever a developer needs to detect a website’s tech stack. For most of its life, it shipped a free Chrome extension and an MIT-licensed fingerprint database that anyone could fork and self-host. Then in 2023 the project went closed source — the database was relicensed under a commercial agreement, the public repo stopped accepting fingerprint contributions, and self-hosting against fresh data became a paid relationship.

Three years on, the question most teams are still asking is the same: what does Wappalyzer’s API actually cost in 2026, what do you get for the price, and is it the right tool for your use case? This guide walks through the pricing as published on Wappalyzer’s site at the time of writing, what changed after the closed-source transition, and where a focused detection API delivers the same outcome at a fraction of the cost.

Wappalyzer API Pricing in 2026 at a Glance

Wappalyzer publishes several paid tiers for its Lookup API and Lead List products. There is no perpetual free API tier — only a limited trial — and the cheapest plan that gets you usable monthly volume starts at around $250/month. Higher tiers add seats, more lookups, and access to the prospect-list product.

Two patterns are worth highlighting up front. First, the entry tier is positioned for sales-intelligence buyers, not developers prototyping a feature. Second, the product is sold by lookups and seats, so the price you eventually pay depends as much on team size as on call volume.

What Changed After Wappalyzer Went Closed Source

The Wappalyzer of 2026 looks different from the Wappalyzer most developers remember. Two shifts matter for anyone evaluating it as an API.

Timeline of the Closed-Source Transition

The relevant beats:

• Pre-2023 — Wappalyzer ships an open-source crawler and an MIT-licensed technologies.json file. Community contributions add fingerprints. Self-hosting is normal.
• 2023 — Wappalyzer relicenses the database under a proprietary commercial license. The GitHub repo is archived for fingerprint contributions. The hosted Lookup API and the prospect-list product become the canonical way to use the data.
• 2024–2025 — The hosted product matures. Pricing tiers expand to target sales teams alongside developers. The Chrome extension stays free for individual use, but the underlying database it depends on is no longer openly maintained.
• 2026 — Forks of the last MIT-era snapshot still exist on GitHub, but they steadily drift out of date. New frameworks, CDNs, and analytics tools land in the hosted product before they (if ever) make it back to the forks.

Impact on Self-Hosters and Open Source Users

If you originally adopted Wappalyzer because it was free and self-hostable, the closed-source transition pushes you to pick a path:

• Stay on the MIT-era fork. Detection still works for older frameworks, but accuracy on newer libraries and ecosystems decays month over month. Acceptable for hobby projects, painful for anything customer-facing.
• Pay for the hosted Lookup API. You get fresh data, but the price is calibrated for sales orgs, which makes the per-lookup cost feel high if your use case is detection-only.
• Switch to an alternative API that maintains its own active fingerprint database. Several detection APIs (including DetectZeStack, which uses an actively maintained fingerprint set built on the open-source wappalyzergo Go library plus our own DNS and TLS rules) target this gap.

None of these is wrong. The right answer depends on whether your project tolerates stale fingerprints, your call volume, and how much you can spend on data.

Wappalyzer API Plans and Per-Lookup Costs in 2026

The pricing page on wappalyzer.com is the canonical reference, and tiers do change. As of writing, the lineup looks like this.

Free Tier and Trial Limits

Wappalyzer offers a trial, not a perpetual free tier. You get a small number of lookups to evaluate the API shape and confirm it returns the technologies you need. Once you exceed the trial, you have to pick a paid plan. For a developer prototyping a feature, the trial is enough to confirm the JSON shape but not enough to back a real product.

The free Chrome extension is a separate product. It is fine for ad-hoc, manual checks while browsing, but it is not an API and you cannot script it for batch lookups, monitoring, or enrichment.

Paid Tiers and Volume Pricing

The headline numbers most developers see when shopping the Wappalyzer API:

• Standard (~$250/mo) — Lookup API access with a monthly cap. No prospect lists. Suitable for small-volume integrations and individual users.
• Plus — Higher monthly price. Adds the lead/prospect lists product (filter the web by technology to build outbound lists), more seats, and a larger lookup quota.
• Enterprise — Custom pricing. Larger lookup quotas, bigger team seats, priority support.

Two structural points to remember. (1) The published prices typically assume annual billing — month-to-month is more expensive. (2) Several plans charge per seat, so a 3-person team can effectively pay 3x the headline number for the same workload. Read the small print on the plan you are about to pick.

If you divide the entry-tier price by its monthly lookup cap, the implied per-lookup cost on Wappalyzer’s Standard plan lands in the low cents range. That is fine for sales prospecting, where each enriched lead is worth dollars. It is rough for an SEO dashboard, a portfolio analyzer, or any feature where you call the API on every page view.

What You Get for the Price: Features and Data Coverage

The Lookup API itself is straightforward. You hand it a URL, it returns a list of detected technologies with categories and metadata, plus a confidence score. Wappalyzer’s strengths in 2026:

• Mature fingerprint database. Years of accumulated patterns covering JavaScript frameworks, CMS platforms, ecommerce systems, analytics, ad networks, and hosting/CDN providers.
• Bundled prospect lists on higher tiers. If you want to email every Shopify store using Klaviyo, the higher Wappalyzer plans support that workflow natively.
• Brand recognition. Stakeholders recognize the name. That has value if you are pitching the source of your data internally.

The honest tradeoffs:

• Detection-only buyers pay for products they will not use. If you only need “what is this site running right now,” the Plus and Enterprise pricing bundles in lead-list and trends products you do not need.
• Closed-source database. You cannot inspect, fork, or contribute fingerprints. If a category you care about is under-covered, you wait.
• HTTP-only signals on the public Lookup API. DNS-only signatures (e.g., MX records that reveal Google Workspace or Microsoft 365), TLS issuer patterns, and security-headers data are not part of the same response shape.

When Wappalyzer Pricing Makes Sense (and When It Doesn’t)

Wappalyzer’s 2026 pricing is well calibrated for some buyers and poorly calibrated for others. The honest split:

Wappalyzer is a fit when:

• You are a sales team doing technographic prospecting and the lead lists pay for the plan in one closed deal.
• You are an analyst tracking technology adoption trends and need a recognized data source for reports to stakeholders.
• You are a large enterprise where vendor brand and procurement-friendly contracts matter more than per-call cost.

Wappalyzer is a poor fit when:

• You are an indie developer adding a tech-detection feature to a side project with $0–$50/month total infrastructure budget.
• You are building a SaaS feature where the API is called once per user action and you need predictable per-call unit economics.
• You need DNS, TLS, or security-headers data alongside HTTP-based detection in a single response.
• You want to evaluate the API end-to-end before paying anything.

Comparing Wappalyzer API Pricing to Other Detection APIs in 2026

Wappalyzer does not exist in a vacuum. Three other names show up in the same evaluation cycle: BuiltWith, SimilarTech, and DetectZeStack. The price spread is wide.

At low volumes, the spread between $0/$9 and $250+ is the difference between “ship the feature this weekend” and “ask procurement.” At high volumes (millions of lookups), the calculus shifts and you re-evaluate based on data quality and SLAs. Most teams are not at high volume on day one.

Try a Live Tech Stack Detection API in Under a Minute

The fastest way to compare detection APIs is to call one. DetectZeStack’s /demo endpoint requires no API key and no signup, so you can paste it into a terminal right now and see exactly what the JSON looks like.

Example: Detecting a Tech Stack with curl

$ curl -s "https://detectzestack.com/demo?url=stripe.com" | python3 -m json.tool

A trimmed example response (real shape, real fields):

{
  "url": "https://stripe.com",
  "domain": "stripe.com",
  "technologies": [
    {
      "name": "React",
      "categories": ["JavaScript frameworks"],
      "confidence": 100,
      "description": "React is an open-source JavaScript library for building user interfaces.",
      "website": "https://reactjs.org",
      "icon": "React.svg",
      "source": "http",
      "version": "",
      "cpe": ""
    },
    {
      "name": "Cloudflare",
      "categories": ["CDN"],
      "confidence": 100,
      "description": "Cloudflare is a web-infrastructure and security company.",
      "website": "https://www.cloudflare.com",
      "icon": "CloudFlare.svg",
      "source": "http",
      "version": "",
      "cpe": ""
    }
  ],
  "categories": {
    "JavaScript frameworks": ["React"],
    "CDN": ["Cloudflare"]
  },
  "meta": {
    "status_code": 200,
    "tech_count": 14,
    "scan_depth": "full"
  },
  "cached": false,
  "response_ms": 1842
}

Once you have an API key, the production endpoint uses the same shape with authentication via the RapidAPI proxy:

$ curl -s "https://detectzestack.p.rapidapi.com/analyze?url=shopify.com" \
  -H "X-RapidAPI-Key: YOUR_KEY" \
  -H "X-RapidAPI-Host: detectzestack.p.rapidapi.com" \
  | python3 -m json.tool

Example: Comparing Two Sites in One Workflow

One pattern that comes up a lot in evaluation: pick two sites you know well and run the same call against both. If the technologies you expect (React, Next.js, Tailwind CSS, Cloudflare, Stripe, Google Analytics, HubSpot, WordPress, Shopify) all appear with sensible confidence scores, the API is doing its job. If they do not, you have an answer about data quality before you spend a dollar.

$ for url in stripe.com shopify.com; do
    echo "=== $url ==="
    curl -s "https://detectzestack.com/demo?url=$url" \
      | python3 -c 'import json,sys; d=json.load(sys.stdin); print("\n".join(t["name"] for t in d["technologies"]))'
  done

The free demo endpoint is rate-limited per IP, so do not loop over thousands of URLs. For batch work, sign up for a key and use /analyze.

Pricing Math: Wappalyzer vs DetectZeStack at 10K Lookups/Month

To make the comparison concrete, suppose you need 10,000 detections per month for a feature in your product, an enrichment pipeline, or a monitoring job that scans a list of vendors every day.

At 10,000 lookups per month, DetectZeStack costs roughly an order of magnitude less per lookup than Wappalyzer’s entry tier, and ~$2,650 less per year in absolute terms. That is the difference between a credit-card line item and a procurement conversation.

How to Choose Between Wappalyzer and Lower-Cost APIs

The decision tree most teams arrive at, after going through this evaluation:

1. Do you need lead lists or technographic prospecting? If yes, Wappalyzer’s Plus tier or BuiltWith’s Pro plan are designed for that workflow and will pay for themselves in closed deals. Buy the bundle.
2. Do you need detection only? Skip the bundled products. The detection capability is now commoditized; pick the API with the best price-per-call and the right data shape for your code.
3. Do you need DNS, TLS, or security-headers data alongside detection? Wappalyzer’s Lookup API is HTTP-focused. DetectZeStack ships these signals as part of the same product surface.
4. Do you want to evaluate before paying? Wappalyzer offers a trial, not a perpetual free tier. DetectZeStack offers 100 free requests per month with no credit card.
5. Are you a large enterprise with procurement constraints? Brand and contract terms may push you toward Wappalyzer or BuiltWith regardless of per-call price.

The cheapest answer is not always the right one. But if you are an indie developer or a small team, the cost difference between $9–$29/month and $250+/month is large enough that it deserves a deliberate decision, not a default.

Conclusion: Picking the Right Detection API for Your Budget

Wappalyzer’s 2026 pricing reflects a deliberate repositioning of the product after the closed-source transition. The hosted Lookup API and the prospect-list bundle are calibrated for sales-intelligence buyers, not for developers prototyping a feature on the weekend. If your use case matches that buyer profile, the price is fair and the data is good.

If your use case is “detect what tech a site is running right now, in code, on every call,” the math is harder to justify. The detection capability is no longer the scarce ingredient it was when Wappalyzer first shipped, and a focused detection API like DetectZeStack covers the same primary use case for roughly an order of magnitude less per call — while bundling DNS, TLS, security-headers, and CVE data that the Lookup API does not return in the same response.

Match the tool to the job. If you need lead lists and brand-recognized data, pay Wappalyzer. If you need detection at developer prices, do not.