DataSpice changelog

This is what has changed in DataSpice, newest first. It exists so that anyone deciding whether the product is actively maintained can answer that from evidence rather than from a marketing page. Entries are added when something ships, and dated with the day it shipped.

August 2026: the public pages became real HTML

Every public page is now rendered to static HTML at build time rather than assembled in the browser. Before this, an AI crawler that does not execute JavaScript received an empty document with the home page's title on every URL; now the full text, the metadata and the structured data are all in the response body.

  • All public routes prerendered: the home page, pricing, the FAQ, every comparison, every article, the legal pages, and the new documentation and use-case pages.
  • Per-page titles, meta descriptions and canonical URLs, unique on every URL.
  • Structured data server-rendered: Organization, WebSite, SoftwareApplication, FAQPage, BlogPosting and BreadcrumbList.
  • Five new comparisons: PostHog, Matomo, Simple Analytics, Umami and Cloudflare Web Analytics.
  • A missing page now returns a real 404 instead of the home page with a 200.
  • `llms-full.txt` added: the product summary and the full text of every article in one fetch.

August 2026: the writing section and AI insight fixes

  • A writing section on the public site, with six articles published from a single content file and mirrored as Markdown at `/blog/<slug>.md`.
  • AI explanations now reach the model correctly; the App Store history no longer takes two weeks to fill.
  • The Insights screen is marked as coming soon rather than shipping half-built.
  • A new brand mark across the public surfaces.

How this page is maintained

Entries are written when something ships and are not backdated. A changelog that is filled in retrospectively is a changelog that says nothing about whether the product is being worked on, which is the only reason to publish one.