Friday, 4 May 2012

What is TeamMentor Licensing model?

I got a couple questions recently on the licensing model of TeamMentor, so it's better if I answer it here.

TeamMentor has an 'interesting' license structure and deployment:

  • The master version of TeamMentor's source code is published at GitHub, can be freely downloaded/cloned, AND is released under a soft 'not-for-commercial-use' license:
    • this means that you can use TeamMentor as long as you don't sell it (the application) or use it commercially as a service
    • note that any content created using TeamMentor is owned by the author (ie. you)
    • just to be clear: THIS is the full application! Apart from specific customer customizations, this is the same code-base as the one used in the 'paid for version' (which is a Git Fork)
    • There is no license restriction/controls, so we are trusting the community not to abuse it :)
  • There is an 'TeamMentor+OWASP Library' version (see ,which we call our 'evaluation version' and contains:
    • a Git Fork of the full source code of TeamMentor (with the same soft 'not for commercial use' license)
    • an TeamMentor Library (written by SI about the OWASP top 10) which is released under CreativeCommons
  • There is paid version of 'TeamMentor + SI Library' which is the one with the 4000+ articles:
  • If you are security consultancy (providing security services to other companies), then you are what we call a 'Partner' and you can use TeamMentor for free internally and with your customers
  • if you are a product company (and want to embed/consume TeamMentor's content), you are also what we call a 'Parter' and will be able to use its content for free in your product (we have agreed internally on similar rules-of-engagement as the one used for security consultants)
Bottom line, TeamMentor is NOT FOSS software, but its closer than most products out there.

Note that the center-of-gravity at SecurityInnovation (SI) is more aligned with Content than with Tools. For example see their 40+ elearning courses delivered under the TeamProfessor platform, which should explain why SI is comfortable with this model for TeamMentor.
Post a Comment