When to Use GitOps
- Colocate database and application changes. Your database schema lives in the same repository and goes through the same CI/CD pipeline as your application code.
- Consistent multi-environment deployment. A single merge fans out changes to all target databases — test, staging, production — with the same rollout and approval controls.
- Faster iteration. Developers use the same pull request workflow for both application and database changes — no context switching, no separate approval process.
- AI agent friendly. SQL files in Git are easy for AI coding agents to read, modify, and submit as pull requests.
Next Steps
Get Started
Set up GitOps with Bytebase step by step

