The problem: SQL migrations remain the weak link in DevOps
Application code goes through a pull request: clear diff, mandatory review, CI green before merge. The SQL migration often arrives via message or shared file, is run manually on the production server, and if something goes wrong — manual rollback, in the best case.
Bytebase closes this gap. It imposes an explicit workflow: the developer submits the migration, a reviewer sees the diff, automatic lint rules run (missing index, missing WHERE clause, naming convention violations), then the migration is applied in order: env → staging → production. Each step is timestamped and searchable in an immutable audit log.
What Bytebase adds to your stack
- Structured SQL review: 200+ built-in rules detect common anti-patterns before the migration reaches production
- Multi-environment pipeline: dev → staging → prod with approval gates and rollback at each step
- Web access without direct credentials: developers query production through Bytebase's SQL editor — credentials never leave the server
- Complete audit trail: every query, migration, approval and rejection is logged with author name and timestamp
- GitOps integration: connect GitHub or GitLab, Bytebase detects new migration files and opens a review task from the PR
- 20+ supported engines: PostgreSQL, MySQL, MariaDB, MongoDB, Redis, ClickHouse, SQL Server, Oracle, TiDB and more
Architecture: one container, zero external dependencies
Bytebase runs as a single Docker container with an embedded PostgreSQL instance. No external database to provision, no Redis, no separate workers — just one docker run and port 8080. Version 3.21.1 (August 2026) is about 120 MB compressed and starts in under 20 seconds on a 1 GB VPS.
It then connects to your existing (or new) database servers as a client — it does not replace your PostgreSQL or MySQL, it connects to them to orchestrate changes. Your data infrastructure stays intact.
Deploy Bytebase on ServOrbit in 15 minutes
Order a VPS and deploy from the Marketplace
In your ServOrbit dashboard, choose a 1 GB+ RAM plan (2 GB for teams), open the Marketplace under Development and click Deploy on the Bytebase card. Docker is installed and the container starts automatically.
Create the admin account
Navigate to https://your-domain (if a domain is attached) or open an SSH tunnel — ssh -L 8080:127.0.0.1:8080 root@<ip> — then open http://localhost:8080. The first-run wizard asks you to create your admin account: email and password.
Add your first database instance
In the interface, click Instances → Add instance. Enter the engine type (PostgreSQL, MySQL…), host, port and credentials. Bytebase tests the connection, discovers databases and schemas, and shows them in the tree.
Configure environments
In Environments, define your environments (Dev, Staging, Production) and associate each instance with its environment. You can require mandatory human approval for production migrations.
Submit and approve a migration
Click New Issue → Database change. Write your SQL, select target databases, add a reviewer and submit. The reviewer gets a notification, sees the diff and lint results, then approves or requests a correction. Bytebase applies in environment order and logs every action.
GitOps: trigger reviews from your pull requests
Bytebase connects to your GitHub or GitLab repository. Configure the migration path (e.g. db/migrations/) and file pattern (e.g. V{{version}}__{{description}}.sql). Every PR adding a file in that path automatically opens a review task linked to the PR: migration status (pending, approved, applied) appears directly in the GitHub PR.
This integration closes the DevOps loop: code and migration travel together in the same PR, are reviewed by the same people, and deployed in a coordinated way.
Bytebase vs alternatives
| bytebase | liquibase | flyway | |
|---|---|---|---|
| Web review interface | ✅ Built-in | ❌ CLI only | ❌ CLI / plugin |
| Automatic SQL lint | ✅ 200+ rules | ⚠️ Limited | ❌ No |
| Secure web SQL access | ✅ Yes | ❌ No | ❌ No |
| Audit trail | ✅ Complete | ⚠️ Basic | ⚠️ Basic |
| Self-hosted, single container | ✅ Yes | ✅ Yes (CLI) | ✅ Yes (CLI) |
Team use: access without direct credentials
For teams, Bytebase's SQL editor replaces direct production access. You grant developers access to Bytebase — without giving them the database credentials. Bytebase proxies all queries, enforces masking policies on sensitive columns (email, phone, card number), and keeps a log of every operation.
In case of an incident, you can find exactly who ran what query, when, on which database. This is a prerequisite for SOC 2, ISO 27001 or GDPR compliance.
Community Edition: free and unlimited users
The Community Edition covers the full change management workflow, SQL editor, audit trail and GitOps integrations. Enterprise features (SSO, fine-grained RBAC, advanced data masking, custom approval workflows) are available in the paid plan. For most self-hosted teams, the Community Edition is sufficient.
