SaaSpark · magazineBuild your stack →
About

How we work

SaaSpark is a curated, opinionated SaaS catalog — assembled by humans, refreshed by code, kept honest by review.

Why this exists

Launching a SaaS today means picking 15–30 tools across auth, payments, email, analytics, support, ops, and AI. For each category there are 50+ options. The market is well-served by directories (Product Hunt, G2, Capterra), but no one answers the real question: "what's the right stack for my profile?"

SaaSpark prescribes stacks, not isolated tools. Our atomic unit is the stack template — a curated bundle of 10–15 tools that work well together for a defined founder persona (B2B SaaS, AI wrapper, marketplace, B2C mobile, internal tool).

How content gets here

  1. Discovery. Daily, our pipeline pulls candidates from Product Hunt and curated RSS feeds. Editors also drop URLs into a review queue manually.
  2. Grounded extraction. Each candidate URL gets fetched (home + /pricing + /integrations), sent through Gemini Flash, and every extracted field is verified against a literal quote from the source. No hallucinations.
  3. Human review. An editor approves or rejects each fiche in the admin queue. Average time per fiche: ≤ 3 minutes. Only approved fiches land on saaspark.dev.
  4. Editorial drafts. Comparisons and "alternatives to X" pages are drafted by Gemini Pro from the verified tool data, then polished by an editor before publishing on saaspark.net.
  5. Weekly refresh. Every Monday a scheduled job re-extracts every published tool. Small pricing deltas auto-publish; anything material (name change, new tier, structural shift) drops back into the review queue.

What we don't do

Two domains

saaspark.dev is the product — the catalog, tool fiches, MCP registry, and the stack-builder. It owns every piece of tool-detail content.

saaspark.net is the magazine — comparisons, alternatives rankings, guides. SEO surface. Always points readers back to the product side for tool detail.

Want to suggest a tool?

Email hello@saaspark.dev with the URL. If it clears our editorial bar (active product, paid tier exists, real integrations) we add it to the discovery queue.

The detailed criteria live in our methodology.