Product introduction¶
What is MatrixOne Intelligence?¶
MatrixOne Intelligence (MOI) is an all-in-one, AI-native multimodal data-intelligence platform. It brings data processing and agent building into the same platform, covering the entire process from data connection, parsing, and governance to intelligent retrieval and agent building. It helps enterprises turn scattered raw data into high-quality AI-Ready data that agents can use reliably.
The product’s core promise can be expressed in one sentence: Control Your Data, Trust Your AI. Data can be connected, governed, traced, and authorized, while AI answers and actions can be verified, audited, and improved.
Three platforms, one path¶
Internally, MOI is a complete path from data to agents. Externally, it is divided into three platforms so that users in different roles can find the appropriate entry point. They are not three parallel products; each is responsible for a different segment of the same path:
Platform |
Segment of the path |
When to use it |
|---|---|---|
Connect data, make it AI-Ready, and build agents (the primary day-to-day workspace) |
When connecting data, running workflows, creating knowledge bases, or building agents |
|
The storage and compute foundation for data |
When creating database instances, writing SQL, or performing engine-side operations |
|
Model supply through a unified model API service |
When obtaining an API Key to call models, viewing usage, or managing keys |
How the path works¶
A typical path connects all three platforms:
① AI Studio: Connectors ingest data → Catalog → Workflow processing → Knowledge base → Agent
│ │
(tables / volumes / vectors / SQL run on) (chat / Embedding / model nodes call models)
▼ ▼
② MatrixOne: Hyper-converged database foundation ③ Genesis: Unified model API service
(storage and compute · vectors · Git-for-Data) (model marketplace · keys · usage · ledger)
AI Studio is where you work: connect data, process it, and make it available to agents.
The storage, querying, and vector retrieval for that data all run on the MatrixOne engine underneath.
The models called by agents and workflows are supplied uniformly through Genesis. Internal platform use is charged to the “AI services” ledger, while external use through an API Key is charged to the “Genesis” ledger.
The three platforms share one account system and one Credit billing system, forming a single platform rather than three isolated products. For details about how they fit together and how their ledgers are separated, see How the three platforms work together.
Typical use cases¶
Scenario |
Main platforms involved |
|---|---|
Enterprise knowledge agents (document Q&A / Agentic RAG) |
AI Studio + MatrixOne underneath |
Mixed structured and unstructured Q&A (query data, then retrieve documents) |
AI Studio + MatrixOne |
Natural-language data queries (NL2SQL, row/column permissions, and traceability) |
AI Studio + MatrixOne |
Providing model APIs to your own applications or third-party systems |
Genesis |
Database-instance operations and SQL development |
MatrixOne |
Recommended reading order¶
Read in path order to understand most easily how the three platforms connect:
AI Studio — your primary day-to-day workspace and where the work happens
MatrixOne — the data foundation beneath AI Studio
Genesis — where the models used by agents come from and how they are provided externally
How the three platforms work together — a detailed explanation of their connections, ledgers, and account system