Over 3500 Awesome Clients
These customers seriously like what we do.
Here is what our users say about us
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:)
Since evaluating JRebel, we have seen redeploy times significantly reduced and I am therefore hoping that we can be more productive and turn around our development projects in a quicker timeframe.
It used to take 5 mins to rebuild and restart the server - now we see changes pretty much instantaneously. I saw the value right away.
Just a few compiles without having to deploy was enough to convince me to buy JRebel.
I'm afraid our developers might go for a strike if we say to them, ‘Hey, we're not going to use JRebel anymore.
Jrebel is so awesome it almost hurts. Or rather, not using it hurts.
I seriously cannot understand how I used to do my job without #jrebel.
I like the way [JRebel monitors] the file system for changes and smartly reloads Java changes into Hot Swap/Hot code memory. It just eliminated by build time during development by 90%.
Since migrating to IBM WAS 7.0, we've had trouble with replacing HotCode - we're now using JRebel for uninterrupted development and it's working fine :)
Every delay sucks, so whatever causes less delays rocks.
We’ve had some real OutOfMemory problems in our production environment for quite some time. Once I got XRebel up and running I noticed that our most used webapplication uses around 15MB/User session. By tuning a few JSF parameters I got the average user session from 15MB to 0,5MB.
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.
We are writing up loads more case studies now. If you'd like to be one of our case studies, please contact email@example.com