Agent mode
When the customer's database lives behind a firewall, agent mode
AI features
PLACEHOLDER Cloud uses an LLM you configure — OpenAI, Anthropic, Ollama, or any OpenAI-compatible endpoint — for three things: proposing rules, explaining anomalies, and (planned) translating natural-language descriptions into custom SQL expectations.
Alerts
An alert is how PLACEHOLDER Cloud tells you something went wrong. Two model rows back it: an AlertRule is the configuration ("on every failure of checkpoint X, post to Slack"); an AlertEvent is the occurrence — one row per dispatched message.
Anomalies
An anomaly is a statistical deviation in a tracked metric — row count, null percentage, distinct count — relative to that asset's recent profile runs. Anomalies are how PLACEHOLDER Cloud catches problems your rule suites didn't explicitly assert against.
Checkpoints
A checkpoint is the unit of execution. It bundles one or more (asset, rule-suite) pairs and runs them as a single job — manually with Run now or automatically on a schedule.
Data assets
A data asset is one table, one view, or one parquet dataset that you want PLACEHOLDER Cloud to look after. Assets belong to a datasource; rule suites and profile runs belong to assets.
Datasources
A datasource in PLACEHOLDER Cloud is one logical place data lives — a Postgres database, a Snowflake account, an S3 prefix. You connect a datasource once and PLACEHOLDER Cloud reuses that connection to profile assets, run checkpoints, and discover schemas.
Incidents
Status: new. The in-app incident lifecycle ships with this release — manual + auto creation, triage/assign/resolve, and a timeline are live. The notification fan-out (assignee alert on open, resolution notice, daily digest), resolution auto-link to the first passing run, and bidirectional Jira/ServiceNow status sync are planned follow-ups under #411.
Lakehouse checks (Iceberg + Delta)
PLACEHOLDER Cloud treats Apache Iceberg and Delta Lake tables as first-class datasources. You connect a catalog, point at a table, and write the same rule suites you would for a Postgres or Snowflake asset — PLACEHOLDER Cloud handles the snapshot read for you. Two new expectation types layer on top so you can alert on snapshot-level concerns no row-DB adapter can replicate.
MCP server
Status: available (self-host); hosted endpoint rolling out. The MCP server is the first-class way to drive the platform with AI — bring your own MCP client (Claude, Cursor, the claude CLI) rather than an in-app chatbot. You can run it yourself today (Dockerfile.mcp, or the mcp service in infra/docker-compose.yml). A hosted public endpoint on PLACEHOLDER Cloud's fleet (the dq-cloud-mcp service) is being finalized behind a public load balancer — once live, its URL appears in Settings → Connect AI. Authentication is by a personal API key (dqk_…) carried as a bearer; OAuth-2.1 + Dynamic Client Registration is on the roadmap (see Roadmap below).
Multi-tenancy
PLACEHOLDER Cloud is schema-per-tenant multi-tenant. One Postgres database hosts every org's metadata; each org gets its own schema for its tenant-scoped data (datasources, assets, suites, results, anomalies, suggestions).
Profile runs
A profile run is a statistical snapshot of a data asset taken at a point in time. PLACEHOLDER Cloud uses profile runs for three things: surfacing column metadata in the UI, seeding AI rule suggestions, and detecting anomalies against a rolling baseline.
Root cause analysis
Status: first cut (FEATURE-410) — this slice ships the heuristic correlation surface and an optional AI narrative. Several signal families and the ML side are deferred; see What's deferred below.
Rule Groups
Status: in preview (#640). Rule Groups are the MeasuredCloud core-model tier-1 runnable unit and ship alongside Checkpoints and Rule Suites today — both navigation entries stay until the cutover (#642) makes Rule Groups the canonical authoring surface. Agent-mode datasources are not runnable as group members yet (#688).
Rule suites
A rule suite is a named set of expectations — declarative assumptions about your data — that PLACEHOLDER Cloud runs against a data asset. A suite is the unit of authoring; a checkpoint is the unit of execution.
Validation results
A validation result in PLACEHOLDER Cloud is what a checkpoint run produces — one row per (asset, rule-suite) pair inside the checkpoint. It records whether every expectation passed, the failing rows (when available), and metadata about the run.