Question 1

How does contract auto-generation work?

Accepted Answer

Connect your repo (GitHub, GitLab, Azure DevOps). LakeLogic scans your SQL, dbt models, and Spark jobs, infers schemas and dependencies, then generates production-ready contracts automatically.

Question 2

How are contracts enforced?

Accepted Answer

Contracts validate at runtime or in CI/CD. If a change violates a contract (schema drift, quality rule failure), the pipeline fails early — bad rows route to quarantine with exact failure reasons.

Question 3

Can business users define context without YAML?

Accepted Answer

Yes. The visual Contract Studio lets non-technical users add business context, ownership, and SLAs. Changes sync back to your version-controlled source of truth automatically.

Question 4

Is my data secure?

Accepted Answer

We only parse metadata (table names, column names, lineage) — never your actual row-level data. Telemetry from your OSS pipelines carries rule names and row counts only. SOC 2 Type II certification is on our roadmap.

Engineering essays

from the data trust front

The Global Standard: Understanding the Open Data Contract Standard (ODCS)

Data Contracts Explained: Why 'Shifting Left' is the Future of Data Quality

Implementing Data Mesh: From Principles to Practical Domain Ownership