Free
$0/ forever
Public repositories and evaluation
- 1 public / open-source repo · ~150K LOC
- Unlimited developers
- 1 full scan / mo · unlimited incremental
- 50 PR impact comments / mo
- Hosted MCP for Cursor / Claude Code / Cline
Pay for repos,
not developers.
Plans include the repositories Wystan keeps mapped; add more without buying seats. Pro stays $99 whether 8 teammates use the map or 50. Your first full scan is included.
Pro
$99/ org / mo
Product teams of ~8–50 engineers
- 2 repos included · +$25 / repo / mo
- Unlimited developers (never per-seat)
- 30 full re-scans / mo · unlimited incremental
- 2,000 PR impact comments / mo
- Weekly Slack digest + drift report
- Sentry + PostHog overlay
Scale
$299/ org / mo
Several products, bigger monorepos
- 10 repos included · +$19 / repo / mo
- ~5M LOC fair use
- 150 full re-scans / mo
- 10,000 PR impact comments / mo
- Everything in Pro
- Priority support
Repos are the unit you buy; codebase size (LOC) is a fair-use fence, not a meter; developers are never counted. Incremental scans re-map only what a push or PR changed — unlimited everywhere. Full re-scans rebuild the whole map (first scan, on-demand rescans, and the weekly calibration on paid tiers) and draw from your monthly cap.
Bigger, or need it in your own VPC? Self-hosting and SSO are on the roadmap — tell us what you need and we'll tell you honestly whether we're there yet: hello@wystan.ai
one-time audits · separate from the subscription
Need a verdict, not a subscription?
Same engine, plus human judgment. We run the scan, verify every finding by hand against your repo, and deliver a report you can act on — or hand to a board or an investor. The Codebase Audit is fully credited toward any plan, so it doubles as a paid trial.
Feature-Map Snapshot
$499one-time
See your codebase mapped
- 1 repo · up to ~150K LOC
- Automated report: features, flows, contribution evidence, maintenance receipts and source-aware test evidence
- PDF + 30 days of dashboard access
- 24h turnaround
Codebase Audit
$1,900one-time
New CTO, refactor quarter, handover
- Up to 3 repos · ~1M LOC
- Every finding verified by a human
- Prioritized top-10 evidence-backed action register
- 60-min walkthrough call
- 48–72h turnaround
- 100% credited toward any plan within 60 days
Due-Diligence Screen
From $5,500one-time
Investors & acquirers — the first pass before full tech DD
- Any size · multi-repo
- Written third-party report, under NDA
- Ownership concentration & inactive-author risk assessment
- Q&A session with your investment team
- ~5 business days
what's inside the audit
Evidence organised around product features.
Your subscription maps product change reach, within-repository prioritization and weekly movement. Audits add a human-verified view of people, process, architecture and dependency exposure, joined to the same product features. Estimates are labelled; every finding keeps its evidence trail. How every metric is computed →
REACH · tech lead · reviewer
Blast Radius / Affected Flows
The product features and user journeys a PR's changed files touch, and the largest number of other mapped flows that share a file with a touched flow.
Know which features, journeys and owners belong in the review before merge. It is file-level structural reach, not a probability of breakage.
How it’s measured →TESTS · EM · QA
Journey test evidence
For each user journey: an end-to-end test visits it, only integration tests reach its code, or nothing does — with the spec and test title as receipts. Runtime coverage appears only from a parsed report.
Know which journeys a change touches without an e2e test. Static lower bound; unsupported e2e frameworks show as not measured, never untested.
How it’s measured →PRIORITY · EM · tech lead
Future Fix-Work Rank
A within-repository percentile of modelled future fix-labelled work, withheld below five attributed commits. Its receipts are maintenance pressure: the recency-weighted share of commits labelled corrective, with k/n and the commits behind it.
Allocate review and test attention inside one repository. The rank is not a failure probability and cannot be compared across repositories.
How it’s measured →KNOWLEDGE · EM · tech lead
Knowledge Risk
The share of a feature's lines last touched by authors inactive in the recent window, next to the number of distinct human authors who changed it in that window.
A prompt to verify ownership and context, read from authorship alone — not a claim that someone left the company, and not a bus factor.
How it’s measured →RUNTIME · EM · PM
Runtime Usage & Errors
PostHog traffic and Sentry errors per mapped product feature, kept as separate observed channels.
Add business and production context to the review watchlist without folding unlike evidence into a score.
How it’s measured →what's included
Compare the tiers.
| Feature | Free | Pro | Scale |
|---|---|---|---|
| Core | |||
| Source-available CLI (FSL) + hosted MCP server | |||
| Hosted dashboard | |||
| Repositories included | 1 | 2 | 10 |
| Extra repos | $25 / repo / mo | $19 / repo / mo | |
| Private repos | |||
| Developers | Unlimited | Unlimited | Unlimited |
| Usage | |||
| Full re-scans / month (weekly calibration included) | 1 | 30 | 150 |
| PR impact comments / month | 50 | 2,000 | 10,000 |
| Incremental scans | Unlimited | Unlimited | Unlimited |
| Weekly calibration re-scan + drift report | |||
| Fair-use codebase size (LOC) | ~150K | ~1M | ~5M |
| Boost packs (200 / 1,000 / 5,000 extra full scans) | |||
| Runtime & delivery | |||
| Sentry + PostHog attribution per feature | |||
| Slack digests + REST API | |||
| PR comments on every pull request | |||
honest positioning
Where Wystan fits.
Not a replacement for your PR reviewer, your error tracker or your static analyser. Wystan lives in a specific slice — the persistent, feature-grained map of your product built from git history, with runtime joined to it. Here's where that slice overlaps with the tools you probably already pay for.
ToolWhat it ownsWystan’s distinct slice
CodeRabbitAI review of the PR diff — and now groups a diff by system behaviourWe keep the map the diff lands in: product features, their history, their runtime — between PRs, not just inside one→SentryProduction errors, stack traces, Seer AI reviewWe group Sentry's errors by product feature — “Checkout broke”, not “this stack trace broke”→CodeSceneBehavioral analysis — hotspots, knowledge risk, at file levelFeatures and user journeys instead of files, plus runtime signal and agent context→SonarQubeStatic analysis & SAST, at the lineWe group issues by feature and attach runtime signal→SourcegraphCode search & navigation across reposAbstracts code into scored features & flows→Swarmia · LinearBEngineering metrics, per developerFeature-level evidence and runtime context — never developer ranking→PostHogProduct usage & eventsWe consume it — traffic per mapped feature, kept as separate evidence→questions
Frequently asked.
Why unlimited developers instead of per-seat?
Developers aren't what cost us money — the code we scan and PR-comment volume are. Invite every engineer, EM, PM and contractor; your bill doesn't move. Per-seat tools punish you for inviting the people who most need visibility.
Is per-repo pricing a good deal compared with per-seat tools?
For a 10-engineer team, $99/month is about $119 per engineer per year — against $240–400/month for per-seat review tools at the same headcount. Below ~5 engineers a per-seat tool can be cheaper; Wystan pays off from roughly 8 engineers up, and the gap widens as you grow, because your bill doesn't.
What is the Founding 20 offer?
The first 20 organizations get 40% off for their first 12 months — Pro at $59/mo, Scale at $179/mo — in exchange for a 30-minute feedback call each month for the first three months and a short quote we may publish. After 12 months, list pricing applies; after 20 orgs, the offer closes.
How is a one-time audit different from a subscription?
Same engine, different deliverable. The subscription is the living map: it re-scans on every push, comments on every PR, and sends weekly drift digests — fully automated. An audit is a point-in-time deep read where a human verifies every finding, writes a prioritized risk register, and walks you through it — a report you can hand to a board or an investor. The Codebase Audit is 100% credited toward any plan within 60 days, so it works as a paid trial, not a fork in the road.
Is there really a free tier?
Yes, with no trial clock. The engine is source-available (FSL-1.1 — free to use and read; each release converts to Apache-2.0 after two years). The hosted Free tier covers one public / open-source repo up to ~150K LOC, with one full scan a month and 50 PR comments — incremental scans stay unlimited. Runtime integrations (Sentry, PostHog, Slack) are Pro and above.
What counts as a scan?
Incremental scans (on push / PR) are unlimited on every tier. Full re-scans (initial, on-demand, and the weekly calibration re-scan on paid tiers) draw from your monthly cap — 1 on Free, 30 on Pro, 150 on Scale. The billing page shows your running usage. Need more in a busy month? Boost packs add 200, 1,000 or 5,000 extra full scans as one-time top-ups — incremental scans are never limited.
What is the weekly calibration re-scan?
Once a week (paid tiers) we re-run a full cold scan of each repo and diff it against last week's anchor. The fresh full scan corrects structural drift from incremental scans; mapped features, flows and comparable versioned evidence movements land in Slack. Runtime coverage moves only when compatible parsed reports exist. It draws from the same monthly full-scan cap.
How do monorepos count against the repo limit?
One repository = one slot, monorepos included — a 12-package Turborepo is still one repo. Pro includes 2 repos and Scale 10; extra repos are $25 (Pro) or $19 (Scale) per repo per month. What scales with codebase size is the fair-use LOC cap (~150K Free, ~1M Pro, ~5M Scale). Inside the dashboard each workspace package is still mapped and scored as its own project.
Do you ever store our source code?
Never, on any tier. The scanner processes code in memory only and discards it. We store derived metadata — feature names and metrics are readable today, scan content is encrypted at rest. See the security page for the full data-flow.
Do you offer on-prem or self-hosted deployment?
Not today. Self-hosting (engine, dashboard and MCP inside your VPC), SSO and Customer-Managed Keys are on the roadmap. If you need one of them, email hello@wystan.ai — we'll tell you honestly where we are and what we can do in the meantime.