| |
|
+ |
= Pricing for AnthillPro =
|
| |
|
+ |
There are no per-server fees, per-project fees, and per-agent fees. Pricing for AnthillPro is based on the number of developers working on projects managed by AnthillPro. So how do we determine who is a developer? Simply, if a user is committing code to a project, that user is considered a developer. What about team turnover (you use mostly contractors that come and go every couple of months)? No problem. We use a sliding window to calculate the number of developers. So if a user has stopped committing code, that user will not be included in the developer count any more. What if a developer is committing code to two projects, will that developer be counted twice? No. Each developer is counted only once. If a developer is committing code to multiple projects our license system will notice that and count the developer only once.
|
| |
|
+ |
Please contact sales for a quote tailored for your specific configuration, including your specific SCM (CVS, SVN, ClearCase, Perforce, AccuRev, Dimensions, MKS, StarTeam, etc.).
|
| |
|
+ |
= Site-wide and Enterprise-level Licensing =
|
| |
|
+ |
We do support site-wide and enterprise-level pricing and licensing. Please contact sales if you're interested in these options.
|
| |
|
+ |
We use many Open Source projects and tools on a daily basis and are eager to give back to the community. We offer free licenses of AnthillPro to legitimate Open Source projects. Please contact sales to learn more.
|
| |
|
+ |
= Why this Licensing Model? =
|
| |
|
+ |
The goal of the AnthillPro pricing model is to scale from the little guy to the big guy, and achieve a price proportional to delivered value. The only way to accomplish this goal was to come up with one or more scaling variables that are used to calculate the price. That's where our search for scaling variables began. We looked at the number of servers or the number of agents as the scaling variables. At first glance it appeared that the number of agents would be a good scaling variable. But upon closer inspection, it turns out that because of support for network deployments, a large company with hundreds of project and hundreds of servers may not need any more agents than a 5-person shop working on two projects with a handful of servers. We then looked at the number of administrators defined within AnthillPro as the scaling variable. But here again we know of enterprises with one or two build masters supporting hundreds of projects and even the smallest team will still need at least one admin account. So this turned out to be a sub optimal scaling variable. The number of projects configured in AnthillPro is also not a very good scaling variable because it encourages poor development practices in the form of monolithic projects. We strongly believe in modular or component development and encourage users to have many individual projects with dependencies between them. It would not be fair for us to encourage a practice where the better you are at it, the more we charge you. What we eventually found is that the only appropriate scaling variable that accurately scales from the little guy to the big guy, and is proportional to the value delivered, is the number of developers.
|
| |
|
+ |
= Upgrades From AnthillPro 2.x =
|
| |
|
+ |
Teams current on their maintenance for AnthillPro 2.x are generally eligible for an upgrade to a single agent, unlimited user license for AnthillPro BMS 3.x. Upgrades to multi-server BMS installations or AnthillPro ALA generally require a migration to the new licensing model.
|
| |
|
+ |
[http://web.archive.org/web/20100225045838/http://www.anthillpro.com/html/products/anthillpro/price-list.html Wayback Machine - AnthillPro Licensing Page, Feb. 2010]
|
