JRebel for Teams
JRebel is an award-winning application that drastically reduces the Turnaround process for Java Developers. It is easy to get your team up and running, easy to track ROI, and you’ll see the time savings, starting on day one.
This page answers the following questions:
- Why should I consider rolling out JRebel to my development team?
- How does JRebel reduce Turnaround for my team?
- Who else is already using JRebel?
- How much does it cost and how can we calculate ROI?
- How do we get started?
If you’re considering JRebel for your team and have any other questions, contact sales@zeroturnaround.com
Why should I consider rolling out JRebel to my development team?
Every year, development teams waste significant time on a process called Turnaround. Two phases of the Java Development Cycle contribute the heaviest to Turnaround:
- The Redeploy Phase, which costs 3 to 7, full, 40-hour weeks annually, depending on the container your team is using (see The Redeploy Report from over 1100 developers), and
- The Build Phase, which costs 1.5 to 6.5 weeks (see The Build Tool Report from over 600 developers) depending on the tools your team uses.
These phases are considered a regular part of Java development, but developers using other technology (including languages such as: .NET, Ruby, Python, and more) don’t suffer from the Turnaround process, and consider it a serious waste of time. Instead of waiting on Turnaround, these development teams are busy coding new features, fixing bugs, improving the quality of code, finishing more projects on time, working on new projects, and hitting more deadlines. For management, this means quicker realization of projects and improved returns from teams. It means software that works better, delivered faster, and under a tighter budget.
Unfortunately, it’s not easy to move from Java to another language, and in some cases, nearly impossible. If increasing productivity is your goal, then reducing Turnaround is an easy way to realize big gains. This is where JRebel comes in.
JRebel eliminates 80% of the Turnaround in Java development, helping you to reclaim the development time previously wasted – every year, and it costs less than $150 per developer. What is one week of a developer’s time worth to your team?
How does JRebel reduce Turnaround for my team?
JRebel maps your project workspace directly to your running application. When a developer makes a change to any class or resource in their IDE (Phase One) the change is immediately reflected in the application (Phase Four), skipping the build and redeploy phases. For details on the types of changes JRebel recognizes, see the Feature Comparison.
For a more technical description of how JRebel works, see the FAQ Page.
Who else is already using JRebel?
Our tools are used by some of the best development teams in existence, including:
Check out the customer quotes on the right side of this page, and feel free to take a look at a larger list of clients on our customer page.
How much does it cost and how can we calculate ROI?
JRebel typically pays for itself within the first two weeks of usage. It is an annual subscription, sold on a per developer basis, or Site Licensing for teams with more than 100 developers. Since it is priced to pay for itself in under 2 weeks, we do not offer discounts for purchases under 100 licenses.
| Corporate Licensing | Site Licensing |
|---|---|
| $149 / year / developer | Contact sales@zeroturnaround.com |
To calculate the ROI or business value of JRebel for your team, use the Business Value Calculator. As a special note – if you do not feel that JRebel has paid for itself after one month, we’ll give a full refund.
How do we get started?
Test JRebel on two of your development projects, so the teams can compare results. It’s easy to install and configure JRebel for your environment
- Download the free 30 day eval here. This eval can be used by any number of developers.
- Talk to your team leads about JRebel, and ask them to check out the Rebel Report (this appears each time you start your server with JRebel enabled) at the end of the month. This will help determine ROI for your team, based on the container your team is using.
