[rover2]

I recently came across the ndisapi project and am interested in using it for software we are needing to develop. However I am confused by the licensing setup. The ndisapi project has a MIT license, but one must pay money for commercial use? Or am I not understanding something?

If we have to buy a license we probably won’t be able to use it in our software, because although we are not a nonprofit, we are a very small business with a tight budget.

[Vadim Smirnov]

Thank you for reaching out and for your interest in the NDISAPI project. I completely understand the confusion—licensing details can sometimes be tricky.

You’re correct that the NDISAPI library source code is open-source under the MIT license, which allows for a lot of flexibility. However, the Windows Packet NDIS drivers are a bit different—they’re free for personal and non-commercial use, but if you’re planning to use them for commercial purposes, I believe it’s fair to share a portion of the revenue.

I understand that as a small business, you might have a tight budget. If the licensing costs are a concern, I’m open to discussing flexible options, such as installment payments or perhaps a profit-sharing arrangement. My goal is to find a solution that works for both of us.

Looking forward to hearing your thoughts.

[rover2]

Thanks for the clarification.

I agree that it’s fair to share the revenue for commercial use, and I’m definitely not opposed to paying for a good-quality product. However we are looking to keep our end-user costs for this project to a minimum; and my main attraction to this library was the first-glance possibility of it being free. So I suppose we will continue exploring our other options, but I’ll keep this in mind if we can’t make something else work.

[Vadim Smirnov]

Thanks for your openness and understanding. I appreciate your perspective on keeping end-user costs to a minimum—it’s a crucial factor in any project. However, I must emphasize that kernel mode software, while powerful, carries significant risks for end users if not thoroughly tested and vetted. We’ve seen cases like CrowdStrike that underscore the importance of using well-tested, reliable solutions.

That said, I understand the need to explore cost-effective options, and it’s great that you’re considering all possibilities. If you find that other options don’t meet your needs, please feel free to reach out. We’re here to provide a well-tested and robust solution that you can trust.

[Barbara456]

I think the confusion mainly comes from the fact that the MIT license applies to the NDISAPI project source code, while the Windows Packet NDIS drivers have separate licensing terms for commercial use. So, being MIT-licensed does not necessarily mean every component associated with the project is free for commercial deployment.

For a small business, I would recommend confirming exactly which components your application will use and whether a commercial license is required before committing to the project. It may also be worth contacting NT Kernel directly to ask whether they offer a small-business or startup-friendly licensing option. That way, you can understand the actual cost and avoid any licensing issues later.

[george456]

I can understand why the licensing structure would be confusing, especially when the project itself is described as MIT-licensed. The distinction between the open-source library and the NDIS drivers seems to be the key point here. For a small business, it would definitely be worth clarifying exactly which components require a commercial license and whether there are affordable options available. Hopefully, the maintainers can provide a clear breakdown so developers can make an informed decision before building the technology into their products. 👍

[Author]

Posts