Skip to main content
As of July 23, 2026.

Platform Architecture

Prizm is an “AI-native” control plane — AI is embedded in how context is gathered, how signals are interpreted, how priorities are set, and how actions are orchestrated, rather than bolted on as a chat feature.

1. AI/ML-Powered Capabilities, Descriptions, Use Cases & Availability

DQLabs does not publish a formal GA/Preview/Roadmap matrix. Status below is inferred from how each capability is presented on DQLabs’ current product pages: features described as live, core platform functionality are marked GA; the one feature explicitly gated behind a public waitlist is marked Private Beta / Roadmap.

2. Underlying AI/ML Technology

The following technology layers are enabled by OpenAI and Claude-supported models. Gemini support is not yet generally available:
  • Statistical/ML anomaly and drift detection with configurable thresholds — the platform FAQ confirms anomaly detection is “not limited to the AI & ML-based default configuration”; users can set manual thresholds alongside the ML defaults.
  • A semantic/context layer that uses AI to connect technical metadata to business terms and to find relationships between data entities.
  • Generative AI (“GenAI-enabled remediation”) for rule generation and remediation suggestions, layered on top of the semantic engine.
  • Role-driven, multi-agent orchestration (an “agentic AI” design) coordinating Quality, Observability, Cataloging, and Governance agents around a shared context store.

Per-capability model details

3. Data Processing Requirements & Model Training on Customer Data

Prizm uses your metadata to enable data observability, data quality, and context-aware operations, without retaining any customer data from your data platforms. The core architecture is built to operate primarily on metadata, lineage, and statistical profiles rather than always requiring full raw-data movement out of the customer’s environment. The platform supports both on-premises and cloud/hybrid deployments and is suited for multi-cloud workloads — implying data processing location is configurable to the customer’s environment rather than fixed to a single DQLabs-hosted store. No Customer Data is also used for any model training. Currently no custom models are used and only OpenAI/Claude models are supported using Azure / AWS hosting environments in a secure, private network.

4. Hosting & Deployment Details

5. Security, Privacy & Compliance Controls

6. Prerequisites, Licensing & Configuration

Licensing model

Prizm is sold as a single unified package plus optional add-ons (no tiered plans), custom-quoted to the customer’s environment:
  • Included in the base package: full Prizm platform (Data Quality, Observability, Context); one workflow integration (ServiceNow or Jira); one data catalog integration; one data source type with unlimited assets, data volume, users, and DQ rules; two alert channels (email plus Teams/Slack/chat); and 8×5 onboarding, training, and support.
  • Available add-ons: native cataloging; additional data source types (warehouse, lake, pipeline, or BI — each unlimited once added); additional app integrations; additional tenants (for divisions, regions, or pre-production); a non-production sandbox; orchestration compute for tighter SLAs; extended support (12×5 or 24×7, or hourly experts); and custom development.
  • No per-seat, per-row, or per-asset fees within a connected data source — pricing scales by the number of source connectors and add-ons, not by users or data volume.

Prerequisites / configuration steps

  • Connect at least one supported data source (warehouse, lake/lakehouse, pipeline tool, or BI tool).
  • Optionally connect an existing data catalog (e.g., Collibra, Alation) or add native cataloging as an add-on.
  • Configure identity/SSO (Azure AD, Okta, PingFederate, or SAML) and assign RBAC roles (Admin, Owner, User) before granting user access.
  • Set up alert-channel integrations (email plus Slack/Teams/chat) and, if used, a workflow tool (Jira or ServiceNow) for issue routing.
  • Pricing and final scope are only available via a custom quote (“Talk to Sales”) — there is no public self-serve price list.

Per-capability prerequisites and configuration