Yearning
Every ALTER TABLE and bulk UPDATE bound for production passes through Yearning first, where an AI reviewer reads the SQL, approvers sign off, and a frozen record shows who ran what. The precheck parses up to 100,000 statements per order, groups look-alike statements into fingerprint groups, and lets the AI inspect real table metadata, indexes, and EXPLAIN plans through five read-only tools. Forty-eight built-in rules, plus your own prompt skills and DBA knowledge entries, turn violations into blocking findings. Cloud models see only anonymized SQL, or reviews can be routed to vLLM or Ollama on a private network. Orders move through serial datasource stages, such as staging then production, with up to ten approval steps each and designated executors who run or schedule the change. MySQL ALTER TABLE statements run through a built-in gh-ost with live copy progress, and captured before-images let one click generate a linked rollback order for MySQL, PostgreSQL, TiDB, OceanBase, and PolarDB. A query workspace grants time-bounded read-only access with column masking and export controls, while diagnostics chart top SQL and draft index fixes. A scoped AI assistant writes SQL from plain English without executing it. Sign-in works with LDAP or OIDC, notifications go out by email, DingTalk, Feishu, or Slack, and an OpenAPI plus an agent skill lets Claude Code or Codex submit orders and run prechecks. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0-or-later licensed.
Deploy