WireMock .NET joins the WireMock family

The WireMock team is delighted to share some big news for our .NET users -- WireMock .NET is joining the core WireMock project!

For years, .NET developers have relied on WireMock .NET as an independent implementation of the WireMock engine. The library was created and maintained by Stef Heyenrath, a Microsoft specialist who has been developing on the .NET Framework since 2007. Stef released early versions of WireMock .NET back in February 2017 and has steadily evolved it into a feature‑rich API mock server.

As of today, the WireMock organisation is taking stewardship of the project to bring it under the same umbrella as the Java engine -- and Stef will be as active as ever in overseeing the .NET development. 

Why the change?

WireMock .NET is more than a port -- it replicates many of WireMock’s advanced features, such as HTTP response stubbing and request matching, dynamic Handlebars response templating, recording & playback and fault simulation. Yet because it has been a separate project, .NET users have missed out on the latest innovations happening on the main WireMock roadmap and have had to navigate slightly different configuration formats and Admin REST APIs.

By merging the projects we can:

• One shared home for code -- WireMock .NET now lives in the main WireMock GitHub organization, bringing all issues and pull requests together.
  
  
• One source of documentation -- All guides and API references are hosted together on wiremock.org, covering Java, .NET, and other integrations.
  
  
• One community of users -- Everyone connects in the same Slack and GitHub spaces, sharing ideas and feedback that help WireMock evolve faster.
  

What does this mean for you?

If you’ve been using WireMock .NET, nothing breaks today. Your existing NuGet packages will continue to work, and the project will still be open‑source under the Apache 2.0 licence. What changes is where development happens:

1. New home: the WireMock .NET source code and issue tracker will move into the main WireMock organisation on GitHub. Stef Heyenrath remains an active maintainer and will continue his contributions as part of the wider team.
   
   
2. Unified documentation: the .NET documentation on wiremock.org/dotnet will be integrated into the main docs, alongside the Java guides, so you can find everything in one place.
   
   
3. Join the conversation: we encourage .NET developers to join our community Slack (slack.wiremock.org). This is where we discuss road‑map ideas, announce betas, and answer support questions.
   

Looking back and looking ahead

As we merge efforts, our goal is simple: deliver the best API simulation experience to developers, no matter which language they use. 

Whether you’re writing in C#, Java, Kotlin or another language, you’ll benefit from a consistent set of features — advanced request matching, dynamic response templating, stateful scenarios, HTTP proxying and fault/latency injection.