For the enterprise architect

Get into the decision early. Show impact and dependencies before commitment.

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 solution

What the architect keeps current.

Capability map

Capabilities as records, with their level, their parent and their lifecycle.

Not a slide. Level one and two, phase-in and phase-out dates, the applications that realise each one.

See the architecture product

Interfaces

Every interface with its type, its flow and its frequency.

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.

See how it works

Technical fit

Technical fit on every component, next to what it is worth keeping.

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.

See the architecture product

Impact by layer

What a change touches, by layer, before the decision.

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

See the business analysis product

Day to day

What changes.

Without AlignXWith AlignX
The investment committeeArchitecture is asked after the option is chosen.
The investment committeeThe impact is on the record before the decision is made.
The impact questionSomeone asks what a change touches. The answer takes a fortnight.
The impact questionThe change record names every layer it touches, today.
The inventoryA spreadsheet from March that nobody trusts.
The inventoryThe register is where the work happens, so it is current.
The waiverA standard exception agreed in a meeting and forgotten.
The waiverStandards, exceptions and waivers are decisions with an authority and a date.
The rationalisation caseBuilt by hand from three sources.
The rationalisation caseTechnical fit, cost and risk on every component; the case writes itself.
The strategy questionNobody can say which objective an application serves.
The strategy questionEvery architecture decision traces to the objective it supports.

The AlignX technology

Nothing new to govern.

  • Runs inside Microsoft 365In your tenant, on your Dataverse. Nothing leaves it.
  • Entra ID governs who sees whatThe roles you already run decide access. No second directory.
  • Australian data residencyYour Dataverse environment sits in an Australian region. Purview and retention policies apply as they do everywhere else.

How AlignX sits inside Microsoft 365

Questions

What enterprise architects ask us.

Does AlignX replace our EA tool (LeanIX, Ardoq, Sparx, Bizzdesign)?

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.

How does AlignX integrate with our ITSM and CMDB?

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.

How does AlignX handle capability, application, technology, data and business models in one place?

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.

How do we import our existing capability map, application catalogue and EA artefacts?

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.

Can architects, PMO and risk teams see the same source of truth without stepping on each other?

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.

How does AlignX support architecture review boards and Technical Design Authority (TDA) governance?

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.

What tools can we retire when we move architecture into AlignX?

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.

See where you stand.

Ten minutes, twenty-one questions, an instant maturity score.