StackScope Data

Find out what new products are built with, the week they launch. Which ones chose your tool, which chose a competitor, which mention the words you watch for, and what the rest of their stack looks like.

Paid features How billing works API reference

Pricing

Billing. Billed monthly by card, change or cancel from your account. Every request costs one credit and each launch you access counts once a month against the allowance. When either runs out we stop, with no overage charge. How billing works

Not sure yet? You can try it before you subscribe. Write to [email protected] and we will set you up with a trial key.

What you agree to. Every plan is covered by the paid data terms and licence. Your product may show parts of the data alongside analysis or functionality of its own, but it may not let users extract, query or rebuild the corpus, or stand in for StackScope itself.

Full comparison every limit on every plan

What people use this for

Vendors watch a competitor. A standing watch on another tool's technology tells you when a new launch ships with it, in the week the choice was made instead of at renewal.

Agencies run it the other way round, and find new sites in their own country running the stack they work in, new enough that nobody has been appointed yet.

Analysts want the shape more than the rows, and track how the share of new launches on a given framework moves month to month, measured on a population that is genuinely new.

Inside a product, a lookup on a signup's domain returns its stack, hosting and launch date in one call, which is enough to route or score an account before anyone speaks to it.

Anyone selling to a market rather than a stack watches for words instead: a new site that mentions photogrammetry or drone surveying, the week it goes live, whatever it is built with.

Paid features

• Explore. Pick a slice of the corpus and see what is in it: a technology, a product type, a country, a launch type, a date range. Looking is free.
• Stackdar alerts. Standing watches over newly detected launches, by email digest, Slack or webhook. "Tell me when a new launch ships with Supabase", or "when a site launches with photogrammetry in it".
• Downloads. Pick your filters on the download page and get a spreadsheet back.
• The API. Look up a domain, query the corpus as lists, export any of it.
• AI assistants. Paste https://mcp.stackscope.dev into Claude, ChatGPT or Cursor and ask in plain language.

More about these features API reference

The numbers

The web-scale directories index everything. We index the newest slice of it, found mostly by our own discovery pipeline, and analyse each site at launch time instead of on a revisit schedule.

These are queried live from the corpus. They are cached for a few hours and move constantly.

Sites indexed in total	3,580,172
Available through the API and feeds	3,499,355
Of those, promoted as indie launches	638,910
Indie launches promoted from discovery	614,869
Added from launch channels, past 7 days	573
Added from discovery, past 7 days	441,000
Active technology fingerprints	51,172
Technology categories	132
With full launch-time analysis (infra, quality, agent signals)	29,281
Launches under liveness tracking	29,136
Reached a launch platform, past 7 days	7,023
Of those, already on StackScope first	1,251 (17.8%)
When we were first, days ahead on average	17.3

Sites indexed means every site we have crawled and detected technology on, including the broad discovery stream: local businesses, corporate sites, and the general new web our pipeline finds alongside launches. That pipeline came online in July 2026, which is why a single week of inflow is a large fraction of the total.

The paid products serve that corpus with one exception. No Product Hunt data goes through any paid service. A site listed on Product Hunt is served only where our own discovery pipeline found it independently, and never with Product Hunt's name, tagline or link attached.

The last three rows measure how often we get there first. Every launch that reached Product Hunt, Hacker News or PeerPush in the past week counts in the denominator, including the ones we never found, so the figure does not just count our wins. It has climbed since the discovery pipeline came online, and the days-ahead figure covers only the launches where we were in front.

Most of what we index is not a startup launch. Promoted as indie launches is the slice our review classed as an actual launch; the rest are real sites of every other kind. Every row carries an indie flag and the endpoints take an indie filter, so you can query launches only, the wider web only, or all of it.

The two inflow rows are split because almost all of the weekly inflow comes from our own discovery pipeline rather than public launch directories. They count sites as they arrive, before review, so they are much larger than the promoted totals above them. Most of what discovery finds is a real site but not a launch, and is never promoted.

How billing works

Two things are metered. Every data request costs one credit, whether it is a lookup, a feed page or an export. Setting up watches and using the status endpoint are free. Separately, each distinct launch you access in a month counts once against your monthly allowance. Accessing the same launch again that month does not count again.

If we later remove a site from the corpus, as spam or a scam or anything else that should not have been listed, the launch you spent on it stops counting against your allowance. You get the headroom back and your account page shows how many were credited.

Launches that Stackdar sends you count against the same distinct-launch allowance, because they are the same records the API returns. They cost no credits, since you did not make a request for them. When the allowance is reached, Stackdar pauses your watches and tells you. They restart when your billing period resets and pick up from launches shipping then, rather than replaying a backlog of launches that are no longer new.

The two meters work differently. A lookup costs one credit and accesses one launch. An export costs one credit regardless of size, but every launch it returns counts against your distinct-launch allowance. A large export can therefore use the whole allowance at once. Launches you have already accessed during that billing month do not count again. API responses include X-StackScope-Credits-Remaining and X-StackScope-Launches-Remaining so you can see both balances as you go.

Prices are billed monthly, in the currency shown at checkout: pounds in the UK, dollars elsewhere. StackScope is not VAT registered, so no VAT is added and none appears on your invoice. Credits do not roll over and there are no automatic overage charges. When your allowance runs out, we stop there and never bill you for more.

Changing plan. You are not locked to a tier. Moving up applies straight away, with the difference added to your next invoice. Moving down takes effect at the end of the period you have already paid for, so you keep the larger plan until then. Cancelling works the same way. All of it is self-serve from your account.

API keys keep the permissions they had when they were created. After an upgrade, create a new key to use the extra endpoints; your old key will keep working for everything it already had access to.

Where we draw the line

A record is a launch-time observation. It tells you what a site shipped with when it launched, not a guess about what it runs today. There is no scheduled recrawl of the back catalogue, so this data does not support stack-change alerts on existing domains. What each field claims, how liveness and quality scores read, and what the two launch types mean, are set out in the API reference.

We do not serve detection methods, matching rules, or the evidence behind individual detections: a payload tells you what was detected, never how. There is no on-demand scanning of arbitrary domains, no raw DNS records, only the results we derive from them, and no personal data in anything we serve.

Where a site publishes a general business email address, such as hello@ or support@, or has a contact form, we may include it. We do not collect named people's contact details.

Getting access

Subscribing takes you to Stripe, which collects your email and card details; we never see your card details. You will be asked to accept the paid data terms and licence as part of checkout. Your account and API key are ready as soon as the payment goes through.

Back to plans and pricing Read the data licence