Startup Fast Scraper — Launches, Websites & Contact Emails

Turn startupfa.st into a clean, structured dataset. Pick a category from the dropdown — "All categories" or any of 37 verticals — or paste specific Start URLs and let each one be auto-classified.

Get one row per startup/product launch with the essentials: name, tagline, the product's own external website (the lead-gen field), logo, categories, upvotes, launch type, and Twitter/X — plus an optional contact email harvested from each project's own site. Pure HTTP with a real Chrome TLS fingerprint, no browser.

Why Use This Scraper?

• ✅ Pick by category or by URL — choose one of 37 verticals (or "All categories"), or paste /projects, /categories, /, /trending, /directory URLs; each is auto-classified
• ✅ The product's own website on every row — websiteUrl is the external site the launch links to, ready for outreach and enrichment
• ✅ Optional contact email per project — harvested from the product's own website (billed only when an email is actually found)
• ✅ Listing-level or full detail — keep scrapeDetails on for the full field set, or turn it off for cheap, fast rows
• ✅ Catalog coverage built in — a server-rendered category sweep plus related-project discovery walks beyond a single page
• ✅ JSON or CSV output, ready for spreadsheets, CRMs, and newsletters

Overview

The Startup Fast Scraper is built for founders, marketers, and researchers who want startupfa.st launch data in a spreadsheet instead of a browser tab.

The output is project-shaped rows — one row per startup/product launch (rowType: "project"). Whether you start from a category, the homepage, the trending feed, or a direct project URL, the dataset is a single stream of project rows.

The parser reads startupfa.st's server-rendered HTML — Open Graph / Twitter meta tags plus the page's React flight data — rather than driving a headless browser, so it stays fast and cheap and passes Cloudflare on a Chrome TLS fingerprint. There is no official API; everything comes from public pages. URLs are auto-classified by shape — you just paste them, you don't tag them.

Supported Inputs

URL types

URL type	Pattern	Example
Project detail	/projects/{slug}	https://www.startupfa.st/projects/oria
Category listing	/categories?category={slug}	https://www.startupfa.st/categories?category=ai
Homepage	startupfa.st/	https://www.startupfa.st/
Trending feed	/trending	https://www.startupfa.st/trending
Directory	/directory	https://www.startupfa.st/directory

Category, homepage, trending, and directory URLs fan out to project rows and stop once maxItems is reached. A direct /projects/{slug} URL emits a single project row.

Copy-pasteable startUrls

{
  "startUrls": [
    "https://www.startupfa.st/projects/oria",
    "https://www.startupfa.st/categories?category=ai",
    "https://www.startupfa.st/",
    "https://www.startupfa.st/trending",
    "https://www.startupfa.st/directory"
  ]
}

startUrls accepts both plain strings ("https://…") and request objects ({ "url": "https://…" }) — mix freely. When startUrls is set, it overrides the category dropdown.

Unsupported inputs

• ❌ Content behind a startupfa.st login (drafts, account settings)
• ❌ Hosts outside startupfa.st
• ❌ The full client-side-paginated /directory listing in one shot — see the catalog-completeness FAQ below

Use Cases

Audience	Use case
Founders & indie makers	Track new launches in your vertical, study winning taglines, benchmark upvotes
Sales / lead-gen	Build prospect lists from each project's own website, plus optional contact emails
Marketing & growth teams	Turn a category sweep into outreach-ready rows with sites and socials attached
Researchers & analysts	Bulk-export launches by category for SaaS/indie market research
Newsletter & directory builders	Feed fresh launches by category into a roundup or your own directory
Competitive analysis	Watch who's shipping in your space and where they live online

How It Works

1. Input — pick a category (one of 37, or "All categories"), or paste any mix of startupfa.st URLs
2. Discover & fan out — the server-rendered category sweep (/categories?category={slug}) plus the homepage and trending feeds list projects; each project's detail page seeds BFS discovery from its related-project links
3. Fetch — pages are retrieved over HTTP with a real Chrome TLS fingerprint (passes Cloudflare without a browser)
4. Parse & enrich — Open Graph / Twitter meta tags and the React flight data are read for the full field set; optionally fetch a contact email from each project's own website
5. Output — one project row per launch, as JSON or CSV

Input Configuration

Field	Type	Required	Notes
category	string (enum)	no	Default all. Which startupfa.st category to scrape. all sweeps every category plus the homepage and trending feed. One of 37 slugs scrapes just that vertical. Ignored when startUrls is set.
startUrls	array<string | { url }>	no	Optional. Specific startupfa.st URLs (/projects/{slug}, /categories?category={slug}, /, /trending, /directory). Auto-classified. Overrides category.
scrapeDetails	boolean	no	Default true. Fetch each project's detail page for the full field set (name, tagline, website, logo, upvotes, launch type, Twitter, categories). Turn off for cheap listing-level rows (url + slug + categories) without a detail fetch — faster and lower cost.
enrichEmails	boolean	no	Default false. Harvest a contact email for each project from its own website; adds contactEmail, contactWebsite, and a detailed emailEnrichment object. Billed per email found — never charged for a miss. Requires scrapeDetails.
maxItems	integer	no	Hard cap on total project rows. Default 1000. Free-tier runs are capped lower.
maxConcurrency	integer	no	Detail pages fetched in parallel. Default 8 (6–10 is the sweet spot).
minConcurrency	integer	no	Minimum parallelism. Default 1.
maxRequestRetries	integer	no	Per-URL retry budget (each retry uses a fresh proxy session). Default 5.
proxy	object	no	Defaults to Apify Proxy. The Chrome TLS fingerprint usually passes without a proxy; supply your own residential pool if you hit rate-limits.

category enum

all (All categories), plus: ai, analytics, api, ar-vr, blockchain, cms, data-science, databases, design-tools, developer-tools, devops, ecommerce, edtech, finance-tech, gaming, graphics, greentech, hardware, healthtech, iot, machine-learning, marketing-tools, mobile-dev, nlp, open-source, platform, productivity, prototyping, robotics, saas, sales-tools, security, serverless, testing-qa, ui-ux, wearables, web-dev.

Common scenarios

1. One category, full details

{
  "category": "ai",
  "scrapeDetails": true
}

2. Every category, with contact emails

{
  "category": "all",
  "scrapeDetails": true,
  "enrichEmails": true
}

3. Specific projects only

{
  "startUrls": [
    "https://www.startupfa.st/projects/oria",
    "https://www.startupfa.st/projects/soniox"
  ]
}

Output Overview

Each dataset item is a single shape, rowType: "project" — one row per startup/product launch, from a category, the homepage, the trending feed, the directory, or a direct project URL.

Notes on when fields are populated:

• scrapeDetails: false emits cheap listing-level rows (url + slug + categories) and skips the per-project detail fetch. With it on (default), each row carries the full field set below.
• upvoteCount is nullable — premium launches sometimes omit the count on their page.
• twitter, websiteUrl, and logoUrl are best-effort and may be null if a project doesn't expose them.
• contactEmail / contactWebsite / emailEnrichment appear only with enrichEmails and only when an email is actually found.

Output is JSON by default; the Apify Console "Export" tab flattens it to CSV.

Output Samples

Project row — category-discovered

{
  "rowType": "project",
  "url": "https://www.startupfa.st/projects/oria",
  "slug": "oria",
  "projectId": "9f4c7242-2ccc-4cd0-9715-416c1fdcb697",
  "name": "Oria",
  "tagline": "AI for complex professional slides in PowerPoint",
  "websiteUrl": "https://www.oria.one",
  "logoUrl": "https://9s82gn6mgv.ufs.sh/f/gCFgcDLxaF0QCrjG3gFSemd5A61rpuQblhcOwq3svjXHYfg8",
  "upvoteCount": null,
  "launchType": "premium",
  "twitter": null,
  "categories": ["ai"],
  "scrapedAt": "2026-06-23T16:46:02.089Z"
}

Project row — with enrichEmails

{
  "rowType": "project",
  "url": "https://www.startupfa.st/projects/oria",
  "slug": "oria",
  "name": "Oria",
  "websiteUrl": "https://www.oria.one",
  "categories": ["ai"],

  "contactEmail": "hello@oria.one",
  "contactWebsite": "https://www.oria.one",
  "emailEnrichment": {
    "emails": ["hello@oria.one"],
    "website": "https://www.oria.one"
    /* … source/provenance detail … */
  },

  "scrapedAt": "2026-06-23T16:46:02.089Z"
}

Key Output Fields

Identity & links

• rowType — always "project"
• url — the startupfa.st project page
• slug — the project's URL slug
• projectId — startupfa.st's internal UUID
• name — the launch's display name
• tagline / description — the one-line pitch
• websiteUrl — the product's own external website (the lead-gen field)
• logoUrl — the project's logo image
• twitter — Twitter/X handle or URL (nullable)

Classification & engagement

• categories[] — the project's category slugs (e.g. ["ai"])
• upvoteCount — upvotes on the launch (nullable — premium launches sometimes omit it)
• launchType — the launch tier (e.g. "premium")

Enrichment (with enrichEmails)

• contactEmail — the best contact email found on the product's own website
• contactWebsite — the site the email was harvested from
• emailEnrichment — the full enrichment object (all emails found + provenance)

Metadata

• scrapedAt — ISO timestamp of the scrape

FAQ

Which startupfa.st URLs are supported?

Project detail (/projects/{slug}), category listings (/categories?category={slug}), the homepage (/), the trending feed (/trending), and the directory (/directory). Mix any of them in startUrls, or skip URLs entirely and just pick a category from the dropdown.

Do I get one row per project?

Yes. Every entry point fans out to project rows (rowType: "project"). There are no separate category or feed rows — the dataset is a single stream of launches.

Does it need a login?

No. The actor reads only publicly available startupfa.st pages. Nothing behind a login is in scope.

Does it use the official startupfa.st API?

There isn't one. The scraper parses the public server-rendered HTML — Open Graph / Twitter meta tags plus the page's React flight data. No private or authenticated endpoints are touched.

What does scrapeDetails change?

With it on (default), each discovered project's detail page is fetched for the full field set (name, tagline, website, logo, upvotes, launch type, Twitter, categories). With it off, you get cheap listing-level rows (url + slug + categories) and no per-project fetch — faster and lower cost.

Why is upvoteCount sometimes null?

Premium launches sometimes don't render an upvote count on their page, so there's nothing to read. The row is still emitted with every other field populated.

How complete is the catalog?

The category sweep returns the server-rendered projects for each vertical (roughly the first pages), and related-project discovery (BFS) then walks outward from each project's links to reach more. The full /directory listing is paginated client-side (loaded by JavaScript after the page loads), so it isn't enumerated in one shot — but the category sweep plus related discovery cover the catalog well. Raise maxItems to collect more.

Is email enrichment guaranteed?

No. enrichEmails is best-effort — a project's website may not publish an email, may load it via JavaScript, or may obfuscate it. You're billed only when an email is actually found, never for a miss.

Can I export to CSV?

Yes. Output is JSON by default; the Apify Console "Export" tab flattens it to CSV (or JSON, Excel, etc.).

What about rate limits?

The scraper runs cleanly at maxConcurrency=8 on a Chrome TLS fingerprint that usually passes Cloudflare without a proxy. Lower the concurrency or attach a residential proxy under proxy if you ever see soft-blocks.

Support

Found a bug, hit a block we don't detect, or want another URL kind supported? Open an issue on the actor's Issues tab, or reach out via the memo23 profile on Apify.

Additional Services

Need a custom export shape, a new entry point, or scheduled monitoring? I build tailored scrapers and enrichment pipelines — get in touch via the memo23 profile.

Explore More Scrapers

If you track startup launches, founders, and prospects, these pair well:

• Product Hunt Scraper — the other big launch directory: votes, reviews, makers, and emails
• Y Combinator Scraper — companies + jobs from YC
• G2 Scraper — see how a launched SaaS ranks on G2 reviews
• Trustpilot Scraper — customer sentiment for products you discover
• LinkedIn Profiles Scraper — backfill founder profiles

Full portfolio: apify.com/memo23.

---

⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by startupfa.st or any of its parent companies or subsidiaries. All trademarks mentioned are the property of their respective owners.

The scraper accesses only publicly available startupfa.st pages — no authenticated endpoints, drafts, or content behind a login. Users are responsible for ensuring their use complies with startupfa.st's Terms of Service, applicable data-protection law (GDPR, CCPA, etc.), and any contractual obligations of their own organization. Harvested contact emails are personal data — process them responsibly, honor opt-outs, and seek legal advice before outbound marketing.

---

SEO Keywords

startupfa.st scraper, scrape startupfa.st, startup fast scraper, startup launch scraper, product launch scraper, startup directory scraper, indie launch tracker, startupfast.st api, Apify startupfa.st, startup category scraper, saas launch tracker, new product launch data, startup website scraper, founder contact scraper, b2b lead generation data, startup market research, product directory scraper, launch newsletter data, startup discovery tool, scrape startup launches