We performed a comparison between iServer and MEGA HOPEX based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Architecture Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The initial setup is easy."
"This is a flexible tool compared to some other solutions."
"Integrating the Microsoft documents to the product and visualization matrix where we can see the end-to-end relationship of the network is of great importance to our company."
"We like the governance."
"iServer is a solution that helps catalog enterprise architect solutions and catalog information."
"The solution has wide use within Microsoft products. The integration with Microsoft products, and, in particular, Microsoft Office, is great."
"Good and effective reporting features, which help in decision making."
"I have to think less with this solution. It's simple."
"HOPEX has a panel that offers various views. I think that is very good. MEGA has an app for integrating with a lot of apps. We help our clients integrate HOPEX with a different product like Apple Gateway, for example. I've been with the company for 15 years, and we connect with everything. Our clientele includes almost all of the banks in Mexico."
"The support experience in Latin America is great."
"The most valuable feature is the completeness of HOPEX's meta-model. It's a strong meta-model that's rigid but comprehensive. It's a logical fit for our understanding of how we want things modeled in our database."
"An advantage is its accessibility."
"I find the IT portfolio management very valuable and helpful."
"You do not need to be a professional of enterprise modeling to contribute to the enrichment and improvement of the enterprise repository."
"The most valuable features of MEGA HOPEX are the seamless VPA module and the good user experience. There are built-in connections that provide integration with other platforms, such as ServiceNow. There is a lot of customization available allowing a lot of freedom. The solution is updated frequently adding new features. For example, the feature GraphQL can be integrated into other solutions, such as ManageEngine for ITSM solutions. You are able to use GraphQL to connect APIs and query the APIs."
"We use the portfolio management feature heavily."
"Enhancing integration options with ERP or ITSM-related solutions for triggering automated requests for process definitions, changes, and tracking them in the iServer."
"We could allocate permissions to use only specific components to the users rather than the entire instance."
"It definitely needs help to improve the visual aspect of the solution."
"The one issue is that if you want to import predefined work, you need to put the licensing model in. So if you wanted to import work that was done before, you then need to buy a separate product for that."
"It runs relatively slowly."
"The performance is slow, which is something that should be improved."
"More visualization techniques and ways to report the data might be helpful."
"Requirements management needs to be improved."
"We have a very close relationship with MEGA representatives in Mexico, and we ask them why they don't offer impact analysis. For example, we have a server in the center and provide the client a view of what's in the peripheral area, like one cluster, application, process area, and services. We want to offer our clients that level of visibility with HOPEX."
"In my experience, I've encountered difficulties with consuming custom packages in MEGA HOPEX, which leads to redundant work when deploying them to production. This is an area where improvement is needed. While version six offers better UI and UX, resolving this issue should be a priority. I believe it's important to fully explore MEGA HOPEX's capabilities before suggesting new ones."
"They do tend to push people to their professional services, instead of helping the customers with their problems. I understand this is their business. At the same time, however, they need to work on fact sheets or offer some program to help the customers who want to implement it themselves and to make it run properly in their environment."
"It takes a long time to learn how to use HOPEX. It's hard to work with it because the user interface is bad. For example, if you want to build a complex system diagram, you need a lot of knowledge to do this correctly and make it readable. In MEGA, you need to create a report and it takes a long time to publish it. The publishing is offline. With RDoC, everything is online."
"The product must improve integration with other tools."
"This product is expensive and would be improved by lowering its price."
"I would like to see more regular updates released."
"Scalability can be a problem sometimes."
iServer is ranked 6th in Enterprise Architecture Management with 15 reviews while MEGA HOPEX is ranked 4th in Enterprise Architecture Management with 36 reviews. iServer is rated 7.2, while MEGA HOPEX is rated 7.8. The top reviewer of iServer writes "Enables flexible parameters for any process model and has a valuable document management feature ". On the other hand, the top reviewer of MEGA HOPEX writes "Interactive with good functionality and helps with productivity". iServer is most compared with LeanIX, Sparx Systems Enterprise Architect, Visio, ARIS BPA and BiZZdesign HoriZZon, whereas MEGA HOPEX is most compared with Sparx Systems Enterprise Architect, LeanIX, ARIS BPA, Visio and Camunda. See our MEGA HOPEX vs. iServer report.
See our list of best Enterprise Architecture Management vendors and best Business Process Design vendors.
We monitor all Enterprise Architecture Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.