Licence models + impelementations

[IanWright]

I'm trying to think of a suitable licence model for a toolkit that I'm designing, and have come up with the following, and would like thoughts / opinions or suggestions that people can offer. The toolkit is going to allow setup + solving of specific non linear problems. The ideas I had were:

2 different licences. 1 Developer, 1 Runtime, which I want to strictly be used appropriately.

Developer licence:
Allow many instances of the toolkit to be used at once to aid debugging.
Include various debug outputs to help diagnose potential problems.
Locked to a set of developers using Windows Identity information and Domains.
Higher cost.

licence includes Start date, expiry date, all possible user names, domain name and any additional information required to further restrict the toolkit.

Runtime licence:
Restricted to a single instance running at a time.
Locked to a machine using WMI information.
Lower cost.

licence includes Start date, expiry date, machine information and any additional specific information required to further restrict the toolkit.

I'm trying to think of other differences that would be useful and any extra ways to basically improve the licensing model. Anyone any thoughts?

[Frinavale]

I've had to edit/look over a license agreement once before and the best advice that I can give is to speak to a lawyer.

There are lawyers that specialize in the area of IT. They will know about what should be covered and how to design these documents so that the Licensee (software developer) doesn't take advantage of your intellectual property.

You can probably find some cookie cutter type license agreements online (that's how I started my research before I realized that I wanted a lawyer to handle it).