CNCF Landscape includes Bytebase as the first-ever database CI/CD solution Check Now

Bytebase 1.0.0

2 min read

๐Ÿš€ Announce our Team Plan

With over a year of hard work and 3500+ commits, we finally reach the milestone to announce our 1.0.0 version and our Team Plan. The Team Plan includes:

  • Role-Based-Access-Control (RBAC) with Owner, DBA, Developer roles catering to the collaboration during database development.
  • Login using GitLab account.
  • Sync project membership from the linked GitLab project.
  • SQL backward compatibility check and schema drift detection.
  • Per-environment schema review and backup policy.

The price starts at $29 per instance per month. Please visit our pricing page for more details. _ You can visit to purchase a subscription license and manage your team plan subscription in Settings page. _

๐ŸŽ„ Enhancement

SQL Editor

  • Add an EXPLAIN button adjacent to the run button.


  • Redesign the database connection navigation and connection status.


  • Run non-SELECT SQL navigate to the different workflow.


Sync project members from GitLab

If a project is linked with GitLab repository, one can sync that repository's membership to the project's membership. __Membership from the linked GitLab repository

Improved tenant project pipeline UI

We improve the layout for showing the current database schema change progress across all tenants. _


  • Switch to use PostgreSQL for storing Bytebase metadata. This enables us to handle more complex scenarios down the road.
  • Add quickstart for preparing an environment including Bytebase, GitLab (macOS Apple Silicon) and ClickHouse Cluster.

๐Ÿž Bug fix

SQL Editor

  • Query result table cover display.
  • Query result table attributes order.

๐ŸŒ„ Sunset

Retire issue rollback feature Previously, Bytebase allows user to specify a rollback SQL for the rollback. And if user chooses to rollback the SQL, Bytebase will use the rollback SQL to create that rollback SQL. This only sounds good in theory, because in reality, it's already a big hurdle to write a good schema change SQL, it would be even challenging to ask the developer to provide a correct rollback SQL at the same time.

Thus, we decide to retire this feature. Meanwhile we already have ideas for a much better solution without requiring developer to write the rollback SQL manually. Please stay tuned.

๐ŸŽ  Community

๐Ÿ“• Upgrade instruction

For fresh installation, follow

If you upgrade from the previous version, there is some breaking schema change. Please contact and we will help you manually upgrade to the new version.