How Data complements AI
How Data complements the AI layer.
Data does not replace AI. It complements it by adding the data movement, discovery, analytical storage, distributed processing, streaming, and BI services that some AI solutions need around the AI layer.
Core relationship
| Layer | Main role |
|---|---|
| Foundation | Runs and secures the platform |
| AI | Serves and manages GenAI capabilities |
| Data | Adds enterprise data and analytics services |
Practical extension points
- Data ingestion in Studio brings data from external systems through managed source and destination connectors
- The data catalog shows the governed tables each user can discover
- Compute in Studio and the Spark helper run distributed processing
Kafkasupports event-driven data movement and streaming use casesKubeflowprovides ML pipeline orchestration and notebook-based developmentMLflow, reached through the BSQAI API, records experiments and registers models for servingLakekeeperandSpark Operatorprovide catalog-backed Iceberg processingTuplesauthorizes Data resources per tenant and publishes optional audit eventsSupersetexposes business-facing dashboards and BI views over analytical data
What this enables
- AI systems that depend on synchronized enterprise data
- Models trained in Developer Workspace and served by the AI layer from the MLflow registry
- Analytics and reporting experiences around platform data
- Event-driven architectures that connect AI and data services
- A cleaner separation between AI application logic and enterprise data operations