Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

JRebel Enabling Enterprise

Seven Years and Counting

ZeroTurnaround has spent more than 7 years helping Java developers be more productive. Irrespective of who or where they are, or what projects they work on, JRebel has helped more than 50,000 developers eliminate redeploys in Java, so that they can see the impact of their code changes instantaneously. In short, JRebel has been getting devs home in time for dinner for 7 years. That’s pretty cool.

For the last seven years, we’ve been focusing on product development to deliver quality to our users – developers. We have seen fantastic growth; we love devs and they love us too apparently. A lot of that growth comes from enterprise customers. Larger businesses see value in happy and productive devs and our JRebel floating model was an attempt to satisfy corporate licensing needs for a developer tool.

Managed Licenses

After the last 5 years of offering floating licenses, we have received a lot of feedback from our enterprise customers, and while we were meeting some of their needs with our floating model, we weren’t totally satisfying them and were missing some key license management features they need. So, we worked through the use cases and feedback and came up with this solution.

As of January 1, 2015 we will offer managed licenses instead of floating licenses. This is a huge step forward for our larger customers. For the first time, you will be able to ensure that teams are using their licenses and track return on investment across projects and teams. You will also be able to more accurately assign, budget, and track licenses across renewal periods. And these new features come at the same price as the old model.

For our non-enterprise customers and enterprise customers who do not need these extra capabilities, the dedicated licensing model is still available.

To recap:

  • Dedicated: each license is assigned immediately after purchase to a particular developer. No License Server is used.
  • Managed: a license key is uploaded into the License Server. Licenses can be pooled if needed, and individual developers claim a license from the pool and register it to their email address. This allows administrators to manage the licenses across projects. Think of the licenses as being assigned to the project, and JRebel is available and licensed like other SaaS Licenses.

The managed licenses will still use the License Server and the License Server can support both floating and managed licenses at the same time.

When Can You Get It?

If you want the current floating model, you must purchase JRebel before January 1, 2015. If you want the new managed model, you will be able to purchase it from January 1, 2015 onward. The dedicated model is unchanged and can be purchased immediately and in the future.


If you are an existing JRebel user, please refer to the licensing FAQ and guide.

Got Questions?

Call us at 1-857-221-9900 by phone, or email us at We’re here to help!

  • MilanF

    OK, let’s take an example: a company have 20 developers, but only 10 of them working at the same time. Previously 10 floating licenses have been sufficent. Now you require them to purchase 20 managed licenses instead?

  • sdoca

    How does a developer return a license to the pool? Does it have to be
    done by that developer?

    I really liked the feature of checking out an offline license that had an expiry date. Will this still be available?

    We’ve had issues before with licensing where the user has left the company without returning a license and now it’s no longer available for anyone.

  • Adam Koblentz

    Hi Milan, in your situation, you would need 20 licenses to cover all of your developers. Some of our customers will need to buy more licenses to cover their developers, and some of our customers will renew or buy less licenses as we’re bringing more transparency to licensing and usage rates. If you want to keep the floating option, you can do an early renewal for multiple years.

  • Adam Koblentz

    Hi Sdoca,

    You will still be able to check out a license for offline usage. Developers put in their email address into the IDE plugin along with the License Server token URL. Developers are not responsible or able to return a license themselves. When they change projects, teams, or leave the company the License Server admin or team manager can deallocate the license so it may be consumed by another developer.


  • Twqqis

    I agree with UberCoder. Although you state that you’ve consider the use cases, removing the floating license model doesn’t cater for ALL the clients who DID choose the floating model, those clients have THAT requirement. Not happy.