About Rewindex

Rewindex is an archive of how SaaS vendors change over time. Vendor pages overwrite themselves: a status page shows today’s version of an incident, a pricing page shows today’s prices, a subprocessor list shows today’s list. Once it changes, the old version is gone. Rewindex keeps every version.

What is archived

• Status-page incidents, polled every 10 minutes through each platform’s public JSON API (Atlassian Statuspage, incident.io, Better Stack, Instatus), plus each page’s published history back to its creation.
• Silent edits: every distinct version of every incident is hashed and kept, so a rewritten title, an edited or deleted update, a downgraded impact or a deleted incident is visible.
• Pricing, trust/security and legal pages (terms, privacy, subprocessors), fetched once a day. A new version is stored only when the visible text changes.

Method

• Change detection uses a SHA-256 hash of a canonical form of each document, so cosmetic churn (timestamps, counters) is not a change.
• Failures are data: every fetch attempt is logged, so gaps in coverage stay visible and uptime figures stay honest.
• Incident impact is the vendor’s own label. Durations are resolved minus started, as published.
• Pages are fetched politely by RewindexBot (see /bot), at most a few requests per host per day for pages.

Archive size

Access for people, agents and code

• Every page has a Markdown twin: add .md to the URL, or send Accept: text/markdown.
• JSON API at /api/v1 (OpenAPI 3.1).
• MCP server at /mcp (streamable HTTP).
• llms.txt and llms-full.txt.