PLACEHOLDER Cloud documentation

A self-hostable data-quality platform. You connect a datasource, profile assets, author rule suites, schedule checkpoints, review validation results, and react to anomalies. PLACEHOLDER Cloud is powered by the open-source Great Expectations validation engine; the API, worker, and UI are first-party.

This is the user-facing documentation. If you're working on PLACEHOLDER Cloud as a contributor or an AI agent, the contributor guide is in AGENTS.md at the repo root.

Where to start

You arrive at this product with one of three jobs in mind. Pick the matching guide.

• You want to try PLACEHOLDER Cloud right now. The Quickstart is the five-minute path from git clone to a green validation result — pick the Docker-only path (make compose-up) or the local-dev path (uv + Node, hot-reload).
• You're standing up a fresh PLACEHOLDER Cloud deployment. Read Self-host and then Run your first checkpoint.
• You're a data engineer who needs to add a new datasource or rule. Skim the Concepts you'll need (datasource, data asset, rule suite, checkpoint) and then use the How-to that matches the task.
• You're an operator hardening a production deployment. Start with Deploy to production and the Configuration reference.

Layout

Section	What you find there
getting-started/	The Quickstart, then the longer self-host / first-checkpoint / inviting-teammates walkthroughs.
concepts/	One page per first-class object in PLACEHOLDER Cloud. Definitions, data model, operations.
how-to/	Task-oriented recipes — connect a Postgres datasource, create an API token, connect an MCP client, configure SAML / OIDC SSO, set up Slack alerts, search across objects with Cmd+K, get help in-app, export validation results to CSV, build a quality report, run checkpoints from Apache Airflow, model checkpoints as Dagster asset checks, self-host with Docker Compose, deploy with Docker, rotate a secret key, deploy to production.
reference/	The API surface, the dqc CLI, the env-var configuration table, an architecture overview, and a glossary.

Conventions

• Examples assume PLACEHOLDER Cloud lives at https://placeholder.example.com. Replace with your own hostname.
• PLACEHOLDER in screenshots and code stands in for whatever your operator named the workspace.
• Anything marked > Status: planned (FEATURE-N) is on the roadmap but not yet shipped. The linked ticket describes the planned shape.

Status callouts you'll see

Several pages document features that are still in flight. They open with a callout like:

Status: planned (FEATURE-1) — Snowflake datasources are not yet wired through the test / discover paths. Track the linked ticket for progress.

These callouts exist so you aren't misled about what works today. If you find a page without one but the feature isn't working as described, file an issue.