Guides
Sep 2, 2021
What happens when the database isn't code
Schema lives outside version control
Application code has a single source of truth in Git; the database schema lives in someone's client, a wiki page, and three slightly different environments. No one can say what production actually looks like.
Changes bypass review and CI
A migration runs by hand, skipping the pull request, the lint, and the test suite every other change clears. The first review happens in production.
No history, no rollback
Without versioned migrations there's no diff, no author, no way back. Reproducing an environment means reverse-engineering it from a running database.
How Bytebase makes your database as code
Schema and migrations in version control
Your schema and every change live in Git as the single source of truth, reviewed and deployed through the same pipeline as application code.
Schema as code in Git
Track the full schema and every migration in version control, so the repository — not a running database — is the source of truth.
GitOps change flow
Changes arrive as pull requests, get reviewed and approved, and deploy automatically on merge — no out-of-band SQL.
Declarative or migration-based
Define the desired state and let Bytebase diff it, or manage versioned migration scripts — whichever model your team runs.
Automated review and deploy in your pipeline
Every change clears automated SQL review and ships through CI/CD, so the database moves at the same speed and safety as the rest of your stack.
Automated SQL review
100+ built-in rules catch unsafe migrations — missing indexes, locking DDL, backward-incompatible changes — before they merge.
CI/CD deployment
Wire migrations into GitHub, GitLab, or Bitbucket; deployment runs in the same pipeline as the application.
Rollback built in
Every change carries its diff and a generated rollback plan, so reverting is a click, not a rebuild.
One source of truth across every environment
A live schema catalog keeps dev, staging, and production in sync with what's in Git — drift surfaces the moment it appears.
Drift detection
Compare any environment against the versioned schema and catch out-of-band changes before they cause an incident.
Reproducible environments
Stand up a new environment from the repository, not a hand-copied database dump.
Full change history and audit
Every migration is logged with author, diff, and timestamp — an audit trail you don't assemble by hand.
One database-as-code platform, controls for every team
Integrations
Designed to integrate across modern enterprise environments
Bytebase connects to databases, developer tooling, and collaboration platforms to fit naturally into complex, multi-tool enterprise ecosystems.
Resources
