Launch Readiness Check Where to submit your launch

Terms of Use

Last updated: 8 May 2026

By using StackScope, you agree to these terms. They describe what you can do with the site, what claiming a launch grants, and the rules we apply when something goes wrong. If you disagree with anything here, please stop using the site.

What StackScope is

StackScope is a free, public directory that catalogues the technology stacks of product launch websites. We crawl publicly accessible pages and surface what we find: frameworks, hosting providers, security headers, DNS records, and other observable signals. The full data and analysis methodology is on the methodology page.

StackScope is independent and is not affiliated with, endorsed by, or sponsored by the products, companies, launch platforms, frameworks, hosting providers, or other services we reference unless we state otherwise.

Our analysis is educational. It is a snapshot taken at one point in time, based on signals our crawler can observe. It is not authoritative, and you should not rely on it for compliance, legal, security, or financial decisions.

Our checks are passive and based on publicly observable signals. We do not perform penetration testing, vulnerability scanning, exploit testing, or any private security assessment of listed websites.

Using the site

Browsing, searching, and reading launch pages is open to everyone. No account or sign-in required. You are welcome to link to our pages, share scores, and reference our analysis in articles, blog posts, or commercial work. If you cite our analysis or data in a published piece (an article, blog post, video, or commercial work), include attribution and a link to stackscope.dev. Casual references such as a tweet or private message are fine without.

What we ask you not to do:

  • Scrape, crawl, or otherwise programmatically extract data from the site
  • Republish our content or database in bulk; if you want structured access, write to us
  • Use automated tooling to claim launches you do not own
  • Submit URLs to the private analysis flow (Launch Readiness Check) for sites you do not control. Verification by ownership marker is required to proceed, so failed attempts are not a security issue, but we reserve the right to block IPs that repeatedly probe URLs they do not own
  • Misrepresent our analysis as authoritative or as an endorsement of a product
  • Use any part of the site to harass, defame, or threaten anyone

Search engines and other crawlers may index public StackScope pages where allowed by our robots.txt. This does not permit bulk copying, database replication, or automated use of the claim flow.

Third-party websites

StackScope links to and displays information about third-party websites. We do not control those sites and are not responsible for their content, availability, security, privacy practices, or anything that happens after you visit them.

Private site analysis (self-add)

You can submit your own site for a private analysis via the Launch Readiness Check. By submitting a URL you confirm you control it. We verify control by fetching an ownership marker from a path on the same domain; submissions without a verifiable marker do not produce a launch row.

What a successful self-add grants you:

  • A private launch row (owner-only) not surfaced in the public directory, sitemaps, or aggregate statistics
  • A private report URL and a re-scan trigger URL, each containing a single-purpose capability token. The trigger URL doubles as the removal action.
  • An initial crawl, with screenshots disabled, and rate-limited re-scans on owner request

What a successful self-add does not grant:

  • A public listing. Public listings are populated automatically from Product Hunt, Hacker News, and PeerPush. Your private launch will be converted to a public listing if you submit the same URL to any of those sources yourself; we recognise the match by hostname.
  • Any service-level commitment. The re-scan trigger is best-effort.
  • Indefinite retention of unvalidated submissions. Pending rows that never complete the marker step are deleted after a short window.

Claiming a launch

Anyone who can prove ownership of a launch's domain can claim it via the claim flow. The verification methods, including how to install an ownership marker and how to use the bookmark URL, are documented on the bot page. Claiming a launch is free.

What a successful claim grants you:

  • A public marker on the launch page indicating you are the owner
  • A private bookmark URL (/r/{token}) that triggers a fresh re-scan when you ship fixes
  • Access to a score badge you can embed on your own site
  • The ability to remove your launch from the directory at any time, via the trigger URL

What a claim does not grant:

  • Authority over the analysis content. Our scores, detected technologies, and tips are based on observable signals from the public web, and we do not change them on owner request beyond fixing factual errors.
  • Ownership of the launch page. The page belongs to the directory; the claim is a verified-owner annotation on it.
  • An ongoing relationship. Claiming is stateless on our side. We do not email you, contact you, or share your information with anyone.
  • Any guarantee of inclusion. We may hide, remove, or refuse claims at our discretion (see below).

Our discretion

We reserve the right to take the following actions where we reasonably think it is necessary to protect the site, users, launch owners, third parties, or the integrity of the directory:

  • Refuse claims for launches we judge to be scams, malware, gambling, adult content, or otherwise inconsistent with the educational mission of the directory
  • Revoke a claim if we have evidence the verification was forged, the domain has changed hands, or the launch is being misrepresented
  • Hide or remove launches in response to spam, abuse, security concerns, or copyright complaints
  • Correct or modify our analysis content at any time, with or without notice
  • Block visitors or IP ranges that disrupt the site or attempt to abuse the claim flow

We do not run a formal appeals process. If you think we have made the wrong call, write to [email protected] and we will look at it.

The data we hold about your claim

We do not require an email address, account, or password to claim. The capability URL we send you is the credential. Specifically what we store and how we handle it is described in the privacy policy. If anything in these terms appears to conflict with the privacy policy, the privacy policy governs how we treat data.

Private claim URLs

Your private bookmark URL is a capability link. Anyone who has the link may be able to trigger a fresh scan or access owner-only actions connected to that claim. You are responsible for keeping it secure. If you believe your private URL has been shared, guessed, or misused, contact us and we may revoke or replace it.

Intellectual property

The structure of the directory, the methodology, the scoring logic, the editorial copy, the StackScope name and logo, and our detection rules are ours. The detection rules in particular (the regexes, hashes, scoring weights, and classification logic) are proprietary, are not published, and may not be reverse-engineered, copied, or republished. The product names we display (Stripe, Shopify, and so on) are factual references and may be cited freely.

Screenshots, names, descriptions, logos, and other metadata of launches belong to their respective owners. We display limited excerpts and screenshots for identification, commentary, review, and directory purposes. If you are an owner and want a screenshot or other content removed, follow the removal process in the privacy policy.

No warranty

StackScope is provided as-is, with no warranty of any kind, express or implied. We make no guarantee about:

  • The accuracy of our technology detections, scores, tips, or other analysis
  • The availability or uptime of the site
  • The continued existence of any feature, page, URL, or score format

We try to be useful, but you should treat the directory as informative rather than authoritative.

Limitation of liability

To the fullest extent permitted by applicable law, StackScope and its operator are not liable for any indirect, incidental, special, consequential, or punitive damages arising from your use of the site, including loss of profits, data, goodwill, or business opportunities.

Nothing in these terms excludes or limits liability that cannot be excluded under English law (for example, liability for fraud or for death or personal injury caused by negligence).

Changes to these terms

We may update these terms as the project evolves. The "last updated" date at the top reflects the most recent substantive change. Continued use of the site after a change means you accept the updated terms. We do not collect email addresses, so we cannot notify you directly. Check back if you are concerned.

Governing law

These terms are governed by the law of England and Wales. Any dispute arising from your use of the site is subject to the exclusive jurisdiction of the courts of England and Wales.

Contact

Questions about these terms, about a specific launch page, or anything else: [email protected]. More about the project on the about page.