Introducing JetBrains Toolbox, easier access to your coding tools, more control and flexibility, and a lower entry price

Final Update (September 18th): The licensing model had been updated. Read the update from our CEO Maxim Shafirov.

Update 2 (September 8th): The licensing model announced previously including conditions and prices, is not final. Please expect updates next week.

Update: Please make sure you also read this short update to the announcement below.

Update (December 8th): we’ve closed comments under this blog post. Please contact our sales team with any questions you may have.

At JetBrains we believe that software developers are some of the most forward-thinking people in the world. They are the drivers of the incredible pace with which technologies are developed today. The progress made in software development in the last decade alone is unbelievable and software has become core to so many things today, from pens to spaceships. For us, being a part of such a diverse group of developer communities for over a decade has been a really exciting and enlightening journey.

While ways in which we develop software haven’t drastically changed over the past couple of decades, the role of those who write software has evolved. In effect, developers are no longer pigeonholed to a certain technology. They work with multiple languages, frameworks and platforms. And with this change come new needs.

What happens

As of November 2, 2015, we will introduce JetBrains Toolbox—a collection of our popular desktop tools (IDEs, utilities and extensions) available on a monthly or yearly subscription basis. With JetBrains Toolbox, you can pick and choose one or more tools that best suit your current needs, or go for the ‘All products’ plan that comes with special savings. You decide what to put in your Toolbox and for how long.

This new distribution model will replace the perpetual licensing model that currently is in place.

Why the change

While our existing upgrade subscription mechanism has worked very well for thousands of customers, and for us, it has certain drawbacks in terms of simplicity that we’ve been wanting to address for some time, based on the various feedback we’ve received. We believe this new model is much simpler and easier to understand. In addition, it allows better budget planning and overall provides a more flexible model for everyone; be these individuals, small teams or large corporations. Lower entry costs also make adoption easier.

One of our top goals at JetBrains has always been to provide our users with the best possible experience, both in terms of the product and the services surrounding it. In a fast-paced industry, our customers not only demand quality but also expect support for newest technologies. With already over 30 major feature releases per year and dozens of maintenance releases we really want to make sure all of it is delivered to every user out there.

What JetBrains Toolbox includes

JetBrains ToolboxIntelliJ IDEA, AppCode, CLion, PhpStorm, PyCharm, RubyMine, WebStorm, ReSharper, ReSharper C++, dotTrace, dotCover, and dotMemory. All of these products will be moved to the new license distribution model.

No changes apply to our family of server tools including YouTrack, TeamCity, Upsource, and Hub.

Next steps

We want to offer all our customers the smoothest possible transition which is why we’re announcing the upcoming changes today, two months ahead of time. The most important note is that all previously purchased licenses will stay valid. If you have purchased or are going to purchase a product with a perpetual license and one-year upgrade subscription, even if it is a few days before the change takes place, you will receive all product updates released for one year within your purchase, and you will be able to continue using all the upgrades you were entitled to during this period, indefinitely. You will also have the option to switch to the new model at any time, receiving discounts as an existing customer.

For more information, please check the pricing details as well as the FAQ which should cover most questions. If you have any additional enquiries, feel free to contact us.

Develop with pleasure!

This entry was posted in News and tagged . Bookmark the permalink.

837 Responses to Introducing JetBrains Toolbox, easier access to your coding tools, more control and flexibility, and a lower entry price

  1. Andrea says:

    Great news!

    I hope you will take this opportunity to also improve the licenses manager in JetBrains site, which is a bit cumbersome.

    • Eugene Toporov says:

      Thanks Andrea, there’s a lot of plans and things in the work. Hope we can make it better

      • Zmicier Zaleznicenka says:

        For those who would purchase the full subscription, will it be possible to deliver AppCode and CLion on steroids, including the support of IDEA Ultimate language plugins, e.g. Python and Ruby? I hate it when I have to switch to IDEA from AppCode to fix build scripts or Calabash test steps in these languages.

        • Vierry says:

          Personally, I always wanted such a feature! To have something like different view (manually switching) or having automatically switch when you open different file type.

  2. Andrea says:

    I hope you will take this opportunity to also improve the licenses manager in JetBrains site, which is a bit cumbersome.

  3. Hendrik says:

    And I just bought R# Ultimate three month ago for 199€ :/

    • Eugene Toporov says:

      Well, it means you will receive updates to it 9 more months at no cost and will receive the ‘existing customer’ discount as a permanent license owner.

      Thanks for supporting us and develop with pleasure!

  4. Ben says:

    I’m sure everyone will be thrilled to pay for their tools every month that they once payed for once!

    • Eugene Toporov says:

      Quite many pay once *a year* already to stay up-to-date. This becomes even easier now

      • Fred Jones says:

        The difference is that we can *choose* whether or not to pay for the upgrade on the basis of whether the upgrade is worth paying for.

        Now, we *have* to pay in order to keep using our tools. Forget that — you’ve lost our company as a customer.

        • John says:

          Fred’s comment brings up a request for compromise. If I cancel my subscription, allow us to keep using that last purchased software version permanently. At my discretion, I can resubscribe and hop back on the update train. My compromise as a customer would then be I’m forced into a year subscription, but at a discounted price. Fair?

          • MuppetGate says:

            Not really. People would just jump back onto the subscription every time a new version came out, and then jump off. That would mean they would get updates for about seven quid.

            • Jonathan says:

              Do what every other company does that offers this… give them their permanent license after a year.

            • Zak Jensen says:

              Subscriptions often change the release model from few major updates to many incremental updates, and integrate feedback mechanisms into the software. The information transmitted back to the developers, coupled with frequent updates, creates an environment that produces more finely-tuned software.

              If JetBrains does this, then the idea of paying only one month a year doesn’t pan out–you miss all of the “tuning” that make the software pleasant to use.

              • Thomas Singer says:

                I don’t see why this would contradict with a perpetual license.

              • JTW says:

                Adobe didn’t change their release model when they went subscription based.
                If anything, they now have fewer updates than before because they have even more of a captive audience, millions of users who lose the ability to access their own data (which is in custom Adobe file formats of course) if they elect to stop paying their monthly fees…

            • Brian Popp says:

              Just charge more to get back on the maintenance schedule once someone has allowed their subscription to lapse.

        • Chris Spencer says:

          This is exactly what is wrong with this new scheme. I object to being forced to pay to continue to use something which I’ve already paid for.

          I know in my workplace I wouldn’t have been able to prompt the switch from Eclipse to IntelliJ in the first place if it had required an annual subscription.

        • Przemek says:

          “The difference is that we can *choose* whether or not to pay for the upgrade on the basis of whether the upgrade is worth paying for. “… …and because of that a subscription model should be much more cheaper than perpetual one. In case of IDEA the price looks a little bit smaller, but with WebStorm: definitely not. And all these “*” and “**” makes me scary. They should really reconsider the whole idea…

        • JTW says:

          Indeed. For people who now buy one version and just keep using it, buying a new version once every 3-4 years, which probably is a lot of users, the new license model is a lot more expensive than the old one.

          I’ve been pondering shifting to Netbeans rather than upgrading IntelliJ, this change is what convinces me that shifting to Netbeans is the better choice.

          Which is a shame, as I’ve always liked IntelliJ a lot, and for years it has been my IDE of choice.
          But paying full price every year for a biyearly upgrade is not feasible.

      • Anu says:

        That was a choice. Now it’s a requirement.

  5. Daan Van Heghe says:

    Oh no, not ANOTHER subscription. Wonderful, now you’ve joined Adobe (CC) and Microsoft (Office365) in “renting” your software. Not for the benefit of your users, of course, just for your own benefit to get continuous cash coming in every month. Subscriptions are a form of ransom : if you stop paying, your software no longer works. I bought and used AppCode for years, but I hate subscriptions and now I’m going back to Eclipse. Goodbye, greedy Jetbrains !

    • Daan Van Heghe says:

      I meant xcode, of course, not eclipse…

    • Aldo Fregoso says:

      When Adobe announced Creative Cloud, the price of a single tool (ex. Illustrator) went from $700 USD + $250 USD/upgrade to $250 USD/yr, and existing customers got a 40% discount, so the actual upgrade price was 150 USD.

      When Microsoft announced Office 365, the price of the business suite went from $220 USD/version to 100 USD/year.

      Are you noticing a pattern? The price to upgrade **actually decreased**.

      With Jetbrains, we got the worst of both worlds, a single tool (ex. PhpStorm) will change its price from $99 USD + $49 USD/upgrade to $99 USD/year, not only they’re changing their pricing model, they’re asking for **MORE** money. Thats insane!!!

      Thanks but no thanks, hopefully the efforts to improve FOSS IDEs (ie. Eclipse/Netbeans) will increase. Jetbrains should remember to don’t bite the hand that feeds them.

      • Andrey Cheptsov says:

        Actually for existing PhpStorm users the upgrade price will remain the same: $49 USD / year. For existing IntelliJ IDEA users the upgrade price will in fact **decrease**: $89 USD /year.

        • Michael Stack says:

          Right “existing” customers for “existing” tools. If I choose to pick up a new tool, or if they release a new tool, and subscribe to it for more than a year will the price drop for year two and onward be cheaper for me?

          There’s no longer any reason to remain loyal to JetBrains tools.

        • Andrey, the key question I’ve yet to see answered directly is what happens after this first year. The normal, non-promotional prices shown are 50%-100% increases from the current prices today for those already upgrading every year. This is a huge jump. If you’re saying that all users will drop to $49/yr (PHPStorm example) or $199/year (IDEA Ultimate example), then this actually saves already upgraders money in exchange for rental model. If not, you’re forcing IDEA ultimate users to switch from perpetual to rental for 67% increase of price.

        • JTW says:

          for the FIRST YEAR. And you’re assuming people buy every single upgrade now.
          A lot of people, maybe most of them, will skip every other upgrade, maybe more.

          And that of course is the real reason companies go for a subscription model.
          It forces people to pay full upgrade fees every upgrade, which means extra income from people who now happily use older versions and largely have no load on the support system.

        • Carighan says:

          And this is ignoring that a typical use case is needing a tool briefly, for a month or three.

          In which case the ability to buy a monthly license is actually quite interesting. I’m not saying it’s perfect, there’s the loss of version ownership, but still it’s hardly a loss-only situation.

      • Przemek says:

        Well said. Subscription should imply a huge price drop.

      • Josh Harwood says:

        Remember though that companies would by that $220 copy of office, and run it for 5-6 + years without upgrading.

        Making the previous total cost much more realistic on an ongoing basis.

  6. Anu says:

    This is very confusing.

    I have an existing licence for PHPStorm, which expires in April 2016.

    At that point, if I want to receive updates and new versions, do I have to switch to this new licensing? How long will the price for existing users be valid for? What happens if i then after a year decide to stop my subscription? Which version of PHPStorm can I then still use?

    Basically, this looks like you are doubling the cost for a licence, and it seems reducing the value – if we stop paying, then we don’t have any rights to use the software, unlike now, where if we don’t upgrade, we can still use the old version.

    • Eugene Toporov says:

      Yes, once your current free upgrade period ends and if you want updates, you can switch to the new licensing and redeem your existing customer discount.
      Here is the full details on the offer:

      But your permanent license that you have now will be with you forever and you will be able to use the version of PhpStorm that will be current in April 2016

      Hope it helps.

  7. Jonathan says:

    I tweeted about this but this is bad news for an indie developer… if you let your subscription lapse you have NO ACCESS to a previous version, unless you buy before this policy goes into effect. What do you do if you have to fix some bugs in an older project? Subscribe for a month? Use TextMate?

    The prices have skyrocketed for WebStorm ($99 vs $49? And no permanent license?) No price change for PHPStorm except you get a poisoned license. (beware of promotional pricing hooks)

    I think you sat down with big companies and came up with this idea but forgot (or ignored) the little guy.

    • Kris says:

      It’s not like your code is in a proprietary format (looking at you Adobe Cloud). You could use a dozen editors, or even contribute to the EAP’s bug-finding mission if you find yourself in a subscription lull.

      • Jonathan says:

        TextMate is an editor. I knew that. But if you wanted to do debugging or refactoring, they have you over a barrel.

        • Carighan says:

          His point is that you’re not bound to jetbrains tools if your license lapses and you lack the funds to re-sub, you can easily switch to eclipse etc.

          But yes, what you say is the one key issue to me as a customer, but ofc also the one key benefit to Jetbrains, lack of people sitting on old versions eternally.

      • JTW says:

        IntelliJ uses a custom format and libraries for GUI development.
        While you can work without them, doing so greatly reduces the power of the editor so you’d be better off without IntelliJ and using say Netbeans which works better when working directly with the code.

      • Piskvor says:

        You could do that, sure. Let’s see: if my PHPStorm died on me tomorrow morning, I could start looking for a dozen other tools to replace them (editor, debugger, REST tester, version control, SFTP client, code linter, stacktrace analyzer, terminal emulator, diff tools, clipboard manager, that’s not to mention the aerial photography ;)) – but I’d probably get no work done on that day, and the impact to productivity will be significant further on, as I’d need to switch between various tools. Oh, and did I mention that I’m not the only programmer here? Times $programmer_count, therefore $wasted_man_hours = HUMONGOUS. And we sorta need to use those man-hours for something more productive than fiddling with a stack that randomly might or might not work (because the bean counters are feeling cranky/because the license server is unreachable/because JB said so) when we get to work on next Monday morning.

        TL;DR: switching IDE stack has costs, and if the IDE is timebombed (a.k.a. “subscription-based”), the risk of “you WILL switch your IDE stack NOW” is always hanging above you.

    • Hadi Hariri says:


      The price for WebStorm has always been substantially lower than its sister IDEs yet offering similar functionality. We’ve aligned the prices. For existing customers, the price remains the same.

      • Jonathan says:

        $99 > $49. Don’t you see that?

        You’ve aligned the prices, meaning you’re charging the same for WebStorm and PHPStorm or PyCharm despite their all having the same WebStorm functionality?

        What’s next? Freemium and IAPs?

        • Hadi Hariri says:

          The price for WebStorm is now aligned with the other IDEs, so yes it’s more expensive for new users.

          • Jonathan says:

            Are you still going to argue that it’s a customer focused decision, and less expensive?

            • Zak Jensen says:

              If I understand the announcement,it’s easier for a new user to understand how much they’re going to pay. Since they’ve never paid before, they’re not subject to a price-hike, they’re subject to a fresh decision. Meanwhile, the existing users get a discount that keeps their investment at the level they agreed to when they purchased the software.

              Objectively speaking, it’s not a bad deal. Subjectively, you took the licensing model for granted, and so it feels like you’re losing something.

              • Your argument is predicated on the PREPOSITION that the hook price for existing users will be *perpetual*! I am under no such delusions until I see it specified clearly otherwise. It seems like it’s a one-year discount, to me.

          • Ben says:

            Hadi, can you explain this line from the PhpStorm page description (as of September 3, 2015):
            PhpStorm comes with all features of WebStorm and adds full-fledged support for PHP and Databases/SQL.

            What’s the value of WebStorm if I can get a more full featured product for the exact same price?

    • Kenny says:

      What’s wrong with subscribing for a month? It’s $8 – surely you can bump your rate to cover that. Or are you on the hook for fixing bugs for free forever? You should be charging for support – which is (at least partially) what JetBrains is doing with this change to subscription pricing.

      • Przemek says:

        It’s always interesting to see a citizen of a country with an average salary of ~4500$ per month to tell people from Europe earning only fraction of that amount what is and what isn’t cheap.

        Btw. – it’s 8€  for Europeans, not 8$. We earn less, we pay more. So yeah, fuck logic.

        • ICesarI says:

          Well, for Colombians is like paying six time the price than you thanks to the actual value of the crude oil.

    • Nick says:

      Steal it (torrents).

      • Robert Demmer says:

        Seriously Nick.

      • Jonathan says:

        That’s dumb from the average person, from a developer it’s ridiculously stupid. You want people to steal your code?

        • Nick says:

          Yeah, it sucks, and isn’t something one should do, but it will happen once certain people find themselves in the boat you described. From a moral perspective, it’s easier for most people to make the jump to pirate something if they’ve already been paying for it, especially if they feel like they’re getting burned, which seems to be the overwhelming sentiment here.

  8. Dmitry Tsitelov says:

    Sad to hear that. I think that subscription based licensing models are less fair than perpetual+upgrade as the latter implies some stimulus for vendor to offer upgrades worth paying for :)

    • Eugene Toporov says:

      On the other hand, we think we’ll be able to concentrate on quality more than trying to impress users with new features so they buy upgrades. Our products are more than feature-full and we believe the quality is something that can always be improved.

      • Fred Jones says:

        Whether you do or not will be entirely dependent on your internal whims, not on being immediately answerable to your customers.

        If we chain ourselves up to your coercive subscription service, you’d have to really screw up before we could easily justify breaking the entire company’s tools by ceasing payments.

        • Robert Demmer says:

          Fred, do you have any reason to doubt that we will continue to deliver industry leading products?

          • Justin Hall says:

            The reason most of the comments here are doubting that, is because the perpetual license obligated you to deliver amazing upgrades so we’d have a reason to pay for them. Now you don’t.

            • Terence Martin says:

              Well and succinctly said, sir.

              • Charlie says:

                Yeah I have to agree, there is no longer any driving motivation for you to put out the quality of work you have so far done.

                Jetbrains, please consider offering both models.

      • Martin Lind says:

        I’m not buying version 14. The features isn’t what is stopping me.
        You have two bugs that need to be fixed first, Which I hoped would be fixed by version 15.

        But now you don’t need to bother anymore.

        Your arguments are moot, you’re customer base is the wrong audience to fool with these arguments.

      • D walker says:

        Your products are not feature full. That you think this is the case is why a subscription model is such a bad idea from a portion of your customer’s perspective.

        • Robert Demmer says:

          D, We are continually working to improve our products. If you have feature ideas or know of something that is missing, tell us. We would love to hear your thoughts.

          • Andrzej Sliwa says:

            some of bugs where not fixed by years! and even now are not fully fixed.


            seriously! show me who will like renting over owning (not only software but any stuff like apartments, cars etc.) We as developers really dislike any kind of DEPENDENCY! you should know it.

            • Anton Naumov says:

              Ok, you’ve got one. I’d rather rent an appartment instead of renovate my own one on regular basis. As well, I’d rather rent a car instead of get a headache with parking, insurance, maintenance and so on. It logically bring both of us to idea I’d rather subscribe to full steak toolbox for 20 euros per month instead of buying some tools I’m using quite rearly.
              At the end that the half of my monthly coffee expense.

              • Andrzej Sliwa says:

                Everything is about looking on long term perspective, renting is always much more expensive. Sure with renting you don’t need to care about some details (somebody making it for your money).
                Every car/apartment needs maintenance, with renting you just delegating this but for the price you paying for.

                Difference between owning and renting is also that with my car I could use/drive it whenever I want, how I want and I don’t need to wait for permission of owner (or maybe some of my papers or driver licenses has expired – in this case I will ask my wife to drive our car without being blocked by waiting for next license)
                You have more rights as owner.

                Renting (of anything) is a huge business, and make only sense if you (as customer) doing it rarely (like renting car for 1 week in year, and you get the point here), or jumping between locations/products but with regular basis you will overpay with comparing to owning.

                so lets summarise if IDEA and/or RUBYMINE etc.. is for some of use most important tool used daily which we depends on it, then renting of it is just bad joke.

              • Mihai Drebot says:

                You are both right, and as usual it depends on the context. Where I live, it’s cheaper to own an apartment than renting one on the long run. Also, if i feel like painting the walls green, they are my walls, so i can do it. Same for a car. Perhaps where Anton lives this is not true. It applies to software licences too, for some a subscription might be better than owning a copy. Not for all, that’s for sure.

      • I’m not sure that “It’s great for us, since it’ll mean we can stop worrying about adding new features!” is a great argument for winning over customers’ hearts…

        • Robert Demmer says:

          Jason, Rest assured the adding of new features won’t stop. JetBrains is the same company, delivery the same tools, albeit a different license model.

          • Terence Martin says:

            I think a better plan might have been to lengthen your release window from 1 new major version bump a year to one every 1 1/2 years or so, and then spend that extra 1/2 year just hammering away at all of the bugs in the last major version before embarking on the Next Big Thing ™.

            • Bjørn T Johansen says:

              AMEN! It’s been many year since “Development with pleasure” was a correct statement for Jetbrains’ products, now it’s just add more and more features and to hell with all the bugs……

      • Frustrated User says:

        I agree with the quality statement, R# has been virtually unusable for me because of the numerous performance issues for close to 8 or 9 months now. I only have about 15 projects, of which half that have loads of typescript… if the performance and robustness were to improve I’d consider it, otherwise, I will probably move on to different tooling.

      • ICesarI says:

        You should consider Xamarin model. They give you a perpetual license if you pay annually.

  9. Jonathan says:

    You lost me at subscription… Creative Cloud for developers…. dumb so now I really don’t own my software :/ very disappointed in you guys I once respected you but this has made me consider alternatives.

    • Eugene Toporov says:

      Really sorry to hear this Jonathan. But thanks a lot for your feedback

    • UntouchedWagons says:

      >I really don’t own my software

      You have never “owned” software you purchased. You owned a license to use the software.

      • NK says:

        Of which license would you will not own at all under the new scheme. That’s the whole point.

      • Terence Martin says:

        Owning a license to perpetually use some software for as long as you are able is very much like owning the software, in the same way that owning a license to use some software that only remains valid for the time frame over which you keep making payments constitutes renting it.

        I think we all know that’s exactly what most people know and most people think, and trying to argue around it by saying that “you only ever owned the license” is just being pedantic to no good end.

  10. Mike says:

    Sweet. Now can you fix the 879,000 bugs that have been popping up in WebStorm over the past year?

  11. Anu says:

    Can we “stack renewals”? If I buy a renewal for my PHPStorm license, will it extend my current one? What rights do I have for software released during this period?

    • Robert Demmer says:

      Anu, in regards to “stack renewals” it depends on your account. You should contact for more details. If you purchase a PhpStorm or any other IDE and .NET tool license before November 2nd, you will receive one year of free updates during that term and the license is yours. You continue on with that license indefinitely or choose to move to any newer versions on the subscription model.

    • Sathish says:

      No, You cant stack renewals. You cant even buy an upgrade for an year if it current licence is valid, let say till December 2015. You are forced to go to subscription model.

      You lost mine also.

  12. Mccxiv says:

    This makes me really sad, I was about to buy a copy of Webstorm but I hate subscriptions.

    It becomes another thing in my mind instead of a simple purchase, every month I’ll be considering if I should cancel, that’s A LOT more friction than a one time sum of money. Have you guys considered that?

    • Eugene Toporov says:

      But if you need the tool constantly and you renew yearly now, what’s the difference? You can also choose yearly billing and do it once a year. If you need it periodically, then you can use monthly and save.

      • Jonathan says:

        The price is what’s the difference… and if for some reason you can’t make it that month you don’t have the tool until you can re-up. I think we should be given the option to own the software. As another aside the pay per upgrade was a bit wonky as well, bug fixes should not be payed for… new features yes.

        • Robert Demmer says:

          Jonathan, bug fixes and and new features are included in JetBrains Toolbox. You should always have the best that we can deliver.

      • Andres Galindo says:

        The difference is it’s not a subscription, if at the end of the year I do not *want* to renew – I don’t, the choice is mine. Now, I’m FORCED to which leaves a bad taste in my mouth.

        I love PhpStorm, but I do not agree with this move.

        • Robert Demmer says:

          Andres, Thank you for sharing your opinion. We have heard your voice.

          • JD says:

            … and won’t do a thing about it!

            I just started using WebStorm and was considering buying a copy for myself. Now that you’ve made that impossible, you’ve made my patronage impossible. I won’t pay monthly for the rest of my life, since you don’t have a monopoly on text.

      • JTW says:

        most people do NOT upgrade every release, but every 2-3 releases.
        If everyone upgraded every release, you’d not need to force people to pay every year…

        So for a large number of users who now pay $150 every 2-3 years they’d now be paying $100 every year, for $200-300 every 2-3 years.

        That’s a major price increase, for no return whatsoever to the customer, not even a guarantee that there will be more bugfixes and delivered functionality.

  13. Derek says:

    This is very disappointing.

    I switched from open source tools to Pycharm because of the fair and easy licensing. Most of my development occurs in an environment without internet access; I cannot have my IDE phone home every month to see if it is licensed. I see in the FAQ that JetBrains is “…committed to finding solutions to ease the transition to subscription-based models” in regard to the need for constant internet access but this strikes me as an ambiguous non answer.

    I feel like my only option now is to find a replacement.

    • Hadi Hariri says:


      We’re making the requirement as convenient as possible for people, specially in order to avoid constant Internet connection. And per the FAQ we truly are committed to helping you

      • Eugene says:

        > constant Internet connection

        Does this means that it would require *some* Internet connection? Because sometimes I work in conditions when there are simply no Internet connection at all.

        p.s. Not quite happy with the change either. This is definitely not goes together with “simplicity”. At least until “Will it stop working?” question is answered.

      • Raffi says:

        Why check the license online at all? Simply embed the date in the license key. Setting the computer’s date back is a pain. All those files that will be modified in the future … things just won’t work correctly, it’s too confusing for all the software. Most software is programmed under the (not so wrong) premise, that time is moving forward constantly.

        You can’t work reasonably with a computer that has a completely wrong date set, especially not developers (version control). And those few people who can – oh well, just let them …

        I see no need to phone home.

    • Pasi says:

      I did exactly like that too a year ago. I ditched open source in favor for PyCharm; a well made good IDE with reasonably license for indie developer.

      I’ll look this for a year and then might go back in open source or some alternative.

      I did plan to get a new license once every year but with this model I don’t. phone home and actually forcing is not the way to go. There are months where I don’t use IDE for a less that a 2 days but still I like the old model better.


  14. Nick Donais says:

    So I like this change as it makes it cheaper for those of us that work in multiple different languages, my main issue is what happens when your sub runs out. I would much rather not be able to receive updates without a sub like how the current model works (just any updates, not only Major) rather than getting locked out completely (or still offer the upfront purchase option). I think that’s a bad decision honestly =\ I’d rather not be forced to pay to continue to use software I’ve already bought.

  15. PaulT says:

    So I currently have a webstorm licence which I personally use and just renewed at 37 GBP, next year it will cost me 63 GBP – 40% increase – not too sure how this benefits me

  16. David Vierra says:

    From the blog post about your previous licensing change in 2013:

    It is important to note that your license does not expire after the 1-year period ends, i.e. you can continue using the product. But to continue receiving updates after that period ends, you should renew your subscription.

    Is the bolded part still correct for the new Toolbox licensing scheme? This is what everyone is worried about, I think: Will my tools suddenly stop working, if I can no longer pay?

    Since you seem to be retiring the “perpetual license” model, this may be correct. In this case, it behooves everyone to immediately buy a perpetual license while they are still available – and to choose not to switch to the new Toolbox licensing scheme – to make sure that the tools will continue to work even after the upgrade period ends.

    • Nick Donais says:

      Would really like to know the answer to this as well, as it’s my only real big complaint about this change.

      • Robert Demmer says:

        Nick, Copying the answer here for you to:

        If you purchase before November 2, 2015 the license is perpetual with 1 year of free updates. You can continue using the software as long as you like.

        In order to continue receiving updates of your product beyond that initial one year, you can move to the subscription model and receive an existing customer discount.

        • dave says:

          Way to use the wrong words.

          In order to continue receiving updates of your product beyond that initial one year, you HAVE TO move to the subscription model…

    • Robert Demmer says:

      David, If you purchase before November 2, 2015 the license is perpetual with 1 year of free updates. You can continue using the software as long as you like.

      In order to continue receiving updates of your product beyond that initial one year, you can move to the subscription model and receive an existing customer discount.

      • David Vierra says:

        If you purchase before November 2, 2015 the license is perpetual with 1 year of free updates. You can continue using the software as long as you like.

        My question is about the converse:

        If I purchase after November 2, 2015, may I continue using the software as long as I like?

      • Matthieu Napoli says:

        Is this a joke? Carefully avoiding the real question everyone is asking…

        • Robert Demmer says:

          Matthieu, We’re not purposefully avoiding any question. Maybe we (I) did not fully understand. Can you please ask us again what you wish to know?

          • Brennan says:

            I think the general consensus is the subscription model is fine and a great thing in most cases (Though for some products the cost appears to have gone up? PHPStorm). It’s great for the All products subscription or for providing a lower barrier of entry after a trial period.

            The problem though that we’re all having is with the current licensing model, we have security in knowing that the last version we paid for we have access to forever. We may love your products and renew yearly, which makes the issue seem irrelevant with most of the subscription prices matching current pricing(not sure if after the first year of subscription for new customers they get that renewal discount, eg $29 a year for Webstorm).

            You’ve stated that we can purchase a license or renewal prior to the switch and be great for a year, and it’s fantastic that you support this…yet it has a cut off point which again messes with that security of our investments into your products, several years from now if we stop we’ll be ‘luckier’ than the new customers and be able to fall back to our perpetual license from 2016…

            For some products going back that many versions may not be too viable, the customer can then either hop back on the subscription wagon, or if alternatives offer a similar/better experience the customer may jump ship. You’ve made your users feel locked in with this subscription model, if they do not continue payments they will not be able to use the IDEs with features that they might depend on daily. As mentioned earlier, this is probably unlikely to happen for the majority of your users, JetBrains makes great products, I’ve just finished my first year with WebStorm and offered a renewal for $29, I’m pretty sure I’ll be great with my current version for some time, but happy to support a great product provided I can afford it in my budget( $29 is sadly still quite a bit for someone in my situation ). I am safe to do this renewal it will be just like the previous year, but after that any new updates I get via the subscription model cease to exist ‘if’ I stop payments.

            I believe this has been a very clear explanation of the problem :) It would be great if you implement what others have suggested. After 1 year( or paying for 1 year of subscription in advanced ), entitle the loyal user to a perpetual license of the product from when that 1 year subscription ends. If this is not desirable on JetBrains end, then compromise with either a license that allows the loyal customer to use the software for a period of time without new updates, 12-36 months, whatever you deem appropriate would surely be better than a straight cut off of access. Another alternative would be to provide this with an increase in subscription fee, the price increase may disgruntle users, but at least you can offer them the security of a perpetual license of the version they last used via subscription ‘should’ they stop payments.

            • CJ Thompson says:

              This sums it up perfectly.

              You guys are avoiding the issue and trying to spin this to a group of people who are very sensitive to it. This deal stinks if you look past the dollar sign, and I hope it blows up in your faces. It’s lost you at least one customer; I don’t need my productivity held hostage.

            • Egwor says:

              One other key situation: what happens if JeBrains goes bust? We now no longer have a way to use the IDE, and we may not be able to even open IDEA (because it phones home). Imagine if you’re in the middle of a project for a client and you have to change IDE in the middle!

              My suggestion:
              Keep the subscription model as you have it now, but set it so that if you’ve subscribed for a year you can use that specific version of the software perpetually.

  17. Kevin Herron says:

    This is incredibly disappointing. You’ve turned a happy customer and an advocate for your products into an unhappy customer.

    I will continue to use IDEA, albeit begrudgingly, because there is currently no better alternative. But I will do so unhappily and I will no longer be able to advocate or recommend IntelliJ products. Here’s hoping Eclipse can make a comeback, some how…

    To be clear, I have no issue paying for quality software, nor do I have an issue continuing to pay for such software through support and upgrade subscriptions. I think that model is fine. However, the idea that a critical piece of DESKTOP software will stop working because I no longer pay the ransom or because it couldn’t phone home to your server for 30 days is unacceptable.

    • Robert Demmer says:

      Kevin, thank you for the support you have shown us. As the JetBrains Toolbox launches we hope that you see the value in it and that we change your opinion with top-notch releases.

    • Zmicier Zaleznicenka says:

      Oh come on, Eclipse will never make it, we both know it.

      Not even close.

    • Ben Claar says:

      This sums up my feelings perfectly. I can’t switch IDEs, but I can and will stop recommending it. This new licensing model is unwelcome.

      • Brian Riehman says:

        Likewise. I was eager to upgrade my license and pay for the new version of IntelliJ and get the latest features. However, I am extremely unhappy to hear that software that is delivered to the customer cannot be purchased for perpetual use.

        The current license model allows people that are satisfied with the existing product to use it forever and those that want to upgrade get a nominal discount on renewal. If the software is on my system and I like it, why do I need to be forced into paying for it forever when I may not want and or need anything more?

        I will no longer be able to advocate for Jetbrains nor will I be eager to upgrade. Instead I will feel that I am being coerced into payment against my will.

        • Michelle says:

          i’ve used jetbrains software for a few years now, but i think the november purchase will be my last. I was happy with eclipse and left it because using your software had some benefits. Changing your License Model makes it unbearable for me follow you any longer. I’ll go back after this (its will cost much time but i’ll do it anyway) . PS. the last update of your software was a few month ago. Some bugs are quite anoying (like gradle in a multi project env using sub projects as assets locations is not possible – tinkering around this problem took much time and the result doesn’t make me happy …) So … is this intended?

          Well, i liked you – much. But i can’t pay forever (i’d have to stop the payment in case of other expenses) for nothing.

          • Michael says:

            Exactly that came to my mind as well. What really annoys me how long it takes to get fixes for really bad bugs / missing features in the products. Like the missing Maven testSource / testTarget support (IDEA-85478) in IDEA. Open since 2012 and still nothing.

            Will JetBrains get more Developers for maintenance when changing to the subscription model?

  18. GT says:

    I think this is an unfortunate decision. Subscription models never seem to be popular.

    Will Community Edition of IntelliJ IDEA still exist?
    If I purchase a yearly subscription, then cancel my subscription (in effect subscribing for one year) will I be prevented from using IntelliJ IDEA after the end of my subscription?

    Currently I have the choice to pay for another years license and get all the new features or continue using the “old” version of ultimate that I have paid for, allowing me to skip release that didnt have updates I was interested in.

    How will the subscription be validated? I mean will I need a constant internet connection so that the IDE can phone home? What happens if I cant get internet connection will I be unable to develop end up with reduced functionality?

    • GT says:

      The deal breaker for me is the requirement to have a JetBrains account.

      • Robert Demmer says:

        Why is a JetBrains account a deal breaker for you?

        • GT says:

          Its a personal thing, I am trying to keep my online footprint to a minimum, the constant having to sign up, even to pay, feels more and more like an invasion of my privacy.
          It is another password to remember, to secure, to worry about, another source of data leakage, another point of tracking.
          Is there really the need for an account, what (beyond a license) do I get in return for giving you my personal details?
          I am sure given the talent available to you, a better alternative could have been thought up.

          I think the subscription model is great for companies, I can see how its flexibility works there, for individuals, it seems to be a worse deal, once we stop paying we cant use the software any more.

    • Robert Demmer says:

      GT, IntelliJ IDEA Community Edition will continue. Any licenses bought before November 2, 2015 are perpetual and will receive one free year of updates. That license is yours forever. If you wish to have any new releases beyond that point you will need to have a subscription.

      Here’s a link to our FAQ that has information about validation and Internet connection:

  19. Leonardo says:

    This is a bad news for developer that use your software.
    Developers that expend time learn all the possibilities and shortcuts for all tools.
    Now we need buy a new license to not lost for what we had already paid.

    • Robert Demmer says:

      There is still the option to buy a perpetual license before November 2, 2015. With JetBrains Toolbox subscription you will continue to benefit from the newest releases, enhancements and features.

      • Leonardo says:

        Sorry, but your argument is little mind.
        After November 2, 2015 the software will become a Service not a product.
        We want a product not a service.
        Please keep option to buy a product not a service.

  20. Adrian Carr says:

    I love JetBrains products, but this really feels like it benefits JetBrains a whole lot more than it benefits me. With this model, I’ll end up paying a lot more or going without.

  21. Jonathan Scott says:

    I am really disappointed to hear of this decision. I love PHPStorm and have sold the product to many of my colleagues but this is just wrong. I’m afraid that I will not be renewing and I will be recommending my company and colleagues to do the same.

    • Robert Demmer says:

      Jonathan, we are sorry to hear that you feel this way. We hope after you have time to digest this change your initial impression will change.

      • Wil says:

        Robert, We, the customers, are sorry that this is the path forward for JetBrains.
        We hope after you have time to digest, you will reconsider this pricing model change.

        Hopefully this isn’t the beginning of the end for what was a fantastic software company.

        Companies that ignore their customers quickly discover just how many alternatives exist.

      • Tobi says:

        Robert, you sound as if you think that we do not have any other options and we have to swallow this anyway. But, sorry, you are not in the position of Adobe.

    • Rafael says:

      I feel the same, I’ve convinced my boss to buy PHPStorm licenses but once he notices the whole subscription thing he will tell me to either stay with what we have or switch to another thing, “no cool toys for you”.

      As for me I might switch to the subscription thing because i’m already a personal customer for side projects but still disappointed. I’ve paid without a doubt because i love the product but also think subscriptions should be optional, not a forced path

  22. Graham Wheeler says:

    I suggest everyone unhappy with this (myself included) start investing more in making Atom a first class OSS alternative.

  23. David says:

    I was actually very close to purchasing two of your ides this week, but after hearing this I have to reconsider it. If you look at the current model for commercial IDEs (so.. Visual Studio) once your purchase say VS2010 you can use it in perpetuity. I wouldn’t mind the subscription if it was an either/or sort of thing.

    Take Webstorm for example. A single developer license costs $50 for perpetuity. Now you will pay $80 a year, and lose access if you stop paying. You can dress this up in whatever flowery language you want but this antagonistic towards the consumer.

    • Robert Demmer says:

      David, Any IDE or .Net tool purchased before November 2, 2015 is a perpetual license with free upgrades for 1 year. Afterwards you can decide to continue with the license you purchased indefinitely or move to a subscription. As Hadi mentioned above, the price for WebStorm has been substantially lower than our other IDEs yet offering similar functionality. The pricing has just be aligned to reflect this. For existing customers, the price remains the same.

      • Fun Tub says:

        why bother responding if you can’t address the real issue… if 01/2016 comes up and i want to use php storm i now have to have pay a monthly fee. If something happens and i can’t pay that fee, see what happened in Greece two months ago on how quick this happens, i can no longer use this product. Or if i don’t have internet connection i can not use this product.

        The point is no one wants to rent an IDE, we will and have been paying for these, your revenue growth shows that. You already make a boat load by keeping the different IDEs under their own licenses, even though we all know it’s the same product with different plugins.

        just stop answering unless you want to address your customers concerns.

  24. Daniel Alvarez says:

    This is going to cost you guys customers. JetBrains had an almost cult like following, touted as the best in every forum I visited. Now, the overwhelming consensus is that this is a bad move. Whoever was in charge of this idea at your company really needs to take a good luck at the feedback for this move, it will not be a net positive. Just look at how other subscription based companies are regarded, e.g. Adobe, etc..

    Oh well, back to eclipse.

  25. Jessey says:

    Alright, so for complete verification, I am a student, most likely to get my degree in 6 months. I LOVE phpStorm, and I want to start my own company. I was going to get a license for Phpstorm, but right now I am unsure what’s going on.

    So my question(s) are:

    1. IF I purchase a license right now, will I be able to continue to use phpstorm even after my license has expired, but without getting the newer updates?

    • Robert Demmer says:

      Jessey, Yes. If you purchase PhpStorm before November 2nd, 2015 your license is perpetual and you receive 1 free year of updates. It is yours indefinitely.

      Only if you want to receive updates and new releases beyond that initial one year term would you need to move to a subscription.

  26. MuppetGate says:

    Okay, so I appear to be the only person here who thinks this is the best news out of Jetbrains in forever.

    I need to use IDEA, RubyMine and PyCharm. I’m going to start iOS programming this year, so that chances are I’m going to start using AppCode too. The cost of all those IDEs is pretty steep, especially since I upgrade about once a year. Now I can have the whole lot for a hundred quid a year! I’m mugging them!

    If you’re just using the one IDE, how much is that? £79.00, which is pretty close to what I was paying anyway.

    I can see why folk don’t like subscriptions, but I object to them based on value for money, not on principle; you don’t own the software either way.

    • Robert Demmer says:

      Thanks. We are happy to read your comment. Good luck with iOS and our tools!

    • Michael Taylor says:

      You realize that IDEA has plugins for Ruby and Python, right? It might for Objective-C, I dunno since I never use that language. You shouldn’t be buying IDEA, RubyMine, and PyCharm, though, since IDEA alone with plugins makes for a much better multi-language developer.

      • Robert Demmer says:

        Michael, All products go beyond those you listed and no IntelliJ doesn’t support Objective-C. “All Products” include: IntelliJ IDEA, AppCode, CLion, PhpStorm, PyCharm, RubyMine, WebStorm, ReSharper, ReSharper C++, dotTrace, dotCover, and dotMemory. There’s plenty of time for people to research what they need and make the right selection.

      • MuppetGate says:

        I’ve tried using IntelliJ for other languages and I don’t like it. All the plugins give you the functionality, but the workflow is too disjointed. I don’t like having to wade through standard java libraries while working on a Python-only project. That’s why I use PyCharm.

    • kybernetikos says:

      > I object to them based on value for money, not on principle; you don’t own the software either way.

      If you’re using most of the tools, this does offer value for money, if you use only one, it’s similar to what you have at the moment, but that is a horrible value for money proposition compared to the current state of affairs.

      There is clearly a monetary value to be placed on having the right to use a piece of software into the future, without worrying about phoning home every 30 days. This comment page is full of people who attach quite significant value to this. Suppose you’ve got two options, one where you pay $X and can use a piece of software for a year, and one where you pay $X and can use it for as long as you want, clearly the second option is better value for money, by a long way.

  27. Mario says:

    I for one like subscriptions as I feel it gives me more control on how long to test drive a tool, and provides me with freedom to change tools as I only commit on a monthly basis. Saying that, I wish the announcement was a little more ‘open.’ I imagine the switch to the subscription model is in partially driven, if not completely, by the desire to better predict revenue from licenses. Nothing wrong with this, as you are a business and not a charity. But how about you also state this plainly? Just a thought.

    • Robert Demmer says:

      Mario, thank you for your feedback. Is there something in particular you feel that we could have communicated better? What didn’t come across clearly?

      • Tobi says:

        Your communication was an assault on the intelligence of us. You write as if you would do us a favour, but it is obvious, that this is a money grab.

  28. Dan says:

    Please at least retain the option for perpetual, non-subscription licenses. Given the network requirements where I work and the difficulty in changing any infrastructure, this looks like it will prevent us from using any JetBrains tools. We just got everybody on the ReSharper bandwagon; I’d hate to lose that.

    • Robert Demmer says:

      Dan, licenses purchased before November 2, 2015 are perpetual. Can you further explain what network requirements are a hinderance to using our tools? You can find our FAQ on this topic here:

      • Brennan says:

        Perpetual for a year? After that we cannot renew the perpetual license for another year and so on to keep updates can we? This is why it’s a problem. By allowing us to have a perpetual license but not renew from 2017 on wards we cannot have updated software unless we use subscription. This additional year of updates for perpetual licenses just delays the issue by about a year, after that we’re stuck with that version unless we switch to subscription( which if we stop we can only use the older perpetual license version we have ). This is the problem everyone is concerned about here.

      • Dan says:

        No internet access at work, and setting up an internal license server will add more work to our already very busy IT team. Also, I use my personal license for ReSharper Ultimate at work, since our corporate licenses are just for Resharper… vanilla? I have at times also used my personal IntelliJ license; we have no corporate IntelliJ licenses. From what I’ve read, there’s no way to install a personal license into an internal license server.

        We’ll work with the JetBrains sales team, but it looks like I will lose access to things that I could previously do.

      • Minras says:

        I can explain network requirements.

        Our development is done in a local network without any Internet access.
        For all external communications we have separate laptops. Actually I use this laptop only to read emails and use Google.

        This corporate policy is quite common for Western Europe at least. My company has 300-500 developers, not all of them use JB software, but it’s quite popular. You will lose all of them right after implementing that subscription model.

  29. Martin Lind says:

    Back to eclipse… lel.

    • Robert Demmer says:

      Sorry to hear that Martin. IntelliJ IDEA Community Edition is still here and free. Is there something you are missing that is in Eclipse?

      • Martin Lind says:

        You’re product is great. I really love it.

        But subscriptions is for me a (big) negative point. So much that I rather use a lesser option. Unless there exists no other option and options do exist.

        Eclipse is better for working with JBoss tooling. (Camel designer, dialogs for everything etc). So you have competition. Your product is far superior when it comes to editing code though.

        I dislike subscription because I want to feel like I own the stuff I use. (Don’t give me the “You don’t own the software”. I own the right to use the software, rather than renting the right to use the software).

        • Martin Lind says:

          I can add: I’ve bought IntelliJ IDEA 13 Ultimate edition.

          Plus what you can make to keep me a customer, user and fan: Copy all features from Ultimate into Community Edition.

          • Robert Demmer says:

            Well we can’t promise to copy all features from Ultimate into Community Edition but if you relay and what are missing in CE with Eclipse, I can make sure the right people receive it. Send me an email if you can at robert(dot)demmer [at]jetbrains(dot)com.

  30. Leonard says:

    I’m definitely OK with this. I use Idea, CLion, AppCode, and sometimes Resharper. I use most of these actively enough that I want to stay current, so I already purchase upgrade subscriptions to the first three of these. Because they come due at different times, I am renewing something every few months. A single annual renewal is more convenient. The pricing certainly looks reasonable.

    • Robert Demmer says:

      Thanks for your comment Leonard and your support! We will keep impressing you with your our new releases.

  31. Sean Heaton says:

    I normally do not bother commenting on threads such as this, but I thinks this is such a *terrible* idea that I can’t help it. I have used IntelliJ IDEA Ultimate for a few years now. I have always been really impressed with it and with JetBrains. However, like another person said above, you have turned a happy customer into a very unhappy one. I have never minded upgrading because you have always provided enough features to make it more than worth it. But–like others have said–it was my CHOICE. I could upgrade if I wanted, but I could keep using the software I purchased either way. You are now taking that choice away from me.

    You mentioned above that, “we think we’ll be able to concentrate on quality more than trying to impress users with new features so they buy upgrades.”

    All that says to me is that instead of innovating and continuously giving us our money’s worth by making the product better, you will instead hold us all hostage and force us to pay just to use your tools, even if they do not improve at all.

    Back to Eclipse for me.

    • Eugene Toporov says:

      Thanks for taking time to tell us what you feel Sean, it is much appreciated.

      I’m just not sure why you think the innovation should stop. We do not imagine our work and future updates without it.

      • Sean Heaton says:

        You already don’t seem to care that this move is apparently making many of your customers unhappy, so why would I trust that you will keep us happy by innovating?

      • Emil says:

        I believe that the current (perpetual+paid updates) licence model creates a necessary incentive for you to deliver meaningful updates to your product and customers; no worthwhile updates = no more money from your established user base. The subscription model does take away that incentive by holding the product ransom and as a result you wouldn’t need to update your product to get a continuously flowing stream of greens.

        I’m not saying you would stop innovate and deliver great updates with new features, but now you don’t HAVE to. And that is not as customer friendly as you are portraying it to be. You are focusing more on the price details than the overall principal and its consequences.

        On the other hand, I can see that the subscription model would make it much easier for your customers to switch tools, but if you are going to use that as an argument we both know that it should be offered in addition to the current licence model to satisfy the relevant user base. I feel like this announcement is more of an insult to our intelligence, and a concealed money grab, than a favour to customers.

    • Sören says:


      I have been a happy IntelliJ IDEA Ultimate customer for a couple of years now. Just as Sean described it, I’ve upgraded every year. It was my decision and I’m ready to upgrade this year as well. But I can stop at any time and still use the software. This has been a fair deal.

      Sorry to say that but selling your subscription based model as being “easier” is nonsense. It’s better for JetBrains and worse for the customer. If you really switch to a subscription based model I will definitely install Eclipse and give it another try.

  32. Jonathan Davis says:

    You may have just lost me and all developers at my company as customers.

  33. Mikey says:

    $150/yr for existing customers and $200/yr for new customers to get everything? I never considered using JetBrains stuff for all of my development, but you’re right, the lower entry price is extremely appealing. Currently it’s around $1000 for new licences of all products and $530 for renewing all products, so uh, yeah. Way better.

    It does suck that the perpetual model is going away, it’s definitely great for a few use cases. However, the technologies the products are built around are moving fast so using an older version might not be the best idea anyway.

    Anyway, this is definitely great news for me as I renew licenses as I start working with a certain technology. This license model is more in line with how I work.

    • Egor Anisimov says:

      Seems like this was written by someone from JetBrains

      • Mikey says:

        Dude, I already pay $200+/yr for their products. Getting ALL of their products for $150-250/yr is awesome for me. If you think everyone who likes this change potentially works for JetBrains you’re an idiot. Take your FUD and shove it.

        • Jonathan Tullett says:

          You’re missing one key fact: you do get ALL their products for $150-200/year, as long as you keep paying the fee. If you want to stop paying the fee, you have NONE of their products.

          With the current subscription model, you get their products for $whateveryouarepaying and if you decide to stop using paying for upgrades, you get to KEEP those products.

          That’s what people are upset about. It’s the perpetual paid tie-in to the ecosystem.

          • Mikey says:

            I have been well aware of that fact, but it doesn’t really affect me and my work habits. Namely, I don’t want to use an outdated product so I would be paying to upgrade my license anyway.

            However, I do understand why people are upset and I agree that it’s not a very customer-friendly change to the licensing model.

            • None says:

              “I don’t want to use an outdated product”

              The great thing about IntelliJ has been that it does not become “outdated” just because it’s a version (or few) behind the cutting edge – just don’t expect it to support more recent tools out of the box. It’s like that for quality pieces of software, you know the kind you and I are happy to “buy”. Now however, even if you have no intention of using the new faddy bloat features, you still have to pay for the “upgrade” which is now just called “your subscription”. Thanks but no thanks. I’ve been using IntelliJ since v3, with my own personal licence since v5 (generally upgrading every 2-3 years on a “I want those features” basis).

              After the move to subscription based products I will CONTINUE to use my IntelliJ 14 because my licence allows it. Hahah. For anyone using IntelliJ as of 2016, they will not have that opportunity. They MUST keep paying.

      • Hadi Hariri says:

        We certainly don’t engage in this kind of activity.

    • Terence Martin says:

      Would that every JetBrains customer had a need and desire for the entire complement of tools that they offer.

  34. jack fruh says:

    To me, what is disappointing is that you already had the best licensing model out there!
    Developers bought the software at a higher initial price, then paid yearly for updates. Your updates were always back dated, so that there was no benefit to delaying an upgrade.

    I actually had thought that you were geniuses for coming up with this model.

    From a psychology perspective, users had a feel good about you, your company and your products. While we ‘owned’ the product, we also paid yearly to keep product development going. It really was a subscription model all along, but users had the flexibility to defer payments.

  35. Egor Anisimov says:


    is it possible to leave the normal licenses in place as well? The subscription model will definitely increase the payments developers make for their tools. And if the company cares about the clients and their needs (which is stated several times in this text), then it should care about the ones with less demand for updates.

    Let me explain. I don’t need updates too often, so like my PHPStorm 2 worked fine for me for 3 years, until the code I worked with evolved. After that I bought PHPStorm 7. And it works pretty well for me still. I usually pay money myself, so i don’t rely on my current employer and the tools they use. It means, that I don’t have budgets of hundreds of thousands dollars and track my expenses carefully. Which many other developers do as well.

    So, can you, please, keep the current licensing model available? Which would mean, that the company indeed is flexible and follows the needs of all the clients it has. And the clients indeed can choose the product which is most appropriate for them.

    Thank you.

    RT or upvote, if you agree.

    • Robert Demmer says:

      Egor, Thank you for sharing your situation and your continued support. If you upgrade your PhpStorm license (if it is out of the free 1 year of updates) before November 2nd, 2015 then the license is perpetual and yours to keep. This would include the upcoming PhpStorm 9.5 release and updates over the next year too. Based upon your upgrade history it may last years as it has in the past. By this point maybe the situation would have changed to where a subscription makes sense for you.

      • Egor Anisimov says:

        So two negative items here:
        1) Right now JetBrains already goes wild and forces me to pay money until Nov 2nd to buy last normal license, although this is not yet the time I need to upgrade

        2) In two years, when I’d like to upgrade again I’ll have no choice but start paying monthly ransom, otherwise my IDE just stops working

        Sorry, guys, I won’t let happen to both of the things. I won’t upgrade now, just because Jet Brains wants it. I will switch to another IDE in two years, if I need to.

        BTW, it’s a pity, that Jet Brains is not a public company. The consequences of this announcement are so clear, that I’d made a fortune by short selling its stocks :)

  36. Henk Jansen says:

    Well, crap. Back to NetBeans then. I will not pay a ransom to keep my IDE working.

    • Robert Demmer says:

      Sorry to hear that Henk. IntelliJ IDEA Community Edition which is also open source and free will continue to be available. Is there something you feel it is missing?

      • Olaf says:

        What Netbeans has, but IntelliJ IDEA Community Edition is missing:
        * Support for the whole Java EE stack
        * Support for HTML/CSS
        * Support for JavaScript
        * Support for Application Servers

        IntelliJ IDEA Community Edition is not an IDE for Java EE development, Netbeans certainly is.

        I also dislike the new software subscription model and feel tempted to have give Netbeans a real try (after using and loving IDEA for many years).

        • JTW says:

          Correct. CE is nice for schoolkids making their small homework thingies.
          For the professional developer it just lacks everything you need to get your job done.

          None of us are unwilling to pay a decent price for our tools (even paying out of our own pockets because our employers and customers ARE unwilling to spend money on something when something else can be got for free), but we’re an independent minded bunch who don’t want to be held to ransom for fear that our tools will become so many dead bytes on our computer drives.

          And no, I’m not now going to upgrade to IntelliJ 14 just so I get one more year of free bug fixes after which I’m beholden to pay a ransom fee for the privilege of paying you another ransom fee a month later.

          Netbeans it is. It used to be terrible, but by now is good enough that it’s at least equivalent to IntelliJ 12 and certainly better than a non-functional IntelliJ 14 or whatever version you may or may not produce in the future now that the incentive to deliver anything is pretty much gone.

  37. I am sad to see JetBrains following the online subscription model. I have advocated and in many instances even been responsible for pushing purchase orders towards JetBrains due to my advocacy of the products. But with this stupid model I cannot in good consciousness keep doing this.

    As others above me have, more eloquently than me, said the subscription licensing model is a killer. It is all about choice. I never liked this form of DRM with EA and UbiSoft, why would I even bother with this from my *tool* vendor?

    JetBrains, you lost an advocate and a customer with this move.

    • Robert Demmer says:

      Jeroen, we wish you felt otherwise. What exactly bothers you about the move to JetBrains Toolbox?

      • Tim De Grande says:

        I can’t speak for Jeroen, but here’s what’s bothering me.

        I’ve been an IntelliJ user for quite a few years and spent hundreds of euros upgrading to the version I have now. I’ve done this knowing that if I ever can’t or don’t want to upgrade, that the money hasn’t been wasted and that I’ll be able to keep using the then current version (current at the time I stop paying).

        Now, with the toolbox subscription, it doesn’t matter how much more money I spent. The version I have now is the only one I’ll be able to use if I want to stop upgrading. If that time occurs in 2019, I’ll suddenly revert back to IntelliJ 14 (basically making it useless).

        I’ve seen it suggested a few times in this thread already: why not allow users to “keep” the version they last paid an entire year for? Meaning that if I subscribe until November 2019 and then cancel, I’ll be able to revert the version of IntelliJ that was current in November 2018. It’s still arguably worse than what I have now (now I keep the upgrades that were releases a year *after* I stop paying, then I lose all upgrades that were released the year before.) but it would make the change a whole lot more palatable.

  38. Tropper says:

    If you are professional user and rely every day on your JetBrain product then this is not much of a chance actually. Back then I bought a new version/major update of idea every year – now I have a yearly subscription.

    Yes, back then you were not forced to update – but I sure most people who used IDEA everyday did buy the update when the first bug fix release (x.1) was out to get use the new features.

    And I personally prefer the subscription model because JetBrain is no longer forced to release a new major update with “killer” feature every year – with a subscription model you can release new feature when they are done.

    • Egor Anisimov says:

      > JetBrain is no longer forced to release a new major update with “killer” feature every year

      And you say this is good… Cool point of view.

      Let me explain it in simple words – now the company doesn’t need to bring any value to clients, except for keeping their tools from shutting down.

      • Tropper says:

        It is:

        a) you get a new feature when its done – not when a year is over. This means you could get a feature much earlier. This also means when you get a feature it really works because you no longer have to care about time constraints.

        b) you don’t have to do a “big new killer” feature which sounds good on paper to convince people to update. Instead you can focus on your existing feature. From a marketing point of view it is much better to have big new feature. But from a customer side it is much better to have 100 little things.

        • Egor Anisimov says:

          Nice dreams about an ideal world…

          • Robert Demmer says:

            Egor, I don’t see this as off-base.

            • JTW says:

              it’s a pipe dream. In the real world you get NO new “killer features” at all, merely small visual things to keep the pundits from giving up hope that those new features will come at some point.

              Maybe Jetbrains is different, but such is the experience many of us have with any company supplying software using a subscription model or something similar.

        • Henk says:

          Well, you assume that everyone only pay their licenses if there are killer features.

          Only speaking for myself: I have paid two products (PHP Storm and PyCharm for 6 and 4 years in a row). Not for the new killerfeatures, but for simple big fixing is no problem.

          So I don’t understand the logic behind your reasoning.

          But the subscription method will kill this relationship.

          For the record: My Pycharm renewal is due in october. I will not do it until the licensing is perpertual again.

          Same for PHPStorm in december.

          You can’t build a business on a company you no longer trust.

  39. Mark Grimes says:

    I’m OK with this. I’m very much addicted to using my IDE rather than it using me.
    The competitors’ year-after-year neglect of all the areas explaining why I buy JetBrains products is ongoing. JetBrains made a happy customer out of me and I bought several products to support all my language interests — yet dread the cumulative cost of upgrading all these tools annually.

    As a polyglot programmer who perpetually upgrades IntelliJ, AppCode and CLion and wouldn’t mind access to other tools (0xDBE post release, C# tooling), this passes on a cost-savings. I feel less impacted because this “choice” we had before was always something I looked at as a “requirement” for keeping up with *continual platform toolchain changes*.

    • Robert Demmer says:

      Mark, thank you for your comment. We are happy you are onboard and will continue to deliver releases that exceed your expectations.

  40. John Smith says:

    I am not interested in renting software – when unemployed looking to save money you need to cut back on things and if I am back in that situation again I don’t want to chose between paying for software to continue a hobby/keep in practice for work (at a time I most need a cheap hobby) or putting food on the table/paying bills – especially when there are plenty of alternatives.

  41. If we’re an existing user of two products (say WebStorm and Resharper), can we upgrade (and qualify for the discount) to the All Products plan, or just the individual products?

  42. Gabriel Smith says:

    Will IntelliJ IDEA Ultimate still offer other language plugins (PHP, Python, Ruby, etc)?

  43. Sven says:

    I’m very much against subscription but can see why a company may think they are good and accountant love it.

    I would suggest a 3rd way.
    Subscription however if you have paid continuously on the single or indie models for a duration say of 12 or 18 months then you get a perpetual style use from that version should you cancel. No more updates till you pay again…then if you have a break like that then the clock starts again before you get the perpetual.

    That would appease most people I’m sure. If Adobe did that they would have my Lightroom money now

    • Brad says:


      Given the firestorm of complaints here, I think if you made this *one* modification, you would ease the criticisms substantially. After 12 mos, or an annual subscription, you can drop off, keep your current version indefinitely–then join again later to get updates. Those updates go away if you only stay for a month or 11 (meaning you revert back to the version you qualified for by staying subscribed for 12 mos or more), but after a year of re-subscribing, you get permanently bumped up and perpetual again as long as you stay current (or you stop at the version you last had 12 mos of subscription for). Best of old and new models. Lower income devs can adjust their budgets and most others pay subscription rates.

    • Robert Demmer says:

      Sven, thank you for proposing your 3rd way.

    • Jacob W says:

      + 1 This is the best of both worlds in my opinion.

    • Julian Schnidder says:


      • Kristian Hellang says:

        This would indeed be a good solution, but it also has one problem; If you “earn” a perpetual license after subscribing for 12 months and keep the subscription for two more months, what happens to updates you’ve installed in the last two months? Do you have to downgrade? Also, which products would you get a perpetual license for? Surely it would be cheap if you got a license for all tools in the toolbox.

        • Wesley says:

          He is saying that once you hit the time limit of consecutives months then you get a perpetual license for the product, so if the limit is 12months and you stop after 14months then you get a perpetual license of the version that was out during month 14.

          If you skip a month at any point you have to start over.

    • Florian Waltersdorfer says:


      • Steve Ovens says:

        I’ve always upgraded my (multiple) IntelliJ products and advocated the tools to others. The move to a subscription model is clearly a good thing for IntelliJ – and equally clearly not a popular one with many customers.

        This proposal is a very sensible middle ground – after paying the subscription for at least a year – if at any time I stop paying, I still retain a perpetual license for whatever the latest version was at the time of my last payment.

        If this also removes the *requirement* to have an internet connection available to check the license every 30 days – (i.e. you would only need to check the license when you check for updates) – then it fixes the two biggest issues I have with the new model.

    • Lance says:

      I’m really, Really, REALLY hoping that this will be the main change in JetBrains announces in their pending update.

  44. Mike Jay says:

    So this boils down to sticking with the latest version available at 2 November 2016 (free upgrades) or join the subscription model from there on.
    If people don’t want to join the subscription model now, what makes you think they will in a year from now? Sure very large companies will dig into it because status-quo, startups will probably adopt this too because lower price of entry, but small and medium companies won’t.

    • Robert Demmer says:

      Mike, thank you for your comment. There isn’t a one size fits all solution. Personally speaking, I had many of the same objections and issues with the subscription model. Today I find myself happy with multiple ones. Time can change opinions and we hope that you will see the benefits.

      • Jonathan says:

        But not your opinions, just ours. Yours are set in stone, apparently.

        Hopefully you can give this as much thought as you expect from your customers.

        • Robert Demmer says:

          Nothing is ever set in stone but this is our direction and trust me your voice will be heard.

          • JTW says:

            heard, but not heeded.
            At least not until your customers have deserted you and then it’ll be too late for you or your customers.
            And those customers aren’t likely to return when you revert your policy, not only won’t they trust you to not backpedal on them but they’ll have invested in other tools already.

      • Robert Fisher says:

        One size does not fit all. Exactly. Which is why the sensible thing to do would be to provide this as an option for the people it fits and keep the old model as an option for those who it does not fit.

      • Sam says:

        Time can change opinions

        But that’s EXACTLY the problem.

        As much as I trust you guys at the moment, you have no possible way to guarantee that your company’s decisions will stay aligned with my needs as much as they have in the past.
        And in fact the claim above in the comments already reads to me that you intend to take advantage of the fact that subscription locks your customers in more. Even if you’re not planning to do so consciously yet, the lessened pressure from competition will definitely influence some of your decisions internally.

        Opinions change, key people leave the company, Sales influences decisions, companies get bought out, etc. This is all normal for any business and has to be expected.

        Up until now we could vote against changes we don’t agree with our wallets. However after we change our perpetual licenses to the enslaving subscription model (and wait a few months/years) we lose the ability to vote with our wallets without directly influencing our ability to open the software on our disks (or go back to an ancient perpetual version dated Nov2016).

        In order to somewhat salvage this situation you need to at least provide a way to back out properly by allowing 12+months subscribers to transfer back to a perpetual license at the point in time they choose.

  45. Annoymous says:

    This is bad. Under this new system, if my renewal falls on the periodic corporate spending freeze, I’m hosed, not just missing new functionality.

    • Robert Demmer says:

      Tell us what we can do to help ensure this doesn’t happen at your organization. How can we clearly communicate to those with who hold the wallet the benefits of JetBrains Toolbox. We would be happy to help ensure this wouldn’t happen.

      • dave says:

        Yes, tell us when you have money, and we will be more than happy to bill you then.

      • Wil says:

        So if a corporation chooses not to pay the recurring fee for the ide subscription, JetBrains will happily accommodate them.

        If an individual chooses not to pay the recurring fee, she is locked out of the ide?

  46. Sudhir Boddu says:

    Liked this model. How Jet Brains is going to manage community edition (intelliJ IDEA, Upsource, Youtrack etc.)? Are you guys starting community services in Tool Box as well.?

    • Hadi Hariri says:

      There are no changes to the Teamware tools nor our free OSS editions. And no plans for changes either.

  47. Mark says:

    Two questions. First, is there a way to extend existing IntelliJ licenses before November 2, to get another year of updates before having to switch to subscription (although I always thought the IntelliJ licenses went by major version number, not per-year)?

    Second, is there a typo on the “Companies and Organizations” tab? It says the All Products Existing User price will be $399/year, which is the same as the new user price for the same bundle; no discount at that price point.

    • Robert Demmer says:

      Mark, In regards to “stacking” it would be best if you contact based upon your account. If it isn’t too much of a hassle could you send a screenshot of the typo to robert(dot)demmer [at] jetbrains(dot)com. We are trying to replicate but this might help.

  48. Mike L says:

    I have been a Jet Brains user for a long time (Resharper and IntelliJ since at least version 4). I also usually carry a personal license for each as well as for the office.

    I develop in both .NET and Java and use both Resharper and IDEA. At least I used to. I work for a large Bank and they will never pay for a continuous license or allow our developer machines to access the internet for get licenses. I have a hard enough time getting the current version approved when we add new people.

    The main problem that I have is that I don’t mind paying for a license from time to time, even a personal license for personal projects. The problem is that I may not use the app for months at a time (work on .NET for a few months and Java, or perhaps SCALA). I don’t need all the new bells and features and tend to skip upgrades from time to time. Now I can’t. You lost a very loud advocate for your product in a large organization.

    I can live with Eclipse and Code Rush, so back to that.

    • Robert Demmer says:

      Mike, Thanks for your comment. I am not sure we can talk through this here as your situation is more complex than others with potentially more barriers that you have explained. I would recommend sending an email to robert(dot)demmer [at] jetbrains(dot)com and we can try and work through this with a sales team member. If you are only using an app for months at a time and moving on to another then JetBrains Toolbox sounds like a good option for you and your organziation.

    • Andrey Cheptsov says:

      > I work for a large Bank and they will never pay for a continuous license or allow our developer machines to access the internet for get licenses.

      There is no need in an Internet connection for large organisations: you can set up a local “license server”. This is what many our customers already do.

      From our experience for companies a subscription-based model is even more convenient as it implies more flexible budget planning.

    • Andy says:

      I also work in a large bank and this change means we will have to stop using Intellij. It doesn’t work from a purchase order point of view and due to the lead time involved in getting new software versions packaged. If you don’t already know this then you are out of touch with how most large bureaucratic corporations work. It simply won’t be possible for developer advocates to get approval to buy Intellij any more and the community edition doesn’t have the necessary features for enterprise development.

  49. Nate says:

    I’m going to chime in with what everyone else is saying. At my office, we already paid to renew every year. But I think we’ll probably just keep our current version for awhile now when our license runs out.

    We, your customers, don’t like this change. It’s not that we don’t want to pay (we were already paying every year!) It’s that we don’t like the model. Please communicate this to whatever pointy-haired boss made this decision.

    • Robert Demmer says:

      Nate, Thanks for your comment and concerns. If you are upgrading to every year can you explain more about your objections?

      • Nate says:

        I’m not sure I could say it any better than Mathieu’s post a few posts down from here.

        The short version: I want the ability to stop paying and still use what I purchased. (One example: Sometimes my organization is very slow with purchases. I don’t want my tools to stop working during this time).

        • dave says:

          Obviously, the solution is to give Jetbrains more money up front, so instead of paying for a year in advance, you have to pay for two years, then a year from now, pay for another year. That way, you always have a good long time to pay before your license runs out.

          Morning Win! …well, for Jetbrains…

  50. Max says:

    I personally recommended Intellij for our company, around 12 licenses. Really loved it.
    It’s back to Netbeans then.
    Good bye, Jetbrains.

    • Robert Demmer says:

      Max, sorry to hear this and would hate to see this happen. What does NetBeans offer that the free and open source IntelliJ IDEA Community Edition doesn’t?

      • Olaf says:

        What Netbeans has, but IntelliJ IDEA Community Edition is missing:
        * Support for the whole Java EE stack
        * Support for HTML/CSS
        * Support for JavaScript
        * Support for Application Servers

        IntelliJ IDEA Community Edition is not an IDE for Java EE development, Netbeans certainly is.

      • Tobi says:

        You can use it without accepting any ransom crap.

  51. Michal says:

    Not happy about that, Jetbrains! At my company, obtaining subscription-based software is difficult – they are not pleased to hear that they will need to pay for something every year. With the old model, I would apply for Idea upgrade when the new version appeared, and wait for company approval. If the approval was delayed by couple of months, no problem – I could still use the old version.

    Now they will probably object to buying a subscription in the first place, so you will quite possibly lose a customer.

    • Michal says:

      And on top of that, how do I look now in the eyes of the colleagues to which I advocated your products, and who I converted to using them? I can’t believe this decision is coming from a company I really trusted.

    • Robert Demmer says:

      Michal, Organizations can be a beast to navigate. I think the clearly communicating the benefits of the subscription model could be helpful. Is there something we can do better in this regards?

      • Michal says:

        Your presumed benefits will be overshadowed by the necessity to pay every year. At my company, Idea is considered a non-standard IDE for which you have to make a valid business case. Last time I was requesting a licence, they were already apprehensive about renewals. By introducing the new payment scheme, you just make this task much more difficult, if not impossible, and your marketing department has 1% chances to influence that.
        And, on a side note – what’s with this talk about organizations? Let’s stick to the point.

  52. Matthieu Napoli says:

    This is terrible. Absolutely terrible.

    I’ve been advocating PhpStorm to everybody, up to the point of being annoying. Now I’ll be actively looking for an alternative.

    Please reconsider letting the “forever” license-model leave in parallel with the subscription one. I would pay for subscription (yes, subscription!) without caring if I was still able to buy a full license whenever I needed one.

    The big problem is having no alternative to being forced to pay every month/year to keep using the software. If I had an alternative, I would pay for it.

    • Robert Demmer says:

      Matthieu, Thanks for the feedback. If you like the tool why look for an alternative? Choosing the best tool is paramount. If you are willing to pay for a subscription and understand the benefits then help us better understand your objections.

      • Brad says:

        Robert, I appreciate you responding to all the thoughts here.

        Let me try to answer what you don’t seem to be “hearing” from most comments here: That it’s the *model* that is being resisted, not the total $$ spent. We’re wanting to be treated fairly, and for Jetbrains to make money, fairly.

        A subscription model just feels unfair, even if we end up spending less $$ with you, overall. This is why we have always loved your old licensing model, it felt fair, even if you raised prices, we could choose or not choose to continue to purchase.

        These are not micropayments. If I dipped into an IDE for an hour to fix a bug from code I wrote last year in Python, and a $0.40 charge was applied to me from Jetbrains, I wouldn’t have any issue, if I didn’t have to enter a credit card, it was totally seamless, etc. If I am regularly using the product, then yeah, I’d like a monthly or annual subscription and not worry about it. You’re kind of in the painful middle where there’s a bunch of cognitive ‘noise’ in a devs head about whether it’s worth it.

        THAT is the worst place to be. Developers have to do everything they can to avoid distraction and cognitive ‘noise’ in their jobs. The LAST place we want cognitive load increased from, is from our tools vendors.

        Anyway, hope that helps explain it. It’s the subscription model, not the $$, that matter here. This is (I’m guessing!–correct me if I’m wrong Matthieu) why Matthieu says he’s willing to pay for a subscription, as long as he could also get a perpetual. We want choice and to not have to ‘worry’ or be forced to make these economic decisions on a monthly basis. [I think my replies supporting Sven’s idea would advance Jetbrains goals a lot, not totally, but enough and it might alleviate a lot of customer churn and revenue loss otherwise. See Netflix’s attempting to separate DVDs from streaming “too early” from a few years ago, as another example that blew up.]

        • Matthieu Napoli says:

          > This is (I’m guessing!–correct me if I’m wrong Matthieu) why Matthieu says he’s willing to pay for a subscription, as long as he could also get a perpetual. We want choice and to not have to ‘worry’ or be forced


          > Let me try to answer what you don’t seem to be “hearing” from most comments here

          I wonder if they don’t “hear” it, or just don’t want to discuss that…

          • Robert Demmer says:

            We hear you but we don’t have an answer to every comment that is going to be satisfactory to the person at the moment. We are certainly open, willing and want to discuss it. We are just processing loads of feedback at the moment. Not every question will have a “final” decision at the moment. The date set is November 2nd and there is time between now and then to share and discuss.

        • Robert Demmer says:

          Brad, appreciate the thoughtful feedback. Give us some time to process the feedback from all the channels. Lots of information to comb through right now.

      • Matthieu Napoli says:

        I want to know that, if some day I can’t pay or don’t need the new features, I’ll still be able to use the software I bought. The price might not be an issue today (and I’d be more than happy to pay/have my company pay a subscription *for updates* because I think the product is worth it), but I want the *choice* to be able to not update and not pay. It’s about not being forced by Jetbrains to pay forever. Nobody likes that.

        Additionally, today I know that Jetbrains has to create new features for me to buy the updates. With a subscription, we have *no guarantee at all* that Jetbrains will continue innovating forward. Repeating “yes we will for sure” bears no value whatsoever, especially when we see how you customers are been treated today…

        If I have the option to fall back to a perpetual license, I know that: I’ll be able to use PhpStorm the day I can’t pay for it (or don’t need updates), and that Jetbrains has to keep improving its products (else I move back to perpetual licenses).

        • Robert Demmer says:

          Matthieu, again thank you for your comment. You have legitimate concerns that we will address in the coming days. At the moment, I can only repeat what I have said about adding features. Have you been left standing at the alter so far? JetBrains has, can and will continue to deliver the software you want, need and include features you didn’t even think was possible.

          • Collin says:


            You’ve completely missed the point. The present model, where all upgrades are purchased at the discretion of the consumer, *requires* that you produce updates worth buying. The new model *forces* the consumer to continue paying; there is no business incentive for you to release quality updates. We don’t trust you to necessarily continue releasing the same quality of product when your incentive is removed, especially when we are already feeling alienated by the abandonment of perpetual licensing.

  53. Max says:

    Looks like Jetbrains are about to shoot themselves in the foot :)
    A LOT of disgruntled paying customers.

    • Robert Demmer says:

      Max, there’s lots of discussions out there at the moment. Let’s see when the dust settles. Change is often resisted.

      • Nate says:

        Change is often resisted.

        Yes, particularly when it provides a net negative. If your change had real value for your customers, it wouldn’t be so strongly resisted.

        I appreciate you responding to people’s comments here, but this dismissive comment makes you sound like Facebook, not like the Jetbrains that many people here have been fans of.

  54. Oletros says:

    ” Lower entry costs also make adoption easier.”

    Talking about individual developers

    Someone that buys Pycharm past 01/01/2016 will pay 99€/year, until now they paid 99€ the first year and 59€ every upgrade.

    How is this a lower entry cost? That person will pay 40€ more every year

    Webstorm was until now 49€ the first year and 29€ next years

    Now is 99€/year, 70€ more each year

    I don’t understand. Well, in fact, I understand, and it doesn’t look good

  55. Jason says:

    Like others I am was torn about this announcement. I loathe subscription fees but in this case feel the pricing is fair and appreciate that you announced this in advance so we can plan accordingly.

    I take contracts across multiple languages so I have ultimate for php/java. I have been wanting access to resharper and AppCode but the cost just got unreasonable. Not unfair, just didn’t want to keep breaking out the credit card. This models ensures I can use the best tool for the job regardless of what language they want me to work in that month and is a very reasonable price for existing customers.

  56. M says:

    I have always been a supporter of Jetbrains, right back to the old days. This is a obvious money grab. We’d all love a monthly top-off, but this wont cut it with the mega-corps. People like me have worked hard to get a license with with FTSE 500’s (I’ve got Idea into at least 4 Billion Dollar companies).

    Now I get to enjoy eating my hat, and learning Eclipse/Netbeans all over again. I am literally in the middle of getting sign off for Idea 14.x at a major investment bank – that’ll be pulled tomorrow. Poor form guys.

    • M says:

      …And that’s taken me a few months to arrange…

      • Tim hawkins says:

        Im the same, in tbe middle of a major evaluation/rollout. Now we are going to have to shut it down. There is absolutly no way im going to be allowed to use subscrition based tools in our group. (55 devs). We only use one tool, phpstorm so there is no benifit to the toolbox other than we will lose access to our tools each year while we try and get the subscription renewal through the budgeting process.

      • Robert Demmer says:

        M, If you have advocated IntelliJ IDEA then let’s not throw in the towel over change. Let’s get sales together and make sure everybody is on the same page: + – We appreciate your support and everything you have done to support our tools. We support you.

        • Terence Martin says:

          Incidentally, your apparent stance of “This new system is in the best interests of all of our customers, but if you have deep enough pockets we can totally make it even better for you” may, just possibly, not sit well with all of the schlubs that have the same problems but pockets that are not as deep.

  57. Graham says:

    Where I work (large corporation) they don’t like subscriptions. I have to create a compelling business case based on need (initial versions or upgrades) to buy things like IDEA. Our projects go in cycles, sometimes with long breaks in between. It will be impossible to convince them to keep paying for something unless it is being used regularly. We cannot have it stop working because we do support in between projects too. The administration I have to go through to buy things makes subscriptions painful or impossible. We definitely need perpetual license options. I had already started working on a business case to buy IDEA but now I’m sure they won’t accept it. I really like IDEA and have been advocating it but will be a much harder sell with subscriptions. Plus Community Edition isn’t an option — we need the full feature set.

  58. Tomasz says:

    So… subscriptions model, great! It’s easier, cheaper and stuff!

    For individual developer, who updates PHPStorm every year: 49Euro/year. In the new subscription model new client will pay you 79 Euro/year.
    It is 30 Euro more than now. Well played Jetbrains, well played.

    • Hadi Hariri says:


      A new customer does not pay the initial cost that existing customers have paid.

      • Oletros says:

        “A new customer does not pay the initial cost that existing customers have paid.”

        It is the first year free? If not, until now a new customers pays 99€ for a perpetual license. With the new model, he pays 99€/year.

        There is something that I don’t get about “initial costs”?

      • Tomasz says:

        Or… If i will not pay for one month, because my budget was too low…

    • Oletros says:

      New client buying a license past 1/1/2016 will pay 99€/year, 50€ more than now

  59. Very disappointing. I understand that investors and the business people have a strong hunger for the SaaS model, but the overwhelming majority of customers clearly do not want this.

    The only people offering any sort of positive feedback seem to be people who currently work with three or four programming languages… and who would save money compared to purchasing three or four separate IDE’s. However, as a Java-only user of your flagship IntelliJ product… all I see is that my costs will go up from $100/yr to $150/yr, **without** the option to skip an upgrade cycle if I don’t find it compelling.

    No thanks. I’ll just continue to use my current Ultimate Edition license until it falls too far out of date, and then revert back to Community Edition. Or who knows, perhaps Eclipse or Netbeans can regain some momentum? They’ve gone stagnant over the past few years as IntelliJ sucked all the oxygen out of the room, but if developers balk on the new rental model then perhaps they can recapture some mindshare and resources.

    • Steve, I agree, I get the move to subscription. I can deal with that. What I don’t understand is the 50% (personal) to 67% (commerical) price increase per year for IDEA Ultimate even for those already renewing every year (even more increase for those that might have skipped a version). I’ve been using IDEA since 2001 when it was known for its refactoring support and I’ve never seen a price jump like this.

    • Robert Demmer says:

      Steve, your voice has been heard.

  60. Gunter Grodotzki says:

    Why would I rent software? The new license model only makes sense for corporates that pay for their employees software licenses.

    As an individual/freelancer this makes zero sense.

    • Robert Demmer says:

      Gunter, If you are not working on something regularly or in different languages/tools wouldn’t this model help you?

      • MuppetGate says:

        Yes, it would, but Jetbrains – and me – have made a serious error in working out the number of polyglot developers out there. I think what happened is that you received lots of emails from people who asked for a ‘bundle pack’: a cheaper way to buy multiple IDEs (I know that I certainly sent such a message), but it’s clear to me now that so-called polyglot developers are the minority, and this model clearly doesn’t work for anyone else.

        I guess the other problem is convincing people to upgrade year after year. As the products mature you are probably finding there is less new functionality you can build in that qualifies as a compelling upgrade. I think Adobe and Microsoft ran into the same problem. :-(

        Wish I had an answer.

        • Robert Fisher says:

          I am a polyglot, but perhaps with less “mainstream” languages. C++ is the only language I regularly use that JetBrains has a tool for. And while they do have multiple C++ tools, only CLion is useful for me.

  61. Mark says:

    I skip the occasional release if the new features don’t offer much benefit to my development flow. For example, I couldn’t justify the cost of upgrading to 14.1. Under the new scheme if I do that I can’t use the software I’ve already paid for? No. Not acceptable. On top of that, if I upgrade after 2nd November I lose my existing perpetual license?

    I’m not just disappointed: I’m thoroughly disgusted. If this is how you’re going to treat your exisitng customers I’m checking out right now. I will not be purchasing any future upgrades. I hope your management team are keeping count.

    • M says:

      Couldn’t agree more. As a growing company they’ve enjoyed our support an evangelism and now they’ve opted to rewrite the rules.

      I’m stepping out

      • Robert Demmer says:

        M, Don’t believe for a minute that we haven’t noticed, appreciated and strived to deliver products that would delight you over the last decade+. This hasn’t changed nor has our focus on delivering the best developer tools. The licensing has changed but not the company nor our dedication to you.

    • Robert Demmer says:

      Mark, I wish this announcement wasn’t a disappointment. You can contact about upgrading early. Over a 1 year period a dot release may not be a game changer but a major release is likely to deliver wanted/needed features & functionality. Our release cycle won’t stop and we will continue to deliver the high quality releases you have come to expect from JetBrains.

    • Eugene Toporov says:

      Mark, no, you do not lose your existing license. You can use it for as long as you wish with the appropriate version of the software.

  62. Tyler says:

    This is extremely disappointing news. I have been a loyal customer for years, and have recommended JetBrains products to many friends and coworkers. Forcing users into a perpetual license for a product that has no hosted features is ridiculous. It’s just another way for a company to update their product less but still maintain constant income. If there is not a purchase option with the original license model, I will no longer be using your products.

    • Robert Demmer says:

      Tyler, It is the opposite. It doesn’t mean less innovation or less updates, it means a deeper focus on quality and delivery of the software. Not that it wasn’t there before but there aren’t necessarily the marketing drivers.

      • Gudjon says:

        Robert, I’m not sure I understand how this means a deeper focus on quality and delivery of the software? With the old model the customer could update each time there was an available update. How does the new subscription model enhance this? Updates won’t become more rapid or frequent.

  63. Richard says:

    Well JetBrians, it’s been a good run and I have genuinely enjoyed using your products. But this is not a change I can, or even want to work with. What a disappointing announcement.

    • Robert Demmer says:

      Richard, Sorry to hear that. Anything you care to elaborate on?

      • Richard says:

        As it stands, your subscription charges don’t cost me any more than I’m currently paying, which is great. However I don’t like the risk associated with subscription to software that is integral to my development process. Ultimately, your products are tools, excellent tools, which I have come to depend on. I “invest” in these tools by paying for them, but if your prices go too high, or your updates cease to be value for money, I have to keep paying anyway, or lose my tools; and I don’t like that arrangement.

        I would have preferred:

        – The option to be able to continue to use the version that I’m on at the point I cancel a subscription. A “minimum subscription length”, to protect against abuse of this would be fine by me.

        – If I cancel a subscription for the toolbox (say I don’t use them for a year) I lose the “existing customer” privilege and get a 62% price hike, and that’s not a nice position to be in. Your subscription price is affordable to me because of the discount, but I can’t justify the subscription price without the discount because I have to keep upgrading.

        • max hodges says:

          what a bizarre argument. It’s really just about cost of ownership right? $29 is just $2.42 per month. If the tool isn’t worth that much to you–sayonara.

          Think about it this way: would you rather pay $499 to “own” a copy (no upgrades) or $29 per year (upgrades included)? Which is more risky?

          • Richard says:

            Actually I think the argument is reasonable and echoed through the sentiments of other people who have raised concerns about the new pricing model, and who for an array of valid reasons, do not wish to pay a subscription to use software.

            To answer your question; your price comparison is moot as it isn’t a true reflection of the prices they are advertising, neither is it a reflection of the prices I am paying. That said however, yes I would rather have the higher price tag if that meant the software would not cease to function should a subscription be cancelled.

            If that’s not an option, then, as you scornfully put it–sayonara.

        • JTW says:

          even worse, there’s nothing preventing Jetbrains from deciding that that discount for existing customers is a one time discount, that next year everyone will pay the full price…
          In fact that’s exactly how I interpret the announcement.

  64. Mechanical Man says:

    JetBrains has many great products. Under this new subscription model, I’ll just pirate it so I don’t have to worry every x-month about payments. This is a horrendous idea. The least you could do is keep both models, and have best of both. Pay for updates, and also subscription based.

    • Robert Demmer says:

      Really piracy? You say that JetBrains has many great products and then threaten to steal the software. Seems counterintuitive and counterproductive, no?

      • Michael Yoo says:

        No, honestly, I don’t think it is.

        You don’t seem to understand that we are all willing to pay a bit more, if that means keeping JetBrains as an IDE without subscriptions.

        What we are not satisfied with is the subscription model. Bumb the license prices if you’d like, introduce a new “package” offer.

        Keep it off subscription. That’s all we’re asking.

        Simple, isn’t it?

        We just don’t want to be bothered by forced payments.

        • max hodges says:

          How is it “forced”? You pay to use it; or you don’t. Let’s be honest. You have a choice. No one is being coerced here.

      • JTW says:

        hack the version you got under the “subscription” so it doesn’t call home and disable itself once you’re no longer paying ransom?
        Sounds feasible to me.

        Can’t be bothered myself, I’m switching to another product, but it’s certainly an option.

  65. I want to ask about IntelliJ IDEA Ultimate specifically that I don’t get why no one has mentioned. Let’s say we already are buying upgrade subscriptions now, it’s $239 a year, and if we stopped, we can still use IDEA. Now with the new model we all qualify for $199 for the first year, losing perpetual use. OK, that’s not a bad deal. But then after the first year the price doubles to $399 a year? I really hope I’m missing something because it seems like you are increasing price by 67% versus the original $239/year AND losing the ability to use the software if you decide to cancel. I’m honestly afraid my company won’t accept that.

    I was recently able to convince our group of 12 to switch from Eclipse to IDEA and saving money on dropping JRebel at the same time (because they felt burned by its subscription model). I think we could get past the subscription part as we planned on doing yearly upgrades anyway, but the price bump to $399 a year AND losing features I honestly don’t understand. We have less rights under the new license so I’d expect price to either drop or stay the same! Even under the original model, going from $239 to $399 seems completely insane to me.

    • Chris Emerson says:

      If you stay subscribed, the existing customer discount applies indefinitely according to their FAQ

      • v. says:

        no. it applies as long as you keep paying. you stop for a month – goodbye to discount. it’s still unclear if you lose perpetual license when you start toolbox subscription…

        • Eugene Toporov says:

          V, you never lose the perpetual license. It will work with the appropriate version of the software as long as you can run it.

      • JTW says:

        right… And that’s set in stone just like the existing license model was set in stone.
        I don’t believe for a moment they’re not going to push people into the higher bracket after a year, after they’re locked into the payment model and can’t get out again without significant investment in reverting projects and other generated code to a state that will work with an old (or entirely different) product that doesn’t carry the pricetag.

    • Robert Demmer says:

      There’s a discount for existing customers. Why do you feel that you would be losing features?

      • OK, this is very unclear to me, I know that the blog says “it’s clear now” — If our company switches next year when our current sub runs out, we get the $199/year. Does that continue to apply as long as we are upgrading? What if we add more team members and licenses, would they be $199/year after their first year? This is confusing is it $399/year first year then $199/year after that? If that is really what you are telling us then I have no complaints at all about the new plans. If you are telling us that the new price for us who’ve been buying every year all along will go up from $239/year to $399/year, that’s a big difference to jump that high AND lose ability to keep running if you have to cancel.

        Robert, by losing features what I mean is everyone is asked to pay more (50-67% more) for renting software rather than perpetual license. Again, if you’re saying the upgrades are $199/year every year from here on out, that’s not a bad deal, but $399 is a big jump. This is the part that is not clear to me.

      • Zmicier Zaleznicenka says:

        Who qualifies for an existing customer exactly? If I own IDEA and CLion and would like to subscribe for AppCode, what price will I have to pay?

  66. Mister2 says:

    At least by glancing at the pricing it seems to be reasonable and maybe even a bit cheaper for Intellij at least.

    What is negative, I feel, is strictly psychological effects – first thought might be “now I don’t own”, which if you pay yearly renewal is only feeling of freedom – “I will buy new one, but I have option not to”.
    The second issue I feel somewhat negatively about is feeling that now I am somewhat more trapped if prices suddenly go up – basically feeling of being locked in.

    • Robert Demmer says:

      Mister2, There may be a battle of the mind but I wouldn’t stress about the prices. There is no money grab in play.

      • Oletros says:

        Yeah, sure, the fact that the subscription prices are higher than the current prices it is not a money grab

  67. maddoer says:

    It really feels like you haven’t taken corporate realities into account; a subscription model simply isn’t possible in some places. This effectively locks us out of your products.

    At the very least, a perpetual model on a few select products would have been helpful to us.

    • Robert Demmer says:

      Maddoer, The team does take into account, as much as possible, the corporate realities today, in the past, and into the future. It would be helpful to understand why JetBrains Toolbox could face obstacles in your workplace.

      • Tobi says:

        Maybe it would have been a good idea to learn about those corporate realities before you make such decisions.

    • max hodges says:

      If your company can pay once a year to maintain the license, they can pay once a year to maintain the subscription. Are you assuming annual payment is not available?

  68. Dima says:

    This is being done out of pure greed.

    I was a loyal fan for years, but now I’m switching to anything else. Thanks for the important lesson for all of us – your tools that you come to depend on have to be free and open, otherwise they can be easily taken from you and impede your productivity and skill.

    • Robert Demmer says:

      Dima, Thank you for being a loyal fan through the years. I can assure you as much as possible that this move is not being done out of greed. We take pride in the productivity we have helped developers achieve and plan to do only more great things in the future. JetBrains remains a great supporter of free (and open source) software that includes: IntelliJ IDEA Community Edition (Basis of Android Studio), Kotlin, MPS, PyCharm Educational Edition, etc.

  69. pipsqueaker says:

    If I choose to purchase a toolbox subscription to a product under the new plan, let’s say CLion, and then stop paying toolbox’s monthly fee, will I still be able to use the local copy of CLion on my machine?

  70. Dev says:

    Well, at least you don’t give us a choice.

    • Robert Demmer says:

      Dev, We are doing our best to be transparent about the upcoming changes and allowing time to make a decision that is right for you. It is possible to still purchase a perpetual license until November 2, 2015 or explore our JetBrians Toolbox offering. Depending on your work we continue to offer free versions of our products that include IntelliJ IDEA Community Edition, PyCharm Community Edition, and PyCharm Educational Edition, and more.

  71. Glenn De Backer says:

    So goodbye jetbrains, hello netbeans… ! What I dislike more then the renting scheme’s themself is the fact that they always seem to touted it as pro-consumer while those renting schemes only exist to give companies a steady stream of income and squeezing more money from the customers. Yes there is an edge case where renting is less expensive then buying perpetual licenses, but for a lot of people it will be more expensive in the long run. How many polyglots are really out there? Give me a break, it’s all about the money… .

  72. hepin says:

    If you really like the subscription model,then you need to it like this:
    1. be able to buy a based version
    2. be able to buy a selected feature
    3. be able to buy the upgrade for these
    4. do not charge for the bug fix,only new feature.

    I don’t think we should buy the whole,I am using only scala,and Play2,why should me buy the asp support?Why should I subscribe for the whole thing?

  73. Sergei Rodionov says:

    We own maybe 10 IDE licenses. They lost us as a customer. It doesn’t work for us financially and I’m not going to be coerced into the new scheme.

  74. hepin says:

    If you think you don’t know how to impress user to buy or upgrade,then you should make it a based version and enhanced feature.making it as the unity store.

  75. Tobi says:

    Greed eats brain.

  76. Odilon Alves says:

    Terrible announcement, JetBrains please listen to your customers feedback and add another option instead of subscriptions.

    Don’t look for the short term, look to retain or increase you customer base for years to come.

  77. Chris N says:

    What a condescending post that was. This will end up costing me more per year, and I don’t own it anymore, just rent it! What a good deal.

    So you got a few tweets from people who want a subscription… then offer a subscription option. Don’t force everyone onto it and say it’s really for our benefit. And if you think your products are worth more, then be honest about it and raise the rates.

    I don’t mind paying more, I mind the subscription model.

  78. Geo Mealer says:

    I’m not in the rock-throwing camp, but I’m also not super-jazzed by this. There are a few things I’m curious about.

    * This has already been mentioned, but what’s up with WebStorm being the same pricing as the other single-language IDEs?

    All the single-language IDEs are HTML/JS+another language, so doesn’t make sense to price the HTML/JS-only IDE equally. It’s even split out in the pricing info as if it’d be different…but set the same. What’s even weirder is that the -existing customer- prices are more sensible ($49/yr vs. $29/yr) but not the subscription prices.

    * Can I switch plans on a month over month basis as I do or don’t need other languages? How about if I subscribe for a year? Can I upgrade/downgrade during the year for a prorate?

    * Is the competitive-product discount still available on perpetual licenses bought between now and the November changeover?

    * If I’m an “existing customer” on, say, PyCharm, does that give me any existing customer discount for subscribing to IntelliJ IDEA Ultimate? Or just for the PyCharm sub? If the latter, what happens re: switching plans away from PyCharm then back?

    • Eugene Toporov says:

      Thanks for your questions Geo,

      I’ll try to answer some for the rest please write to our sales team at

      * While many features of WebStorm are available in other IDEs we think it is a solid product with a rich feature set for frontend, JS and Node developers. Its price was historically lower and we think it is reasonable to fix it now. We maintain the lower ‘existing customer’ price for WebStorm so the people who invested in the product already do not feel bad about the price increase.

      * competitive licenses are available, please contact our sales team

      * yes, it is possible to switch month to month

      I’m sure our sales team will clarify the rest of your questions.
      Thanks again for your feedback

      • Geo Mealer says:

        Thanks for the reply!

        The ability to switch month-to-month and having a viable route for “polyglot” other than the plugins are really the only value-adds here from my POV. But as I haven’t become a paying customer yet I expect that to be taken with a grain of salt.

        It has made a less-than-ideal impression on me that the year over year prices are generally higher than the previous upgrade path, particularly given the inability to keep the last version.

        If you are considering the “keep after 12/18/whatever most” option, that would be a major plus for me as a prospective paying customer.

        In an effort to make that even more realistic, I offer this:

        I would personally understand were that option not available on the Toolbox edition, where it makes less sense, and I would personally understand if that option applied only to the last version, and then only after the next version were out for some period of time.

        In other words, if you release IDEA 16, 17, and 18 on a yearly schedule and I quit before 18 is out for, say, a month, it’d seem reasonable to me to only grant a perpetual license to 16. If I quit after 18 were out a month, I’d get a license to 17.

        That would address the “got the new version, rush of cancellations” issue with the basic idea, while still giving a lot of incentive for people to continue a subscription. They will end up trying the next version because of the one month rule so they have a chance to get hooked on it. If they don’t continue after that, their tooling moves backwards..

        From my POV, the bonus here is that you would have considerably more incentive to make 18 good, otherwise I’d cancel and keep 17 once I tried 18 for a month.

        In essence this becomes a yearly upgrade model with monthly payments available and incentives set up for maximum retention while still preserving some level of permanent value and risk mitigation for the customer. You would have a more attractive and steady income to you with the monthly payments, as well as an excuse to ditch the “first year X, subsequent years X*.5” pricing model I suspect isn’t working for you.

        And I think the described model would lure quite a few people into staying subscribed year over year. Everyone would end up trying the newest version, and nobody wants to move backwards in their tooling so they’re likely to keep it.

        EAP does this already to an extent but this would catch more people. And it’s considerably less hostile than taking the tooling away entirely.

        I’ll contact Sales for the rest of my questions. Thanks again for the considered answer.

  79. Brad says:

    Just one more plug for this idea, in case my comment to Sven’s idea gets lost above; here it is:

    I would suggest a 3rd way.

    Subscription however if you have paid continuously on the single or indie models for a duration say of 12 or 18 months then you get a perpetual style use from that version should you cancel. No more updates till you pay again…then if you have a break like that then the clock starts again before you get the perpetual.

    That would appease most people I’m sure. If Adobe did that they would have my Lightroom money now


    Given the firestorm of complaints here, I think if you made this *one* modification, you would ease the criticisms substantially. After 12 mos, or an annual subscription, you can drop off, keep your current version indefinitely–then join again later to get updates.

    Those updates go away if you only stay for a month or 11 (meaning you revert back to the version you qualified for by staying subscribed for 12 mos or more), but after a year of re-subscribing, you get permanently bumped up and perpetual again as long as you stay current (or you stop at the version you last had 12 mos of subscription for).

    Best of old and new models. Lower income devs can adjust their budgets and most others pay subscription rates.

  80. rosdi says:

    I understand a company needs to be profitable otherwise it can’t exist. As a compromise, I suggest jetbrains allow us to continue using the product even after the subscription expires, but enforce a ‘re-subsribe’ fee if we let our subscription lapsed.

    That way, we have enough motivation not to let subscription expires, and we don’t feel like we are being held at gun point.

    This is the most gentleman way of doing this.

    What say you?

    • Brad says:

      I’m not in favor of this, mainly because it still feels a bit like extortion, because you’re always caught in the quandary of whether or not to keep subscribing. Although combined with Sven’s idea above, perhaps there could be a fee to get back to a perpetual license status–without having to wait 12 months–I guess that’s just the cost of the 12 month subscription.

      I’d prefer that I just lose my ‘updates’ that I get (within 30 days of not connecting in to Jetbrains servers), if I haven’t subscribed for at least at year. Once I’ve subscribed for a year–as described in my restatement of Sven’s idea directly above this post–then I get a perpetual license that is good until I stop subscribing.

      The only main loss (penalty if you were) in this idea, is that you’d lose updates/bug fixes back to the last time you were subscribed for 12 mos or more, so that’s a bit of a penalty, but not much and doesn’t feel so much like you’re a hostage of Jetbrains. Feels fair, to me at least.

      By way of a further example, say if I subscribe for 32 months, from versions 2.2.0 to 4.8.1, then let my subscription lapse in the 33rd month, when 4.8.1 was the latest, then I get to use 4.8.1 indefinitely, forever, but with no updates (other than perhaps security patches); no features, maybe 4.8.x bug fixes that are product destabilizing, but definitely no new features. If later I decide I want to subscribe again, at the 40th month perhaps, I get the newest 4.9.2 that’s out then, but if I lapse and don’t renew after the 43rd month, then I revert back to 4.8.1… if however I subscribe from the beginning of the 40th month through end of the 51st month (12 more months), then I get perpetual for the version 5.2.5 that’s was last released in the (maybe 49th) month. And so on…

  81. Marc says:

    I also don’t like this change. The blog article states “In effect, developers are no longer pigeonholed to a certain technology.” … sounds good, but this doesn’t make it true. I’m a Java desktop application developer and IDEA alone is sufficient for me since over 10 years and most likely will be for the next 10 years as well.

    JetBrains Toolbox may be a great thing for others, but please continue to provide perpetual licenses for guys like me (and the majority of the commenters before).

    • Eugene Toporov says:

      Thanks for adding your thoughts Marc. While we see a clear trend of multi-technology projects and development, we realize this is not 100% valid for everyone.

    • JTW says:

      In fact I see more and more that employers expect their employees to be experts in one particular language and not bother with others (at least at a professional level).
      So while for larger organisations it may be true that they use a variety of languages (but most of those will be legacy), for individuals (at the professional level) it isn’t true at all.
      When looking for a new job this year, having multiple languages listed on my CV seriously hurt me (and I got that stated by several recruiters and HR managers, as well as development leads in job interviews) as it “gives the appearance you’re not serious about Java”.

  82. Simon says:

    Please listen to your customers. I don’t like any subscription models, but I could live with a subscription model where you can still use the IDE if you paid for at least a year.

    Existing customers should also be able to use their IDE four a unlimited time if they update to the subscription model – otherwise I will stay on my current version until it’s so obsolete that I have to switch to eclipse or something like that.

  83. Kevin says:

    Hello code rush…meaning to give it try for a while now I guess now it the time

  84. Ian W says:

    I for one will not be renewing or staying a customer, i will also no longer recommend your product to friends, and will have my employer look into other solutions, as opposed to being held hostage.

    You seem to be pretty stuck on this decision, despite the massive outpouring of negative feelings on it… this makes it pretty clear to me that this is entirely profit driven, not customer happiness driven.

    I wonder what new IDE will fill the void. You are leaving your lunch out to be stolen, cant wait until someone does.

    • Andrey Cheptsov says:

      You should also understand that being profitable is important to be able to maintain a high standard of quality (which has been always our main focus), and make you happy.

      I honestly can assure you, it’s not about money. Believe me. For us this is just a more sustainable model that lets us stay on the market on continue deliver the products developers love.

      We DO understand the disadvantages of the new model (no need to hide that). Still I hope our loyal customers will understand why we do that, and will support us.

      • Fred Jones says:

        Loyalty is a two-way street. If you’re not loyal to your customers, why should we remain loyal to you?

        The double-speak is insulting: How is a “more sustainable model that lets us stay on the market” not about money?

        If renewals have been dropping off, you should look at whether you’ve spread your resources too thin and are delivering too little value with your upgrades.

        I can tell you right off that IDEA 13 -> 14 -> 15 has added nothing I needed, and has left unfixed a litany of bugs that affect my day-to-day work.

        Meanwhile, AppCode development has failed to fix critical bugs quickly, is not yet a replacement for Xcode, and does not appear to be rapidly heading towards being one. CLion (which probably should have been integrated into IDEA!) is unusable for me given the CMake requirement, lack of support for multiple toolchains, etc.

        The end result is that I haven’t purchased updated AppCode licenses, I haven’t bought CLion at all, and paid for the last two IDEA updates entirely out of a mixture of loyalty and habit.

        I also haven’t complained, because I liked JetBrains, I had the choice to upgrade or not, and in not doing so, I assumed that JetBrains would understand that the value equation just wasn’t there.

        Instead, you’re expecting users pay for value they aren’t receiving because your resources have been spread too thin, as if somehow accepting a bum deal out of “loyalty” was our responsibility.

        • Terence Martin says:

          My situation is the same as yours, sir. With the sole exception of the Darcula color scheme (whenever that came around), based on what I use IntelliJ for, absolutely 0 new features have been useful for me. In the meantime there are a myriad of bugs that, over time, make IntelliJ more and more of a pain; it grates to constantly be working around your tools.

          However, I did upgrade my AppCode license. I also bought CLion even though I knew ahead of time it would be useless to me for the same reasons that it’s useless to you; I figured I would support the company and hope that it would become a better product.

          Maybe it will or maybe it won’t (IIRC, consensus currently is that despite the outcry for different build systems, they want to focus on parsing C++ better instead) but the likelihood of that happening before the upgrade period on my current license expires seems pretty infinitesimal.

      • a former customer says:

        I honestly can assure you, it’s not about money. Believe me.

        Once the offer is used, the special price is available indefinitely until payments are canceled or paused.

        So the decision to discard the discount once the subscription is paused/cancelled is not about the money? Are you serious?

        You’re hurting your credibility when you’re asking us to believe obviously false statements.

  85. This is not a name says:

    I am not interested in renting software. Full stop.

    (Why? A couple reasons. First: I will not run software that requires a phone home. Partially because I am often without internet access, partially because of the privacy implications (or rather, lack thereof.), partially because of the security implications, partly because I have no desire to have features removely removed (like so many auto-“updating” software does). Second: having things that make money be taken from you if you don’t have the money creates an interestingly nasty catch-22. If I buy software and then later on an update is released and I am currently down on my luck, boo hoo. My software doesn’t suddenly stop working. But if I am renting it, that is not the case.)

    As such, I know what I am reccomending everyone to ditch now (or rather, either to ditch or to buy the last version before this ill-conceved licensing scheme comes into effect).

    Kindly reconsider this.

  86. Ben says:

    I’m in the same boat as most people in this thread, not happy about the move to a subscription; but I noticed that no one seems to have brought up the fact that they’re also hiding a 50% to 100% increase in the price of their product after the 31st of January.

    For example the current (and grandfather’ed) price of upgrading a PyCharm company license is $99, after the 31st of January this goes up to $149. If you take a look at IntelliJ IDEA Ultimate it goes from $199 to $399.

    Similar price increases exist for individuals as well. PyCharm individual is jumping from $49 to $99 and IntelliJ IDEA Ultimate is going from $89 to $149.

    Not to mention the price increase for WebStorm that has been discussed (this is actually a 200% increase)

    I’m not sure how you are hoping to get new customers after January 31st, where they are going to pay a measurable about more per year (assuming a continual renewal) and forgo the option to keep the software if they decide not to renew.

    • Ben, thanks for pointing this out. I tried to ask the same question earlier. I actually think the subscription concept is better and I like that you can buy for a few months to try something out, or contractors who are maybe on a Python project for only a few months. It’s great. But I’ve been trying to understand if the $199 IDEA Ultimate price is a one-time only thing or only a single year. If they are saying “renews” are $199 a year, then I think this is a good model, even if I understand some people’s qualms about renting/phone home. But my fear is they are trying to just increase the price for those who already are upgrading every year. I’ve used every version of IDEA since 3.x and the upgrade cost has never been anywhere near $400.

    • Ben says:

      To be clear I’m not against a slight increase in price (10% would be a more reasonable margin), it’s that we’re getting a very large increase in price and moving to a subscription (AKA rental) model with no tangible benefit for the customer.

  87. Alex says:

    I’ve been IntelliJ Ultimate user for years, and I love this change. License price is NOTHING compared to Microsoft pricing for MSDN (though MSDN has other benefits, but…). Played a bit with trials of other products (AppCode, PyCharm, etc) – now, I’m getting all that for price which is even lower I paid before just for single product.
    @To all who’re unhappy now: first of all Community edition is still there. Absolutely free of charge.
    If you want good software, you have to pay for it – there’s no such thing as a free lunch: code has to be written, years of R&D has to be funded, premium plugin developers should get their awards (like Clojure stuff ;-), etc. If that’s not done, then you’ll see what’s happening with Eclipse – at some point they had no money to run even continuous integration so Google stepped in and donated some money to keep project alive.

    Looking forward for upgrade.

    • Alex says:

      Just a small question: is EAP still going to be available? I really enjoying get stuff hot – just from the oven.

    • Sean Heaton says:

      Respectfully, Alex, I don’t mind paying for Ultimate at all–I have been doing that for a few of years now and I’m not looking for a free lunch.

      I just don’t like the idea of having to keep paying to keep using something that I have traditionally been able to pay once for. I am perfectly happy to keep paying for each version as it comes out–but I only want to pay once and only if it is worth it. Now if I stop paying, I can’t use anything.


    • Tobi says:

      “If you want good software, you have to pay for it ”
      Come on, that is such a cheap argument.
      Did anybody complain, that he doesn’t want to pay anything?
      But yeaah, as a MS developer you might be used to ransom.

    • Leonardo says:

      “If you want good software, you have to pay for it ”
      Yes, but only once.

  88. Fii says:

    Wow.. That is just not a good idea guys.. I hope you hear your customers and change your mind.. No subscription wanted!!

  89. Steve says:

    I certainly hope Jetbrains listens to developers. They’ve been building industry leading products, but it seems like the marketers are running the show. Remember Steve’s warning about letting the marketers run things. It’s down hill. On the positive side if these types of decisions are allowed to stick it opens opportunities for companies to come along with less draconian pricing models to grab some business. Just look at what’s happened to Microsoft.

  90. Kevin says:

    Right now, I pay for the upgrade every year. I’m one of the guys that likes the upgrades you guys provide. I even sold my team on switching off of Eclipse to PHPStorm. However, I am adamantly against subscription models. I don’t care if it only costs me $30/year instead of $49…lost me. I have the last non-subscription versions of Adobe Production Premium, and I have the last non-subscription versions of MS Office. Now, it looks like I’ll have PHPStorm 9 for a long, long time…I would assume until intellisense doesn’t work on the version of PHP I’m using…so PHP 8? Since most companies I’ve worked for are still stuck on PHP 5.4…might be a decade. PHPStorm 9 is a great product and does everything I need, so looks like I’ll stop here.

    Anyway, I don’t begrudge you for it…do what you think is best for your company…but you will definitely lose some like me for as long as we can hold out.

  91. Karol says:

    My license expires in January. Can I extend it by another year if I buy it now again before the new licensing model starts in November?

    Am I correct to assume that once my license expires and I don’t switch to subscription model I can continue to use my current version of IntelliJ?

    Shame you are implementing such a horrible licensing model :(

  92. v. says:

    It was a no-brainer decision to start using jetbrains tools (free-trial was still cheaper ‘to get started’ and more than enough to convince someone to buy). Now we have to think if it’s fair enough to continue.
    Obviously, we who bought perpetual licenses (got IDEA 12 and PHPStorm 9) and were not convinced to renew – are kindly asked to let the time heal our broken hearts, while people who claim to have corporate obstacles are offered help from JB sales.
    In the meanwhile – let’s learn all languages and buy full-stacked toolbox that will allow us to make a yearly subscription in matter of minutes.

  93. Enrique says:

    Very bad news.

    So a new user to PHPStorm today:

    – 99€ year 1, 49€ year 2, 49€ year 3, …

    With subscription:

    – 99€ year 1, 99€ year 2, 99€ year 3, …

    ¡ Great, I love it ! “ironic off”

    My company (+40 licenses) have differents versions of PhpStorm: not all teams needs last version. With subscription, bye bye. Or all computers updates, or we change IDE.

    Sad day :(

  94. Jimmy Smutek says:

    There’s not much to say that hasn’t already been said, so I’m just dropping a comment to say I’m not happy either. This is my first year as a PHP Storm user, but I most definitely will not be moving to the subscription model.

    I cannot stand the feeling that someone always has their hand in my pockets, and that’s exactly how Sass feels to me. There’s only so much money to go around and a subscription here and a subscription there quickly adds up. how many monthly subscriptions am I supposed to maintain?

    For services where I am actively using their resources, like Harvest or Dploy for example, I understand it. For desktop software, like my IDE, or Adobe, it just feels insulting.

    I think the market as a whole is fairly sick of SaaS, but I know that won’t stop you.

  95. MuppetGate says:

    Okay then. I’m okay with it, but clearly everyone else isn’t.

    I think Jetbrains – like myself – has miscalculated the number of polyglot developers out there. Just because we make a big noise on the internet, doesn’t mean we’re the majority.

    Most Java developers aren’t working on sexy open source projects in exciting start-ups.

    The subscription model works for me, but perhaps stopping the perpetual licence is a mistake. It would be a shame for Eclipse to get a toe-hold, especially as I’m working so hard to break its hold at the office. Government projects don’t like these kind of licences.

    • MuppetGate says:

      Even Microsoft offers both subscription and pay-once models for Office 2016 (might be Mac only). I’m pretty sure Jetbrains can come up with something that will suit everybody … well, not absolutely everybody.

    • matt says:

      I’m not sure I understand this comment, or any of the comments about how this might benefit “polyglot developers” to begin with. IDEA Ultimate already supports Ruby, Python, PHP, Javascript, HTML/CSS/etc, and everything that runs on the JVM. There’s already no reason at all to buy PHPStorm, Webstorm, Pycharm or Rubymine if you have an IDEA Ultimate license; the same functionality is included in IDEA.

      So the only polyglot developers that might possibly benefit from this new “All Products” option are those who work in something covered by IDEA and also C#, C or Swift. Yes, I can believe that that particular niche of polyglot programmers is not huge. And to be clear, we’re not talking about all of those developers who work in another language during the day but, say, dabble in iOS development from time to time — even they wouldn’t benefit here. You’d need to do enough with multiple different platforms to make it worth the $100 upcharge to buy the kitchen sink. Otherwise, XCode or whatever will do just fine for your weekend projects.

      • MuppetGate says:

        Polyglot developers prefer separate IDEs if they code they are working on is in a separate project. You can use IDEA for other languages, but it is geared towards Java and the plugins can’t get you away from that.

        Speaking as a polyglot developer.

        • matt says:

          “Polyglot programmers prefer”… That’s a curiously strong statement. I — and every other polyglot developer I know — would always prefer to have 1 editor to 2, given equal capabilities. One set of preferences to update, one program to update, one less thing to mess with. And I — like many polyglot programmers — often use multiple languages within the same project, depending on purpose. Multiple editors would be a nightmare.
          And I don’t understand how IntelliJ is “java focused” when using it for Python. Everything I see in my editor view is quite Python-focused.

          Speaking as a polyglot developer.

  96. Seoyeon says:

    – Currently IntelliJ upgrade plan : $99/year
    – Switching new subscription model : $89/year (But, just first year only)
    – After years can I pay $149/year?

    I don’t understand what is benefit for me?
    I think that is increase $50(33.5%) per year for me.

  97. j says:

    Well, I have been a paying customer for a while now. And the only bug I ever wanted fixed: is blatantly obvious, yet it has been open and ignored for almost 6 years (happy birthday mr bug!). It affects more than webstorm, also PyCharm and IDEA.

    If this was an open source tool, I’m sure this would be a <24h fix. Or even, please give me the source code to pycharm and I'll fix it myself, and then license the code back to you for free!

    This definitely does not make me want to give you any more money.

    • Terence Martin says:

      I know what you mean sir. There are several bugs that I run into when using JetBrains tools all the time (like, every one; they are apparently in the core engine) that severely slow down my work flow. They’ve been there from the very beginning and I highly doubt that they will ever get fixed; so much so that I don’t even bother reporting bugs any more, because what’s the point?

      JetBrains seems more inclined to come out with new products and new features without bothering to fix the usability problems in the existing features. Is this new model supposed to fix that? Because I don’t think it’s going to fix that.

      • Josh Kelley says:

        Eugene Toporov addressed this above:

        We think we’ll be able to concentrate on quality more than trying to impress users with new features so they buy upgrades. Our products are more than feature-full and we believe the quality is something that can always be improved.

        • j says:

          I take the point, but I have been paying them this much for years already, and it still hasn’t changed anything…

        • Terence Martin says:

          Yeah, well, I’m going to call that a case of “too little, too late”.

          “I know you’ve been waiting for these bugs to be fixed for 5 years, and you’ve been paying a premium price every year to upgrade in hopes that it would happen, but let us assure you that now that we’re taking LESS of your money, we’re TOTALLY going to fix all of those things that bug you.”

          Basically, I’m not seeing anything that gives me any assurance that this would actually be the case. The current system of bugs only being fixed if large numbers of people also happen to experience it, find the bug report, and add their support, is broken.

          Put it this way: Is there actually value in reporting a bug (outside of an EAP)? I say, “No, there is not.” If it’s in a production version and it’s not already reported, not enough people are experiencing it, so even if you do report it, nobody will ever get around to fixing it anyway.

          • j says:

            I wish that was true, but this particular bug has >250 votes and >250 comments.

            • dave says:

              All I can do is vote with my money. I don’t plan on re-upping once my current year is done.

              Best of luck with fewer customers going forward.

  98. Alex B. says:

    So i currently have a perpetual license for IDEA, with the standard 1 year of upgrades. Per the details of this post and already answered questions, i cam continue using IDEA forever with no sub so long as i can live with the last updated version under my year of upgrades. This is cool and changes little for me right now.

    But when/if i ever decided, after my year, that to get updates again i will then have to move to the sub model. My question is: is that considered a new license or does it somehow replace my current, perpetual one?

    That is, if i have a perpetual license and then jump on the sub model later…if i stop doing the sub model after 6 months will i still be able to use my perpetual licensed version of IDEA, just using the old updates?

    • JTW says:

      if it works like skipping upgrade cycles does now, after 2 terms you’re no longer considered an existing customer…

      Which right now is roughly 2 years, under the subscription model is likely to be 2 months.

  99. Jason Holland says:

    I personally bought WebStorm and was considering ReSharper. With this new subscription model I’ll skip ReSharper unless my company will pay for it. I’ll longer consider any of your products for personal/freelance work.

  100. Matthew O'Connell says:

    Very disappointed to hear you’re moving to a subscription model. We use jet brains products through work but sometimes funding for development tools come sporadically. We may go a few years without additional funding to upgrade. Under this new plan we’d just be SOL and would be forced to use a different tool in the meantime. Going to make it a pretty hard sell to management.

  101. Jacob W says:

    I am a polygot so this benefits me financially, but I will NOT be signing into this.

    You guys have always done a great job at your IDEs, and I really love your product. I am sure having a constant stream of income will help you guys focus on improving the product as a whole, instead of needing big features to woo people into buying an upgrade.

    What I have problems with is that you lose the perpetual use after you cancel your subscription. You promise to be awesome and I’m sure you guys mean it 100%, but what about 5 years down the road? We have all seen how companies can change in an instant. If 2 years down the line for some reason JetBrains decided to NOT DEVELOP ANYTHING ANYMORE, what recourse do we have other than to switch?

    I think Sven’s suggestion is the best. After being on subscription for a certain amount of time, you earn perpetual use of that version even if you cancel the subscription. This is the best of both worlds and it will make everyone happy.

    With Sven’s model:

    – You get immediate upgrades -> This satisfies the “I upgrade every year anyway” crowd
    – Same low barrier of entry -> This helps getting new customers.
    – You get to keep using an old version after being subscribed to it for 12+ months -> This satisfies the “I want perpetual use of my product” crowd

    For companies who doesn’t like subscription model, offer one time purchase like the old times.

    You can tweak the numbers to make it work for you guys. The productivity gain through using your product can easily justify w/e you come up with. We are standing up for what we believe is fair, not for the supposedly increase in price.

  102. Julio says:

    I’ll give you a solution…. If a customer pays a subscription license for more than a year then he gets to keep that version, until he starts paying again (he will keep the new acquired license after year). The sense of ownership is not a good feeling to Devs that love their IDEs.

  103. roger aqhue says:

    I gave up JetBrains bloatware IDEs last mainly due to:

    1. Font rendering in Linux is just trash, as it uses JDK renderer.
    2. Memory insatiability, aka memory leaks everywhere.
    3. Confuse syntax highlighting configuration. Too many options.
    4. Stupid code formatting bugs that were solved a long time a go in Eclipse and NetBeans.
    5. Heavy I/O that was eating my SSD life.

    Now, this new subscription scheme proved I was right in leaving Jetbrains.

  104. Dan Brown says:

    Looks like I dodged the bullet here. I was about to pay for PHPStorm and CLion after being impressed by the trials. But this payment model I wouldn’t touch with a bargepole. I’ll stick to Eclipse PDT/CDT instead.

    I have no objection to the subscription itself. If a yearly cost is similar to the one-off current cost then it helps me as a hobbyist to spread the cost which is a strong plus point and in all likelihood I would continue it indefinitely. The full toolbox does look like a very nice price point in fact. But not having access to any version at all (even an older one from the start of the subscription/cycle) if I take a break in the subscription as my interests and financial position change outweighs that entirely.

    In my view, the price of software is a investment and maintenance in a tool, not a running cost.

    Somebody else here has already suggested that after 12 months you ‘unlock’ a perpetual no-upgrades license for the version from from the start of that cycle. That sounds like a possible tradeoff. Still not great but much more palatable than the current offering.

  105. Andy D says:

    Horrible news guys… Nobody likes software that expires. Nobody likes software that phones home.

    If you must do this then please offer a perpetual license version alongside this new subscription model.

  106. pt says:

    Why don’t you fix the font rendering on Linux, it’s worse than Eclipse and other editors like Sublime.

  107. A Previously Loyal Customer says:

    This is very sad to hear. My current license runs out in October, so I will upgrade to the new version then and then you will have no more of my money. I will continue on the perpetual license with whatever the latest version I get is. Once that becomes too outdated, if you haven’t abandoned this stupidity, I will move to whichever competitor fills the void you have left.

    I sincerely hope that after reading the comments from your many unhappy customers, you will realise this is a mistake and change your minds.

    • v. says:

      I believe this really is about making us who are happy with an oldish version (i.e. don’t want to renew), renew ‘for one last time’ and wait what happens next. It’s totally JB’s fault that most of us complaining here will be hoping that competition will get it right, so we don’t ever have to switch to subscription.

  108. Yoann says:

    I have currently no money because I’m buying a flat. This is why I postponed the renew of my webstorm licence, so yeah, I’m using webstorm 9 without any updates even thought the 10th version came out a few months ago… but at least I can still USE the software I paid for… and this the most important thing for me.

    So I think I’ll renew my licence on november 1st to get a perpetual one with the updates for the longest time possible with the possibility to still use the software after november 1st 2016, and consider toolbox or something else in about a year and a half… but to be honest, I wouldn’t be surprised to see a lot of people doing exactly what I’ll do, and I also wouldn’t be surprised to see perpetual licences back in a few times along side with the toolbox plan, due to the amount of negative feedbacks you have in here :/

    Still a great fan of all of your products, I think you are smart people producing smart softwares, but as many other people, I’m really not convinced with this new plan thing…
    As for me, I prefer paying a bit more and not worry about not being able to use my software anymore someday.

    Last but not least : I’m wondering if this is this is really in the best interest of your customers, especially the ones that are only using one or two of your products… yes, having a lot of tools is temping… but for me who uses only webstorm, I was tempted to buy a new version because of the new interesting features… now people will have to renew whatever they are interested in the new features or not. They will simply have no choice. So you could just not provide any new (interesting) things, people will be forced to pay anyway (not saying that this is what you will do). With the old perpetual licences, the power was in my hands to renew or not, to give you money for new features or not if I’m interested enough in these new features or not. In other words, you had to provide better versions every time to convince me. With the new plan, you are simply taking back that power to your consumers : they have to pay, wathever they like the new version, or not… In other words, you simply have to be better than freewares, which is not that difficult for you do to your current level of expertise… So this new plan is not challenging you to provide innovations, only your burning desire to be innovative does. Will it be enough ?

  109. Aon says:

    If I decide to first switch to the “IntelliJ IDEA Ultimate” offer which is “$ 89 /year for existing users”, then maybe in the future I want to switch to the “All Products” offer because I need to use ReSharper. In this case, will I have to pay “$ 199 /year” or “$ 149 /year for existing users”.

  110. Harvey Falcic says:

    With this, you have lost me, and the company I am affiliated with, as customers for life.

    As someone else said, I am *not* interested in renting software. This is despicable and I am very disappointed. I am sorry to see that the reasons why I always recommended JetBrains’ products to everyone no longer apply.

  111. Anne says:

    I love IDEA. It saves us so much time and effort, you could have almost doubled your current price and our company would still have happily paid it every year. I am very sad I will have to give it up. But we can’t afford to base our business on a toolset that we can’t depend on being able to use. We are a small company. It is possible we won’t be able to pay a large software renewal bill on a due date, especially with the direction current exchange rates are going. At the moment, that is fine. We pay a few weeks late, and no harm done.

    But with this new subscription model, we have no tools during those few weeks, and hence can’t do the work to earn the money.

    The need to access the Internet also bothers me. We have used several tools in the past with this requirement. We only continue to use one of these (a server-based one) because of the problems we experienced. Even the server-based one is a nuisance, because it doesn’t handle IPv6 properly.

    Goodbye IntelliJ IDEA. I will miss you.

  112. Alex says:

    Bad idea.

    You need to offer perpetual either as a standalone option or consecutive subscription of X months.

    Otherwise “how the mighty have fallen” will probably be used to describe JetBrains later next year.

    I love your IDEs and try to convince ithets to convert from Eclipse. Do us a favor and don’t commit corporate suicide here.

  113. Josh Kelley says:

    I haven’t been using JetBrains products long, but I’m hugely impressed with what I’ve seen. And as someone who dabbles in multiple languages, I’m very happy to see an economical Toolbox option.

    However, to me, there’s a huge difference in mindset under the new model.

    Under the current model, I feel like I’m buying a great product for a good price, and I’m a fan. Because of this, I’m happy to upgrade every year.

    Under the new model, even if I’m paying the same annual amount, the terms of the relationship have changed. There’s an unavoidable risk or threat in the purchase. I upgrade, not because I want to, but because I have no choice. It’s hard to feel like a fan in those circumstances. I’m less likely to categorically recommend JetBrains to others; I’m less likely to stick with them if other tools come along.

    A carrot feels a lot different than a stick, even if you end up in the same place.

  114. Pingback: 【悲報】JetBrains、サブスクリプション製の「JetBrains Toolbox」の導入を発表し、コメント欄が大荒れに

  115. Ryan says:

    I’m deeply disappointed by this move. We’re all developers here. We can agree good work deserves remuneration. But that shouldn’t come from the threat of taking away a user’s desktop software.

    As a JetBrains customer I have no plans to transition to a non-perpetual license. I can also no longer recommend your software to friends and colleagues in good faith, something I’ve done many times in the past. That’s truly unfortunate.

    I know you’re working hard to make this look desired by and beneficial to your customer base. I just hope you can step back for a moment and listen to the majority who are saying this takes away a significant portion of your products’ value.

  116. Josh says:

    I can’t imagine myself going to this model. This is obtrusive to the customer and really only benefits those that use many JetBrains products (I only use PhpStorm). Right now, I can choose not to renew for a year and then buy new the following and just deal with a year old version of PhpStorm for a year. This model eradicates that. Now, if I don’t want to continue paying, I lose the software completely. If I lose my job and have to cut down on things until I find a new one, I cannot do work using my freelance license. In that instance, JetBrains is being very harmful to their customer and could actively harm the chances of a developer getting a new job.

    This is outrageous and if this is a sign of things to come from JetBrains (subscription software models usually come before software stagnation which is what I worryis coming), then I’m done with this company and its software. It is the best IDE at the moment, but not enough so to have to deal with this disaster of a plan.

    I’m already looking at returning to Eclipse PDT or possibly going to JetBrains to replace PhpStorm (or sticking with PhpStorm 9 for as long as possible). I’ll lose some features, features I am most willing to pay for, but won’t be screwed in the future. My team of 15 will also have to look at this because we will not be able to sell a subscription model to our owner, meaning upgrades are out of the question once our current license support ends.

    • Josh says:

      On another thought, what if I go to a restrictive country such as China for a month or two and they have your servers blocked? Half-way through my trip, I am completely dead in the water because my IDE has completely stopped working because it’s been 30 days since I was able to phone-home and I either have to break that country’s laws and get around their block or use another IDE in order to continue doing my job.

      There are a few other scenarios in my head where I simply cannot do my job despite having paid JetBrains hundreds of dollars for software that is nothing more than a digital paper-weight on my hard drive. All I can think is that I am going to pay JetBrains $8 every month with the inevitability that they will cost me thousands in lost man-hours later on.

      This move is not for the consumer, not in the slightest. This is purely a business decision to try to take more money from customers.

      • Terence Martin says:

        What if you’re not in China at all, but right at the time of the month when the thing needs to phone home, there is some server/internet outage problem on their end?

        Now it doesn’t matter what your situation is; hope you have some other way to get vital work done.

        Are chances of it happening slim? Probaby. Is slim% and 0% the same thing? Absolutely not.

    • Josh says:

      Just noticed a typo. Going to NetBeans, not JetBrains (which obviously makes no sense)

  117. None of your business says:

    Never in a million years will you get me to pay for a new subscription. This is dumb. But you are going to go thru with it anyways because some dumb pointy haired boas over there is trying to make a name for himself.

    I hope this goes side ways and you learn the lesson.

  118. eli says:

    Ridiculous. A crucial piece like an IDE will just stop working?

    Time to stop recommending jetbrains products. I may renew because I really like webstorm, but I won’t be able to recommend a ransomware to future colleagues.

    Silly move.

  119. Eric K says:

    This is terrible… :(

  120. Mike Jacobs says:

    First, can you give a straight answer to this question, because I’ve seen conflicting answers between these comments and the comments from your employee on reddit:

    If we take the existing customer discount and move to the subscription model, are we forfeiting our existing perpetual license? Your FAQ states “The offer is available to customers with or without upgrade subscriptions regardless of the subscription status, provided a customer switches their existing licenses to the new model before January 1, 2017”. When you say “switches their existing license”, it implies that after we switch, we now have a subscription license and our perpetual license is gone, and that’s completely unacceptable.

    Secondly, this new PHPStorm pricing scheme is an outright insult. If I ever let my subscription lapse, my price gets jacked up to $99/yr for a piece of software I don’t even get to keep? Right now I’m paying $49/yr and I keep the last version of the software I paid for. Why would I rent something for $99/yr that I was previously owning for $49/yr?

    Every other company I can think of that has moved to a subscription model has done so with a decrease in price because there’s an inherent decrease in value associated with not getting to keep the software when you stop paying. How is it you feel justified in doubling your prices while simultaneously decreasing value?

    I love your software, but I honestly can’t justify giving more money to a company so obviously out of touch with their smaller customers.

  121. Terence Martin says:

    Huh; blog ate my post. Well, I’ll try one more time.

    I know it doesn’t change anything, but in case you’re keeping count, I am one of your customers that won’t be returning.

    I’ve been struggling more and more the last couple of years with the various small bugs and usability problems in the IntelliJ core (which means that they also exhibit in AppCode and CLion) and was trending towards potentially giving the next version a miss. However, seeing your new plan to force me into upgrading has allowed me to say for sure that it won’t be happening.

    Aside: I am fully aware of how your bug tracking system is supposed to work. You think it’s democratic and gets the most important bugs fixed and I think that the way it works it’s impossible to get any bug, big or small, fixed. I’ve ridden this merry-go-round. I’m not going to convince you and you’re not going to convince me, so lets do each other the courtesy of not bothering, OK?

    Call me a Curmudgeon if you want (many do) but I don’t want to rent my software. I want to reach into my pocket, remove some of my hard earned cash, and slide it into your pocket in exchange for owning a copy of your software. Yes, I’m aware, I don’t really “own” anything, I just have a license. However, a perpetual license is like owning a thing; a thing that can’t be taken away from you in the future if you don’t keep up the payments.

    It’s a little hyperbolic, but a subscription model is akin to a ransom demand or a protection scheme. (“That’s some nice code you have there. It would be a shame if something were to stop you from refactoring it.”). Maybe you don’t see it that way, but I do. Maybe others do too; I don’t know.

    In any case, no hard feelings and I wish your company well. From the looks of things you’re losing customers, but you’ll likely end up gaining some new ones, so it will all work out.

    My only regret is that I won’t get to ever use CLion on a project; I’m one of the many votes to have something other than CMake as a build system. As such I bought into it to support future development that I hoped would include my ability to actually use it, but c’est la vie.

    Incidentally, I would like to add that you cherry picking a couple of tweets that support this new scheme and putting them in the post is really irksome. It’s like you’re trying to say “Hey look, everyone supports this!”. No. No we don’t. Please don’t put words in my mouth.

    • Nathan says:

      I cannot agree more.

    • Maksim says:

      +1, I totally agree.

    • Alexander says:

      > Aside: I am fully aware of how your bug tracking system is supposed to work.
      > You think it’s democratic and gets the most important bugs fixed and I think
      > that the way it works it’s impossible to get any bug, big or small, fixed.

      It’s interesting. Why do you think it’s impossible to get any bug fixed?

      • Terence Martin says:

        Well, I was a little hyperbolic there, for which I apologize; it’s not impossible, it’s just very very improbable for bugs that aren’t in the latest features of the latest versions to get fixed. It’s also kind of long, but like an Allman bother, I’m a rambling man.

        I’m going to preface all of my comments below by pointing out that I’m a software developer at my company, and if I have X bugs on my plate to fix, but only Y time to fix them, some sort of prioritization has to be done to determine which bug gets fixed first, and I totally get that.

        JetBrains has a lot of developers, a lot of tools, and a lot of bugs (not a condemnation by any stretch, that’s just the nature of such a large platform). Clearly they need a way to best organize what bugs to focus on first so as to make the maximal amount of developers happy.

        To that end, their bug system is democratic in the sense that the bug tracker allows you to “favorite” a bug as your way of saying “This bug is important to me”. So the bugs that have been so marked are prioritized for fixing.

        That’s all well and good; that means that the bugs that are affecting the most number of people are the ones that are going to get fixed first, and to me that sounds like a sound business practice.

        Now where this all falls down flat on its face as far as I can see is that the situation is not “the most favorited bugs are fixed FIRST”, the situation is “the most favorited bugs are fixed ONLY”.

        By the time all (or most of) the highly rated bugs are fixed, it’s time to start focusing development effort on the next big feature set in the next version; time is taken away from fixing defects in existing features.

        Having a new feature means more code, which means more bugs (inevitably), which means more bugs are being added to the bug tracker.

        If the new feature is hot enough and tons of people are using that feature, that bug is going to get a lot of favorites in the bug tracker, so it will get fixed.

        But what happens to the rest of the bugs? Maybe the new feature temporarily knocks one of the most top rated bugs down the ladder, but it also makes the ladder TALLER. The longer this goes on, the taller the ladder of bugs grows, but the number of them that are actually fixed goes down as a result. In effect, only the most popular bugs in the most recent feature set stand an adequate chance of being repaired.

        The situation ends up being this: If I find a bug or a usability problem with a JetBrains tool (e.g. IntelliJ), I can go check YouTrack to see if someone else has already reported this bug or not.

        If they have, I will favorite it, and maybe it will actually get fixed, which would be great.

        If I don’t find the bug reported already, should I report it? My heart as a developer tells me “Yes, report that bug! Spend some time to see if you can reproduce this, write a good report, and let them know”.

        My heart as a JetBrains customer (up to now) tells me “No, don’t bother? What’s the point?”

        I’m just one guy sitting in a room, using IntelliJ. If I find a bug in something and it’s not already reported, but I know a ton of people are using this software, why would I report the bug?

        The bug will only get fixed if a lot of people support it being fixed, but if *I* am the one that found it (and I’m not using IntelliJ for hours and hours a day like many are) it’s not a bug that enough people are running into. Even if I DO report it, it’s not going to get enough favorites to get fixed.

        Using software in which there are bugs that get in the way of what you do that you constantly have to work around but knowing that not enough other people also experience that same problem so it will never get fixed is extremely demoralizing. It makes a person feel as if they’re paying their money so that other people can get better software instead.

        It certainly doesn’t foster the attitude that you should spend your own time to try and pinpoint exactly what causes something to go wrong and then report your findings if you think it’s falling on deaf ears.

        As I said above, I was really seriously considering not bothering to upgrade anything this year because it just really seems so much like “what’s the point?”.

        Now with the recent announcements it has become clear that indeed JetBrains *was* spending a lot of their focus on coming up with new features because they needed that to drive continuing sales.

        With the changes to the plan to include a fallback license and what else has been said by Maxim in the other blog comment threads, I have hope again that more focus is going to be placed on fixing more bugs.

        Based on that I am very willing to pay for one more round of updates (at least) and give them the time to see how this all plays out. I’m hoping we see a large upswing in the number of bugs fixed and a large upswing in the number of releases.

        In fact, I hope all of the people that are complaining about having to roll back to a previous version get absolutely crushed by just how many point releases we’re going to see in the first year as they crack down and just hammer the hell out of that bug database.

        • Alexander says:

          Thank you for expressing your opinion.

          I’m a tester in IDEA team. Not in any lead position, so I can’t give a “promising” answer. (And asking a question here was my personal initiative, not “approved” by anybody.) But anyway, if a user sees the situation from such point, it’s a thing to consider, at least.

          I can only confirm that the flow of incoming bug reports is really high, so if something is not fixed, it’s not a bad attitude of development team, just a lack of resources here or there.

  122. John says:

    Wow, what a shame. I love your products but I absolutely refuse to “subscribe” to desktop applications, especially ones that are central to my workflow.

    I’ve never done it and I never will. I’ll have to find an alternative. Again, what a shame.

  123. Alex says:

    Not the idea of a genius at all. After reading all these negative feedback, will you review at the very least this decision?

  124. Keegan Novik says:

    As a loyal JetBrains customer and someone who has convinced around a dozen friend and six different companies to buy your software, I’m very happy with this change overall. I have two suggestions for you.

    – First: Offer your existing user pricing both to existing users, and to any new users who pay 12 months in advance. This deal will make it easier for me to recommend the software to people since subscriptions generally make people uncomfortable, but everyone likes a deal.
    – Second: When someone pays in advance reflect that on the clientside license information. Then when one of the above customers isn’t able to connect to the Internet their software won’t disable itself until the license date expires. This will make it safe for someone who’s traveling or something to still be able to work on the go without worrying about losing their IDE.

  125. Mark says:

    At least be honest and say that this is beneficial to you as a company and NOT for your (soon to be ex) customers.

  126. Harold Chan says:

    I think I will move back to Eclipse.

  127. Titusz says:

    Hello Jetbrains,

    please reconsider your decision to force your customers to use as subscription
    only model. The perpetual liscense is very much appreciated and I bet that
    most of your active uses will upgrade yearly anyways (as I do). And they do it
    out of free choice and feeling good doing it. This is a psychology of positive
    feedback. But if you kill the perpetual license you kill free choice and with
    it the positive attitude towards JetBrains for many of your customers.
    You kill the very reason the became your customer. Such a move can kill a company.

    Never change a running system!

    In case the perpetual liscense doesn´t actualy work out for Jetbrains in
    terms of financial sustainability you should just say so and raise the prices
    for the perpetual licenses. I am sure customers would have more sympathy for
    that than killing the perpetual model. You could still offer the subscription
    based model as an aditional option.

    Is all about giving your customers the choice and being a trusted partner to them.

  128. I love IDEA since its version 1.5. I more or less regularly updated my license. But a subscription license is a no-go for me. I most likely will NOT purchase a subscription – I want to make a decision when to pay and when not. We only need the IDEA Ultimate license for managing our website (~10% of our development time; the remainder is pure Java development), so I reckon we will continue using our existing license or find a different solution.

    We at are offering subscriptions since approx. 1 year to our customers – but as an alternative to a perpetual license. Only ~3 out of 10 customers takes a subscription. We don’t have too much customers to reject 7 out of 10 potential customers.

  129. Jaan Teodor says:

    As I only use ReSharper, I find this a really weird decision. Visual Studio has been constantly improving, to the point where having r# is nice-to-have, and not need-to have. I would have expected a major price drop, and not price hike/subscription.

  130. Jonathan Windridge says:

    What a horrendous move. I have been a huge advocate for JetBrains for several years now, but the idea of paying a yearly subscription for a desktop product seems absolutely ludicrous.
    As many other users have said, those who upgrade on a yearly basis do so on the basis of purchasing a better product with new features that they consider to be worth the money.

    This just strikes me as an easy way for your company to maintain a constant cashflow without continuing to drive innovation, and a quick cash grab above all else.

    I would urge you to reconsider your position, as otherwise you will lose me in with the swathes of your userbase leaving for other products that are either Open Source or have sane licensing agreements.

  131. Martin says:

    At least lower the price so 1-year subscription is less than a previous perpetual license.

  132. Marek Hanzal says:

    One more opinion. Shortly: I love JetBrains products (IntelliJ and PhpStorm). Its best I’ve ever found. It has many features – and now will came new – and must say KILLING feature. This feature (yes, subscription model) will kill me “love” for JetBrains product.

    Who has balls to say that this is for customers? Maybe I’m alone with this opinion, but everywhere I hated short-term things. I wanna *buy* this, but don’t want *rent* this. So – cars will be one day only rented for insane prices? No no. That isn’t for me.

    I’m currently using company’s licence and I wanted originally buy my own. Now? It’s time to cry and look for another – worse – but another product (permanent)…

    God with you; try to reconsider and… provide way to choose way how to use your products.


    • Mark says:

      At JetBrains we believe that software developers are some of the most forward-thinking people in the world.

      And yet you insult us by presenting this as something that would benefit us, your paying customers, and not as it is; something that is only beneficial to you as a company.

      If you want more money, at least have the guts to say it straight, most of us have more than enough experience to see through your marketing BS.

  133. Henk says:

    We ditched Adobe after they started their subscription model. I won’t use microsoft office although it is certainly better then openoffice.

    There are a lot of other issues:
    – Is the subscription license for one machine only, or can we keep using it on different machines, as long it is only one at a time?
    – If I donot have an internet connection for a month (what happens in my situation), will the ide become useless?
    – Why, wtf why, will the ide become useless after your subscription ends. This is sooo bad. What are our benefits? This is bad for your customers, so please donot sell it as a good thing for your users!! It puts your credibility to below zero in a simple statement.

    If you cannot keep your business running at the current rates, pls tell so. Everybody understands when you need more money. On the other hand, please be carefull to not give a lot away to others, and let the folks that use it for their work pay the bills!

    I did never mind to pay your license fees (two products, for 6 and 4 years in a row). Now I do.

  134. Lucas says:

    Why do you do this? I’m a IntelliJ user and did a yearly upgrade of my Version since a couple of years. I like the fact that I can choose whenever i want to pay for the update or not.
    I do not like this subscription license model and the fact that i HAVE to pay in order to be able to use the Software. It will cost me 10USD less with the new model (right?) but i would like to pay 10 bucks more in order to have the freedom of choice.
    Too stupid you took the way like Office365 and Adobe.
    I’ll stick to last possible version with my (old) license. I really like your IDE. It’s a pity.

  135. Eric Bartels says:

    This is bad news … another company making greedy decisions!

  136. Markus says:

    I am using PyCharm now for almost 3 years I think, and I always paid for the subscription. Partly, because I am convinced of this product and want to support you, partly because the licensing was not too expensive.
    I will however not accept a price model where my software stops working when I do no want to pay anymore. I will absolutely NOT rent any software. Please reconsider this move or find an acceptable way. For example I am willing to pay extra if i did not renew my license for a year or two, but at least let me use my last version if I do not want/can pay anymore.

    • rosdi says:

      This is exactly what I said earlier. Allow us to continue using the last version we have even though our subscription has ended. Later if we choose to renew then jetbrains can charge us ‘re-subscription’ fee.. fair and square.

  137. Dude says:

    Sad, sad news… Hopefully Roslyn-based community projects will get better soon enough.

    We are trully a generation “Rent Forever”…

    There isn’t even ReSharper Community Edition. Why would I be interested in other free crap?

  138. Marat Dreizin says:

    Hate new model! It is not developer friendly. Why I should pay $99 (new price) instead of $49 (regular price) for WebStorm?

  139. Pingback: JetBrains Toolbox: JetBrains stellt neues Lizenzmodell für Entwicklerwerkzeuge vor -

  140. Vincent Jaubert says:

    Don’t try to fix what’s not broken !
    Don’t take me for a fool pretending this is beneficial to me since your goal is only money driven.
    Another previously happy now unhappy user that WON’T subscribe to the new model.
    Back to open source for me.

  141. James Mallison says:

    Well, my company will no longer be using this either. Say goodbye to a lot of customers, JetBrains.

  142. Jonathan says:

    Surely, out of all audiences that exist for software, you could anticipate that individual developers would be among the most sensitive to a SaaS model especially for *desktop* software.
    We are pretty much the only people who have thought deeply about and actually hold strong idealogical opinions on software licensing issues! Many developers have passionate ideologies about software IP issues, that’s why we see so many heated debates on the pros and cons of different OSS licenses, licenses created by developers who have unshakable and very political opinions about software freedoms.

    This just seems like such a tone-deaf move for a company that makes developer tools to make – but maybe you are only thinking of the more lucrative enterprise market.

    It’s not about the money, it’s the principle of the thing; I don’t want to live in a world of software subscriptions. The only way I can make my vote count is with my wallet.

    Finally, there’s the issue of exchange rates – at a time when many currencies are in a great state of flux against the euro and the USD, what seems like a good deal one month may not be the next, and I don’t have the option of holding off on my purchase if current exchange rates are unfavourable to me. How can one budget for such a variable?

  143. Richard "Virgo" Richter says:

    I don’t know what kind of response Jetbrains expected, but I see exactly the kind of comments I expected after reading the announcement. Makes me sad. I understand subscriptions for MMO games where they need to run clusters and what-not. I definitely don’t like it for desktop development tools (does anybody?!).

    I’ll have to seriously reconsider whether to switch to the new model – because that will render my perpetual licence non-pertpetual. And that is a major blow for me, even if it doesn’t seem reasonable to you. Not to mention you spending customer’s money for initiatives customers seem to dislike.

  144. Daniel Hoffend says:

    Sorry … I really dislike your choice to switch to a subscription model. While it might be useful for commercial customers who can decide to buy more licences or drop them if needed, but for personal users or small indie developers this is a basic no-go.

    Really …

    As a personal user I’ve used a previous phpstorm version for quite some time and just decided to buy the current version again. It’s my decision based on my needs if I need to upgrade and buy a new version or keep the one I’m happy with. Sometimes I don’t need the newest version.

    I would like to see that still both options should be available. Buy with 1 year upgrade support for personal or small companies and subscription model for those that need it.

    Well … I can just speak for myself. I will never switch to a subscription model. I would rather go back to vim, atom., ultraedit or whatelse, but would not accept any subscription model for my hobby … no never …

    Enjoy loosing happy customers. (The rest of my wishes are not public)

  145. Joerg P. says:

    For me the new model is a goodbye to JetBrains (unfortunately). I bought a private license of ReSharper as part of the end of the year sale a couple of years ago. Since I am also a professional software engineer I started using my personal license at work (my work does not offer ReSharper for their employees unfortunately, but it didn’t matter to me). Besides the fact that my employer saved a bunch of money because of my efficiency boost using ReSharper for years, I was also a lot happier since ReSharper makes my everyday life easier and my users happier since I am producing nice a (almost) bug free code.
    I am not able to pay a yearly fee that my employeer does not reimburse for ReSharper. And my private projects are just for fun projects and also do not reimburse any yearly license costs.
    So I am gonna buy the latest version of ReSharper before JetBrains change their licensing model and be done with it. Goodbye JetBrains :(

    • v. says:

      So you are going to bite the bait? I am afraid that the whole fuss is about making users like you (and me) do ‘one last update’ before admitting that it was a wrong move to make.

  146. Barry says:

    This is very disappointing. I doubt I’ll renew my subscription when it means I lose perpetual rights to something *I’ve already paid for*. The only thing I’m prepared to pay rent for, is a home, not software.

  147. D. Karvounaris says:

    This is really really bad news!

    NO gain, yet we are enforced to keep paying to use a software, where there was no issue by having it previously once paid and only pay for updates, when they seemed useful.

    There’s no other reason for companies to switch to such a subscription model, than the thinking they are going to earn more money and keep their users stuck in their system.

    I have respected Jetbrains for many reasons and have suggested it to so many others, but this is really taking a hit now. I can’t suggest a software to anyone, that asks you to keep paying and modifies your system to not use something installed on your pc, if you don’t keep paying, even if that person might just need to start it up only for a simple task.

    Every software company should understand, there ARE alternatives and they are growing and becoming better too! And where there aren’t alternatives or good alternatives, a competitor always hits the market, especially when things like this gives THEM an opportunity to do so!

    I just renewed my license for PHPStorm 9, I would had _NOT_ done that, if I knew that suddenly I can’t keep pay when and if I need another update, say in an year, because I’ll be enforced into a different model in future with which my software would be locked down.

    You just lost another customer with this.

  148. Well done guys on getting this out the door, I hope it goes well for you.

  149. Sully says:

    How upsetting. First Adobe and now JetBrains. These kind of nasty subscription models make me completely lose interest in an otherwise stellar product. You have lost a customer.

  150. Saraf says:

    back to working with open source IDEs.
    webstorm was great.
    sorry to see this new rental model.

  151. Benjamin says:

    You just lost a customer. I will not allow you to shove a subscription model down my throat. I will indeed keep using my current licence indefinitely.

  152. Ladislav Mrnka says:

    I’m Adobe CC for Photographers subscriber and it brought me the best value on Adobe products I could ever imagine – I would never go for standalone Adobe Photoshop.

    Subscription based SW is a future. You may not like it but it makes a very strong business case and if implemented correctly it makes sense even for end users as they always have the latest and the greatest version and support.

    As a developer you use SW to create value and get paid for that value. Is it really so bad to pay few $ a month for a tool you use to increase you productivity and actually make more $ for yourselves or your company? Yes people who are using it for their hobby projects may complain that they don’t make money but that is why community editions exist.

    I use more than one JetBrains tool – Resharper Ultimate and IntelliJ Idea (+ Python plugin). I was considering CLion as well. Now I can actually pay less and have Resharper, Idea, CLion and PyCharm. Plus I can pay monthly which I like more, even if it is more expensive at the end. It does not seem like a bad offer. I had to upgrade those tools almost every year anyway to get support for the latest Java / .NET versions or the latest Python plugin with fixed bugs.

    Although I agree with complains about individual licenses – they seem to be too high and there is too obvious push to ALL in license.

    • Ladislav Mrnka says:

      In general I believe that the same thing which happened to Adobe happens here as well: Prices which are currently promotional (**) will be the real prices at the end. All comments around are not only against the subscription model but mostly against much worse value/cost ratio due to price hike and lost of license ownership. Subscription model can be sold to individuals and companies only when it is much cheaper than perpetual licenses used to be, which currently doesn’t seem to be case for individual products.

      • Tobi says:

        Comparing Adobe products to JetBrain products does not make sense, the “API” of your images do usually not change.

    • Terence Martin says:

      “Yes people who are using it for their hobby projects may complain that they don’t make money but that is why community editions exist.”

      I find it sort of off-putting and elitist to think that just because someone is not actively making money doing something (e.g. a hobbyist), they’re not entitled to use the tools they want for what they’re doing. Which is what you’re saying, or what it appears that you are saying.

      Again, please don’t misunderstand that what many/most people are mad about is not the inherent cost, it’s the forced lock in to using these tools.

      If I have a perpetual license, whether I am a hobbyist or a professional, if I decide that there is no value added by the next version of Tool X, I can choose not to pay and keep using what I’m using.

      If I have a subscription, then as long as I need to use Tool X I need to pay for it, forever, in perpetuity, or I lose my access. Choice is lost.

      The Hobbyist should be allowed to say “You know what, I only work on Java programs as a side hobby and don’t make much, if any, money from those programs. However, I am going to treat myself to a copy of IntelliJ Ultimate because I have a lot of use cases for it and it’s money well spent”

      That has now been removed.

      • Ladislav Mrnka says:

        I never meant to say that. I myself have several personal licenses and they are mostly used just for hobby. I spent almost all my dev time at work in Sublime as none of JetBrains tools fits my needs and our custom build system. Even though I recently purchased Resharper Ultimate personal license as it was still great value for me.

        • Terence Martin says:

          That’s fair enough, sir. I’m in the same general boat as you, so I apologize if I came off as a little snarky there, as that was not my intention either.

          I carry licenses for IntelliJ, AppCode and CLion but the only one that’s useful for me for day to day operations that I earn money for is AppCode for iOS work.

          I would love it if CLion supported something other than CMake, as then I could use it for my hobby projects. If they also copied the ObjC support from AppCode into CLion, I could actually use it for work purposes (yeah, I write ObjC code for Linux servers, not Macs). However, at least 50% of that is never going to happen, so I generally spend most of my day in vim.

          • matt says:

            Unfortunately, with this new model, that kind of cross-polination of features will happen less. The system incentivizes them to make more specialized standalone products in order to drive people toward the “all products” license.
            I predict that in a year or two, Jetbrains drops support for Python, PHP and Ruby from IntelliJ. They’ll have a similarly poorly-done blog post that tries to pass it off as a positive thing for developers, but it will be in an effort to drive people toward the “all products” license.

  153. Nikita says:

    I love the idea of subscription!
    But I think, that you should give 2 ways to buy your software:
    1) Subscription way
    2) Old way, but prices must be higher at 30-40%

    Everybody choose themselves

  154. Sorry, but even as someone who generally renews every year I am not remotely interested in a ransom-based pricing model. Your comment that the main reason for this change was so you don’t need to bother introducing new features to convince people to buy upgrades also doesn’t fill me with confidence.

  155. Joe C. says:

    Glad I’m on Windows, I can use VS Studio 2015 Community edition with excellent support for Javascript, node.js , Python and Django for free. Don’t see any advantage to going with WebStorm or Pycharm now.

  156. Martin Anlauf says:


    I really love to work with Intellij Idea and would like to stay customer. I want to ask you to consider keeping the traditional “buy” model (perpetual licensing) as an option, and not to try to force customers to switch to a “rent” model. If you would want to offer a “rent” model in addition, that’s fine.

    It would be sad if you reduce your customer base by such a marketing shift.

    Best Regards,


  157. Diego Agulló says:

    Develop with pleasure!

    Not anymore I’m afraid…

  158. This announcement shows absolute contempt for your customers. We aren’t idiots. We can all see this change is for your benefit, not ours. The very least you can do is be honest about it.

    Like other customers who have commented here, I am not at all comfortable with the idea that my tools will hold me to ransom every month.

    I have always been very happy to pay for JetBrains products. Now, if I do so at all, I shall do so very grudgingly, and I will constantly be looking for an alternative.

    Consider Adobe. Have you ever met a happy Adobe customer? I haven’t. Adobe get away with this abusive business practice because they have a near-monopoly in many industries. Many Adobe customers would switch to an alternative tomorrow if they could. Do you really want to be more like them?

    • Nikita says:

      I am happy Adobe customer

    • Nikita says:

      I am happy Adobe customer and dont want to switch

    • Ladislav Mrnka says:

      I’m also very happy Adobe customer. Their CC offering actually made Photoshop affordable for me.

    • Joe C. says:

      I’m very happy with the current Adobe subscription model. Makes all their software affordable. I think this is what Jetbrains is trying to do with their all inclusive option. The difference is…I use several of the Adobe products (photoshop, lightroom, premier,aftereffects, illustrator, audition…) plus Adobe offers several free apps for IOS devices included with the subscription.
      I don’t see people using all the tools in the all inclusive package, so paying for stuff they won’t ever use (why pay for resharper is you don’t program in C#?) 9.99 a month for a single tool ends up being more expensive than purchasing an individual license each year. 7.99 saves 2 dollars a year, but requires you to always pay.
      p.s. Adobe’s intro price was 29.99 a month for one year, then went to 49.99, but still a great value.
      I understand this is a revenue model that can keep a company profitable and able to continue to provide good service and products, just needs to be adjusted for reality.

      • Mike Jacobs says:

        I agree, the new pricing is unrealistic for small (single-IDE) developers.

        I absolutely hate the subscription model, but I subscribe to Office365 because it’s a great value. They even offer 1 TB of online storage in addition to their full software Suite, for the same $99 Jetbrains wants to charge for a single IDE.

        Switching to a subscription model, while unfortunate, is at least somewhat understandable. Doubling the price of an IDE at the same time, though? Most other companies LOWER their price when they switch to subscription, because it’s less valuable to the consumer to not have a perpetual license.

        • Kevin says:

          Heck…didn’t know Office365 offers 1TB of storage. That’s SaaS I can get behind…they are storing your data on their servers…that’s something that makes sense as SaaS. I’ll still keep my older office versions on hand, though, in the event I decide I don’t need the 1TB anymore.

          • Oletros says:

            They offer 10TB

            • Kevin says:

              Free with Office365 or in addition to? If it’s free with Office365, I’m sold at 1TB. If it’s $99 in addition to Office365, then Google Drive is still good enough for me and I’ll stick with my old office perpetual licenses.

              • Mike Jacobs says:

                Sorry for taking so long to respond. The 1TB is free with the Office 365 Home (the $99.99/yr one for 5 PCs).

  159. Zlonax Bubuka says:

    When company trades its customers hearts to bucks – it’s well known sign of company sunset, meanwhile the managers try their best to convince that everything is under control. It’s the customers hearts what brought company to success, it’s the underestimated customers personal efforts to spread the IDEA. But some managers just don’t get it, because $ is the only measure for them, and hearts and volunteer efforts are not in their spreadsheets. You just traded your future for quick profit today. Looks like the decision to terminate Jetbrains is already made, and owner is monetizing everything before departure.

    • Wil says:

      Well said. It’s a sad day.
      Something better will come along though. eg: Chrome and Firefox were born out of frustration and lack of innovation from IE.

      It would have been better if they just said…”hey loyal customers, we aren’t making enough money to keep doing what we’re doing. We hope that changing the pricing model with fix this”

      I wonder how much time was spent trying to spin this into something that sounds like a benefit to the customers/developers that made them a success (thru plugins, spreading the word, convincing managers, pull requests…)

  160. Pingback: Wirbel um JetBrains Toolbox: Langjährige Kunden verärgert über neues Bezahlmodell -

  161. Sean says:

    Can’t you just offer both licensing arrangements, the old and the new, perpetually? If the new licensing model is so much better, you won’t lose anything by doing so. Also – when JetBrains goes belly up because of this, what server does the “pay day after day licensed software” contact to validate the license?

  162. Brian O'Malley says:

    We are loyal fans of ReSharper, but we won’t pay for your product monthly. Our purchasing and procurement model here (I work for a government agency) won’t back this. Let’s hope the Rosyln compiler for C# 5 with it’s light bulbs will catch up to ReSharper eventually.

  163. Yshm says:

    My coworker uses a pirated PHPStorm.
    Go get him.

  164. Thomas Glaser says:

    For me, this is a good change. I’m building JS/PHP/Python applications, constantly trying out new things, so I had to upgrade most of the time anyway.

    But I can certainly understand why some people do not like this change at all. In my opinion, you should reconsider moving to a subscription-only model. Or at least give people a license that works indefinitely when they buy a yearly subscription? So they can cancel it when they do want, and keep using that version, without updates of course.

    Though there is one question that I have: When I upgrade my IntellIJ Ultimate to this new subscription for Intellij Ultimate, can I later decide to change it to “All Products” subscription and keep my reduced price (I mean the 150$/yr for existing customers)? And what about downgrading when I no longer need it?

  165. Alejandro Zuleta says:

    WebStorm users are the ones who lose the most with this change. Not only its price has almost doubled but now, whenever we stop paying, we can’t use it anymore. Great move! Sadly, I’ll have to move back to Sublime or Netbeans.

  166. rosdi says:

    We should be given a CHOICE.

    Offer both license model, with the perpetual license model is naturally more expensive than subscription model.

    Let this run for 2-3 years, and see how many percentages of those customers choose which licensing model.

    • Kevin says:

      +1 – Clearly, they are capable of doing this because they are going to be running both types of licenses over the next year…too bad. I’d gladly pay more to upgrade a perpetual license every year before I’d sign-up for a subscription.

  167. Victor says:

    As a user of ReSharper I am not happy with this change at all.

  168. dam9 says:

    We are currently a really happy little enterprise of 2 developers using everyday PHPStorm since 4-5 years I believe, and for now, our boss renew our licence every year without problem, even if we don’t “roule sur l’or” as with say in french (“rolling in money” in english ?). And if next year, our finance is so bad that our boss can’t renew our license, we can say to him that it’s ok, we won’t have new updates for now, but we can still work.
    But here you’re telling me that if our boss tell us that in 2 years instead, like “sorry guys I can’t renew right now, maybe in next few months”, just on the moment to renew our license, we won’t be able to WORK ??
    Because all our projects and workflow uses tools and configuration of PHPStorm, so not being able to use it overnight will drastically low down our efficiency and rapidity, therefore make both our boss and our clients unhappy… And us also, being so accustomed to these workflow, tools, features, shortcuts, etc.

    Really really bad move here… I’ll have to start to find an alternative…

  169. Stefano Gombi says:

    When I tried WebStorm and PyCharm I thought I could finally stop searching “my” IDE. Sadly, I was wrong.

    Bad move. Please consider to fire all your business department.

  170. Sean says:

    On the whole “phone home” thing – you know, everyone writing in on this thread writes software with extreme dedication and care. We are all employing the best practices we can find time to learn and implement (TDD, BDD, human and automated testing…) so that the software is as rock-solid as we can get it. You at JetBrains do the same thing. And now, under the new licensing model, all of that same care, all of that attention to detail, the hours upon hours of testing, will go out the out the window when a functionally unnecessary Internet connection cannot be obtained. The entirety of the software functionality is broken in that circumstance. I can’t write software like that. Can you? Over what? Trust? Really? Heck, a simple rainstorm knock out my Internet connection for hours. Bug report: Your new licensing model introduces a crippling spurious bug that causes the program to be unusable – can you please fix it?

  171. Alex Collins says:

    Because of this change I will no longer be purchasing JetBrains products.

  172. machak says:

    for my company this mean “leave jetbrains with pleasure..”…

  173. AaronH says:

    While this may suit a handful of people it’s definitely worse for the majority. People like to own their software – not rent it. This is far worse for people who love a single product of yours but only uses it for their own uses/hobby coding. They may decide a $100 one of is worth it for a copy of the software for their dabbling, but having to pay an amount every year is going to suck for them.

  174. Ben says:

    The change to a subscription model is extremely disappointing. I work as part of a in-house development team for a small company, so knowing we own a license to use the software in perpetuity is very important because if the company has a rough year we know we can just carry on using an older version of Resharper and upgrade when times are better. This subscription method means we are forced to pay for updates we don’t necessarily need at the time, even if the money is not available.

    There’s no way we can really rely on software that we are not guaranteed to have access to indefinitely, so we will be unlikely to move onto the subscription model. It’s a real shame as you guys make fantastic software but we’re going to be forced to look for alternatives because of this decision.

  175. Jack says:

    I would like to add my voice to those that for one reason or another *require* a perpetual license. I use IntelliJ IDEA heavily inside an environment where a ‘phone home’ connection is just not possible, nor desirable. PLEASE do not do away with the perpetual license. I would be willing to pay even more than the USD $99 upgrade.

  176. Evert says:

    No no no! just no!
    I hate subscription models. When I buy software I want to be able to use it whenever for however long I want. I might not have x amount of money each month. Also i may not have the money to upgrade every time, so I only upgrade when I saved enough.
    I realize most will use phpstorm (or another jetbrains product) regularly, perhaps every day. I use it at most 3 or 4 days a month and upgrade at most every 3 years (sooner if there is something big added I need.)
    This subscription model just doesn’t work for me.

  177. Ricardo says:

    I’m just starting looking for alternatives. This new pricing model freak me out !

  178. electrobardo says:

    What will happen if JetBrains dissapears?

    • Tobi says:

      They will not dissapear. They will lay next to other IDEs killed by marketing and greed on the graveyard for irrelevant software. There is a nice place free between VisualAge and the Borland Suite.

      • Rob says:

        e.g. if JetBrains gets bought by another company and they follow their own interests?

        Then all of us are hosed.

  179. Taylor Jones says:

    I’m sure this has been said a dozen times already, but I’d like to add my voice to the chorus: “Please don’t take away perpetual licenses, we want them and we’re your customers.” I love the idea of an additional subscription model for the various IDEs, but if I want to have a perpetual license, I should still be able to buy one. Don’t become Adobe :(

  180. Dumb says:

    I think it is clear from the comments here that the decision to move to a subscription-based model is not only unpopular, but reviled. Perhaps you should heed the suggestions of your constituents and seriously reconsider the poor decision to pursue greed instead of a VALUED CUSTOMER EXPERIENCE.

    Cue canned apologetic/grateful marketing team response…

  181. Carter Mitchell says:

    This model is becoming the favorite of software companies, not to make things better for the customer, but to ensure a steady revenue stream, by eliminating the ability to purchase once (i.e. Windows XP) and be happy with the original product, not paying for the updates.

    The move is purely to benefit JetBrains, not their customers.

  182. Arjan says:

    Thanks for announcing this just while we were about to decide what tooling to use for our future Node.js/Meteor projects. Xcode has just won, no more doubts.

  183. BirdPerson says:

    In birdperson culture, this is what we call a “dick move”.

  184. Jon Whitcraft says:

    So i’m confused on the toolbox concept, I have RubyMine and PHPStorm. Do i just pay the 7.90 a month or 49 a year (existing customer) and get access to both or do i have to pay the 49 a a year for both?

    • Mike Jacobs says:

      It appears you’d pay the $49 for each of those. But if you let your subscription lapse, it would be $99 each when you resubscribe.

  185. Stephen Richards says:

    End of days for my PHPStorm installation ;(

  186. Nat says:

    I know I’m just echoing what most have said above. I love your IDEs. I find them in many ways superior to others but I will not switch to a subscription based licensing model. I will no longer “sing your praises” because of this.

  187. Simone Bernini says:

    I was just about to buy one or two of your products. I think they’re great.
    Now i’m looking for alternatives.

  188. Max Kalus says:

    Even though I will pay less for my licenses, I dislike the subscription model, too. I will check alternatives, even though I love your products.

    +1 to vote for perpetual licenses!

  189. Tobi says:

    Even if you would step back from this decision, Intellij as a IDE is dead for me. It is essential for my business that I can reactivate a project even after years. With your decision you have shown that this requirement is not important in your opinion.
    I have paid for Ultimate the last seven years, even I only need the features of the CE edition. But CE is not a viable solution also anymore, because it is predictable that you will start to cripple down the CE version in the future.

  190. Andrew Rawnsley says:

    That there is room for a subscription model I don’t dispute – I can see many situations where that would be useful. But the removal of choice is NEVER an advantage to a customer base as wide and diverse as this one is, particularly one who (as we see in all the comments above) who cite the benefits of the existing arrangements as a reason they use the product to begin with. Even if the price on the perpetual license went up I doubt most would mind if they retained some choice in the matter.

    Compounding the problem is hiding it under the tired and cynical “for the benefit of our customers” line indicates that whole segments of JetBrains has jumped the shark. People can take honesty even if they don’t like it, but don’t like being asked to swallow that sort of empty marketing fluff. It does not engender trust, and trust is what you’re asking your customers to have, trust that:

    1) Your updates are always non-disruptive and better than the existing one (sorry, fat chance),
    2) It will be to your customer’s economic benefit, and (most importantly),
    3) You’re not trying to drive your customers to draconian vendor lock-in, which is the inevitable outcome of limiting your customer’s choices.

    This cynicism towards the customer base is what may in the end make any well of trust built up over the years evaporate. How JetBrains responds to the backlash will tell us, the customers, how much trust we can eventually maintain.

  191. Pingback: JetBrains Toolbox: JetBrains führt neues Abomodell ein

  192. Anonymous says:

    I can picture the guy writing this blog post thinking:

    “What I need to do is camouflage this effort to make more money into something useful for all the developers base. Let’s pull some tweet, after all you can get *all* opinions on twitter (good, bad, right, wrong, genius, stupid). Let’s also take a flashlight and point it only on the faintly good side and pretend that the rest is either obvious or not worth mentioning. Also let’s get some of our guys monitor the comments so we contain the damage”

    Really guys? Your readers/customer base are some of the brightest developers around and you’d think they know better than to be dragged by the nose by some sugar-coating of a bad news as a good news.

    But now I think why was this move necessary. Maybe you just want to make more money. If it’s that, no use elaborating. Or maybe you just need the money as you’re finding out it’s no easy feat to make and maintain an IDE for a long time. In that case, other alternatives are welcome.

    In any case, at least open source developers are fair towards their users and just do their best, even though that might not be enough. After all it almost rarely is. Just as this post.

    • Wil says:


      It looks like the damage control folks have given up for now (Andrey Cheptsov, Eugene Toporov, Robert Demmer).

      Maybe this will be like the “New Coke” experiment of the 1990s. They realized they did something silly and changed course, after hemorrhaging customers.

      (Sorry for the old reference if you weren’t a soda drinker in the 1990s,

  193. John Schroedl says:

    Such a colossally bad move. I held JetBrains to a much higher standard than this. Let’s hope this plan is reversed ASAP or the devs will be fleeing in droves.

  194. ds says:

    Sorry guy’s not going in for another sub. CC is enough, already got it down to just PSD and I’m gone the second I can replace it with something else. First year fine, second year goes up, third up again. You will have no incentive to have meaninful updated and we will get the whole ‘we are updating are code base’ crap for the first few years.

    As for IDE’s there are plenty of options and it’s not enough to keep me for the sake of a little convenience. Bye Bye Phpstorm hello again Komodo.

  195. Pingback: We are listening | JetBrains Company Blog

  196. ML says:

    Our company purchased a couple of PhpStorm licenses and renewed them several times. Subscription-based software is against our policy. We will move on to NetBeans or other alternatives then. Bye PhpStorm.

    • lazarus says:

      NetBeans? haha, good luck with that!

      • Terence Martin says:

        Interestingly, I tried NetBeans a couple of years ago as part of a work project. I downloaded the latest version today and successfully managed to open up the project even though I hadn’t sent anyone a check first…

        *tongue firmly in cheek*

        • Tim hawkins says:

          Been playing with the Netbeans 8.1 beta in the last few days for php, and comparing with phpstorm. I must admit it has come a long way since i last looked at it. The only things i see that i foumd to be clunky was tbe lack of easy configuration of the debuger targets, and the lack of external tool setup. Almost everything else seems to be there, and aside from needing to implicity save files which was irritating, after spending a day with it in one of my projects it was not too bad. Not up the the satandards of phpstorm, but deffinatly very useable. Its version of inspections found a bunch of things in my code that Phpstorm had missed.

  197. Hussain says:

    Your loyal customers are indirectly your sales people. We try to convince our team, company and colleagues to try these products at least once. You guys are not paying us any fees for this, we do this because we love your products and want others to see its benefit. Now, with this new model, it is other way round. Instead of adding more, you are now losing existing. Good luck with your ransom based model.

  198. Shawn Morrison says:

    This is honestly a pretty big letdown. A year ago I’d never have imagined I would be able to get Visual Studio for free, but have to pay a subscription fee for ReSharper. Have Microsoft and Jetbrains swapped profit models? 😛

    I was planning to upgrade to the next version of ReSharper, but now if I choose to “up”grade, I’m getting a product that is provably worse than what I currently have because it will only work for a year before going on strike and demanding more money.

    I hope you will reconsider this decision, Jetbrains. Ever since I started paying for ReSharper, I’ve never looked back. It’s a great tool at a fair price. I’ve convinced my employers to buy many licenses because I could tell them with 100% certainty that it was worth every dime they’d pay for it.

    But now I really feel like I need to shop around before signing up for yet another recurring fee. If my employer asks me whether it’s worth it now, I’ll have to start with “Well, it depends on how much you use it….” I’ll have to give some consideration whether to maintain my personal license as well. I don’t make any money off the work I do at home, so paying a recurring fee just to write browser video games in my spare time… maybe isn’t worth it any more.

  199. Mikkel Lauritsen says:

    We have IDEA Ultimate licences that we currently don’t renew yearly; only when new features show up that make it attractive (or even necessary) to upgrade. So even if I guess that makes us a less valuable customer, for us the new subscription scheme is a net loss and definitely something that will make me consider moving away from your products.

    But the main problem may be the way you communicate. The fact that you try to present it as a move without any downsides makes it look as if you’re trying to pull a fast one on your customers, and your continued attempts at evading issues by (in particular) Robert Demmer above only makes it worse.

  200. Jake H says:

    Quite sad to wake up to this news. Epic fail for developers today.

    I just want to add my voice with the many others in protest. I’ve used IDEA for years but with this current news my relationship with jetbrains will come to a jarring halt.

    I have no qualms with adding a new pricing plan as long as the old model remains in place. If the new model is as appealing as you believe it is.. then let people vote with their choice.

    You may get a few people who upgrade their perpetual license prior to Nov 2nd. This will boost numbers.. but then your company will get starved out because of this short sighted blunder.

    Also.. what’s to stop you from increasing the cost of the toolbox once you have customers locked in?

    This is a classic case of letting the inmates run the asylum.

  201. Uwe says:

    I am using Eclipse for the backend work but for HTML and JavaScript WebStorm is brilliant. So it really hurts that you are moving to perpetual subscription model – I will not follow because I buy things and use them as long as I like.

    It will be hard to find another tool like WebStorm…

  202. ulon says:

    Subscription is bad. Before I could buy IDEA and use it as much as I want, unlimited. Now with subscriptions if I stop paying, I stop having the right to use the software.

    You don’t buy the right to use of the software, you rent it for a limited time.

    They’ll see a piracy increase

  203. Pingback: JetBrains Lockin: We Told You So | Life at Eclipse

  204. Nigel says:


    Thats the sound of losing loyal individual advocates that help drive tool adoptions at companies.

    I was about to recommend moving to Webstorm. Now there’s not a chance.

    Wow. Simply stunning miscalculation. You keep saying “your voice has been heard”. Lol…my kids hear me too but they aren’t always listening.

    If you continue down this path this is likely to become one of those case studies used in business classes. Like the decision Borland made to flush name recognition down the drain by renaming themselves Inprise (who?).

  205. Barry Johnson says:

    I’m not as outraged as some here about the move to subscription pricing, however it is disappointing. I often go long stretches without firing up IntelliJ anymore, although I do like having it handy for when I want it. I’m not sure I’d go for the subscription just for “having it around” even though I have consistently bought each version upgrade.

    I think most of all I am just really tired of all these subscription expenses on my credit card that just act as a slow cash drain when they fall into some disuse while the meter keeps running. I just canceled something yesterday that had eaten up $200 over the past year (quarterly billings) for a product I have not used for at least 11 months.

  206. Andreas says:

    So you argue that if I renew yearly anyway, it is getting cheaper now? Ok I get that. But what about customers that actually don’t renew yearly? I was very happy with IDEA 11 for the past few years, since I was working on the same (legacy) project which didn’t need new features in the IDE.
    I switched to the current IDEA 14 because I’m in a new project now and don’t intend to buy 15 or 16 – most likely. What about users like me? I’m basically f*cked now or have to pay much more than I would have had to pay before. (I’m speaking about the licensing model, not my actual situation – I know I can simply keep using version 14 “forever”.)

    I use IDEA privately (and yes, I like the ultimate features) and also at my work place. If I convince my employer to spend the subscription I’m still lost in my private projects. And as I said: paying for the subscription myself is much more expensive than paying for an upgrade every few years.

    Why don’t you offer both models? Same price with same conditions as usual and cheaper rates for subscriptions for people who prefer that?

    Anyway: if you keep the subscription-only model, I’ll be back at checking out the alternatives (NetBeans and Eclipse) again. I’m very sad and disappointed.

  207. Dmitry says:

    Sad but… It’s time to move on. Thank you for your work on IDEA – it really worth its money and I’m used to this IDE for the last 4 years. But I can’t accept this fraudulent subscription model and follow it. Bye and good luck to you.

  208. Pierre says:

    Here is another big fan of Jetbrains products, deeply disappointed. It will become hard to advocate for your products with a subscription model.

    After years of IDEA, I was strongly considering WebStorm for a Node/Angular side project.

    I will start to watch for alternatives (doesn’t mean I will switch over very soon, but I will definitely keep an eye out and weigh my options before starting a subscription…).

  209. Bad move. I submit that Jetbrains overestimates its position in the marketplace.

    I’m willing to pay for an automatic service subscription fee. Even agree to a 5 year contract. But definitively not for the availability of the development tools.

    This move introduces an inherent business continuity risk not under the control of any company, including my own. If, for whatever reason, Jetbrains services cease to be available (DDOS, Takeover, War, Bankrupticy, or, again a change of “core” business), expensive employees are twiddling their thumbs not being able to do their work and costing a lot of money. Moreover, it is an illusion to suggest that in all circumstances everyone is always online. So, in addition to a structural continuity risk, there is also the incidental continuity risk. Adding up to an unacceptable risk for any development shop. Whether doing in-house development or oursourced consulting.

    I predict that this move bij Jetbrains will spur initiatives in the community to improve other tools or spwan the development of new tools. I’m working more than 30 years in this industry and I’ve seen this happen before. Eclipse is regaining some attractiveness.

    Anyway, I’m sorry to leave Jetbrains, they were a good lot.

  210. Greg Mallett says:

    I switched a long time ago from Eclipse because I loved IntelliJ, and the licensing/pricing was reasonable. But after this announcement, I will be taking a hard look at Eclipse again going forward.

    Normally I upgrade when I need a particular new feature or bug fix. Paying monthly/yearly for the “privilege” of using the software is hard to stomach when it’s exactly the same price as the current perpetual upgrade model. Cut the price in half and maybe I’ll reconsider. As is, you’re going to drive away a lot of your previously happy customers.

  211. Aaron says:

    This is a terrible policy change. My tools will cease to function if there is a snag in the payment process. You are losing a massive amount of customer goodwill here. Whoever made this decision should be run out of your offices.

    My(fairly large) company will be looking to replace our JetBrains products ASAP.

  212. Carsten says:

    I’m glad I bought the 1-year upgrade just a few weeks ago, as I’ll do anything I can to avoid software subscriptions by any vendor. Adobe will never see anything from my money again, and JetBrains has just applied to be treated the same way.

  213. lazarus says:

    how can you complain about € 119 /year? A junior dev makes those money in ONE DAY! Switch back to vim, emacs, notepad++ and watch your productivity plumment

    • For me, its not about the money. Its about business continuity risk: structurally and incidentally (see my original comment)

    • Tobi says:

      I (and most others here) do not complain about the price hike, I don’t care if I have to pay 100, 200 or 300$, because the products are worth it. But it is not acceptable that a tool I use for building a project might stop working some day. With the new subscription this can happen any time, even if I would plan to pay the subscription for the rest of my life.

  214. Thomas says:

    Feel free to offer this as an additional licensing model, but if you are not making this an optional licensing model then you will lose me as a customer.

  215. JC says:

    I’ve spent the last several months working to convince my 15 person development team that we should move to Intellij. We finally have the developers on board and I have to admit that I was excited to switch! However, this licensing change is very frustrating because I know that I won’t be able secure funding without a perpetual license option. There’s no way I’ll be able to justify this to my company, even if your new licensing scheme ends up being cheaper! I think you’d better rethink your plans here because I know my company isn’t the only one that’s going to have an issue with this model.

  216. Thomas says:

    I think everything has been said so just my +1 for I don’t like subscription based software!

  217. Chris W. Rea says:

    You already get my recurring business when I choose/really need to upgrade. Now you want to force it? “Your software will stop working if you don’t continue to pay” is like holding a gun to the head of those who already depend on your software.

    I prefer your licenses and upgrades the way they are, thank you. Too many vendors have moved to this kind of subscription model and it is a serious pain in the ass.

  218. Pingback: Random Links – Sept 4th | Random notes and links of FE Dev

  219. Dino says:

    I used to use Netbeans. 2 years ago I gave PhpStorm a try. After 30 days I gladly paid the $99 license for one year. Sooo much better than Netbeans! It truly is “feature-full” (although I still use NB for anything that is not PHP). After the first year I gladly paid the $49 to keep up with the EAP.

    I’m a FOSS guy at heart. I don’t pirate software and I don’t usually pay for software. But for me, the value and productivity PhpStorm offers is totally worth this price.

    It already felt like PhpStorm was using a subscription model. I’m OK with this change – for now. Especially knowing that Netbeans (or some other opensource IDE) will be there if I become unhappy with JetBrains.

  220. Dave says:

    At work our department have also recently agreed to buy commercial IntelliJ licenses for our team (after my recommendations having been a personal IntelliJ license holder since IntelliJ 10). The internal beaurocracy involved with us switching from a one-off payment to a subscription model, and the risk of losing access to our tools if someone somewhere screws up makes this a very unattractive change. Especially as even if we buy perpetual licenses before November, future new members to the team will be forced onto the new model.

    For the corporate licenses it isn’t about the cost – it is about the risk and it being easier to internally approve a cash payment for the cost of the IDE than it is to commit to a subscription.

    For my personal license, it isn’t attractive either. Changes to IntelliJ are nice, but rarely that important to me, not to the extent that I would want to pay £69 AND destroy my perpetual license for them.

  221. Siarhei says:

    What about about selling major updates at a fixed price (a bit lower then current :) ) and having updates under subscription? That seems more flexible: you do not force us to buy subscriptions (nobody likes them), and we decide on our own, whether to have the updates or not.

  222. Dave Burke says:

    I know I’m merely repeating what many have already said. IntelliJ IDEA rocks and JetBrains deserve every penny of my license fees. I am more than happy to pay and will do so again when v15 is released.

    I am near the end of my 2nd year as a paying IntelliJ IDEA user. I moved to IntelliJ from Eclipse which I liked very much and have no problem using again. If there is to be no option to the monthly subscription I’ll be going back to Eclipse and promoting it on my blog as I now promote IntelliJ in nearly every post with screenshots and process descriptions.

    As much as I like IntelliJ IDEA and JetBrains, leasing the development IDE that I spend all day, every day working in just ain’t gonna happen.

    Thanks for your consideration.

  223. Philipp says:

    The last eclipse release is very interesting.
    Bye bye….

  224. Kevin says:

    There’s only one way to truly talk JetBrains out of this. Do NOT subscribe. They have to see how many customers they are really going to lose. If they only lose 10%, but they have a steady revenue stream, it benefits them. If they lose 50%, it’s gonna hurt. So, make it hurt.

    It’ll hurt us a bit to not upgrade, perhaps, but unless you are using PHP7, or have some weird requirements, I’m pretty sure you could program efficiently with a 2012 copy of PHPStorm.

  225. Delas says:

    I was about to buy Intellij 15 but wont subscribe for any software. Dont know anyone of my colleagues who will subscribe either.

    A deal is based on an agreement by both parties. Guess you will learn it the hard way.

  226. Jose Gomez says:

    This is a welcome change.

  227. Florian says:

    Moving to a subcription-based licensing model with no perpetual license entitlement after a subscription ends is unreasonable, an unacceptable move for me and very disappointing.

    You have lost me as a customer.

    JetBrains was one of the few software vendors that until now seemed to treat its customers well and reasonable. Although there were plenty of other options out there (Eclipse, NetBeans just to name the most obvious ones) I was buying IDEA upgrades since I wanted to support a vendor that was an alternative to other vendors that just got unreasonable in terms of their licensing.

    Now it seems to me that for whatever reason JetBrains joined the crowd of greedy software companies that just want to see my credit card details after 12 months.
    Very sad but I’ll look for alternatives now.

  228. Jaffar Mohamed says:

    I used pirated software when i was a naive sophomore back in college. But after graduating and working with a team of other developers i came to understand the value of supporting good software and the evil of piracy. With this new model, going back to my evil ways is now an option to consider.

  229. Yann Ollivier says:

    Just wanted to add my +1 to the horde of unpleased developers out there, who do not want to be kept as hostages by their main tool. I love IntelliJ, but you crossed the line.
    Subscription = ransom

  230. Keen says:

    I’m really dissapointed to read about this subscription model. I bought CLion in February because that’s the only IDE i really need. I don’t wan’t to rent it, i want to “own” it, as i do now. I planned to renew the licence next year to get still all the newest updates. If i would have bought CLion under the new subscription model that would mean that if i dont buy next February another subscription, i wouldn’t be able to use CLion at all. This really sucks, i won’t parcitipate in this. Especially not as an indie developer.

  231. Kyle Devers says:

    I understand the draw of the subscription model for JetBrains, but it’s disingenuous to claim this is for the user’s benefit. The tagline for this change is “putting you in control of how much you pay” which is ludicrous. Normally I would upgrade every 2-3 versions, based on my own criteria for when it’s worth doing so. Now I *have* to buy an upgrade every year, and worse if I don’t I can’t use the old version. I am no longer in control at all. Claiming the opposite is cynical.

    Just be honest. Say that you feel your product is the best in the world and to maintain a product of this quality you need the recurring revenue that a subscription model provides. I can respect that.

    Time will tell whether your new business model works out. You will keep larger clients, but I see smaller developers abandoning JetBrains in droves over this. But the developers you lose are likely to be the ones that weren’t going to buy many upgrades anyway, so maybe it’s no big deal?

    I’d suggest some kind of free edition though to keep the product in the hands of the little guy. Though insignificant individually, they provide a base of acceptance moving into larger businesses.

    I’ll use my current perpetual IntelliJ license for as long as I can, and then look for alternatives when it’s time to upgrade. I do believe IntelliJ is the best Java IDE on the market today, but I doubt I will be taking your new offer, as the terms don’t work for me.

  232. Pingback: El intento de aplicar el modelo de suscripción a productos de código abierto genera quejas en los usuarios | Planeta Diego

  233. Nikita says:

    To understand the need for a subscription you need to know the financial position of the company (Jetbrains) and the number of paid upgrades. Each year, to introduce something that will buy – it is impossible, it is true. A free work too, no one wants, which is understandable. Adobe just is not afraid to say it openly. You (Jetbrains) must understand that there is no right or wrong decision, once you come to this – so there is good reason, there is no point looking back, it means the current situation is not favorable to you. Do not hesitate to say it

  234. Joe says:

    Dear Jetbrains,
    I’m a (yet) paying IntelliJ Ultimate user since version 7. The original “pay once and own it ” changed to “pay every year to own it” and finally to “pay every year not to own it – but hey, you may rent for almost the same money”. This is ridiculous.
    I have a personal license. Until now I was able to decide whether I upgrade or not, depending on the feature set of the upgrade.

    Seems to me that the sales department is taking over. Constant cash flow is great, I know. But you are really demolishing your reputation.

    I would like to have both options if you can’t resist to offer subscriptions. Either buy a permanent license/upgrade with a year of bugfixes (as before) or choose to buy a subscription license from the start.
    I would like to own things I pay for.

    Best regards,

  235. Emmanuel Julien says:

    Great move as far as I’m concerned. PyCharm + CLion for 79€/year is a steal.

    I don’t mind paying for my software. And I certainly don’t foresee myself being short 79€ while still programming.

    I hope you have excellent metrics to judge the community feedback as you mostly hear negative comments over the internet.

  236. Kim says:

    This is a most unwelcome change and the “toolbox” is a terrible analogy! I certainly don’t want any of the tools in my “toolbox” to suddenly become unavailable! You’re also making this terribly inconvenient for me to get reimbursed by my employer for the licenses I use.

  237. Pingback: The subscription hook | Software development and other animals

  238. Fran_K says:

    I was amazed at the amount of bellyaching and whining I found here, well, if you’ve ever gone to lunch with a bunch of developers and experienced them trying to pretend they don’t know the simple arithmetic need to split a bill, and lord help us when they try to minimize or eliminate their part of a tip. Never have I seen such a tight fisted penny pinching bunch that make so much money! Oh, everything must be free or developers will sufffer!

    I’ve been using IntelliJ since about version 1.6, it was the first decent java IDE and all of JetBrains’ products have been at the forefront of empowering developrs. My power and reach as a developer has been greatly enhanced by their products and I think the current fees are quite modest. I’m going to upgrade my tools every year as long as I use them, so I don’t see any real difference, well, except that since I use multiple tools I get HUGE price break on my annual costs. The cost of JetBrains’ tools are not bad at all, especially when you consider their quality, their constant improvement and what the alternatives are.

    But I’m a professional developer and have been for three decades. If you’re not a pro, and are broke, then use the community editions. If you aspire to be pro, then you need to understand that you have to spend money to better make money. I estimate that JetBrains improves my productivity by 20% or more. To me that’s a great improvement at a low cost. Really, it would be foolish to not take advantage of tools that make you a better developer than those who use lesser quality tools.

    If you’re a pro and are whining, go use the free OSS tool of your choice. I am happy to compete with you in the market and be able to do much more than you because you find such small fees intolerable. My costomers hire me because I get so much done in a short period of time and I know all of their languages and frameworks and have plugins that talk to their ecosystem, thanks for helping me out, JetBrains!

    For those who threaten to leave and never use the tools again, you are not telling them that they are losing a good customer, you are telling them that you aren’t a good customer to have, one who can’t do simple arithmetics, can’t make simple business decisions based on productivity, who doesn’t believe the company is going to last or that it wants to form a good long term relationship with their customers. I believe that the negative concern with perpetual licensing is foolish. Development tools get stale, you need them to adapt to the constant change in the software industry and you aren’t going to be happy with an old version even if this new licensing regime hadn’t appeared. So the demand makes no real sense since the tool becomes useless after a few years no matter what the licensing. If you leave now then for all intents and purposes you have exercised the natural outcome for you perpetual license. If you want timely upgrades, then you are probably already upgrading your license anyway. Really, paying less is bad?

    Would I prefer to pay less and get more and have everything work the same way forever? Sure, who doesn’t, but I understand that JetBrains is trying to keep the business on an even footing, and really, the cost to the customer is improving and is giving them the ability to make better plans and decisions. I want JetBrains to thrive for the rest of my career, so I’m going along with this without hesitation. Are you going to be using one language/tool/system for your 45 year career? Change is hard sometimes, folks, suck it up, that’s the nature of this business!


    • Kevin says:

      Fran, you apparently don’t know what we are bellyaching about. I don’t care about paying less. Visual Studio is thousands of dollars, so PHPStorm is a drop in the bucket. I would happily pay $300 for a permanent license of PHPStorm 9, as long as it’s perpetual, and I would probably upgrade for $300/year as long as the upgrade was also a perpetual license and had something worthwhile that I wanted to upgrade to. What I, and it sounds like many others here, object to is subscription models. Give us an option to purchase a perpetual license…raise the price if you want, but give us the freaking option…that’s what I, and many like me, are saying.

      • Fran_K says:

        I understand the complaints, I am not confused. I just think many are overreacting and complaining as if this were an apocalyptic event. This is fairly trivial in terms of the costs of development tools and in terms of project budgets and capital expenses. And if the plan drives away customers they will modify it, JetBrains is not insane. Again, dev tools get stale, so you are going to upgrade anyway.

        But the childish behavior is what gets to me. The complaints mainly seem to be that some people like to skip releases and delay subscriptions, but when you add up the costs that’s actually more expensive unless you skip upgrades for years. It is emotional more than anything, you will pay more for a perpetual license rather than subscribe at a lower price? For me that means I’ll pay about 1/3 as much since I used a lot of their tools. Plus I’ll keep IntelliJ up to date even though I rarely write java anymore.

        If I were making decisions at JetBrains I would read the complaints as an imperative to continue the perpetual license (hurrah! says the crowd), but double or triple the annual fees for them (on no!, but at least we got what we wanted so we feel better and feel like we won, says the crowd). In a year or two nearly everybody will get over their emotional response and switch to the subscription model anyway since it so much cheaper. Crazy.

        • Fran_K says:

          And if you don’t think this is primarily emotional, just look at the language being used and the number of people that seem to be in a frothy rage. I could see it if the tool cost $20k or some other big fraction of one’s annual salary, but at these levels it just seems so out of proportion.

        • matt says:

          It is primarily emotional, and there’s nothing at all wrong with that. As many people have said — some more eloquently than others — changing to a rental model fundamentally changes your relationship to the tool. Quite often, it changes how you feel about the tool. And how you feel about the tool — your emotion — is significant. It’s especially important for Jetbrains, who relies on developers feeling positively enough about the tool to recommend it to friends. They need to optimize for a positive emotional response from developers just as much or more than they need to optimize index rebuilding or syntax checking. It’s key to their business.
          That’s not childish, is human. We all do it, to varying extents, and there’s nothing wrong with it. When you get to in the morning and open your tool of choice, you should feel happy about it. You’ll do better work, you’ll concentrate better, you’ll enjoy your day more.
          Maybe the subscription model doesn’t trigger any emotional response for you. That’s fine. It obviously does for many many people. But if the license model makes them feel trapped, or like they’re being held hostage, or makes them wonder in the back of their minds if they are really using it enough to renew this month, then Jetbrains has introduced a critical bug in the software that they need to fix.

          • Fran_K says:

            OK, I understand your point a bit more, thanks for elaborating, and I generally agree that they need to tune their operations for this kind of response, and maybe they should have surveyed people first, or sent up some kind of trial balloon, or given the announcement more time. Bad on them.

            But the responses here ARE childish, and yes childish is human, but really? This is what professionals say in pubic? Reread these postings, the cursing and wailing and gnashing of teeth are what one expects from a four year old child. It is like a playground in here: “I’m taking my ball and going home!” “You’re just a poopy head, I hate you forever!” and other silly remarks of that quality.

            Frankly, I don’t think customers like this are all worth keeping. Look how many are saying something that boils down to “I got this excellent tool super cheap and benefit from it and depend on gaming the system to minimize my cost, but oh well it is going away, too bad, I won’t use it anymore. Why can’t good tools be free for me?” Would you want a customer like that? Developers are typically not living at the bottom of the food chain, barely able to eat. This is absurd.

            Imagine you are a product manager at JetBrains reading these remarks. If I were that person my take-away would be that I am not charging enough for perpetual licenses and I would plot a strategy to raise those fees and point people to the lower priced subscriptions so that I can afford to keep building these tools. The market is littered with tool makers who didn’t survive and JetBrains’ strategy has always been quality tools. I’d survey the people that posted here to see how many actually pay for the tools. I’d also be talking to my corporate customers who buy blocks of licenses to see what they think about the cost of things.

            I agree that this was a PR blunder, but who knew they had so many easily irritated customers? But I don’t think it hurts them in the long run. Someone here pointed out that some corporate environments require a perpetual license, and I recall working in places like that. So, again, raise the cost for that if that is a corporate requirement. That seems very reasonable.

            • Nate Spencer says:

              Really?! How many are swearing and throwing fits. I see a lot saying they will not consider doing business with Jetbrains.

              I consider that a reasonable position. Just because you work with big dollar tools. What I would think as I read this that forcing subscriptions should be ended immediately with an apology. If they wish to offer it as an option, I am sure some will take advantage.

              I have seen very little complaints about the price. In fact the prevailing opinion is fine raise the price on a perpetual license, just give us the option.

              And you know what it is emotional esp. for small individual devs. some of them use these other tools to literally feed their families. So as many have stated this purposes a ton of risk to the customer for little to no gain. And your arrogant disregard for these folks opinions calling them easily irritated is appalling.

              We shall see if Jetbrains learns from this or hubris like many before them becomes their downfall.

        • Kevin_N says:

          “dev tools get stale, so you are going to upgrade anyway.”

          Actually, PhpStorm is already supporting PHP7. My current company upgrades with the “default server install,” so that means on CentOS right now, we are stuck with PHP 5.4. It will probably take YEARS before we get to PHP7…and PhpStorm already supports that.

          Over the last 2 years, the primary reason I’ve upgraded is because it’s such a cheap product and it supports JetBrains’ business going forward. I like supporting businesses that help me. However, I don’t recall any new features in the last 2 years that I needed, so if they switch to subscription model, I’m going to just keep using PhpStorm 9 until I work for a company that is using PHP8, which is probably a decade away. At that point–10 years from now–I will reluctantly sign-up for the subscription model if PhpStorm is still the best editor.

    • Nikita says:


    • Fran, I’m not bellyaching. I hope I’m in the minority, but I’m very bad with money. A recent result is that, while I was between jobs for 6 weeks, I lost home access to the Internet, and had to cut all of my subscriptions.

      But I still had ReSharper!

      I’m sure there are a significant number of developers in the world who either might lack Internet access for over a month at a time, or who might lack cash flow for over a month at a time. These are developers who would lose the ability to use their JetBrains product.

      And that might possibly include me!

  239. Blah blahz says:

    I bought a hammer once, and used it till I needed a new one. When the hardware store started selling subscription based hammers, I was thrilled. Not only could I enjoy the benefits of using a hammer to get my jobs done, I could pay for it forever and ever. Even when the hammer got old and new models were inferior, I could just keep on paying.

    Sarcasm aside. Adobe went this route, and after over a decade of being a loyal customer, buying upgrades as I needed on my budget, not theirs, I sought AND found alternative solutions and have never looked back.

    I’m willing to pay continuously for quality, continuously new entertainment. That makes sense to me. I’m not willing to pay for toolset, which I MUST lock down to build products of my own, and manage the cost of production AND maintenance. From my perspective and experience, subscriptions for tools is the last ditch effort to milk the remaining value out of a product line as production is shifted over to maintenance and minuscule feature updates. It’s a slow death with little benefit to the consumer.

    • rosdi says:

      You forgot to mention that you get spanking brand new hammer every year (as long as you keep paying that is), even though the old hammer works just fine and you dont NEED new ones…

  240. Dennis says:

    I Am Disappointed By This New Model, I Dislike It, I Will Not Agree To It.
    Even though i have no problem in renewing perpetual license.

    As many people have already stated:
    The tool must work at it’s current state even if license has expired. No updates after license expiration? Okay. Customer’s decision not to pay, so he does not receive updates. But it MUST work AS IS.

    Trying to get approval for non-corporate-standard software is a pain in the butt… of the one who tries to get that approval. The larger the organisation is, the bigger the pain.
    But for constant renewal model? No way in seven hells.
    How about strict networking rules on what can, and what cannot exit corporate network?
    Or do you really think that sysadmins would love to care for new infrastructure? Or that the security team has nothing else to do, than evaluate potential security risks? Or that the networking team will be happy about new set of rules to implement? And that all of them will be happy to go all round again each time JetBrains updates the “license server”. It is too much effort for an organisation, which is not developer-centric, yet has development teams working on internal projects.
    Speaking of which (the projects). In such a company it is often the project is frozen in some state for quite some time. Therefore there is no valid business reason to continue to pay renewals and receive new features, but the application still has to be supported in one way or another. Perpetual license fits in very well. For example: you have one team supporting current application and another prepping for the new one? You just upgrade those licenses that are needed.

    I propose a slightly different renewal model.
    Monthly subscription? Be it so, however, should the sub be cancelled, the current version of IDE will continue to work indefinitely. There simply won’t be updates.
    If i, say, decide to come back, i will be charged the time difference up to the cost of a new subscription.
    Say, i didn’t use IDE for 3 months? Upon reactivating the license i’d have to pay standard monthly fee + 3 months before it.
    I come back in 6 months? 1 + 6
    I come back in 18 months? I pay 1 + 12 (a year) and nothing more. (as if i actually bought a perpetual standard license given the old model).
    And also add functionality for license key file generation from the customer account page, that can be fed to the IDE (to circumvent the aforementioned corporate network restrictions).
    Does that make sense?

  241. Campus says:

    I really love my IntelliJ and I have been a user/customer since version 3 and I never complained about the price tag for IntelliJ because it’s a smart product worth the money.
    But I will never ever subscribe to a service that will render my environment useless in case I have to stop paying that fee. I also stopped buying Adobe products and never looked back.

  242. Bollof says:

    I would propose a simple approach for directing the development of Jetbrains products: Every time someone pays for a Jetbrains product he also gets a questionaire where he can vote where future development should go to –> Those who pay also decide what they get for their money.

  243. Alex says:

    I agree with all of the above! Photoshop made the move to a subscription based model, and a newcomer that cost 25$ (now 100$) came in and stole their pie.

    Don’t go that way JetBrains, please. Be cool.

    I have to say that I use a lot of languages, mostly python and js, but I do write in ruby, and php, and the benefit of “all the tools are now cheaper together” doesn’t really rise above not being able to use my IDE without internet or having the chance to get locked out (say I’m between jobs)

  244. Norbert says:

    Well, then: good bye, IntelliJ IDEA Ultimate.
    I’m sure, I’ll find a replacement tool – even if it is a little bit worse. I don’t really make money with this tool – just rarely with a very few projects. I also didn’t update every year because of that.
    So, good bye. Also for Adobe I’ve found good replacements that are good enough and even a lot cheaper – and here I’m there are other tools out there that fit my needs. I don’t need the best IDE, the second best will do as well.

  245. Ken says:

    It is like always:

    If the abo model existing parallel to the sold version model, which can be without time-limit used, then it is good.
    But if that abo model replaces the sold version model, then it is bad.

    So, don’t replace the one option with an other one. Offer both options.

  246. Sean says:

    OK, how about you pay per month like you want, or per year, and it’s less than the old purchase price, but you don’t own it. When you want to opt out, you can pay x amount as calculated from a table based on product, amount pai so far, blah, blah, and then you own the software in perpetuity. I thought this up 1 minute ago – I hope this makes sense to at least some of the readers.

  247. Øyvind Matheson Wergeland says:

    My first thought on this announcement (pardon my langauge) was “Are they out of their f***ing minds?!?”.

    This is clearly a decision made by some marketing/sales/financial people. I believe JetBrains completely forgot who their customers are and what they are selling by making this annoucement. Software developers are above average intelligent people. IDEs are not movies or music or television shows that are continuously made available on Netflix, Spotify or Apple Music. Nor do you provide access to resources as file storage, Internet bandwith or virtual machines where we can run your software as a service. In addition. there is no downside for JetBrains with this new licensing scheme at all. Only if you would provide a bug fix guarantee, say for every month after the first you have not fixed a bug that is critical for said user, the monthly fee is waived, a subscription model makes sense to me. If your are not willing to let the payment model go both ways, your are nothing but greedy.

    From a sales perspective, recurring revenue is the wet dream of any bean counter. But I fail completely to see why you should deny your customers perpetual licenses to run your software in a shipped version, installed on our own computers.

    Robert Demmer, you and your colleagues are going to have a long Monday answering all the questions related to this blog post, but I have some more for you:

    1. If JetBrains decides to discontinue any product under the new plan, how will you ensure that subscribers still can use that product?

    2. If JetBrains goes bankrupt, how will you ensure your subscribers can use the products they subscribed for?

    The last question, improbably as it may seem, is actually a real requirement for many organizations when acquiring software.

  248. Richard says:

    If this model goes through I will be forced to stop upgrading my 4 licenses as our bosses do not allow subscriptions, it is why our in house designer is using Adobe CS6 products. I get that this makes it “easy” for some people, but not all of us have management that allow for this type of model. And all of your nice “reasons” don’t mean squat to people that do everything based on policy precedent. We have a no services policy, I can’t change that. Hopefully you have the ability to offer options for those of us that this fails to help.

  249. dataskills says:

    If phpStorm wasn’t the best php IDE hands down I would jump ship today. But they are so I will buy it no matter what, but I HATE the subscription based idea. It would be just another among the thousand monthly leeches on my wallet. Please reconsider.

  250. Richard says:

    I’ve been a loyal IntelliJ evangelist for more than 5 years. I was hooked after I tried version 9. I quickly and unapologetically kicked Eclipse and NetBeans to the curb. Between then and now, I have introduced a dozen or more developers to the intelligence and elegance of IntelliJ. Every one of those IntelliJ converts happily forked over the $200 buy-in and the $100/year renewal year after year. That stops on Nov. 2. Sorry JetBrains. You may be the undisputed champion of the IDE battle, but you are not the only one in town. I plead to you JetBrains, please continue to offer the perpetual license and allow your loyal customers to remain with you.

  251. Pingback: JetBrains switches to subscription model for tools | JAVA

  252. Stefan Lin says:

    WebStorm changes from 29$/year to 79$/year. This is too expensive for me , cos i use WebStorm just for study and personal coding. Please roll back to previous price : )

  253. David says:

    If you proceed with a subscription based license, then you will have less incentive to push yourselves. You will become comfortable with your reliable stream and add more time between major releases. For example, I use Adobe Lightroom, and recently upgraded from 4.x to 6.x, because I didn’t see anything in 5.x that was worth it for me. Oh, and I bought the perpetual license, even though Adobe’s websites tried very hard to trick me into buying the subscription model and hiding the perpetual license.

    I use IntelliJ IDEA for personal development. I don’t need it every day or even every month, so a perpetual license suits me better; and if the next version doesn’t interest me, then I keep using the one I have.

  254. Alex says:

    I fought over a year to get IntelliJ and PHPStorm licenses approved in the company I’m working for. I know already that I won’t get a subscription model approved – and I won’t fight for it again.

    All my colleagues agree that your IDEs are great – but that’s no use for us if our company doesn’t pay for it.

    Like you said, we’ll get updates until our update-period expires, but what happens after that? There are always changes in framework versions, programming languages, … – an outdated IDE won’t support it and is useless.

  255. Oliver Grätz says:

    The statements about the horrid pricing are correct. When wwitching to a subscription based license model then significantly reducing the prices is a must.

    Let’s try the housing analogy: If you buy a flat then it costs more than 100,000 dollars but it’s yours. You still have to pay for renovation (license renewal) but you always get to keep the last version forever. On the other hand, you can rent the flat for less than 1,000 dollars a month and the owner will do some basic repairs, but you need to move out if you stop paying. This is basically the same and it establishes the rules for pricing: If you switch to renting out your software, then drastically drop the prices!

    Let’s see about that with PhpStorm: As an individual developer I pay 99€ for the first year and then 49€ each year for renewal. That means paying 197€ over the course of three years, ob 66€ per year. If I get the existing customer “special price” then I already did pay those 99€ and I still need to pay that same 49€ per year but the license expires if I stop paying thus throwing me back to the “existing customer” version. This reduces the quality of the license while staying at the same price. On the other hand, if I don’t get that discount, then it will be 79€ per year, costing me 237€ over the course of three years. That’s a price increase of 20.3%, which incidentally is slightly above the allowed maximum increase in rent over the course of three years here in Germany.

    What does the current planning mean for me? I will renew my license one last time should a new version of PhpStorm become available before November 2nd. That’s it. You would never see a cent from me again.

    What would be changed to keep the users? First of all, keep the current licensing model as an option. Heck, even bump the renewal a little from 49€ to 59€. If the users feel that the software “is theirs”, then they’ll gladly pay a bit more than for the subscription model. Secondly, the subscription pricing is much too high. The price needs to be cut in half, to something like 19..29€ per year. This would also distinguish it better from the perpetual license model.

    • Oliver Grätz says:

      The “basic repairs” from the housing analogy also fits for those that think that from the moment you get your monthly rent, you will switch from doing serious renovations to being the landlord that just does the absolutely required basic repairs. Now, I don’t subscribe to this opinion, but it is stunning how good the analogy fits this situation.

  256. Ken says:

    To me, it seems similar to leasing vs. buying a vehicle. To some, a lease fits their situation, others finance. The trouble with this model is that there is no buy option. Because of this, you cut out a good portion of the market.

    Why not offer both options and recover the share of the market you are loosing? Including mine.

  257. Michael McCutcheon says:

    I must join the chorus in speaking my disgust at the new subscription model.

    I’ve recently bought IntelliJ 14 and it’s a great IDE. I would probably pay for the update to 15 when that comes out, but not if it is on a subscription model. I simply refuse to support a company that will turn off my software, especially when the free alternatives (Eclipse, Netbeans, etc.) are almost as good, and getting better by the day.

    Whomever is in charge at Jetbrains, let me submit the following: Get everyone in your company to read the book “The Ultimate Question 2.0: How Net Promoter Companies Thrive in a Customer-Driven World” by Fred Reichheld. In that book he describes how most of the best growing companies make their money by delighting their customers to the point that they don’t even have to advertise…their customers do it for them. These customers are called “Promoters”. It also describes how companies that are in decline have customers that hate them, called “Detractors”. These companies make their money by various hidden fees and subscriptions, similar to what you attempting to do. It explains the Net Promoter Score. It explains the difference between good profits vs bad profits, and much more. I recently joined an extremely successful company, and the first thing they made us do was read that book. With the move towards a subscription model, you are about to turn a whole army of JetBrains promoters (happy customers) into an army of detractors (angry customers).

    Please JetBrains, I urge you to continue to offer the perpetual license. If you want to add an additional subscription option, go ahead, but don’t FORCE us into it. You are trying to make more money by annoying your customers, not delighting them.

    If you need to raise prices on WebStorm to align with other products, then do it. But as for the subscription model, please reconsider or you will never get another dime from me.

    Thank you for listening.

    • Michal Capo says:

      I highly agree.

      Dont force customers to do what they dont want to do. Ive got IDEA, RubyMine and Webstorm licences right now.

      But imagine. Im not selling apps to anybody just developing for my company which is out of IT business. The IDEA and RubyMine right now I’m using, is just for maintenance, so I’m very happy to these version I own licences for. Does nt mater that i'm sticky to older version of these products.

      Or another problem. Currently Webstorm is IDE of my interest. Some time ago 10-th version came out, but I was using 9-th due to bugs in the new one.

      Why should I pay every month for something I dont need? Please stay with the perpetual license or let the customers decide what they want.


  258. Not much to add here. You force us to buy we have to search for alternatives. Pricing was really ok but forced subscription just sucks for various reasons. Take xamarin for example, they offer both license types and it’s fine.

  259. Ron says:

    I think the price is fine – it’s the subscription model that I hate.

    The argument that “it allows better budget planning” is simply false. For me, as a freelancer, it is the exact opposite. I have to keep track of each subscription personally, and every new subscription is an additional burden. It might seem like a trivial reason, but imagine having to manage 20 different subscriptions to various services. I haven’t used adobe products in the last couple years for this very reason.

    I would rather pay upfront for my software, so that I don’t have to worry about renewals, and the unexpected effects on my cash flow. The chance that I may not be able to continue a subscription due to cash flow is very real for me. But because the IDE is one of the most essential tools in the kit, so the effects would be worse. With the regular ‘buy and own’ model, I can decide to buy or wait until I can afford it, then have it forever – which takes me to my next point…

    I also like to have the option to continue using the old version of whatever software I buy if I simply cannot afford the updated version – this is very important.

    Please offer an alternative ‘buy and own’ model.

    Thank you

  260. Hongya Cui says:

    I have IDEA, R#, AppCode & Clion, new business model can help me save a lot.
    but I want more discount because I have more than one product.

  261. Gaahh, we only use Intellij and need no python nor .Net platform tools forced upon us.
    Bad move imho..


  262. Konstantin says:

    Sorry to hear that. We purchased 3 licences of webstorm more than a year ago.

    We didnt update, because basically there are no useful updates for us yet. And it seems, that you dont want to add something usefull there. Many bugs including clipboard problems, auto-completion flooding, laggy cmd, high ram and cpu consumption and and ….
    We reported those bugs, which were “known” more then an year ago.

    As a serious software company joining the movement of “subscripe your shoes” is just wrong.

    I guess now, we wont ever update again, better switch to other IDEs.

  263. Mischa says:

    From HN comments. I think this pretty much summarizes my opinion:

    It’s not about the money, it’s about the principle. Poor people rent things. That’s how they stay poor. How would you feel if you woke up one morning and couldn’t go buy some eggs from the supermarket until you joined their club for 100$ a month? You’d go to another supermarket. What if you couldn’t buy a car, only lease one?

    Developers can go nuts if something is against der principles (tabs vs. spaces?)

  264. Greg says:


    I use WebStorm – paying eur 29/year (an offer to current customers) is not that big of a deal to me. Come on guys, are you that cheap? A least jetbrains might finally focus on polishing their software instead flooding us with useless new hip-features that were suppose to make us upgrade to a new version.

    I think all this cry is exaggerated. And it is all caused by the fact that jetbrains IDEs are pretty much irreplaceable – face the truth. Good luck using NetBeans or some editors like Atom/Sublime/whatever. Nobody forces you to upgrade, really.


  265. Sylvain says:

    Using a software I know will stop working unless I keep paying a subscription makes me very uncomfortable. I use IntelliJ mainly as a hobbyist and I think it is important that we have the freedom to decide each year if we want to update to the new version or not.

    Don’t get me wrong, I think the subscription model makes sense in certain areas. I have a subscription to a music streaming service and I can easily go back to listening to non-streaming music or use another service if I cancel my subscription. On the contrary, learning an IDE is a significant investment in time and resources and I believe such a model wouldn’t be good for a lot of developers.

    Thanks for listening,

  266. Peter says:

    Is it possible to get a subscription for an individual if I run company – with me being the only employee – in order to write off the expenses? I need a bill with the company name…

    • Jozef Izso says:

      Nope, you must buy commercial license.

    • v. says:

      yes, you can. personal license means that it allows you to use it whatever way you want, as long as you do it on a single computer at a time.
      commercial licences are more expensive, because companies keep them if e.g. employees leave.

  267. Arnav says:

    I am a software contractor and am not always working for customers throughout the year, during the off times I drastically cut my living costs. Holding off on using the toolset which I use to learn and grow my skillsets during that time is not a pleasant place to be in. Unlike images (as in the case of Adobe) our base toolset changes constantly and I think expecting to stay on IDEA 14 for perpetuity is silly. While staying on a sub might be beneficial to you it only introduces another resource I have to constantly manage and take care of. I have delayed upgrading my annuals many times as I was in my cost cutting mode and just reupped when I had money to spare.

    I know you do not care about the peculiar lifestyle of one customer but by trying to take away my choice you have lost me as a customer and also as an advocate for your product and I felt I had to say that. I know this might end up NOT hurting you in the long run but this is NOT a customer friendly approach. Also, hiding your cost increases to IDEA Ultimate beyond the 1 year existing customer upgrade discount is downright disgusting and deceptive.

    I guess I will have to look at Atom for my JS needs (now that FB is pouring some resources into it) and Eclipse or NetBeans on the Java side. From getting my 99$ every 1.5 years you will have 0$.

  268. macMan says:

    As much as I like phpstorm, this change has left a bad taste in my mouth. I will likely end up looking into another solution unless you revert this plan.

    The vast majority of us do not want a subscription model.

  269. Murray says:

    I guess what is most frustrating for me is that I personally sold our company on the subscription model a couple of years ago because jet brains told me ‘Yes, it costs more for the initial subscription, but in 4 years you will be paying less!’. How many people got to 4 years, didn’t it come out in 2012 on resharper 7? Even if you got the subscription model on day 1, would you be worse off?

    There is even a whitepaper still up stating this:
    “Although the upgrade subscription license purchase requires a higher
    initial investment (comparing to repeat purchases of individual
    upgrades), the investment delivers you a ROI of almost 20% within 4-year
    software usage period. The annual subscription lowers your TCO (Total
    Cost of Ownership) the longer you renew and actively use ReSharper.”

  270. Andre Venter says:

    This is the worst idea Jetbrains have come up with since it started. I won’t support it.

  271. Pitaq says:

    I have a request from one of my engineers sitting on my desk right now. It’s for an Adobe product, and it will continue to sit on my desk because I don’t want to be in a position where I have to continue to pay for a tool during the entire life cycle of a product. It feels too much like ransomware.

    The same applies to other tools we use, including the products from JetBrains. There’s no way on this earth that I’m going to go with a subscription for something we depend on. My first thought is that we will stick with the current versions until the end of our support, and in the meantime look for alternative tools that will do the job.

  272. Caomhain says:

    This is a huge negative for me. As well as being a Java developer I am a photographer who uses Adobe Photoshop and Lightroom in my work. I HAVE NOT UPGRADED EITHER SINCE ADOBE MOVED TO THE SUBSCRIPTION MODEL. If I have a tool that I use for my work I want to own it. I don’t ever want to lose access to that tool for any reason. If I have a project built in Idea and 10 years from now the world has moved on, Idea is no longer the tool of choice, and my “subscription” is lapsed because it’s not used any more; I still want to be able to go back and open up my 10 year old project with my 10 year old copy of Idea. If I can’t do that I need to find another tool to do all of my Java work in. A subscription model introduces a potential for digital bit rot that is unacceptable for professional software. I will never allow myself to depend on such a tool for my work.

  273. By moving to a subscription model, we as consumer have no way to influence improvements to the products we are using. It can be easier for you, because it will remove the requirement to inovate and improve the product “it’s good enough, if you want to keep using, keep paying”.

    On the otherside, by having to do a better job or else no one will renew licenses, you are constantly having to reinvent yourselves. This puts you out of your confort zone, and forces you to create a better product.

    While I understand that a small subset of your clients will benefit from having access to multiple products, please, make subscription optional.

  274. Lucie Zahorikova says:

    Sorry to hear that, you’re losing me.
    I subscribe for services, not licences.
    I perpetually pay for phone bills, music and books I don’t need to own.
    I pay only once for things that I need to keep, that’s not a thing I’m going to change.
    It’s like buying a small house and losing it after I refuse to buy a the same one with a turret on it.

  275. Eval User says:

    This licensing model could arguably be palatable if bugs & features this very same community deemed ‘important’ weren’t argued with, allowed to fester unattended — sometimes for years — or completely ignored.

    You want subscribers to your company & its products? Show us a product roadmap with dates. Make commitment on features & bug fixes. STOP deflecting “it’s up each developer to decide if & when” something gets fixed or implemented. Oh, and Newsflash: “There is only one JetBrains” as an official response to why you’re NOT making big bugs/features a priority doesn’t cut it.

    Without that commitment and demonstration that you’ll actually do it, rather than talk about, being held-hostage by subscription just to keep the un-upgraded/un-fixed software you’ve already invested in is a non-starter.

    With a perpetual license model, when JetBrains stops delivering, I can choose not to pay anymore & walk away, keep what I’ve already paid for, and end up remaining productive at a level current at that point in time. With a subscription model, I’d simply end up being a chump — with no functional software and less money.

    Eclipse is suddenly VERY much back on the radar. Not simply because of this subscription model, but because of the tone-deafness that leads to it, and the lack of performance to justify it.

    Your argument that ‘by doing this, we’ll be able to focus more on quality’ is specious. Try focusing on quality FIRST for a year to demonstrate that you’re going to “walk the talk”, then have this conversation.

    • Mark A says:

      A very articulate blog post. I have enjoyed the irony of people saying “I love this product and want to use it, but I can’t take the risk of it stopping working so I off to free tool X”. The fact that you can do that makes the point irrelevant doesn’t it; enjoy (and pay for) the tool you like now and then make that move when, or if, you need to.

      Subscription pricing is a rising thing, and JetBrains are facing competition from the cloud delivered IDE providers and they have to respond to that.

      The one issue I can see is for staff of organisations that have a “no subscriptions” policy, but it would be worth asking the finance department if they might be doing their CRM via SalesForce or getting financial info from D&B. In reality organisations are paying subscriptions and if they are telling Devs they can’t have the tools they want when they don’t tell the same thing to Sales and/or Finance then maybe it is their attitude to the Dev team that is the problem!

    • Piskvor says:

      Articulate, yet attacking a straw man. “If you don’t want to pay for software anymore, fine. Just don’t be surprised when no one else does, either.” If you look very, very closely at what Jetbrains does…its products are already for-pay, and have been for some time!

      The issue is elsewhere: it lies with the assumption “the whole world is connected, always will be, the licensing server will run flawlessly forever, and the sales department won’t ever come up with Another Special Idea.” I’ve been paying for the upgrades, indeed – in the knowledge that it’s me who’s in control; and that even if anything happens *after* I purchase a license, the tools will still work. The new scheme has me trusting that current JB __and all its future versions__ will be kind enough to let me use the tools I’m paying for. This introduces a brand new element of risk, one with which I’m not very comfortable, as it amounts to “we will Do No Evil (because see how well it worked for the-company-that-shall-not-be-named), and you have no choice but to trust us.” This is the real issue: a subscription places me at the mercy of JB’s sales team, whereas the previous scheme gave *me* the final say over my tools. I understand the rationale for this power grab, but I intensely dislike it.

      TL;DR: Cost is not the issue – previous arrangement always had the contingency “at least the older version will continue working if things go south;” this is no longer the case.

  276. gerrit says:

    Seriously when this is going live i will immediatly switch back to eclipse or netbeans. Been using ruby mine and idea for many years now and only had good words for this company but this is too much the obvious attemp too max out the amount of money and forcing me to pay even if an older version would suit me well just makes me so angry!11!!

  277. Peter says:

    Whis is this licensing model you will make your product too expensive / inadequate for most users I could think of:

    – a lot(!) of companies do not accept that software stops working once you stop paying (even if just for a while)
    – freelancers that switch focus based on the project will get back to eclipse (otherwise they pay all the time though they need your software only partially)
    – hobbyist will not buy it at all (too expensive for using it once in a while)
    – people feel betrayed since you remove the perpetual license (enforcing payment is not exactly how you create sympathy)

    Personally I will not recommend your product anymore (though it is excellent) due to the new license shackles.

  278. @Peter, it is not about the subscription fee. For me as a professional developer Intellij is its price more than worth. But gripe is with the risk of an essential tool not being available. In the proposed subscription model I’ll be exposed to two kinds of continuity risks not under my control (see my original response).
    With a perpetual license I’ve can mitigate some of these continuity risk.

    If Jetbrains needs more money to continue development and maintenance, raise the price. No problem there.

  279. Pingback: What Microsoft Got Right That JetBrains Didn’t – Dmitry Leskov

  280. Ivan Kharlamov says:

    Been using and advocating your software since 2010. Sad to hear this. Will consider stopping subscribing to your products.

    The concerns were brilliantly summed up by previous posters: poisoned by success, your company management is loosening the feedback loop between user satisfaction and revenue stream. From now on, things will inevitably become worse. Economics/Management 101

  281. Eval User says:

    The ‘phone home’ regularly aspect just dawned on me.

    Um, no. Just , no.

    Apart from the general fact that I’ve had quite enough of home-calling *phone* apps refusing to operate when I’m on an airplane or out in the boondocks, NO *desktop* app anywhere on my LAN gets to decide to poke through the firewall and send/reply “licensing” / usage data when & where it wants and then — if it can’t — throws a hissy, shutting down my ability to work.

  282. Stefan Gross says:

    Sorry to hear about this move, which seems not to be a clever one.

    As a guy using and of course updating IntelliJ and AppCode for some years,
    it is absolutely no idea to pay for software that stops working. Be it due to missing
    internet connection or end of subscription.
    It is ridiculous trying to sell this as “having more control”.

    And the price is the same as before for perpetual license upgrades.

    I supported AppCode, although it does not develop with the same pace as Xcode.
    And AppCode is a pretty good example.
    Regarding new features demanded by customers: I do not believe anybody asked for an alternative UI designer as a replacement for Xcode. If you really would listen to the customer’s voice here, you would have stayed focussed and improved Swift support, refactoring and so on,

    Yes, I haven’t updated my Resharper license for a while, since I have no .Net projects right now. But fiddeling around with some 1 month Resharper, then 4 months IntelliJ is not an option.
    The price tag is absolutely ok, but the “stop working” after subscription expiration is a no go and killer.

    I do really hope, you’ll keep the perpetual option, otherwise I have to switch back to Eclipse. For JScript the free Visual Studio Versions are an option as well for sure.

    Good Luck!

  283. Stefan Gross says:

    Interestingly enough, there is no option anymore to extend the support.
    So, if nothing changes my current update support will end January 2016 if you do not decide to change your approach.

    Not to mention, that a 50% maintenance fee, we all were willing to pay in the past, is an absolutely exception in for normal SW licenses. Even Oracle and other enterprise vendors will charge no more than 20%.

  284. Ricardo de Luna says:

    Being a loyal customer means I choose your product, not that I’m forced to use them. Being able to open an old version in an offline laptop, importing my settings, and to fix an old project is priceless for me.

    additionally, I choose when to upgrade (even If I have to pay all the versions I skipped, as the current pricing model does).

    if this goes in effect, This will be the last year I renew.

    • Joe C. says:

      I don’t see anywhere in their statement that forces you to upgrade or requires you to abandon a previous version. If that is a fact, then I could understand the frustration, but to date JetBrains hasn’t indicated that.
      Adobe doesn’t force me to upgrade and allows previous versions to exist side by side. They continue offer the CS6 versions for download to CC customers. A lot of misleading and unsupported statements are being thrown around here.

      • Tim hawkins says:

        That is exactly what they are saying and the reason why everybody is so upset. On the subscription model, if you decide to stop paying then you ide stops working in its next phone home. So even if jetbrains decides to stop enhancing the product, or they put the prices up, you either accept it, keep paying the alimoney, or you loose your IDE in the divorce.

        • Joe C. says:

          That’s not what I said. I said they haven’t indicated if they will allow you to keep an older version and use it at the same time the way Adobe does.

          I think it’s fair to ask them to put some assurances in place (legally binding ones) so if they go out of business existing customers will be protected.

          On the Windows side of things, there are less expensive and better tools out there already (at least for C++, javascript and python). I don’t think C# developers will tolerate a subscription model for Resharper for long either. Only until MS comes out with a free alternative.

          Someone mentioned Xamarin? Not doing too well either, since they want from 799 to over 1500 a year for their full package over and above what you pay for a MSDN subscription. It’s going over like a lead balloon. When Apple releases Swift to open source, There won’t be any reason at all to use them.

          I went to another, much less expensive alternative for IOS and Android development.

          One bright spot? Embarcadero of all companies (formerly Borland). They offer Rad Studio XE8 with multi-platform support for about 2 grand (less for Windows only) and then upgrades and support offered with a yearly maint plan (last I checked about 300 a year). If you cancel your maint plan, you can still use your tools. They way it should be. Like MS, they have more expensive enterprise level stuff too.

          • Joe, they have indicated that they will not allow you to keep an older version. The only exception to that rule is if you buy a license before November 2, 2015.

            If you buy a license after November 2, 2015, and then stop paying for the subscription, then your product will stop working.

  285. Adrian Green says:

    No mention anywhere about the hassle of having to process yet another ‘bill’ every month. I’m just 1 guy. Very, very busy.

    Will there be an automated payment system so we set-and-forget? Will it be credit-card only? (I don’t use/want/have a CC so alternate payment options are essential).

  286. Adrian B says:

    We had just started the process of considering the switch to IntelliJ at my workplace. I will say that the change to the subscription model will make it harder to convince management that the switch is a good idea. While the initial price may be lower or comparable, we’ve had a number of other subscription products where the vendor jacked the cost of the subscription after a few years. Have you considered allowing perpetual licenses at a higher cost? I could see a higher cost perpetual license being an easier sell to management.

  287. Christopher Kim says:

    After reading the other comments and reading the FAQ, I don’t think the subscription model is a bad idea. The subscription model is indeed more expensive than the current price structure –so I am a little sad — but at the same time, it’s not like the economics of running a business remain unchanged. Costs increase and so the price eventually has to increase — this is life. Also, the current JetBrains IDE offerings are still a lot cheaper than Visual Studio — even though the subscription model became a little more expensive, it still retains a lot of value.

    I remain a fan of JetBrains and I will continue to support them. I have been using the free version of PyCharm for a long while and I am very grateful for this, so I’m also happy to read that JetBrains will be continuing the community edition. Since there is a limited window of opportunity to get cheaper subscription pricing, I now have to make my purchase earlier than I thought, but this is not a big deal for me.

    I will admit though that my first reaction to the subscription pricing wasn’t pleasant as I view subscription models in general to be lower in value (the point made by other commenters about the loss of service once monthly payments stop is the main reason why I view subscription models as lower in value). Then I became more annoyed once I realized that the subscription pricing is also more expensive than the current pricing model.

    However, JetBrains has always been a great company in the past so, in my mind, they definitely deserve the benefit of the doubt. It’s honestly hard for me to really view JetBrains as a greedy company that only cares about the bottom line. They make great products and they have supported Linux from the start. We need more companies like this, not less.

    I do have a few questions though:
    1) Assuming I am on the subscription model for PyCharm and I know that I will be needing the CLion IDE later for a different project, am I allowed to switch my license from PyCharm to CLion for some time (so that I am locked to only using CLion during the subscribed months)? Or will I need the Toolbox subscription at that point?

    2) Let’s say I take advantage of the cheaper PyCharm subscription price because I had purchased a license from the older pricing structure. If, after a year, I decide that I would need to get the Toolbox subscription, would I be eligible for the discounted price of that as well?

    3) How long will the discounted subscription pricing last for users who have opted to convert their perpetual license to a subscription license?

    4) Will CLion ever officially support Arduino?


  288. Ed says:

    Eclipse, darling. I’m sorry I dumped you last year. Can we start over again? Yeah, yeah, I know, I know, but this IDEA turned out to be just a greedy gold digger and a control freak.

  289. Pingback: Introducing JetBrains Toolbox, easier access to your coding tools, more control and flexibility, and a lower entry price | JetBrains Company Blog | Webentwicklung

  290. StrDev says:

    For any permanent users this scheme is beneficial.

    Non-permanent users will actually migrate to other IDEs (like Visual Studio) and it will harm the reputation of Jetbrains IDEs.

    Like e.g. Dreamweaver, which has always been the #1 IDE for web development, but after having introduced the monthly subscription scheme, its reputation is dissolving.

  291. Rod Thomason says:

    Starting November 2, 2015, we will switch back to Eclipse.

  292. Marcus says:

    I work for a large financial services organisation in the UK. Our internal procurement processes cannot handle this sort of subscription based service reliably for a small vendor like JetBrains. With this change in licensing you have effectively moved your software to “sell” on our “buy/hold/sell” list.

  293. carmack says:

    I don’t mind paying to keep the right to updates.

    And it seems, that’s all you really want — pay for updates. The price point is debatable, and you’ll learn over time what the market really will tolerate.

    What you seem to want is for people to pay for updates and get entrained into some kind of ecosystem-loyalty thing, but what you implemented is software as a service — that’s fine for services, but not for tools. People make investments in tools that go way beyond money, and they aren’t going to make those kinds of investments for something that will stop working just because they don’t have an internet connection, or because they’re short on the rent for a couple months. Unreliable tools are generally dirt-cheap, quality tools cost you, but last a lifetime.

    The plan you’ve deployed is pretty risky for users, it does not incentivize investment. I for one will be dusting off my Eclipse skills and refreshing my knowledge of that ecosystem before I make any decisions. I just can’t tolerate the idea that if my tools can’t reach you, they will stop working – that is so…. 1990, where’s my license floppy?.

    What’s strange is, I think you could achieve what appear to be the most important of your goals here without creating risk for users and dis-incentivizing skills investment in your tools:

    1. For someone who isn’t subscribed, or maybe hasn’t been subscribed for a while, there’s a “startup fee” for the subscription. Perhaps the penalty for lapses scales with the duration of the lapse. This incentivizes continuous subscription.
    2. Then there’s a charge per period for updates like you’ve adopted, where you incentivize longer duration subscriptions with price discounting.
    3. Maybe long-time continuous subscribers earn some perks. Make it a game, it works for hotels and airlines.
    4. You validate the subscription as part of attempts to get updates, but not for any other reason. Failure means no update, but not failure to function. (i.e., the license we have is perpetual for the last thing we legally acquired through the update system).

    And this solves most of the community’s concerns (other than price)

    1. I can be on a submarine or the international space station for 5 months and not have the software stop working.
    2. A lapse in subscription doesn’t mean the lights go out, it means I’m taking a risk and not getting new features and fixes.
    3. The ware isn’t being creepy or inconvenient, its just enforcing a pricing scheme for new bytes when I ask for them.
    5. The time and energy I spent learning your tools aren’t just a waste of time and energy.
    6. I can balance my technical risk and cost.

    Ultimately, you are making a value proposition that is weaker than the one you had before, and is weaker than it has to be, even under what appear to be some new objectives for your licensing model. I don’t think you intended to diminish your value proposition, but that’s what this plan does.

  294. jay says:

    here is what the competition does:

    Can I continue to use the products contained within a subscription if the subscription expires and I choose not to renew?

    Absolutely. You can continue to use products which you have licensed and paid for…as long as you require. When a subscription expires, it simply means that you will no longer be issued any product updates or new product releases.

    Is it that hard to do that?

    • dave says:

      Yes. Yes it is. Because that’s the current setup, and Jetbrains doesn’t want to do that anymore.

      Evidently, it’s too hard to come up with enough new features each year to get people to re-up their subscription, so they want to switch to having you pay to continue using the the ide regardless of what they do.

      Of course, they promise to continue to update the ide just like before, only without all that pressure to ship.


      • Jozef Izso says:

        So what will they ship if not under pressure to ship anything?

        People will pay for the *promise* there will be “some” updates?

      • Tuba Libre says:

        New features are one reason to upgrade. Other reasons are compatibility and integration into newer OS versions, with new tools etc. pp. which is not exactly new feature stuff, but product maintenance. Also fixing those bugs is a reason to upgrade. Performance improvements are reasons to upgrade.

        And if you read through the text above you can easily see that nothing will change for JetBrains, because they still have to do this otherwise customers are even more unsatisfied to pay “JetBrains Taxes” for a product that brings no new innovations.

        They might think if they have the customers on the needle that they have no choice – but actually they have. In the simplest case they can just use the existing licenses as long as possible and that will really hurt to JetBrains because lost reputation and image is very expensive to repair.

        JetBrains should think twice.

  295. Denis Shulepov says:

    This is a huge disappointment!
    Previously we had to pay around 100 to upgrade our ReSharper ones a year, now we’ll have to pay 200+ each year just to use it. And don’t tell me about a special price for the first year for existing customers – it’s just a sweet candy before you take away the toy.
    If you’ll apply this, you’ll be loosing customers in packs!

  296. Dmitry Svetlakov says:

    Nice. You are not just remove perpetual license, you’re also increase price. Last year I’ve paid for Idea $99, now next year will cost $89 for me, and after that I should pay 1.5x higher price ($149/year). It’s awful and absolutely not user friendly. Worst thing there for me is there is no good alternative to Idea in my case, it’s like pay more or leave. Very, very disappointing.
    Usually I’ve tried to convince my colleagues to start using your products and pay for them, but now I’ll stop these attempts.

  297. Not a JetBrains official says:

    Dear JetBrains FANS.

    We know you all love deadlines, so we’ve decided to present you with a special one.

    You have 2 months to let go all your bad feelings about your favorite toys being taken away from you.

    What we’ll do now will hurt you a bit in the beginning, but it’s only until you let it go completely.

    There’ll be a little scar in our relationship, but it’ll move you out of your comfort zone, so you’ll eventually get better out of it.

    After a while you’ll start seeing the options that what our effort had opened for you.

    Best regards
    Not a JetBrains official

  298. Thomas Due says:

    I think it is a great idea to move to monthly payments. I cannot see any advantages for your customers in the new license model though.
    I can understand the license model for something like Youtrack Incloud, or other cloud-based services.
    But it simply does not work for tools. I have never in the 15 years I have worked professional seen a license model that required me keep paying in order to use a tool.
    Pay to upgrade yes, pay to use after initial purchase, never.

  299. Piskvor says:

    Good morning.

    I’ve been a happy JB product user for years now, recommending them everywhere, and due to that we have been planning a companywide multilicence (“ooh, nice tools; let’s get them for everyone”). A subscription model is not viable here for a simple reason: power tools being dependent on your goodwill is a no-go; we cannot afford a companywide outage if to everyone’s tools stop functioning. Yes, I’m aware that as long as the subscription is paid, your servers are up and each workstation can connect to it, everything would work as usual; alas, this introduces too many risks and assumptions for the new scheme to be acceptable.

    Pricing is not an issue (IMHO the current pricing is very developer-friendly), nor is the current upgrade cycle; it is the threat of your remote killswitch that is troubling. I’m trying to defend against the usual questions – “so this will be unusable for longer-term offline use?” “what if their servers – or even the company – goes under?” and “what if they decide that the price goes up 10x next month?” but I don’t see any good answers to this.

    Under the current model, the power to use properly licensed tools would have been in our hands; in a subscription, we would be completely at the mercy of your sales team, lest our existing tools stop working. Getting the rug pulled from under our feet – or even a threat of this – is simply an unacceptable risk for us.

    (As for me, I would just be sad, buy the last version without the killswitch for my personal use, and not enroll into your timebombed model. I appreciate your blog update, and I hope for an eventual resolution which would allow me to continue using your great tools.)

  300. Brice says:

    Not happy with this news, while this kind of license may be interesting to some, a lot of people including me do not update every year, b/c not everyone can/will/want to spend each year more (+VAT) than 200€.

  301. Neki Tip says:

    I have a line of code you can add to your customer management application. You can write it in your fancy new rented app:

    customerCount —

    I have IntelliJ and will leave it at that. Great IDE. Really. Thanks for making it. Will not be upgrading it.

    Not so much for the price hike (which is ridiculous) but because of the blackmail which this purchasing model implies. I will not tie all my projects and workflows in a service. I will bundle it with a product. I can manage a product and I have guarantee that it will work years from now. Time to switch.

    There is plenty of fish in this sea. And more will be coming. Adobe’s short sighted renting move spawned Sketch, I am really looking forward to see what will this one bring.

  302. Sergey Podgurskiy says:

    Bad bad bad news.
    It looks like subscription model is flowing in the air over all world.

    You’ve build amazing IDE.
    And this is the most useful application in my toolbox.

    But this is a terrible idea. When I pay money for something I’d like to own it.
    When I buy bricks to build a house, I don’t want to wait when I’ll be asked to give them back.
    My working day can’t be dependent on availability of your license servers. I can’t take a risk that someday you will change subscription model.

    Sad to say, but I’m willing to receive latest allowed updates and will never upgrade.

  303. Gast says:

    This is sad, but this is evidence is that the manager in this bussines are too greedy and everyone are liars. All what they are thinking is belong to the provit and how o get the money from all of us. Shame on u, if u continue this way, i will never go with u and never renew my license next year. I send a big FY to u!!!!!!! And wish u all the worst ever!!!

    PS: That how to destroy a company and get a big bonus and then leave to destroy the next company to get the next bonus. mmmm I studied the wrong subject. xD

  304. Jeff Alvidrez says:

    I’ve been using IDEA since … version 2? I can’t remember. A long time. Since then I have at different times purchased and used many of the JetBrains products.

    During all the intervening years, I have believed the productivity argument that good tools often pay for themselves, and JetBrains tools (most of the time) meet the definition of “good” or even “best” tools. I have debated long and hard with Eclipse fans — and users of Emacs, vi, you name it — and gotten companies I’ve consulted for over the years to buy licenses for whole teams. I have done this not out of any particular favor for JetBrains, but because it is the best thing for my clients.

    The debates with this subscription model that focus on pricing miss the point. The pricing can always be tweaked, and we can assume that JetBrains will do so to maximize their income from these products, which (we hope, but I think likely) also means maximizing the number of people willing to pay. If the prices are too high, that will work itself out. And whether or not this represents a price increase is immaterial; prices could just as easily go up within the existing license model.

    The deeper issue here is productivity, and risks to it. Those debates about tools I’ve been through over the years have taught me how much inertia a development toolchain represents; getting people to change to IDEA and other JetBrains IDEs has never been a quick chat followed by a purchase, but rather a conversation that unfolded over several months: showing staff developers the tools, getting them over the humps that one faces with any new tool as well as the quirky ones specific to the JetBrains tools, and ultimately proving to them that the productivity boost is real and worth the investment, not just in licensing cost, but in developer time taken away from progress toward project goals.

    The fact is that the cost of changing high-touch tools like IDEs is almost never small at team scale, and resistance to change comes from the foreknowledge that getting *out* of an untried IDE that ultimately doesn’t work out will be tough, particularly mid-project, and a significant hit to the timeline. In other words, there is already a bit of feeling held hostage to this class of product, at least for managers of teams. Free tools are (mostly) of lower quality, but they are inert, and not actively exploiting this already uncomfortable position of the development team.

    Under the perpetual license model, to a customer it does not feel any more like active exploitation; it just feels like you’re paying more for a higher quality product. If the quality is not there, you don’t buy — simple.

    I understand that behind the scenes there is a dynamic where in order to ensure renewals you (JetBrains) end up batching improvements and new features, but this doesn’t risk customer access to already purchased features. If it was good enough when the developer customers evaluated it, that will only change over time if the customer requirements change. The decision can be made at a point in time, for a known cost, and both the price and the value received are constant from that point.

    With the subscription/service model, that goes out the window. Now, the ground can shift under us while our projects are in flight. While we’re focused acutely on delivering, we now have to start thinking about: do I need to renew? When? Sure, the software starts to warn us if we forget, but is that early enough to get the next purchase through the potentially byzantine requisition process? And, how long will that process take *this* time? What if the price goes up? What if the bean counters say no this time around?

    And even if we plan for it, I’ve consulted for companies of all sizes, and I’ve never seen a company of any size with a purchasing process to which I would trust key elements of the team’s ability to deliver my project. And forget about setting up a recurring purchase; the companies capable of such things invariably require all kinds of support arrangements and price guarantees, more than a dev manager can afford to worry about.

    But to that point, more generally: business arrangements regarding critical functions usually involve contracts with mutual assurances. This licensing model does not, as far as I can see, make any guarantees regarding the future delivery of services. Yes, your licensing servers may crash at a critical moment, or you may go out of business, or you may simply decide that it is time to raise prices by some significant multiple. You can give assurances that these things will not happen, and perhaps many developers will believe you; but I have encountered few legal departments or executives who would be comfortable with such assurances. Are you prepared to enter into binding contracts with every corporate customer? And even if you are, many will not want to take on *your* business risk on top of theirs.

    And when you pile these risks on top of the already present feeling of being stuck with your IDE choice, at least for the duration of work in progress, I hope you can see why people are using phrases like “held hostage”. It feels an awful lot like maneuvering customers into an even weaker bargaining position, for a benefit that seems to apply only to customers licensing many of your products per seat.

    To some extent it doesn’t matter how you break down the different license options, with annual/monthly/hourly and kitchen-sink/a la carte; the fact is that having the risk of one’s most precious development tool ceasing to work hanging over one’s development effort is a non-starter. Even if it is of lower quality, a tool that a team manager doesn’t need to worry about *during* a project is the one many will choose, because they simply already have too much to think about. Team velocity is hard to increase, but by comparison easy to manage for; changing tools mid project is the kind of thing that is impossible to estimate, and really can’t be managed.

    I would assume you have done some research about this before announcing this model, but perhaps the sampling of customers you surveyed was skewed toward some characteristics for which this model works. I’m sure they’re out there, but I know they aren’t my clients. Judging by the feedback, there are clearly very many for whom it will not.

    Maybe the ones in favor of this model are numerous enough, despite their thin representation here, to sustain your business, in which case, good luck, but we must now part ways. But if not, then there must be another way to solve whatever problem you guys think this solves, including raising prices if you must. At least then there is still a conversation to be had about cost/benefit, and honestly, among my clients the price has rarely been an issue — your products have been generally reasonably priced, and within the reach of a productivity justification. But the risk issue trumps price concerns handily; I think you could charge only $5/seat/year, and it would still be a non-starter because it puts business continuity at perpetual risk.

    To be clear: IDEs are not like other development tools or other technologies like database engines. Developers *live* in their development environments.

    To take the metaphor further — this change is saying to the customer: we’ve been selling you apartments for a one time fee, and once every year or so you have been able to buy a new one from us for a discount, if you like, or you could just continue living in the old one, though it gradually falls out of date with current standards of living.

    But now, we have a better deal! Move into our new apartments, but instead of having to worry about *buying* them, you can just rent! And we’ll maintain them while you live in them, for as long as you live in them! It works out to be roughly the same cost as before, though some people will pay more or less than now, and the apartments are basically the same ones we’ve been selling you outright … but we hope this arrangement will make it possible to improve the quality of the apartments!

    But in the fine print, we see that if we fail to make a rent payment, we have 30 days, and then we are automatically dumped, with all our stuff, on the street. And that the automatic dump mechanism is wired to a deadman switch, so if the landlord (JetBrains) disappears, *everyone* gets evicted, and the apartments will just stand empty.

    Would anyone *want* to live in such conditions? Would anyone except the most risk-tolerant find this to be a good deal, when there is an endless supply of not terribly comfortable but completely and perpetually free apartments around the corner?

  305. Tuba Libre says:

    A good marketing team always find reasons why making customers to paying slaves is a good thing, it actually is the most worse decision JetBrains could make with an eye on image and user satisfaction.

    I’m one of the developers purchased the earliest versions of ReSharper and i recommended the product to dozens of developers and colleagues during the past years. I’m now a satisfied user of IntelliJ too. And yes, i normally purchase the updates every year because they give me not only new features, which is fine, but also from time to time they fix the annoyances and bugs.

    But i am very disappointed and disgusted about the change to a monthly or yearly subscription that forces me to pay. An that’s what happens after the change. It is not longer possible to skip a version or to drop paid update subscriptions and simply use what you have.

    It’s like the thing Adobe does and for what i really hate this Company. But at the end there’s still a difference… While there is no serious alternative to Photoshop, Illustrator or Fireworks, there are alternatives to IntelliJ and all the other tools – also to ReSharper, dotPeak & Co. And these alternatives get stronger.

    While it still might be hard and inconvenient to switch to another product, which always means that one has to learn new shortcuts, new menus, changed behavior and – of course – missing features, it is one of the things a customer can do if a company ignores him. At least it is a statement that this practice is a bad practice.

    If it is true, that most customers pay for upgrades, than it is obvious that there’s no need to change the licensing model. So the reason is different and i would bet that it is simply the greed for more money and attempt the user to hang on the needle and push fully in a future dependency. And this is something i cannot accept, i do not want to accept and i don’t want to support.

    Good chance that i’m alone or that i’m hypersensitive. But i hate Adobe for its licensing model and i hate other companies who try the same because they think they are monopolist and customers must accept or they are out of business.

    But at the end of the day i hope there are more customers who are disappointed and i hope that JetBrains thinks twice before implementing this. If not i’ll have a hard time – but i’ll try to use my existing versions as long as possible before i switch.

    • dave says:

      No, you aren’t alone.

      Of the 1000+ messages on these two posts by Jetbrains, it looks like 90+% of them are against switching to renting Jetbrains software. The only ones that seem to be for it are the ones that use a bunch of tools, which Jetbrains is offering a very substantial discount to access [but still renting].

      I am definitely not switching to renting.

      We’ll see how Jetbrains responds.

  306. Cédric Eberhardt says:

    This is exactly why I quit Adobe and Office. And I’ve found better products.

  307. Thomas A. Anderson says:

    A little different question regarding the current-customer price reduction. I brought a IntelliJ IDEA Ultimate license because I wanted access to the different language plugins, but specialized IDEs are always better.

    I was wondering if we Intellij IDEA Ultimate license holders will get current-customer price reduction on all IDEs with functionality accessible in IntelliJ IDEA U? I would prefer to use PyCharm to a project using primary python, Clion to a project using C/C++ and so on. It’s not more features I’m asking about, it’s a more customized experience that I already “paid” for and it should not inflict extra costs for you.

    • Thomas A. Anderson says:

      I would also like to add that I would gladly pay the IntelliJ IDEA Ultimate fee yearly if I got access to the other IDEs with plugins for IDEA. Like paying for IntelliJ, but using the other IDEs you are offering.

  308. Pingback: JetBrains ToolBox: 9 Things it Means for You | Voxxed

  309. Dino says:

    I fully understand and appreciate the displeasure I hear from fellow users. What I’m hearing is mostly about the principle, not the cost. Especially the phone-home aspect (it concerns me also.) But these are commercial IDEs – not freeware. Don’t you all write off software cost as a business expense anyways? Do you use anything like Quicken or an accountant to do your taxes? It’s a yearly expense as well – neither will do the job year-after-year for a one-time fee. Just something to think about.

    • Mike Jacobs says:

      That’s not really an apt comparison. You can still use Quicken 98 to figure out your finances, assuming you still have a computer that’ll run that old version. You didn’t suddenly lose access to it just because you didn’t pay for Quicken 99. You’d miss out on new features, but you’d still have the software you paid for back in 1998.

      And it’s really not about price at all. I was perfectly happy to buy Adobe’s Creative Suite for as long as they offered perpetual licenses, and that was easily ten times the cost of a Jetbrains IDE. The second they switched to subscription, I stopped upgrading and stuck with my existing version. I didn’t want to pay the $600/yr and then have nothing to show for it if I decided not to subscribe in a couple years.

      That’s really what this is about. I don’t want to lose access to a tool just because I don’t see any value in the latest version of it. Jetbrains themselves call this Toolbox. Well, you should be able to buy a tool, throw it in your toolbox, forget about it for two years, and then take it out and dust it off when you need it again. Obviously you can buy a new one if there are new features you like, but the one you threw in your toolbox two years ago should still do what it did back then.

      In the end, the people this hurts most is the hobbyists who like professional-grade software but don’t actually need it. These are the people that try out new stuff and recommend it to the companies they work for and other people they know in the industry, and burning them is a sure way to lose business.

      • Dino says:

        Thanks Mike. You kind of reiterated what I was saying. It’s the principle, not the price. And people like myself, who paid for PhpStorm 8 and/or 9, we will still be able to use it under the existing model for years to come – or until new tech or OS makes it unusable, like in your Quicken 98 example.

        But I disagree with your hobbyist justification. In a previous post I mentioned I am a FOSS guy and I don’t make a habit of buying any software unless I truly need it. And I seriously doubt a “real hobbyist” would either – if so, then renting it for a couple of months makes complete sense, financially! As for trying out new stuff, there is a 30 day trial period where people can evaluate the product and then recommend to their employer. These people aren’t going to shell out their own money to evaluate beyond 30 days.

        All in all, JB makes really good IDEs. Good developers deserve to make a good living. I can easily afford the $4.08 per month it will cost me, as an existing customer, to keep coding. On the other hand, I can easily work without PhpStorm – I used jEdit and then Netbeans over the course of a decade, and still use NB for non-PHP stuff like Java and JSP. I’ll go back to open source IDEs if I have to.

        We have choices, and in the end this is JBs decision to make. Thanks to all this feedback it looks like they are going to make some changes to their proposed pricing plans :) However, I don’t really expect them to make a complete about-face.

    • Tuba Libre says:

      JetBrains sells tools that (should) make life of developers easier. They are timesavers. Whenever you complain about prices you should do the math: How much will you need with and without the tools and then simply multiply the saved time with the hourly costs of your work.

      If you do this you would agree that the products JetBrains sell are insanely cheap. For me as a freelancer IntelliJ pays itself after 2-3 days. ReSharper even faster. So it’s a no-brainer from the cost perspective.


      These tools are essential and often business critical. And accepting this fact anything which could instantly stop working if your credit card expires, you do not have internet access, servers are down or you’r having a bad time in business, is still a clear NO-GO.

      So yes, pricing might be relevant for Hobbyists who do not earn much money with their work. Also for very small businesses or startups, if they are not performing very well…

      … but all have in common that they must rely on availability of their bread and butter tools. And with a subscription this is missing. Harder: They are slaves of JetBrains and they are paying for their life. If they don’t pay, lights go down.

  310. Crash says:

    As a Webstorm user, I’m pretty happy with the current pricing model. I even re-upped without regard to what new features were in the pipeline.

    This pricing structure change is kind of a bummer from my perspective.

    So I guess the new structure answers how you keep entry costs low without having folks skip out on paying for development of new features like folks buying every other year or so of upgrades.

    Support may be simplified under the new structure as well.

    From a corporate funded point of view, the decision to renew would be simplified with this structure which would be to the advantage of the corp developer.

    As for the individual price increase on Webstorm I say “meh” cuss I think it is under priced.

  311. Yannis Kontos says:

    Some of my colleagues are trying to convince me to try IntelliJ.
    I can’t wait untill tomorrow to see their faces after reading this!! 😀
    As long as Eclipse is still around, we have nothing to fear

    • Dino says:

      You obviously had nothing to fear to begin with. Choices have always been there. You should jump off the Bandwagon of Ignorance most here seem to be riding. Buy your license now so you can get the existing customer discount – then you truly won’t have anything to fear.

      Your colleagues are correct :) Eclipse really is not that great.

      • Yannis Kontos says:

        I never said Eclipse does things better than IntelliJ.

        I’m just saying that the Bandwagon of Ignorance does all that I need, for FREE.
        While the Bandwagon of Supreme Knowledge does not worth the $$$

  312. Dan says:

    I’m not interested in renting my software. I’ll go elsewhere. So long and thanks for all the fish.

  313. Glenn Conrad says:

    will IntelliJ ( ultimate) continue to fully encapsulate the functionality of the language specific IDE’s you offer? If so, why would one want/need an ‘All Tools’ option?

    • Dino says:

      You don’t need an all tools option. There is a lot of misinformed comments here (I am severly understating). It’s clear a lot of people are whining without even reading what’s up.

      The blog post has this link that I think should answer your question:

      • Tim hawkins says:

        Whats up is a switch in licensing model, from outright purchase (run for ever) to rental (keep paying to run) with a phone home mechanism, which nobody wants. All the other issues related to pricing and packaging etc are side shows, and are of little or no consequence.

      • Glenn Conrad says:

        Thank you, that link did address my concerns. I had originally followed a link to just this blog, not seeing the actual subscription model.

    • matt says:

      I strongly suspect that Jetbrains will start dropping support for the Ruby, Python and PHP plugins inside IntelliJ ultimate over the next year or two, in order to drive people toward the “all tools” option.

      They’ll announced it in a blog post much like this one, full of justifications about why this is good for developers.

  314. Glenn Conrad says:

    Okay, I’ll probably get flamed for this, but I’ll be a dissenter and say that I actually like the sub model. For one, I see it improving the tools. The JB devs will no longer have to play the ‘feature vomit’ game and can now comfortably concentrate on usability and performance issues (or bugs) that benefit the long-term, stable user – instead of trying to constantly lure new upgrades with silly, unnecessary features.

    The sub model gives JB a steady, predictable revenue stream that allows them to do things that the actual product developers know need to be done (address technical debt, TEST, refactor, etc.), but normally would not get done because marketing is always dreaming up some know gizmo that needs to hit some pre-announced RTM date. I, too, am a developer for a COTS software provider, and I understand that the tension between marketing desires and developer wishes are often in tension, a tension that results in poor engineering results.

  315. whatever says:

    I stayed with .NET development just because there was a R#. When R# is dead to me, there is no reason to waste my time with enterprise app sh!t.

    I’m free, c ya!

  316. Jens Voss says:

    How does the license work if I upgrade to IntelliJ 14.1 at the end of October?
    I will get free updates for one additional year which I can then use indefinitely, right?
    Does this include a free upgrade to Minerva? Or is there no way to acquire a perpetual license for IntelliJ 15?

  317. Raffaele Castagno says:

    Some random thoughts, since it seems there are some misconceptions:
    – free licenses for education, opensource, etc still applies
    – existing perpetual licenses will remain, you are not forced to upgrade to the new licensing model
    – Jetbrains created some of the best IDEs existing, and opensourced the core of them, making for example the new Android Studio possible; to think that the new subscription model is for evil is just bad faith
    – sarcasm about “now the subscription, than the ADs” etc etc is, again, bad faith; so is the “they will rise the prices and you will be forced to pay”. Just because you don’t like the new licensing mechanism does not mean Jetbrains became an evil money making machine. Also, wishing Jetbrains to loose customers just because you don’t like the new licensing mechanism is at least “unprofessional”
    – for hobbysts, you probabily don’t really need professional grade software more than you need full Microsoft Office for mundane tasks where OpenOffice would be more than enough, just like you don’t need full Photoshop to remove red eyes from photos; if your hobby involve opensource, as said before free licenses for opensource projects can still be requested. Also, Idea Community is still there, and it’s still better than NetBeans and Eclipse.
    – if you already use more than one product, and usually stay up-to-date, the new licensing model is the best deal in ages.
    – startups up to 10 people are eligible for 50% discount for 3 years
    – if those who wrote in the two blogposts (about a 1000?) would count as “unanimously” Jetbrains would have been dead and gone since ages.
    – at least Idea and AppCode are no-lock-in-solutions: you can easily create projects that can live by themselves without needing Idea or AppCode to be compiled etc, so all vendor-lock-in freaking out is nonsense

    • Nikita says:

      Totally agreed

    • whatever says:

      then go and subscribe, if you want.
      I won’t. It just feels wrong.
      it went from
      “I’m proud owner of , look how to solve this and find that bug and refactor it all with style” to colegues wispering behind my back “-lol that dude is paying subscription fee for tools, monthly. -that’s lame!”

      • Dino says:

        Aww, too bad :( You will join your your colleagues in performing extra work per project while using free Icklipse, all because you fail to see the economic benefits.

        It’s great and all, using an old copy you paid for one time. Go with it. You’ll do well, for a while anyhow.

        Or, go ahead and rent for just a few months while you get a new project up and running – and then stop renting. You could do small tweaks using something else and keep the $2 bucks or so a week that you will save. Buy a new pair of shoes or something at the end of the year instead. You win!

        I’ve already been “subscribing” – I like the Early Access Program and getting a fresh release every month with bug fixes, improvements and new features. $4.08 a month is what it works out to be. A hell of a deal for the best IDE out there. But if people like yourself actually like using old, outdated software, then get an updated copy now before it goes rental.

        I’ve tried to be even-handed about this. I respect disagreement, and fully understand the concerns posted here. But it has descended into a “me too” parade of ignorant reaction.

  318. Raffaele Castagno says:

    Just subscribing

  319. Jakub says:

    “Brilliant” idea… bye bye InteliJ! Time to move back to Eclipse.

  320. Ryan Cogswell says:

    We only use IDEA. We do NOT upgrade yearly. We generally only have a compelling reason to upgrade IDEA when we are upgrading our server environment to a new Java version. This means we tend to purchase upgrades every 2 to 3 years. This would make the new pricing model a little bit more expensive without the “existing user” discount and, with the “existing user” discount, a bit less expensive. Given the extra benefit of getting all upgrades and bug fixes, the cost difference wouldn’t be a big issue, but like others who have posted I do not like the idea of losing the option of a perpetual license. I would prefer to have the option to switch at any time (at the end of a subscription period) from a subscription to a perpetual license (which would not receive any upgrades/fixes) at a cost that is approximately two years of the non-discounted annual subscription license cost if switching at the end of an annual license or approximately three years of the annual subscription license cost if purchasing a new perpetual license or switching from a monthly subscription.
    Of course, allowing people to switch between subscription and perpetual increases the complexity for both IntelliJ (managing/tracking/pricing the different licenses) and customers trying to figure out which licensing scheme they should use — especially if they use several of IntelliJ’s products. But that complexity may be worthwhile even if the actual benefit to customers is only psychological. If a subscription license is my only option, I’ll be more likely to investigate options outside of IntelliJ. If a perpetual license remains an option, I’ll stay with IntelliJ and probably go the subscription route.
    From a customer standpoint, the complexity can be mitigated by heavily pushing and incentivizing towards the subscription route, but still providing a link to information for purchasing perpetual licenses.

  321. Anton says:

    I’m using CLion as a development tool for my personal (non-commercial) projects. It has a bunch of cool features and a great potential but it was released too early. The debugger is slow even in current 1.2 EAP (compare it to QtCreator’s implementation and feel the difference). The text editor lags on large files (I have a feeling that this issue won’t be fixed yet for a long time). The code parser errs on complex C++ templates (and it doesn’t yet support C++14 standard) and so on. The fact of releasing such incomplete product is a nonsense. And now you’re forcing me to pay for it annually. I will think twice before doing it. Hope that my feedback does matter for you.

  322. Jay Ross says:

    We were just about to purchase 20 licenses after evaluating IntelliJ. I’m glad this news came out before we did. If this new subscription model holds we will not be purchasing IntelliJ. What a shame. Eclipse it will be for our shop.

  323. I have been using IntelliJ for over a decade. Happy to buy a license since it is good software. But a monthly fee is a really dumb thing; so I’ll probably switch to another IDE. A real shame; IntelliJ was a joy to work with.