Perverse incentives. They want Postman to have a cloud offering that's easy to charge customers for. Customers aren't all that interested in that, and have a ton of security worries about it.
A customer of mine uses Postman for its API docs. I never use it to run API calls. I curl to the server from the terminal. I keep a file with the most common sequences and I can add -d @request.json much more easily than from within Postman. Basically I use it only to edit the documentation.
Enshittification at its best. I used Postman for several years before it become unusable for me. Didn't actually think too much about it, tried several alternatives (ApiDog, Bruno), but none came to the comfort Postman gave me before that.
Now I understand if engineers spend lots of time on software, somehow they need to get paid. But I still believe, there is a more authentic and acceptable path than what most companies do - make people dependend, make the software worse, introduce subscriptions, force you into plans, etc.
I haven't found a good substitute yet. I use Bruno, I use ApiDog, but they feel a little cumbersome at times. Good enough, but not great. I'd had loved to stay with Postman, but I'm not paying that money for a an API debug client.
with my team we built Voiden for some of these reasons, initially for our own internal use (building many APIs for our SaaS marketplace). Most of the folks in the team have been postman power users before so we do remember the time when this was indeed something new.
Problem now is that most of the alternatives out there (including the ones you mentioned) do offer some great things but essentially they feel variations of the same concepts - so I see them as "Enshittification on the way". Reason we built voiden is that we wanted something that challenges these ideas. You can try it out and let me know if it resonates: https://github.com/VoidenHQ/voiden.
apologies for the slight promo - but based on your comment I thought it might be relevant.
Perverse incentives. They want Postman to have a cloud offering that's easy to charge customers for. Customers aren't all that interested in that, and have a ton of security worries about it.
Easy to find long security discussions: https://community.postman.com/t/forced-to-store-environments...
A customer of mine uses Postman for its API docs. I never use it to run API calls. I curl to the server from the terminal. I keep a file with the most common sequences and I can add -d @request.json much more easily than from within Postman. Basically I use it only to edit the documentation.
Enshittification at its best. I used Postman for several years before it become unusable for me. Didn't actually think too much about it, tried several alternatives (ApiDog, Bruno), but none came to the comfort Postman gave me before that.
Now I understand if engineers spend lots of time on software, somehow they need to get paid. But I still believe, there is a more authentic and acceptable path than what most companies do - make people dependend, make the software worse, introduce subscriptions, force you into plans, etc.
I haven't found a good substitute yet. I use Bruno, I use ApiDog, but they feel a little cumbersome at times. Good enough, but not great. I'd had loved to stay with Postman, but I'm not paying that money for a an API debug client.
with my team we built Voiden for some of these reasons, initially for our own internal use (building many APIs for our SaaS marketplace). Most of the folks in the team have been postman power users before so we do remember the time when this was indeed something new.
Problem now is that most of the alternatives out there (including the ones you mentioned) do offer some great things but essentially they feel variations of the same concepts - so I see them as "Enshittification on the way". Reason we built voiden is that we wanted something that challenges these ideas. You can try it out and let me know if it resonates: https://github.com/VoidenHQ/voiden.
apologies for the slight promo - but based on your comment I thought it might be relevant.
No worries, I love to hear about alternatives and other approaches. I'll definitely have a look, thanks!