← Back to home
Sparkpulse · how it works

Frequently asked

A 5-minute read on how Sparkpulse classifies releases, computes velocity, and writes its daily and weekly editorial.

What is Sparkpulse?

Sparkpulse is an editorial AI radar for SaaS products. We track every release across the catalog, then interpret each product's recent moves as editorial — not raw changelog logs. For each release we ask: what just shipped, what does it mean for the product's trajectory, and is this a directional move or noise?

Concretely, every active product gets a sector trajectory page; significant releases surface as sparks on the home feed; and each morning a daily brief ties the day's most directional moves into one read.

What is a "spark"?

A spark is a release that changes a product's direction or capability surface. New model integration, agentic feature, pricing pivot, category-redefining move — that's a spark.

For every changelog entry, our editorial commentator picks one of three classifications:
  • Spark — directionally significant. Surfaces on the homepage spark feed.
  • Improvement — incremental but non-trivial.
  • Trivial — bug fixes, copy edits, infra tweaks.
Sparks are rare on purpose. ~5–10% of releases qualify.

What is the velocity score?

Velocity is a 0.0–10.0 score per product capturing how directionally active the product has been over the last 30 days. We compute it as an additive blend:
  • Sector-relative cadence (0–10): how the product's release count compares to its sector median.
  • Spark count (0–10): how many spark-classified releases shipped in 30 days.
Final velocity = 0.5 × cadence + 0.5 × sparks, clamped to [0, 10]. The leaderboard ranks by velocity desc.

How is the daily brief written?

Every morning, our editor reads all product commentary from the past 24 hours, picks the day's most directionally significant moves, and writes one brief — lead, "what moved", "sectors today", "watch tomorrow". Grounded entirely in observable patterns from the day's releases. See the latest at /brief/today; browse history at /briefs.

What is a weekly sector report?

Each Monday we publish one report per active sector (sectors with ≥3 products updated that week). Lead pattern, leaders, wildcards, themes, watch this week. Browse them at /weekly-reports.

How do "trending comparisons" surface?

We don't track user view counts. Pairs are editorially-derived:
  • Both products in the same sector
  • Both shipped a spark in the last 7 days
  • Velocity scores within 2 points of each other
  • ≥1 shared theme tag
Compare any pair at /compare/A-vs-B.

Who writes Sparkpulse?

Two editors: Yahya Tür (DevTools, development, analytics, design, video conferencing, collaboration) and Onur Öztürk (comms, marketing, CRM, support, HR, PM, finance, accounting, e-commerce, EdTech). Each editor's byline is sticky per product.

How does follow work?

Follow products from any product page, and sectors from the sectors index or sector hero. Your personal feed shows spark releases from anything you follow — your own editorial wire.

Where does the underlying data come from?

Releases come from each product's own changelog — RSS, GitHub releases, or HTML scrapes via stored CSS selectors. Crawled on per-product cadence. The crawler dedupes via SHA-256 content hash. No press releases, no rumors.

How often are things updated?

  • Crawler — rolling per-product (hourly to daily)
  • Commentator — hourly batches of up to 20 products
  • Velocity score — recomputed each commentary run
  • Daily brief — ~09:00 UTC each morning
  • Weekly sector report — ~08:00 UTC each Monday

You got something wrong about my product. How do I flag it?

Open the product page and use the source link to flag a release we missed or misread, or email editorial@sparkpulse.io with the slug and the correction. Editorial corrections land in the next commentator run.