On a Tuesday, the first enterprise question is usually not can you capture AI code? It s who can see the records, how long do they live, and what happens when a policy blocks a change?
That s the part LineageLens is built for. Base gives you local capture. Lite gives a shared team record. Plus and Max move the data into a backend where auth, permissions, retention, and policy live next to the provenance records instead of around them.
The useful thing here is not another dashboard. It s a self-hosted record of prompt, model, tool, file, and outcome that engineering, security, and platform teams can actually govern on their own infrastructure.
I keep seeing AI governance tools start with visibility, then discover that the real enterprise questions are identity, retention, and review. If the record cannot be scoped, retained, and exported on your side, it is not really governable.
In v60, we added AI features to all plans, including Open Source. With v61, we give you the controls for AI governance that make it yours to deploy safely.
Some call it the Fun Police. We prefer: AI that s realistic for orgs of all types to roll out, including those who need tighter oversight over who gets to use it (bit of a mouthful though).
