For the enterprise architect
Capabilities, applications, interfaces, technology, vendors and risks in one model, so the impact of a change is known before the money is committed.
In one sentence
AlignX puts the enterprise architect into the decision early, with one living model of capabilities, applications, data and technology and the impact of every proposed change on it.
Written forChief Enterprise ArchitectHead of Enterprise ArchitectureEnterprise Architect
The challenge
If any of these takes a week to answer, the rest of this page is for you.
The solution
Capability map
Not a slide. Level one and two, phase-in and phase-out dates, the applications that realise each one.

Interfaces
Synchronous or batch, inbound or outbound, real time or nightly. When an application retires, the interfaces that die with it are already on the record.

Technical fit
Unreasonable, inappropriate, adequate or fully appropriate, across three hundred and twelve components. The legacy Oracle database is unreasonable, eliminate, and already end of life — and three products are still doing identity between them.

Impact by layer
Business contexts, capabilities, organisations, applications, interfaces, technology, vendors and risks, each named on the change record.

Day to day
The AlignX technology
Questions
Yes, for most organisations. AlignX can import data from your existing enterprise architecture repositories and offers a more accessible UX for non-architects. Where you keep a specialist tool for deep modelling, AlignX integrates. Most EA teams consolidate onto AlignX within six months because architecture, portfolio and risk finally share one truth.
Two-way integration with ServiceNow ITSM/CMDB and Jira Service Management (JSM). Applications, services, infrastructure and dependencies flow into the AlignX model automatically. Your CMDB stays the source of truth for CI-level data. AlignX layers business capability, ownership, portfolio and risk context on top of it.
One connected metamodel across capability, application, technology, data, business process and organisation. Relationships are first-class (not tags), so you can traverse the architecture in any direction: which apps support this capability, which capabilities this initiative uplifts, which risks affect this data domain.
Import via CSV and Excel. Migration typically completes in two to four weeks including data cleanup. AlignX imports the relationships between records, not just the records themselves, so lineage survives the migration.
Yes. Role-based views mean architects see the architecture lens, PMO sees the delivery lens, risk sees the risk lens, all against the same underlying model. Comment threads and reviews sit on the record, not in a separate tool.
Configurable review workflows for architecture decisions, design reviews and TDA gates. Every decision links to the affected components with rationale, options considered and approver captured. Your architecture repository becomes the decision record automatically.
Typically your standalone EA tool (LeanIX, Ardoq, Sparx, Bizzdesign), your architecture repository (SharePoint or Confluence libraries of Visio), your capability planning spreadsheets, and often your APM tool. Combined licence saving is usually enough to fund the AlignX rollout with change to spare.
Ten minutes, twenty-one questions, an instant maturity score.