Building the Future.

• Open-source runtime engine
• 8 engine support (Spark, DuckDB, Polars, Snowflake, BigQuery, Databricks, Redshift, Fabric)
• CLI + Python API
• Unlimited contracts
• Quarantine & materialization
• Community support

• Visual lineage mapping
• AI contract generation
• Git repository sync
• Slack notifications
• Email support (48-72hr)

• PR impact analysis
• Data quality scoring
• Collaborative workflows
• Advanced lineage features
• Public API

Jira tickets tagged @zeus or with the zeus-auto-remediate label trigger an autonomous triage loop. Zeus reads the ticket, gathers context from the contract registry + lineage + run logs, and posts an RCA comment with a suggested next action. Human still drives.

• Jira webhook → Zeus triage loop
• Auto-RCA from logs + quarantined rows + lineage
• Suggested fix + sandbox dry-run evidence in the ticket
• Estimated delivery rule-based (simple YAML / schema migration / etc.)
• Dynamic labels: rca-complete · awaiting-human-approval

Zeus opens a draft PR linked to the ticket with the proposed contract change, runs CI inside a sandbox, and posts the run evidence back into Jira. Engineers review and merge.

• Draft PR with sandbox proof (Good / Quarantine / Ratio)
• Multi-turn Jira comments (Zeus answers reviewer questions)
• Status transitions: Backlog → In Progress (Zeus) → Awaiting Review
• Learned ETA from your historical PR-review + deployment cadence
• Hard guardrails: schema migrations always require human approval

Enterprise hardening plus narrowly-scoped auto-merge for low-risk change classes (new optional field, additive row-rule). Feature-flag gated; per-org allowlist of change types.

• Auto-merge for safe, additive changes only
• On-premise deployment
• SSO / SAML integration
• Custom SLA + dedicated success manager
• SOC 2 Type II