Get started
How it worksLive scanDocsPricingGet started
feature-level change intelligence

Know what every PR changes in your product — not just in your code.

Wystan maps your repository into named product features and user flows, then comments on each PR with the affected journeys, structural reach and available evidence. Weekly movement goes to Slack; your coding agents read the same map over MCP. No SDK or manual instrumentation.

$99 / month includes 2 repos · unlimited teammates · no per-seat fees

Scan a public repo freeSee a real PR comment
what you actually get

Product impact, delivered before merge.

Every PR names the product features and user journeys it changes, with evidence your team can verify. Slack reports what moved week over week; MCP gives the same product context to your coding agent. The dashboard is there when you need the full map.

GitHub PR comment
Slack digest
GitHub PR comment
Slack digest
GitHub PR comment
Slack digest
GitHub PR comment
GitHub PR comment
Slack digest
Slack digest
GitHub PR comment
GitHub PR comment
the problems we solve

The decisions a file diff
can’t make.

Four engineering decisions, backed by a product map and inspectable evidence. Every metric documents what it measures, how it is computed and where it is weak.

This PR looks fine. What changes for the customer?

Wystan names the product features and user journeys this PR reaches, then links every claim back to the files and lines behind it. Review the product impact before you merge, not after a customer finds it.

before mergefeature + flow map

Where should our limited review time go?

Rank affected features by within-repository future fix-work rank, then inspect test evidence, shared-code reach, PostHog traffic and observed Sentry errors. The result is a review watchlist inside this repo — not a probability of failure.

within-repo rankfuture fix-work percentile

Is Checkout getting worse — or simply changing?

Track maintenance pressure, rework, test-evidence source and inactive-author ownership on stable feature identities across scans. The weekly digest reports evidence-backed movement in product language — and stays quiet when there is none.

week over weekstable feature IDs

Tests are green. What evidence exists for this journey?

See, per journey, whether an end-to-end test visits it, only integration tests reach its code, or nothing does — with the spec and test title as receipts. A static lower bound: unsupported e2e frameworks show as not measured, never untested.

per journeystatic lower bound
Every metric is documented — what it measures, how it’s computed, where it’s weak. Engine source-available (FSL).Read the metric docs →Browse real scans →
how it works

Code goes in. Product context comes out.

One scan turns repository structure and git history into a named map of product features, user flows and the code behind them. Incremental scans keep that map current as pull requests land. See it on a real scan →

security

Your source is processed, not retained.

Repository source is read in memory and never stored at rest on our side. Derived scan content is encrypted with per-scan keys and decrypted server-side only for authorised reads. Feature names, file paths and metrics are readable metadata in Standard today; Private mode, which encrypts those fields too, is on the roadmap.

Read the security page
Encrypted at rest, per-scan keysAES-256-GCM with a one-shot key per scan, wrapped by an HSM-backed KMS key; decrypted server-side only for authorised reads, every unwrap audit-logged.
No source code stored at restHistory is read in memory, mapped, and the working copy is discarded after each run — on every tier.
Encrypted in transit · KMS-backed secretsTLS everywhere; credentials live in a key-management service, never in code.
Read-only git access, least privilegeWystan never pushes, tags, or writes to your repositories.
Isolated, ephemeral scan jobsEach scan runs in a fresh container with no persistent volume; the working copy is destroyed when the job ends.
Source-available engine (FSL-1.1)The engine that touches your code is published under a source-available licence; every release converts to Apache-2.0 after two years.
see it on your code

See your product through the code.
Get your first impact report.

Read the docsScan a public repo free
read-only git accessno SDK to installfull report after every scan