THE STORY

“Software is eating the world,” said Netscape founder and tech investor Marc Andreessen. Line by line, hardware is being consumed by code, and Java is spoken by a massive army of hungry mouths.

However, since the programming language was introduced in 1996, developers have had to write Java code on their own machines and then upload their code to remote servers for testing.

The idea that would become a glass of ice water to coders in redeployment hell was born in Estonia in 2006. That’s when Jevgeni Kabanov found a way to address Java’s core problem – the redeployment bottleneck. His insight led to a start-up and two products that smart Java teams wouldn’t be caught without. In other words, magic happened.

Developers at thousands of companies around the world use JRebel to instantly view code changes without redeploying the application server.

The result? Happy coders writing and testing beautiful code. Happy customers enjoying time and money saved through all that beautiful, productivity-boosting code.

Today, ZeroTurnaround is the labor of love by a global team of 150+. The company’s go-to-market heart beats in Boston, Massachusetts, while our development feet are firmly planted (and rapidly growing) in Estonia, at two offices in Tallinn and Tartu. We also have a branch in Prague, Czech Republic.

We are dedicated to making developers lives better, and we now have over 65,000 active users at 5,200+ customers, including 36% of Fortune 100, in 80+ countries.


DEVELOPERS SAYING REALLY NICE THINGS

We’re developers who make stuff for people just like us. Yes, our software is used by companies, from startups to well-known multinationals. But at their core, our products are consumer products. It’s a stroke of good fortune that our “consumers” happen to be other Java developers. You know, people like us. Here’s what some of them have said about life with the tools we’ve made.

WHAT THEY SAY

It not only takes me at least 2 minutes to redeploy, but it adds another 5 minutes to get back in the zone and I still have to bring the application back to the state where I was developing. This alone is at least 10 minutes lost for a minor change. JRebel deserves every single cent of its selling price.

Bogdan Mustiata

QualySoft

Java EE Developer

We were attracted to JRebel because we had grown very frustrated with starting JBoss app sever constantly. After seeing JRebel mentioned in several blogs recently, we gave it a try. While it doesn't eliminate app server restarts completely, we only redeploy about 10% as much as before, saving both time and attention span!

Adam Wells

PIPE Networks Pty Limited

Development Manager

Finally after seeing that JRebel won the JAX most innovative Java technology award, I am giving it a try. Sick of all the tomcat restarts.

@geoaxis

JRebel Customer

Once we started using our JRebel Evaluation, we realized that we don't want to go back to the old way anymore! :-)

Bob Janousek

Calltrade

Software Engineer

Life without JRebel is no fun...

Sigmund Lundgren

Stein & Lundgren AB

Consultant

Start to really like JRebel. Make Java feel like a scripting language.

@sseong

JRebel Customer

JRebel saves a lot of frustration from dealing with JSF, JPA and Tomcat. One big thing is I don't need to start Tomcat every time to see my code!

Wonman Lee

Barloworld Handling LLC

IS Department

I am so much more productive with Java, JPA and Spring (and JRebel) than i was with RoR the last months… It's really fun again.

@rotnroll666

JRebel Customer

Every java dev should have a copy of #jrebel installed. Buy it yourself if your workplace is cheap. It's soo worth it.

@willvuong

JRebel Customer

We had a need for faster turnarounds since we have huge projects that take ages to build and deploy. Jrebel is an excellent tool to reduce that time:)

Sven Varkel

Ericsson Eesti AS

Development Team Manager

I was attracted to JRebel because of its transparency, simplicity and efficiency. It's easy to set up and very nice to use!

Nikola Tankovic

Superius Ltd

Development Team Leader

We found some very interesting side-effects right away. The worst of those was some badly coded Hibernate which would generate over 700 database queries. The JSF memory footprint was a bad surprise - some beans are in the session, that shouldn’t have been there.

Petri Tuomaala

Elbit Oy

JRebel Customer