“BuildMaster made us re-think what proper deployment is...” “...we implemented a *real* deployment process...” “...all of my projects are building wonderfully and are fully integrated into deployment...” “...this is a very solid piece of software!” “...extremely capable software, especially in an enterprise environment...” “BuildMaster is a great tool for automating the build process, but stands head and shoulders above other tools...” “...it's 2:45 AM your time?! Do you guys never sleep?” “...our confidence in the reliability and repeatability of the deployment process has been restored...” “BuildMaster is absolutely swell!” “...we can now react at the speed of business...” “...the best thing since sliced bread when it comes to managing projects and their environments...” “...BuildMaster makes sense of incremental builds and their very liquid feature sets...” “...manual, error-prone deployments are a thing of the past...”

View Question

« Back to Posts

Developer Licensing

In terms of the licensing, how is a user/developer defined?
From a licensing standpoint, a "user" is simply someone who has access to and uses the functionality of BuildMaster: whether that's designing deploying plans, kicking off new builds, or analyzing data.

That being said, BuildMaster is designed (and priced) to be used by the entire development organization. The reason is that we believe everyone involved in development should be involved in (or atleast aware of) the process, not just those on a Change Management team.

While you can buy as few licenses as you'd like, there's a lot less value when only a small group has access
Reply To Post »