Opportunities › Open-source library replacement for paid resilience tools › Proposed app
Surefoot
Find Polly in your .NET repos, see the licence exposure, plan the switch
- Score
- 51
- confidence 36
- Evidence
- 5
- items on the page
- Rivals
- 3
- named in sources
- First version
- 30 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2013
- Mature market · AI estimate
ScreensConcept
Desktop app: Developers scan repositories, review dependency maps, record migration decisions, and generate audit reports for teams—tasks requiring code context and detail. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Exposure scan
Scanned 3 min ago14 projects
About this appAI proposal
Surefoot scans your .NET repositories for Polly, direct or transitive, and shows which projects, packages and public APIs depend on it. It turns an open-ended licensing worry into a list your team can act on before the November 16, 2026 change.
For each finding it suggests a path: keep, pin, or move to a permissively licensed resilience library with a compatible API. It drafts the code changes as a reviewable pull request, so migration happens in small steps instead of one rewrite.
It is built for .NET leads, platform teams and compliance reviewers who need one report to share. It gathers facts and does not give legal advice. The migration target is a companion permissive library, to be built or adopted.
- Tagline
- Know where Polly sits. Move on your own schedule.
- Voice
- CalmPrecisePractical
- Why this name
- A sure foot is steady when the ground shifts. It suits a tool that helps teams move steadily through a licensing change.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Transitive dependency map
Reads csproj files and NuGet lock files to show every route by which Polly reaches each project, including through Microsoft.Extensions.Resilience.
No member yet
Public API exposure check
Flags packages you publish that expose Polly types in their public surface, since those are the hardest to change for your own consumers.
No member yet
Licence decision sheet
One page per project: where Polly is used, which release you consume, and the options keep, pin, fork or replace. Reviewers record a decision and a note.
No member yet
Migration pull requests
Drafts code changes that map common policies (retry, circuit breaker, timeout, fallback) to a compatible API, as a diff your team reviews before merge.
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#12332FDeep Teal · primary#F6F3EAPaper · surface#1B2A28Ink · text#E8A33DAmber · accent#2E8B7AMoss · data#C0452FBrick · warning
Typography
Aa
Surefoot
PricingAI proposal
The material gives no competitor prices, so these tiers are a starting point to test. It names support contracts and premium add-ons as the opportunity's monetization.
Free
Free
- 1 repository
- Exposure scan
- Shareable summary
Team
$49 a month
- Up to 25 repositories
- Decision sheets
- Migration pull requests
- Parity tests
Enterprise
Contact us
- Unlimited repositories
- Audit exports
- SSO
- Support contract with SLA
Would you pay Team · $49 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Audit reports and decision sheets are shared by link with managers, legal, procurement and other teams who must sign off. Each shows the Surefoot name and the scan date.
- Do they become customers?
- Viewers include engineering managers and platform leads who hold budget and may run their own scans. Test whether report viewers sign up for scans of their own repositories.
- First customers
- Platform and architecture leads at mid-sized companies with 10 to 100 .NET services that publish internal NuGet packages exposing Polly types.
- Where to reach them
- Polly GitHub discussions: Offer the free scan to people commenting on the licensing issue, which has 33 reactions and 4 comments.
- .NET community forums: Post a worked example of a transitive Polly audit with a free scan link.
- Direct outreach: Message .NET leads at firms that publish NuGet packages and offer a free audit of one repository.
- First milestone
- Ten teams run a scan, and three pay for Team before the November 16, 2026 date.
Why people already pay for this
- VerifiedOpen GitHub issue has 33 reactions and 4 comments
- AI inferencePolly is adopting Open Source Maintenance Fee model for binary releases starting November 16, 2026, affecting downstream .NET packages.
- AI inferenceMicrosoft's .Extensions.Resilience packages directly depend on Polly and expose its types in public APIs, creating licensing obligations.
- AI inferenceCommunity is already exploring fork alternatives to address the licensing change.
- Public claim
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Repository accessGitHub App with read and pull request scopesScans repos and opens migration pull requests without users handing over tokens.
- This app · Code analysisRoslyn-based analyser in a worker serviceFinds Polly usage and public API exposure accurately, which text search cannot do.
RisksAI inference
- CommercialThe need may be short-lived if Polly's terms prove light, or if Microsoft decides for everyone. Teams may also be content to pay or pin. Demand must be tested before building.
- TechnicalAutomatic migration depends on a target library with a compatible API. If none is mature, the product is an audit tool only, which is a smaller offer.
- RegulatoryReports may be read as legal advice on licence obligations. Wording must stay factual and point reviewers to their own counsel.
- DataEnterprises may refuse to give a third-party app read access to private source. A local CLI or self-hosted scan may be needed.
- Intellectual propertyMimicking Polly's API could raise copyright or trademark questions. Compatibility must be clean-room and named neutrally.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.