The common language for conversational data management and analytics.
SemantIQ connects to your data, discovers the schema, and drafts the catalog with AI. Your stewards review and confirm. The result becomes the shared language behind every xAQUA capability โ so your team can go from raw data to advanced analytics in plain English.
Most catalogs are silos โ one project, one set of sources, one isolated search. SemantIQ federates them. Ask one question and get one answer that spans HR, Sales, Finance, Operations. Across catalogs. Across sources. Across files and virtual assets.
Reciprocal Rank Fusion (RRF) to combine both signals โ keyword precision plus semantic recall โ without sacrificing either. This is why every Zyra answer and every default API call uses hybrid mode. You can override to BM25 or Vector for specialized use cases via the mode parameter, but hybrid is what you want 95% of the time.
Traditional catalogs are documentation-first. Every business name, every description, every PII tag, every glossary entry โ typed by hand, by your team, on top of their day jobs. Six months in, half is wrong. A year in, half doesn't exist. The data team writes definitions. The business team disagrees. The catalog you bought to standardize answers becomes the source of three different answers.
That's not a team failure. It's a catalog failure. Documentation-first catalogs scale with human effort โ and human effort doesn't scale. Schemas evolve faster than your stewards can type.
SemantIQ inverts the problem. The AI drafts every business name, every description, every classification โ read directly from the schema, never from your data. Your stewards review, edit, and confirm. The catalog stays current because curation scales. Transcription doesn't.
Your stewards stay in charge. The AI does the heavy lifting.This is the line that separates SemantIQ from every legacy catalog on the market.
Collibra, Atlan, OpenMetadata โ these are documentation tools. They tell you what exists. They put a glossary in front of it. They draw lineage diagrams. After that, the work happens somewhere else: a SQL editor, a BI tool, a transformation product, an ML platform. The catalog is a reference manual.
SemantIQ is built differently. The same enriched metadata you see in the catalog is the metadata that drives execution across xAQUA. Update a column's business name in SemantIQ โ ConverseSQL generates better SQL. Mark a column as PII โ SenseMask masks it automatically. Confirm a cross-source join โ ConverseDataIQ uses it in query plans. Certify a table โ Trust Score reflects it for every business user.
A single shared semantic model โ organized into five pillars. Every module reads and writes through the same governed layer.
Connect once. Bind many. One catalog can bind to DEV, TEST, and PROD versions of the same source โ schema drift between environments is tracked automatically.
Drag-and-drop a CSV, Excel, Parquet, or JSON file. SemantIQ infers the schema, detects multi-sheet workbooks, runs the same enrichment pipeline as a database source, and binds it to a catalog.
SemantIQ watches every bound source. Breaking changes raise alerts before they hit production. Non-breaking changes update the catalog. Schema change history is audit-grade and queryable.
Business names. Plain-English descriptions. Domain. Sensitivity. PII detection. Column roles. Glossary links. Over 50 enrichment fields per container and per column โ drafted by the AI, confirmed by your stewards.
Seven ISO quality dimensions scored continuously. Over 30 metrics across 7 categories. Trend snapshots. Threshold alerts. The same scores feed Qualix and the Trust Score visible to every business user.
A living glossary of business terms linked directly to the physical columns that implement them. Cross-catalog. Cross-source. When the business says "Active Member," every system that uses the term points to the same definition.
Affinity scan finds joins you didn't know existed. Four signals weighed: name (40%), type (20%), value overlap (30%), cardinality (10%). One click to confirm. Confirmed joins flow straight into the query planner.
Drill-down hierarchies. Metric decomposition trees. Asset inheritance. The structures business analysts navigate by โ codified once, reused everywhere. Narratix uses them. ConverseDataIQ uses them. Reeve uses them.
Sensitivity levels from PUBLIC to TOP_SECRET. Certification from UNCERTIFIED through CERTIFIED. Owner and steward assignment. Compliance reporting. Every classification captured as part of the semantic layer โ not bolted on.
The catalog is under strict governance. No one edits definitions, classifications, or relationships directly. Every change goes through a change request โ submitted, reviewed by the catalog owner or steward, accepted or rejected with full reasoning captured.
Zyra is the AI Data Steward built into SemantIQ. She writes insights as the data changes โ root-cause analyses when quality drops, volume anomalies, distribution drift, schema impact, governance recommendations. Every insight rated by your team. Ask her anything about your catalog in plain English. Try Zyra below โ
The catalog category is crowded and confused. Buyers compare products that don't actually do the same thing. Here's the clean separation.
Most catalogs index your schema. SemantIQ enriches it. Every container and column carries 50+ semantic fields. That's why xAQUA agents can answer questions in plain English.
Most catalogs allow direct edits and call the audit log "governance." SemantIQ doesn't. Every change flows through a formal change request reviewed by the catalog owner or steward. Accepted or rejected with reasoning logged.
The LLM never sees customer data. Schema metadata only. Enforced at the service layer. The same model can run inside your private deployment if you need it to.
Every AI-generated field carries a confidence score. Every confirmed field is treated as absolute truth. Stewards can lock fields against re-enrichment. The catalog gets smarter as your team works in it.
A column rename never breaks your catalog. Permanent UUIDs survive structural change. Enrichment is overlay, not overwrite. Curation work compounds over time instead of getting wiped on every refresh.
Most catalogs only know about source tables. SemantIQ catalogs both โ discovered sources and xAQUA-created assets: queries, blends, pipelines, reports, ADLs, ML applications.
Most catalogs are silos. SemantIQ is a unified semantic layer across all your catalogs โ HR, Sales, Finance, Operations, Compliance. Hybrid BM25 + semantic search returns one answer that spans every catalog, source, and asset you have access to. Through Zyra or via API.
Stop writing descriptions by hand. Curate AI-drafted ones. Confirm what's right, edit what's wrong, certify what's ready. Every change flows through the change-request workflow you control.
A defensible, board-ready foundation. Sensitivity classification, certification status, governed change management, and full audit trails โ all native, all current, all auditable.
The catalog tells your pipelines what changed. Breaking schema changes raise alerts before they hit production. Cross-source joins are reusable. Migration work is catalog-driven.
You don't have to know what SemantIQ is. You just notice that when you ask Cezu a question, it returns the right answer โ because the platform finally speaks your language.
Because every xAQUA module reads and writes through the same semantic layer, definitions stay consistent everywhere. No second source of truth. No re-modeling per tool. No definition drift.
See SemantIQ enrich a real source from your stack โ in a 30-minute walkthrough.