LakeLogic helps data platform teams agree what their tables should look like, enforce it where the data is processed, and see across the whole estate whether it holds.
The three parts
| Part | What it is | Where it runs |
|---|---|---|
| Open Lakehouse Contract (OLC) | The standard. A contract is a YAML file that describes a dataset: its schema, quality rules, ownership and how it is refreshed. | In your Git repository |
| LakeLogic Core | The open-source engine (Apache 2.0). It reads a contract and validates, quarantines and loads data on Spark, Polars or DuckDB. | In your environment |
| LakeLogic Platform | Where your team designs, builds, governs and operates data products: lakehouse projects designed and tested before they ship, contracts written and changed down to the field, and quality, governance and health tracked across the estate. | Hosted by LakeLogic |
Core is free and runs in your environment, so your pipelines keep running whatever your platform plan is. See Choose the plan that fits.
What the platform does
| You want to | In the platform |
|---|---|
| Stand up a lakehouse quickly | Lakehouse Studio: start a project from your sources, design bronze, silver and gold, and get the contracts generated |
| Test before anything reaches production | Run the project's contracts on generated data with deliberately broken rows, and see what passes, what is quarantined and why |
| Change a table safely | Contract Studio: edit fields, types and quality rules visually or in YAML; every change is a draft with its impact, delivered as a pull request |
| Keep contracts complete | Contract Health: find gaps in documentation and governance across your contracts |
| Know your rules cover what matters | Quality Rule Coverage: find fields and layers with no quality rule |
| Hold every contract to a standard | Standards: governance gates that check each change before it merges |
| Run it day to day | Incidents, service levels and notifications from your pipelines' telemetry |
| Work with AI | Ask Zeus, or your own assistant over MCP |
What you can achieve
The app's sidebar is organised by these outcomes.
Understand: know your estate
Find out what data you have, who owns it, how much is governed, and what depends on it. Sidebar items: Estate, Data Products, Environments, Lineage. See Know your estate and See downstream impact.
Build: design and test before you ship
Design your lakehouse and test a change before it reaches production. Sidebar item: Lakehouse Studio. See Design and test a lakehouse.
Govern: agree the rules and prove they hold
Define contracts, quality rules and standards, and keep the evidence. Sidebar items: Contracts, Standards, Compliance, Governance Posture. See Write a data contract, Stop bad changes and Approve changes with evidence.
Operate: keep data healthy
Monitor health and investigate when something breaks or arrives late. Sidebar items: Dataset Health, Incidents, Pipelines, Service Levels, Notifications. See Fix data incidents and Data freshness alerts.
AI: get answers grounded in your estate
Zeus is the platform's AI assistant. Ask Zeus sits at the top of the sidebar, below Home, because you can ask it about the estate, an incident or a change you are building. You can also use your own assistant over MCP. See Ask Zeus, Connect your AI assistant and Track AI spend.
Admin: set up the workspace
Admins manage AI, Team, Integrations, Notifications, Variables & Secrets and Billing. Integrations is the one place to connect a platform or tool. See Connect your tools.
Where to start
- Book a demo and start a trial.
- Connect your platform and run Discovery.
- Know your estate from what Discovery found.