SmartBear code review tool,
CodeCollaborator and its lightweight version,
CodeReviewer are available in the form of Concurrent License and Named License.
Request a Quote
|
|
CodeCollaborator |
CodeReviewer |
|
Named |
$489
|
$289
|
|
Concurrent |
$1299
|
-
|
Explain license differences
License Differences
Concurrent Licenses
With a concurrent license, you are allowed a maximum number of "concurrent users." A user is considered "active" if he/she has used the system in the past hour and has not explicitly logged out. Users with any CodeCollaborator page open in a browser will remain logged in regardless of whether they are actively navigating through the site. Concurrent licensing is more appropriate when you have many users that will use the system only occasionally. In both cases, a "user" is a human being, not tied to a particular machine or client. This means that if someone uses both the Eclipse client, stand-alone client, and command-line client, plus uses CodeCollaborator on a work machine and laptop, that all counts as one "seat" whether fixed or floating.
Named Licenses
With a named license, you are allowed a fixed number of "named users." A "named user" is a human being (not a machine) that is active in the past 30 days. Therefore, if some users never log in, or if a user leaves the group and doesn't log in again, that user does not count towards the named license. Named licensing is more appropriate when most users will be using the product daily.
How many licenses do I need?
It's hard to give guidance because it varies quite a bit. Generally the best advice is: Just try CodeCollaborator. There is a report on the User Administration page that tells you exactly how many named and cuncurrent licenses you would be using right now. Use that empirical information to determine which is best for your team. Typically, a trial doesn't involve everyone, and typically the usage pattern isn't exactly the same as when it will be deployed, so you'll have to estimate. Still, you'll be doing so with some real numbers.
Here are some additional pointers:
-
If you have developers in many timezones, concurrent license usually becomes more economical.
-
If each person will be inside CodeCollaborator at least once per day (either as author or reviewer), typically named licenses are cheaper. If less frequently than that, concurrent.
-
If you expect large spikes in usage - where perhaps everyone is online at once during a code review crunch - you'll want named. Otherwise, you have to get enough comcurrent to handle that peak usage.
-
Remember that you can upgrade from named licenses to concurrent licenses later, with credit for your named license investment. So if it turns out you purchased the wrong model, or your needs change, we make it economical to upgrade anytime.
Download CodeCollaborator
|
Version Comparison |
CodeCollaborator |
CodeReviewer |
|
Tool-assisted lightweight code review |
|
|
|
Awesome technical support |
|
|
|
Cross-platform |
|
|
|
Web interface & rich client interface |
|
|
|
Review code before or after check-in to version control |
|
|
|
Subscribe to changes made to certain files or by certain authors |
|
|
|
Track defects during review |
|
|
|
Eclipes plug-in |
|
|
|
Visual Studio add-in |
|
|
|
Customizable reports |
|
|
|
Multiple workflow configurations |
|
- |
|
Organize users & reviews by organization hierarchy |
|
- |
|
Scriptable system administration |
|
- |
|
LDAP/ActiveDirectory authentication |
|
- |
|
Customizable fields for reviews and defects |
|
- |
|
Pre-participant customizable fields for reviews |
|
- |
|
Review deadlines |
|
- |
|
Automatically collects metrics |
|
- |
|
Restrict user access to reviews |
|
- |
|
Server-side triggers |
|
- |
|
Document review (PDF, Microsoft Office, etc.) |
|
- |
|
URL review |
|
- |
|
User groups |
|
- |
|
Version Control Systems |
CVS, Git, Mercurial,
Perforce, Subversion,
Vault, AccuRev,
CMVC, MKS, Rational
ClearCase, Rational
Synergy, Rational
Team Concert,
StarTeam,
Surround, Team
Foundation Server,
Visual Source Safe |
CVS, Git, Mercurial,
Perforce,
Subversion, Vault |
|
Database back-ends |
MySQL, SQL Server, Oracle |
MySQL |
|
Support & Upgrades |
All upgrades, phone & email support |
All upgrades, phone & email support |
Questions?
What is the typical ratio of users to floating seats?
Typically, 2-3 developers can share a floating license depending on usage and the geographic location of develpers. Please contact sales with detailed questions or for an estimate.
Can I upgrade from CodeReviewer to CodeCollaborator?
Yes. Plese contact sales. They can arrange a credit of your initial purchase of CodeReviewer and apply it to a CodeCollaborator license.
Where can I get a copy of the EULA?
CodeCollaborator shows you the end user license agreement during the installation process. Download the server software, invoke the install wisard, click next when the Welcome page appears and the license will pop-up.
What is the difference between fixed (named) vs. floating (concurrent) licenses?
Named license allow a fixed number of "named users." A "named user" is a human being (not a machine) that is active in the past 30 days. Therefore, if some users never log in, or if a user leaves the group and doesn't log in again, that user does not count towards the named license. Named licensing is more appropriate when users will be using the product daily.
With a concurrent license, you are allowed a maximum number of "concurrent users." A user is considered "active" if he/she has used the system in the past hour and has not explicitly logged out. Users with any CodeCollaborator page open in a browser will remain logged in regardless of whether they are actively navigating through the site. Concurrent licensing is more appropriate when you have many users that will use the system only occasionally.
In both cases, a "user" is a human being, not tied to a particular machine or client. This means that if someone uses both the Eclipse client, stand-alone client, and command-line client, plus uses CodeCollaborator on a work machine and laptop, that all counts as one "seat" whether fixed or floating.