Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Postman vs ElasticHQ, the Slant community recommends ElasticHQ for most people. In the question“What are the best Elasticsearch GUI clients?” ElasticHQ is ranked 2nd while Postman is ranked 3rd. The most important reason people chose ElasticHQ is:
Can be deployed on AWS, Azure and any other cloud service.
Specs
Question Ranking
Pros
Pro Free
Pro Flexible and powerful
Can easily add/remove parameters, headers, tests and more. Displays all the info you would want in a partitioned way so you can track exactly what you want. Able to save request and run them in bulk for testing real-user scenarios very efficiently.
Pro Clear interface
The interface of the program is clean and intuitive. Almost all features are accessible through a single click.
Pro Two versions of apps are available
Packaged app and an in-browser app are available for Google Chrome.
Pro Excellent user feedback loop
Postman is very responsive to users and listens to user feedback.
Pro Dark theme
Pro Cloud ready
Can be deployed on AWS, Azure and any other cloud service.
Pro Most comprehensive set of tools
Can manage and keep track of ES Datasets in real time, is cloud-ready and has been battle-tested by multiple large companies.
Pro Installation is easy
ElasticHQ is easy to install and accessible from your browser. Can be installed in just 2 commands and will remain running until shutdown. Installation docs can be found here.
Pro Real-Time Monitoring
ElasticHQ allows you to view real-time threads, individual cluster nodes, cluster runtime metrics, and configurations.
Pro Open source
Licensed under Apache 2 can be used and re-distributed without complications.
Pro Cluster management
Complete control over clusters, nodes, indexes, and mappings.
Cons
Con Version 8.x killed Postman - some problem related to "Teams"
Postman is forcing everybody to move their data to the cloud.
Con Insecure off-premise storage
To properly use this with full development and testing it stores API details, including security, in an off-site storage managed by Postman. It also stores details about employees, teams they are members of, and projects they are working on.
This makes it inappropriate for any organization that is required to exercise a high level of security hygiene when developing software products. This issue may be compounded by the lack of details concerning the geolocation of data storage.
Con Proprietary, closed source software
Not free and open source.
Con Resource hog
Con Bloated & cluttered
Bloated and cluttered, it's quicker to just have a js/ts template available to run some requests.
Con Limited free APIs
Con Doesn't work right with localized queries
Con Does not support Proxy authentication
Con Not maintained anymore
Con Error when using SSL and Python 3.6+
This bug is under investigation but is not close to being solved. See here.
