@bmarlok support should be getting back to you in the next few days. If you’re on a paid team you should be getting an email explaining the changes and how the change impacts your team based on your plan. If you’re not getting it I’m sure the support team will be able to transfer it again.
FYI the limit will take effect from the 15th of March for teams on paid plans, only free teams are getting the new limits from today.
While I can’t say when someone will be able to reply to everyone here I can assure that I’m forwarding all the feedback you’re providing here internally.
We have been using Postman for many years (overall, have appreciated the tool) - I understand if you need to make some money but these plans simply do not make sense and they have stopped us dead in the middle of testing for a release - - If they are not changed in a hurry then we will be changing to another tool ASAP -
Robot Framework is a great suggestion for anyone looking.
Concur. $1K+pa per user just to use your own computer more than a trivial amount is a really challenging commercial proposition.
I’ve been using Postman (for some years) on the free plan, so obviously I accept that the company is entirely free to set whatever constraints they want on their tool and maybe they don’t see any point in expending resources supporting freeloaders like myself. I can also see how a pricing change like this might get some people to upgrade to a more functional plan, however reluctantly. I don’t really see how this is going to attract new customers, though; I certainly wouldn’t have even looked at Postman in the first place if the pricing was anything like this.
We’re frustrated by the recent news about changes to Postman’s pricing plan. It’s unfair that paying customers on the basic plan now get the same number of local runs as the free tier. We rely on Postman for our daily work, and now we have to choose between paying more for the same features or losing access to functionality we’ve come to depend on.
Having to resort to workarounds like running the suite in Newman to debug is not ideal, and it’s not what we expect from a paid product. We feel like our loyalty and investment in Postman is being devalued.
We’re now considering whether moving away from Postman is our next move.
Honestly, this is completely unacceptable and has triggered our migration away from Postman.
It’s one thing, and completely ok to lock new functionality behind additional payments, but to take away features (or in this case, restrict usage to the point of making them almost unusable) from customers already paying them, who have made this tool a core part of our workflow is something that has hugely damaged trust in the Postman product.
This change seems really detrimental to the Postman user base. In order for us to have unlimited LOCAL collection runs, we will need to pay over 3x as much to move from professional to enterprise. What is the reasoning behind the chosen limits? Even for the free plan, 25 local collection runs seems so low.
What counts as a collection run? Anything through the runner? What if we are trying to debug or troubleshoot an API issue? We would probably run into that limit pretty quickly. Why should we continue to use a tool that imposes what seems like a very unreasonable limit like this?
Insomnia is the most similar tool on the market, but this ought to be a lesson to people to not put all their eggs into a commercial offering that can have functionality pulled at a moment’s notice. We’ll be moving to a code-first solution rather than continuing to put ourselves at the mercy of Postman, or trusting Insomnia not to pull a similar stunt.
No. Forget insomnia, it’s very convoluted. The free version is fine for a collection of calls, but there’s not scripting or verification or anything built in. And you can’t even log in and sync without being on a paid plan. This one died before it was really born.
Is there any possibility that 25 collection runs limit will be withdrawn?
We have over 500 tests in collection that heavily rely on setNextRequest and this change will kill us. We use local runner for debugging and for developing new tests. I personally use about 100 local runs per day. Please share any information regarding status of that decision. Should we really give up on Postman as a tool?