Features

CryspIQ® is organised into modules that follow the path data takes: it arrives, it is mapped into the enterprise data model, it is loaded and monitored, its quality is measured, and it is consumed — with security applied throughout.

This page describes what each module does, then sets out which capabilities are included in each plan.

Sources — how data arrives

The Sources module manages information entering CryspIQ®. Data can arrive as file uploads, from databases, through APIs, or from a raw or staging layer you already populate in an existing platform.

Every plan supports an unlimited number of sources. That is deliberate: charging per source would penalise exactly the behaviour the model is designed for — bringing more of the business into one place.

Maps — where raw data becomes business information

The Maps module is where source fields are matched to their place in the enterprise data model. It is the most consequential part of the platform, because it is where meaning is established.

Lumen proposes the mapping for each column and a person confirms it, which keeps the step in business language — is this the customer? is this an amount or a quantity? — rather than making it a modelling exercise. Confirmed mappings are remembered and improve later suggestions.

Supporting capabilities include defaults for enriching incomplete data, methods for transforming values on the way in, and rules that govern what is accepted.

Operations — loading and monitoring

The Operations module monitors processing, which follows a push → prepare → load sequence. Administrators can see what is running, what has completed and what has failed, and intervene where needed.

Mapper Control and Load Control are available on every plan — visibility of your own data pipeline is not treated as a premium feature.

Quality — measured on the way in, not after the fact

The Quality module gives visibility into data quality, stewardship and governance performance. Quality is assessed as data loads rather than discovered downstream, and records that fail are held for a steward instead of being silently dropped.

Steward dashboards show individual owners what needs attention
Function dashboards roll that up to a business area
Local methods apply your own validation logic
Scenario notifications alert people when defined conditions occur
External API methods validate against outside services

See data quality for how the organisation-wide score is calculated.

Consume — getting answers out

The Consume module is how people and systems use the data. Because everything reads the same model, the answers agree regardless of route.

Query library — saved, governed queries anyone can run
Query builder — build new queries visually, without SQL
Natural language query — ask in business language, answered by Lumen
Workflow triggers — act on data conditions automatically
Application to application — operational systems reading the model directly

Security — applied to the data

The Security module integrates with Microsoft Entra ID and protects data down to column and field level, supporting both business object and contextual security.

Because access control is applied to the data rather than to a reporting tool, a person sees the same permitted subset whichever route they use — and the security classification carried on the fact type travels with the data into everything that reads it.

What each plan includes

Every plan includes unlimited sources, security to column and field level, the query library, query builder, natural language query, and full operational control. Plans differ mainly in user count, data quality depth and automation.

Module	Capability	Lite	Professional	Enterprise
Sources	Number of sources	Unlimited	Unlimited	Unlimited
Company	Number of users	Up to 5	Up to 20	Unlimited
Security	Secure to column level	✅	✅	✅
Security	Secure to field level	✅	✅	✅
Consume	Query library	✅	✅	✅
Consume	Query builder	✅	✅	✅
Consume	Natural language query	✅	✅	✅
Consume	Workflow triggers	❌	❌	✅
Consume	Application to application	❌	❌	✅
Data Quality	Data steward dashboards	❌	✅	✅
Data Quality	Function dashboards	❌	✅	✅
Data Quality	Local methods	❌	✅	✅
Data Quality	Scenario notifications	❌	❌	✅
Data Quality	External API methods	❌	❌	✅
Operations	Mapper Control	✅	✅	✅
Operations	Load Control	✅	✅	✅

For plan pricing, see pricing.

Architecture — how the modules fit together
The CryspIQ® data model — what mapping targets
Lumen AI — mapping suggestions and natural language query
Navigating CryspIQ® — using each module day to day
Data quality — how the quality score works

Sources — how data arrives​

Maps — where raw data becomes business information​

Operations — loading and monitoring​

Quality — measured on the way in, not after the fact​

Consume — getting answers out​

Security — applied to the data​

What each plan includes​

Related​