Built into every layer to protect, govern and control how data, context and AI are accessed and used.
Built into every layer to protect, govern and control how data, context and AI are accessed and used.
Alex brings together what the data is, what it means, how it is connected, whether it can be trusted and how it should be used, creating a trusted foundation to:
Surface the change, issue or gap that starts the journey.
Explain the business impact using lineage, glossary and context.
Recommend and run the work inside a guided workflow.
Apply policy, approval and evidence so the outcome holds.
One deployment, used across divisions every day — the scale Alex runs at inside a regulated bank.
A catalogue tells you what data exists and where it lives. Alex connects that inventory to business meaning, process, ownership, policy and operational signals — and then uses those connections to answer questions a catalogue can’t: what changed, what it affects, whether it can be trusted, and what to do about it. Alex reads from catalogues rather than replacing them.
Each platform understands what lives inside its own ecosystem. They capture technical metadata well, but they can’t see across the enterprise — into the ERP system, the BI layer, the legacy application, or the business process that depends on all three. Alex operates across those boundaries. It doesn’t replace your platforms; it makes the relationships between them visible.
No. Alex connects to what you already run and enriches it. The design principle is integration rather than migration — your data stays where it lives, and existing governance tooling keeps working alongside Alex rather than being displaced by it.
It depends on the journey’s complexity and on the volume and quality of the underlying metadata, integrations and configuration required. These are not press-the-button-and-go applications: each is configured to your metadata model, roles and workflows. After initial scoping and discovery you get an agreed plan with a timeline and milestones.
At minimum, approved platform connections and the relevant source systems. No pre-existing curated metadata is required — Alex connects to the source and harvests what’s available. Individual Business Journeys may need particular metadata types (lineage, quality, usage or business metadata) and those prerequisites are confirmed during scoping.
One platform subscription, with unlimited users and no separate connector licensing. Business Journeys are subscribed separately from the platform, individually or bundled. Implementation and enablement are agreed upfront and documented in a statement of work.