AutoMapper and MediatR Going Commercial: What .NET Developers Need to Know Now

Jimmy Bogard’s Announcement

You’ve probably heard the news by now — Jimmy Bogard, the mastermind behind AutoMapper and MediatR, has decided to take these beloved .NET libraries commercial. For senior .NET developers like you, who’ve built countless projects relying on these tools, this shift raises questions. What does it mean for your existing codebases? Will it hit your budget? And where do these libraries go from here?

lets break the wall and find the granule details of this change, break down its implications, and explore what it means for your day-to-day work as an experienced developer.

oops!

The News and What’s Changing

Jimmy Bogard recently announced on his blog that AutoMapper and MediatR are adopting a commercial model.

Don’t panic!

— the core libraries aren’t disappearing behind a paywall. Both will stay open-source, meaning you can keep using them as you always have. However, Bogard is introducing commercial versions or additional features that’ll come with a price tag. This move is about sustainability, ensuring these libraries can evolve and stay maintained long-term.

For AutoMapper — this might mean paid extras like advanced mapping options or performance boosts beyond what the free version offers. Think faster object-to-object mapping or more complex transformation tools. MediatR — could see premium features too — maybe better debugging support or integrations with paid platforms. The open-source versions will still work, but the shiny new toys will cost you.

So, what’s the catch for us(.NET developers)? If you’re happy with the current functionality, nothing changes right away. You can keep your existing projects humming along. But if you want those new features — or if your next project demands them — you’ll need to weigh the cost. For teams with tight budgets or solo developers, this could shift how you approach these tools.