Pricing
Start with the public repo scan when you need signal. You can scan a public repo for free. Buy the $5,000 Baseline Sprint when a buyer, audit, or launch needs a repo-specific fix order.
Monitoring and retained execution are listed for planning, but they make sense only after baseline context exists.
Decision Guide
What this shows: This path shows the offer order only; it does not show current repo findings or imply that paid delivery already started. Next move: Start with the free scan when you need current repo findings, and use the baseline sprint as the first paid move only after a real repo signal exists. Guardrail: The baseline and monitoring buttons still open the request page first; monitoring stays behind existing baseline work, and the autonomous retainer stays behind fit review until the scope is clear.
Use this section to choose the least risky next step. This pricing page does not inspect your repository or qualify you for paid work by itself.
Walseth AI already has current repo findings for your next decision only when you run the scan or bring equivalent repo evidence. The baseline sprint is the first paid move. Monitoring starts only after baseline work exists.
1. Free Scan
Use when you need current repo findings. Start here when you need a fresh read on one public repo before deciding whether paid work belongs in the conversation.
2. Baseline Sprint
Use when the signal is real and needs a fix plan. Use this after the free scan or an equivalent repo signal when you need a paid fix plan instead of staying at a score. The request page reviews fit before delivery starts.
3. Monitor
Use only after baseline work exists. Keep this as the continuity layer after baseline work exists, not as the first move from a benchmark or scan. The request page reviews fit first.
4. Execution Retainer
Use when you already need a retained execution lane. This requires fit review because scope depends on repo count, decision rights, and how much recurring execution you want beyond ordinary monitoring. The request page reviews fit before any retained work is implied.
Decision Guide
This page is not a menu where every tier is equally ready to buy right now. Walseth AI has one free scan, one fixed first paid engagement, and two continuity paths that only make sense after baseline context exists.
If you are deciding what to do next:
Read the pricing page as evidence, action, then limits
What this pricing page proves now
This page shows the offer order, public starting prices, and why the Baseline Sprint is the first paid step.
What this page lets you do next
Run the free scan when you need current repo findings, or request the Baseline Sprint when a real review gap needs a fix order.
What still depends on review
Monitoring and retained execution depend on baseline context, repo boundaries, and recurring volume. They are not first-visit purchases.
Front Door
Free scan or baseline sprint
Those are the two front-door choices this page can state cleanly for a new visitor.
Starts Later
Monitoring follows baseline
The monitor is continuity work, not the first paid engagement. It earns its place after the baseline defines what should continue.
Fit Required
Retainer requires fit review
That lane depends on repo count, decision rights, and recurring volume, so it is scoped by fit instead of a flat public rate.
How to act
Read prices as scan, sprint, then later-stage support
Use Run Free Repo Scan when you need fresh repo-specific findings first. Use Request Sprint when you already know the gap is real and want the first paid fix order. Monitoring and retainer requests stay later-stage paths after baseline context exists.
Read prices in order
What you get
The concrete output a visitor can understand before a sales conversation.
When it fits
The business condition that should be true before you choose that path.
Next move
The action a serious buyer should take next.
Primary Public Path
These are the two choices a new visitor should parse first. They cover the current repo scan and the first paid move without making continuity work compete for attention too early.
Teams that want a quick public-repo read before buying deeper work
Run a public repo through the live scanner and get a quick governance signal, sample findings, and a reason to go deeper or stop.
Current offer boundary
What you get
A current public-repo read for one repository.
When it fits
Use it when the repo is public and a first-pass read is enough before deeper review.
Next move
Run the scan before deciding whether paid review is warranted.
Teams that need a bounded paid engagement without enterprise procurement sprawl
A fixed-scope sprint for one AI product or repo family: AI use inventory, data-flow map, security-questionnaire answers, ranked gaps, and starter review materials.
Current offer boundary
What you get
This is the first paid offer with a fixed starting price and bounded baseline deliverables.
When it fits
Use it when one product or repo family has a real buyer, audit, or launch blocker.
Next move
Request the sprint when the gap is real enough to need a fix plan.
Front-Door Rule
Public now means free scan or Baseline Sprint. Monitoring and the retainer still exist, but they should read as post-baseline continuity work instead of equal first-visit choices.
Later-Stage Continuity
Monitoring and the retained lane stay visible, but they depend on existing baseline context, continuity scope, and fit.
Teams that want recurring follow-through after the baseline sprint
Monthly continuity after baseline work exists: recurring checks, bounded reviews, and a standing path for the next fix instead of reactive cleanup.
Current offer boundary
What you get
The public price band starts at $500/mo for narrow continuity scope.
When it fits
Actual monthly scope and price still depend on baseline context, repo boundaries, and recurring volume.
Next move
Ask about monitoring only after baseline work exists and the continuity scope is clear.
Teams that already need a standing execution lane after baseline work exists
A retained path for recurring maintenance, remediation execution, and escalation at real decision points. Scope and pricing depend on repos, system boundaries, and expected recurring volume.
Current offer boundary
What you get
A retained execution lane scoped after baseline context exists, not a flat public rate.
When it fits
Scope and price still depend on repo count, decision rights, and recurring execution volume.
Next move
Confirm baseline context and continuity shape before asking for a retained execution lane.
Keep the front door simple: free scan, baseline sprint, then a scoped monitor only if it earns its place, and the premium retained lane only when you need standing recurring execution.
Read the table as a decision aid, not as a claim that every higher tier is ready right now. Free scan and baseline sprint are the current front-door moves; monitoring and retainer fit still depend on baseline context and scope confirmation.
| Free Scan | Baseline Sprint | Monitor | Execution Retainer | |
|---|---|---|---|---|
| Best for | Quick signal on a public repo | Bounded paid baseline work | Continuity after the sprint | Standing retained execution |
| Deployment | Self-serve | Fixed-scope engagement | Monthly follow-through | Retained lane by fit |
| Primary output | Quick score plus plain-language findings | Inventory, answer map, and ranked fix plan | Recurring review and continuity support | Recurring execution plus escalation |
| Time to value | Minutes | 5 business days | Starts after baseline | Starts after fit and scope confirmation |
| Price range | Free | $5,000 one-time | Starts at $500/mo; broader scope in current band | Request fit |
| Ongoing support | None | Optional monitor upsell | Included monthly | Included in retained lane |
Start with the free scan. If the signals are real, the baseline sprint is the right next step. The higher tiers only fit after that foundation exists.
Run Free Repo Scan