What is Rearview?
Rearview is a change-tracking tool that puts every production-affecting change from across your stack — deploys, feature flags, Stripe billing settings, CMS edits, site changes — onto one searchable timeline. When a metric moves or something breaks, anyone on the team can ask “what changed?” in Slack and get a plain-English answer in seconds, instead of checking six tools by hand.
How is Rearview different from a deploy tracker?
Deploy trackers only see code, and most production incidents don't start with code. A price edited in Stripe, a feature flag pushed to 100%, a page republished in the CMS, a record changed in Airtable — none of that reaches GitHub, so a deploy tracker shows a clean week while the actual change sits somewhere else. Rearview tracks those invisible, non-code changes alongside deploys, which is the whole point: the change graph across tools, not the deploy log.
Which tools does Rearview connect to?
Rearview connects to Stripe, Shopify, Webflow, Contentful, Sanity, GitHub, GitLab, Vercel, LaunchDarkly, and Airtable. There is also a catch-all Change Events API, so any tool that can send a webhook — including internal admin panels and homegrown feature-flag systems — can post changes to the same timeline in a few lines of code.
Do I need to be technical to use Rearview?
No — Rearview is built for whoever gets asked “what changed?”, which is usually a founder, PM, support lead, or ops person rather than an engineer. Asking is a plain-English question in Slack, and the answer comes back in plain English with links to the underlying change. Connecting the tools in the first place is a one-time setup that does need someone with admin access to those tools.
What if a tool we use isn't supported yet?
Any tool that can send a webhook can post to Rearview's Change Events API — a single authenticated endpoint that accepts a change as JSON: a title, a timestamp, who made it, and an optional link. That covers unsupported SaaS tools, internal admin panels, and homegrown feature-flag systems, all landing on the same timeline as the native integrations. In practice this is how teams cover the long tail of tools that will never have an official connector.
How does Rearview decide what counts as a critical change?
You define the rules yourself — Rearview lets you mark which kinds of change are production-critical, such as anything touching payments, a feature flag reaching 100% of users, or a price change. The moment one of those ships, a real-time alert goes to Slack. Everything else still lands on the timeline quietly, so the alerts stay rare enough that people keep reading them.
Does Rearview replace monitoring tools like Datadog or Sentry?
Rearview does not replace monitoring tools, and deliberately doesn't try to. Monitoring tells you that something is wrong — error rates, latency, a failing check. Rearview tells you what changed right before it went wrong. They answer different halves of the same incident, so most teams run Rearview alongside Datadog or Sentry rather than instead of them.
Is Rearview available yet?
Rearview is pre-launch and running a waitlist at joinrearview.com. The product is built and working; access is being opened gradually to design partners first so each integration can be verified against a real account before the team relies on it. Pricing has not been finalised.