Why it matters
Answering "why did this check fail?" or "which contracts hold unprotected personal data?" usually means opening several tools. Zeus answers from your organisation's estate: contracts, lineage, incidents, the knowledge base and governance context. Anything it writes is a draft for a person to review.
What you can do
- Ask about your contracts, lineage and incidents.
- Find out why a pipeline run or a quality check failed.
- Get a draft contract, or a change to one, to review.
- Get suggested quality rules for a table.
- Get SQL for a question about your data.
- Find contracts with unprotected personal data.
- With Jira connected, have Zeus create a ticket, add a comment, move its status or search issues, in the projects that connection can see.
In a workspace with no contracts yet, Zeus can explain how LakeLogic works, draft a first contract from a schema or sample you paste, and write SQL from a description of your tables.
How to do it in LakeLogic
- Open Ask Zeus in the sidebar, directly below Home (
/ai-assistant). Or press Ctrl+J (Cmd+J on Mac) to open the Zeus dock beside the page you are on. - Type your question and send it. On the Ask Zeus page you can also use voice input.
- If the answer contains contract YAML and the Contract Editor is open, use the apply button on the block to put it in the editor. A block that is not valid OLC gets no button; ask Zeus to correct it.
- From the dock, Open Zeus workspace moves the conversation to the full page.
In Slack, once it is connected with a bot token, mention @LakeLogic or use /zeus. See
Connect the tools your data team already uses.
What you get
- Conversations you can rename, pin, delete, search and group into folders.
- From More actions: Save as note, Save as Template (a prompt teammates can reuse), Export as Markdown and Share conversation. A shared link is read-only; a follow-up from it starts the reader's own private conversation.
- Drafts, never published changes. A draft goes through the same review, gates and pull request as any other change. See Approve every contract change with evidence.
Good to know
Credits. Calls on LakeLogic's own provider key use Zeus credits. Calls on your own provider key or a self-hosted model use none.
| Plan | Credits |
|---|---|
| No plan (read-only workspace) | Zeus is not available. See Choose the plan that fits. |
| Trial | 2,000 for the whole trial |
| Paid plans | A monthly pool set by your plan's capacity band |
| Enterprise | Agreed per contract |
On a paid subscription the month runs from your subscription date; otherwise it is the calendar month (UTC). When the pool is used up, Zeus calls on LakeLogic's key stop until it resets. If credits cannot be measured, the call is allowed. See Track and control AI spend.
Providers. An organisation admin chooses the provider and model under AI → Models & routing:
| Source | Who pays the provider | Credits |
|---|---|---|
| LakeLogic-managed | LakeLogic | Yes |
| Your own API key | You | No |
| Self-hosted (Ollama, Hugging Face TGI) | Runs on your infrastructure | No |
Choices include OpenAI, Anthropic, Google Gemini, Azure OpenAI, DeepSeek, OpenRouter, NVIDIA NIM and Hugging Face.
Teams. Zeus does not answer in Microsoft Teams; Teams receives alerts only.
Your own assistant. Claude, Cursor or Copilot can connect over MCP with no Zeus credits. See Connect your AI assistant.