Open-source library replacement for paid resilience tools

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem

Open-source resilience and circuit-breaker libraries that many .NET projects depend on are adopting paid licensing models (Open Source Maintenance Fee), creating licensing uncertainty and compliance costs for downstream consumers and enterprises using those libraries transitively or directly.

Solution concept

A resilience and circuit-breaker library built to be a drop-in alternative to Polly, designed with permissive open-source licensing to avoid ongoing fees, and with API compatibility where needed to reduce migration friction for .NET teams already using Polly.

Who has it

.NET developers and teams, Microsoft and enterprise software companies using or maintaining packages that depend on Polly, organizations concerned about open-source licensing compliance and cost.

How they handle it today

Currently, .NET teams use Polly through direct and transitive dependencies in their projects. They rely on official binary releases and stable public APIs. With OSMF licensing coming into effect, they must now determine licensing obligations, evaluate alternatives (building from source, forking, replacing), and plan for long-term maintenance strategies.

Why now

Polly is adopting OSMF (Open Source Maintenance Fee) starting November 16, 2026, creating immediate licensing questions for Microsoft and other downstream consumers. This creates an urgent need for alternative solutions and is prompting community forks and replacements.

How it could charge

Support contracts for enterprises; premium add-ons (observability, advanced strategies); or potentially dual licensing with commercial support options for organizations that want guaranteed maintenance and SLAs.