What does NinjaTrader look for when approving a new Ecosystem Vendor?

I’m preparing a commercial NinjaTrader Add-On and would like to understand what NinjaTrader generally expects from developers before approving them for the Ecosystem Vendor Program.

Is there a typical readiness standard for applicants? For example, does NinjaTrader expect the product to already be fully released and customer-ready, or is it acceptable to apply while the product is still in late-stage testing?

I’m also curious whether approval is based mainly on the developer/business itself, the quality and stability of the product, documentation/support readiness, licensing/distribution setup, or some combination of those things.

If there are any common reasons applications are delayed or rejected, or anything you would recommend having in place before applying, that would be helpful to know.

Thanks.

Obviously I do not speak for NinjaTrader and they speak for themselves, but my observation would be that many times when an approval fails it is either because (a) the required documents are not available such as corporate formation etc. (b) there is no website or the website has compliance problematic language on it like profit claims without appropriate and equally prominent risk disclaimers or (c) the principal(s) have criminal history or otherwise fail background checks that require further investigation or clarification. Those are not the only reasons, but those all are reasons that come up from time to time. It is also true that the product has to not crash the platform and pass some basic QA from the team. It does not matter what you use for licensing, but you must provide them with a working license so they can verify it works. Again, just my observations, nothing official.

NinjaTrader’s public docs do not publish an approval scorecard, so I would not treat any unofficial list of rejection reasons as a guaranteed checklist.

What the current docs do establish is:

  1. Vendor Support manually enables the NinjaTrader username for the Ecosystem vendor dashboard.
  2. The product is then created in that dashboard and receives the Product ID used by VendorLicense().
  3. You need a working customer or trial license so the add-on can be tested.
  4. The distribution package should install cleanly, avoid source files, use clear version naming, release resources in State.Terminated, perform one license check with a timeout, and provide a clean uninstall path if a custom installer is used.

Because product creation happens after dashboard access, the public process does not state that the product must already be publicly released.

I would apply once the product is a clean release candidate, not just a concept: installable on a clean NinjaTrader setup, reproducible startup and shutdown, a tested invalid-license path, short install/use/uninstall docs, and a support contact. It can still be in late-stage testing, but Vendor Support is the only source that can confirm whether they want a public release for your specific application.

Official references: