A few months ago, MassTransit announced that they are going commercial. That was a big shock for many of us in the .NET ecosystem.

Some of us thought someone would eventually fork the project and keep it open, but that hasn’t really happened yet, probably because it’s not a small project. Understanding it deeply and maintaining it properly would easily be a full-time job.

My idea: an open-source fork called [name-redacted] I’m thinking seriously about maintaining a fully open-source fork of MassTransit, called [name-redacted], that stays community-driven and free forever.

My initial plan:

I’ll take over as the primary maintainer at the beginning.

Over time, we’ll bring in 3/4 core maintainers so the project never depends on a single person.

The goal is long-term stability, improved documentation, and transparent governance.

A bit about me

I’m not anyone special in the .NET world, just a developer with about who loves working deep in the infrastructure layer. I enjoy understanding what happens inside the .NET runtime and working on complex system design problems.

So a project like MassTransit is honestly a dream to work on.

But here are the two big questions that have been keeping me up tonight:

This would basically be a full-time job. How would I manage that?

Does the community even want this? Would you actually use and support a well-maintained open-source fork?

I can’t answer that second question alone; that’s why I’m here, asking the community.

If you’re a current or past MassTransit user, I’d love to hear your honest thoughts. Would a stable, open-source alternative matter to you? Would you consider using it or even contributing if it existed?

Please comment below or DM me. I’d really appreciate it.

My plan, if there’s interest MassTransit v8 will remain open-source and supported until December 2026, which gives me some breathing room. In that time, I plan to:

Deeply understand the code and learn the transports I’m less familiar with.

Restructure and improve the documentation — I think it could be more organized and easier to approach.

Add API references for all types (classes, interfaces, etc.) that are currently missing.

I know it might sound a bit crazy, but I’m okay with that. I’d rather take a shot at something that matters.

Even if you’re not a MassTransit user, I’d still love to hear your opinion. Do you think the .NET ecosystem needs a strong, community-backed service bus library again?

Thanks for reading. (And for tolerating a slightly sleep-deprived 4 AM post.)