Understand the model
Neksur governs each dataset through one Data Contract binding three coupled dimensions — Meaning, Access, State — over one lifecycle. Read the concepts →
Neksur Documentation
The Data Contract Plane for open lakehouses on Apache Iceberg. One Contract per dataset — Meaning, Access, and State — honored by every engine, catalog, and AI agent.
Start here
Section titled “Start here”Ship your first contract
Install Neksur, point it at a catalog, and reject a non-compliant Iceberg commit in ~30 minutes. Getting started →
Connect your engines
Route Spark writes through the gateway, and Trino / BI / AI-agent reads through the policy-enforcing proxy. Connection guides →
Reference
The REST API, the neksur-cli, and the CEL policy language.
Browse the reference →
Explore
Section titled “Explore” Concepts Data Contract, dimensions, lifecycle, enforcement, editions.
Guides Connect engines, author policies and metrics, ship a Contract, prove compliance.
Architecture System design, the commit pipeline, the graph, the ADR index.
Deployment Production deploy, HA, backup/DR, infrastructure, Spark.
Licensing Editions, the four additive tiers, and the BSL.
REST API Gateway, lineage, and the broader API surface.