Solutions · On Microsoft Fabric
Govern your Microsoft Fabric lakehouse with contracts.
LakeLogic runs on Fabric via PySpark. Define contracts across your medallion layers, enforce them at PR time, and let Zeus resolve incidents. Your data stays in OneLake; we read metadata only.
Governed in FabricMetadata only
Bronzeraw_tripsContracted
SilvertripsContracted · PII classified
Goldrevenue_dailyContracted · SLO 1h
Native PySpark notebookRuns in placeno rip-and-replace, no data movement
OneLaketable names, schemas, lineage and row counts are read, never row values
Fabric CIPR-time gatesschema drift blocked before it reaches a Gold table
Quarantine at runtime279 rows heldbad rows route out; consumers keep the last good version
Your data never leaves FabricApache 2.0 core
What you get
6 capabilities
Runs where your data already lives
native PySpark on Fabric, no rip-and-replace
Contracts across the medallion
Bronze → Silver → Gold quality, ownership, and PII per tier
Your data stays in OneLake
metadata only: schemas, lineage, row counts; never row values
PR-time gates in your Fabric CI
block schema drift before it reaches a Gold table
Zeus resolves Fabric incidents
diagnoses failed runs with contract + lineage context
Quarantine bad rows at runtime
bad data routes out before it reaches reporting
Bring contract governance to Fabric.
See LakeLogic governing a live Fabric medallion estate: contracts, gates, lineage, and Zeus, with zero data egress.