|
1 | 1 | --- |
2 | | -title: Why Bytebase |
| 2 | +title: What's Bytebase |
3 | 3 | --- |
4 | 4 |
|
5 | | -Our founding team previously built the Google Cloud database and API infrastructure. We envision Bytebase |
6 | | -to be the GitLab/GitHub equivalent for **Database DevSecOps**, specifically built for the developer, security, DBA and platform engineering teams. |
| 5 | +**Bytebase: The DevSecOps Control Plane for Your Databases** |
7 | 6 |
|
8 | | - |
9 | | - |
10 | | -Bytebase is a **middleware** sitting between you and your database. It can be used in 2 ways: |
11 | | - |
12 | | -- **GUI** - Bytebase provides a point-and-click collaboration workspace for teams to manage database development tasks for all database systems. |
13 | | -- **API (headless)** - Bytebase can go headless. Teams can leverage [Bytebase API](/integrations/api/overview/) as the database operation backend and integrate with their own development workflow. |
| 7 | +Bytebase is the DevSecOps platform that sits between your team and your databases. Built by the team that previously created Google's Cloud database and API infrastructure, it acts as a centralized control plane to deliver two critical outcomes for engineering leaders: **better security and compliance**, and **improved productivity and reliability**. |
14 | 8 |
|
15 | | -## 3-in-1 |
16 | | - |
17 | | - |
18 | | - |
19 | | -Bytebase is an all-in-one solution for database development lifecycle management. It replaces fragmented database tools and unifies the workflow in a single place. Check [all the tools Bytebase replaces](https://www.bytebase.com/blog/all-database-tools-bytebase-replaces). |
| 9 | + |
20 | 10 |
|
21 | | -## Key Features |
| 11 | +It's a unified platform specifically built for your **developer, security, DBA, and platform engineering teams** to collaborate. Its value becomes particularly critical as your organization grows, reducing the friction of managing a large number of databases and instances. Bytebase achieves this by consolidating two distinct workflows. |
22 | 12 |
|
23 | | -[Database CI/CD and Change Automation](/change-database/change-workflow/) |
| 13 | +## 1. For Productivity & Reliability: Managing Schema Changes at Scale 🚀 |
24 | 14 |
|
25 | | -Like code review, Bytebase streamlines the database change process. Within a single workflow, a database change can be requested, reviewed, approved and deployed from the dev environment all the way to the production environment. It also supports [automated SQL Review](/sql-review/overview/) and [GitOps (Database-as-Code)](/vcs-integration/overview/). |
| 15 | +This section covers how Bytebase makes all database changes safer and more efficient. By providing a structured process, it also enhances security by **eliminating the need for engineers to make direct changes against databases**. Bytebase supports two distinct workflows for schema changes: |
26 | 16 |
|
27 | | -[SQL Editor](/sql-editor/overview/) |
| 17 | +**UI-driven Workflow**: Provides a complete, console-based process with built-in risk analysis and multi-step approvals, offering a secure and self-contained way to manage schema changes. |
28 | 18 |
|
29 | | -A web-based SQL Editor to query and export data. DBAs no longer need to give away sensitive database credentials when developers need to access the data. |
| 19 | +**GitOps Workflow (Database-as-Code)**: Features a full GitOps workflow that integrates with your provider (GitHub, GitLab, Bitbucket, Azure DevOps) and existing CI/CD pipelines, allowing developers to manage database migrations entirely as code. |
30 | 20 |
|
31 | | -[Database Permission](/security/database-permission/overview/) |
| 21 | +In addition to these workflows, the platform provides overarching capabilities for reliability and scale: |
32 | 22 |
|
33 | | -Bytebase provides a suite of features to enable organizations to enforce data security policies, avoid data leaks and conform compliance. |
| 23 | +**Fleet-wide Batch Changes**: Manage and apply schema changes across a collection of databases in a single, coordinated workflow, dramatically reducing manual effort. |
34 | 24 |
|
35 | | -[Dynamic Data Masking](/security/data-masking/overview/) |
| 25 | +**1-Click DML Rollback**: Provides streamlined, 1-click rollback for data changes (DML), allowing for instant recovery from unintended UPDATE or DELETE statements. |
36 | 26 |
|
37 | | -Bytebase provides role-based multi-level masking policy with approval workflow to grant unmasked data access. |
| 27 | +## 2. For Security & Compliance: Governing Data Access at Scale 🛡️ |
38 | 28 |
|
39 | | -[1-click Rollback](/change-database/rollback-data-changes/) |
| 29 | +This workflow governs how your database data is accessed, replacing the need for disparate SQL clients and shared credentials. |
40 | 30 |
|
41 | | -Bytebase provides streamlined 1-click data rollback. |
| 31 | +**Centralized Access Control:** Grant data query permissions based on role, not on sharing database passwords. This provides a single place to manage who can see what across your entire environment. |
42 | 32 |
|
43 | | -[Batch Change and Query](/change-database/batch-change/) |
| 33 | +**Compliance & Data Security:** Enforce **dynamic data masking** to protect sensitive PII and maintain a complete audit log of every query for compliance with standards like GDPR and CCPA. |
44 | 34 |
|
45 | | -Bytebase allows you to change a collection of databases in a single workflow. It also allows you to issue |
46 | | -a single query against multiple databases. |
| 35 | +**Efficient Cross-Database Querying:** The web-based SQL Editor allows you to issue a **single query against multiple databases** simultaneously, ideal for analytics and operational oversight. |
47 | 36 |
|
48 | | -[API](/integrations/api/overview/) |
| 37 | +In short, Bytebase unifies the process of **changing the database** with the **process of accessing its data**, giving you a single pane of glass for true database DevSecOps. |
49 | 38 |
|
50 | | -Bytebase GUI is built on the public Bytebase API. In theory, 3rd-party can build a new Bytebase |
51 | | -GUI based on the same API. |
| 39 | + |
52 | 40 |
|
53 | | -## Compare with Liquibase / Flyway / schemachange |
| 41 | +## How Bytebase Compares: Schema Migration Tools |
54 | 42 |
|
55 | | -If Liquibase, Flyway are Git, then Bytebase is GitLab/GitHub. And as an open source project, Bytebase |
56 | | -is growing way faster and ranked No.1 among alternatives. |
| 43 | +While Liquibase and Flyway are powerful command-line migration tools (think Git), Bytebase provides the complete platform experience (think GitHub/GitLab). It wraps these migration capabilities in a collaborative interface with approval workflows, audit trails, and enterprise controls. As the fastest-growing open source solution in this space, Bytebase has become the top choice for teams seeking a unified database DevSecOps platform. |
57 | 44 |
|
58 | 45 |  |
59 | 46 |
|
60 | 47 | - [Bytebase vs. Liquibase](https://www.bytebase.com/blog/bytebase-vs-liquibase/) |
61 | 48 | - [Bytebase vs. Flyway](https://www.bytebase.com/blog/bytebase-vs-flyway/) |
62 | 49 | - [Bytebase vs. schemachange](https://www.bytebase.com/blog/snowflake-schema-change/) |
63 | 50 |
|
64 | | -## Compare with CloudBeaver |
| 51 | +## How Bytebase Compares: SQL Clients |
65 | 52 |
|
66 | | -Both have web-based SQL clients. Additionally, Bytebase offers review workflow, more collaboration and security features. |
| 53 | +Traditional SQL clients like DBeaver, DataGrip, and Navicat excel at individual database access but weren't built for team collaboration or enterprise security. Bytebase transforms SQL access from a personal tool into an enterprise-ready platform—providing not just query capabilities, but also role-based permissions, data masking, audit logging, and centralized governance that eliminates the need to share database credentials. |
67 | 54 |
|
68 | 55 |  |
69 | 56 |
|
70 | | -[Bytebase vs. CloudBeaver](https://www.bytebase.com/blog/bytebase-vs-cloudbeaver/) |
71 | | - |
72 | | -## Compare with DBeaver / DataGrip / Navicat |
73 | | - |
74 | | -SQL GUI Client such as DBeaver, DataGrip, Navicat provide a GUI to interact with the |
75 | | -database. Bytebase not only provides a GUI client, it can also enforce centralized data access control for data security and governance. |
76 | | - |
77 | 57 | - [Bytebase vs. DBeaver](https://www.bytebase.com/blog/bytebase-vs-dbeaver/) |
78 | 58 | - [Bytebase vs. DataGrip](https://www.bytebase.com/blog/bytebase-vs-datagrip/) |
79 | | -- [Bytebase vs. Navicat](https://www.bytebase.com/blog/stop-using-navicat/) |
80 | | - |
81 | | -## Compare with Metabase |
82 | | - |
83 | | -Metabase is a data visualization and business intelligence (BI) tool. It's built for data teams and business analysts |
84 | | -to make sense of the data. |
85 | | - |
86 | | -Bytebase is a database development platform. It's built for the developer teams to perform database operations during the application development lifecycle. |
87 | | - |
88 | | -[Bytebase vs. Metabase](https://www.bytebase.com/blog/bytebase-vs-metabase/) |
89 | | - |
90 | | -## Compare with Jira |
91 | | - |
92 | | -Jira is a general-purpose issue ticketing system. Bytebase is a database domain-specific change management system. |
93 | | -Bytebase provides an integrated experience to plan, review, and deploy database changes. |
94 | | - |
95 | | -[Bytebase vs. Jira](https://www.bytebase.com/blog/use-jira-for-database-change/) |
| 59 | +- [Bytebase vs. Navicat](https://www.bytebase.com/blog/stop-using-navicat/) |
0 commit comments