HOPEX Alternatives: Choosing an Enterprise Architecture Platform
Choosing an alternative to HOPEX depends first on the architecture practice to support: governance, transformation or collected data. The uses held in HOPEX today then set the points to check.
Updated on
HOPEX today
HOPEX was developed by MEGA International, a Paris-based vendor founded in 1991. Bizzdesign announced its acquisition of MEGA in September 2024, then added Alfabet in January 2025. The group keeps the Bizzdesign name and presents the product as Bizzdesign Hopex, alongside Bizzdesign Horizzon, Bizzdesign Alfabet and, since April 2026, Bizzdesign Unify.
Bizzdesign describes Hopex as a platform connecting business, IT, risk and data, with solutions for enterprise architecture management, application and technology portfolio management, business processes, data and GRC. In September 2025, the vendor announced that it would maintain each product’s roadmap for five to seven years.
Place your architecture practice
Three profiles help frame the need. An organisation may combine several; the comparison focuses on the one that weighs most in its decisions.
- Governance-centred practice: standards, principles, architecture boards, exceptions and documentation. The tool is the central repository and keeps the record of decisions.
- Transformation-centred practice: roadmaps, capability-based planning and investment choices. The tool is used first to prepare portfolio decisions.
- Data-fed practice: the CMDB, directories, code repositories and infrastructure feed the repository. The tool must record where each item comes from and have incoming data validated.
Uses to carry over
List what your teams do in Hopex today, solution by solution: enterprise architecture, application and technology portfolio, processes, data, GRC. Each use becomes a line in the comparison, with its users, its data and its reports.
A risk or compliance use held in HOPEX should also be compared with the GRC tools under consideration, not only with architecture tools.
Selection criteria
These criteria can be checked in a trial, with an extract of your current data.
- Contribution beyond the architecture team: application and process owners complete and confirm their information.
- Data collection: imports, connectors, APIs, and validation of what enters the repository.
- Capability maps and roadmaps: how they are updated when an application changes.
- Application portfolio: risks, redundancy, lifecycle and the capabilities served.
- Integration with delivery teams: Jira, ServiceNow, GitHub and cloud tools.
- Metamodel flexibility: the customisation available and the work it takes to keep the model consistent.
Platforms on the market
The descriptions below follow each vendor’s official presentation.
- Bizzdesign Horizzon: a product of the group that also publishes Hopex, for modelling in ArchiMate, C4, BPMN, ERD and UML.
- SAP LeanIX: SAP’s SaaS offering since November 2023, with products for enterprise architecture, application portfolio management, technology risk and roadmap planning; billed by number of applications.
- Ardoq: a platform from the Norwegian vendor Ardoq AS, built around a graph with a configurable metamodel and an MCP gateway for external AI tools; priced per application, with unlimited users.
- Avolution ABACUS: a platform from the Australian vendor Avolution, which lists more than a hundred frameworks available as standard, including TOGAF, ArchiMate and BPMN.
- ADOIT from BOC Group, an Austrian vendor: available as SaaS, private cloud or on-premise, with a free Community Edition limited to one user.
- ArchiLU: published in Luxembourg by MIP-IT SARL and hosted in the European Union; each object can have an owner, the board keeps its decisions with their reasons, and the subscription is annual, per organisation.
Contribution, upkeep and decisions
Before the migration, the teams concerned decide who contributes to the repository, who confirms the data and how architecture feeds decisions. These choices hold whatever tool is selected.
In ArchiLU, each owner receives a task every twelve months to confirm their objects, and objects without an owner remain visible on the architect’s dashboard. Requests, architecture documents and board decisions stay linked to the objects they affect.
Frequently asked questions
- What mistake should we avoid when replacing HOPEX?
- Comparing tools before listing the uses held in HOPEX and the architecture practice to support. Each use carried over needs its users, its data and its reports.
- How do we know whether our practice is governance-centred or transformation-centred?
- Look at where value is expected: control of standards, principles and exceptions, or preparation of roadmaps and portfolio choices.
- What should be measured during the evaluation?
- The time needed to prepare a decision, the effort to keep data current, the depth of integrations and the share of contributors outside the architecture team.
