Bytebase
- 0 ratings
Safe database schema change and version control for DevOps teams, supports MySQL, PostgreSQL, TiDB, ClickHouse, and Snowflake.
Deploy this app to Linode with a free $100 credit!
🔥 Live Demo • ⚙️ Install • 📚 Documentation • 🙋♀️ Get Instant Help
Different database development tasks
Multiple database systems
Unified process
Single tool
🪜
Want to formalize the database change process but don't know how?
| Standard Operating Procedure (SOP) Standardize the database schema and data change process across different database systems, small or large tables and different tenants. SQL Review 100+ lint rules to detect SQL anti-patterns and enforce consistent SQL style in the organization. GitOps Point-and-click GitHub and GitLab integration to enable GitOps workflow for changing database. |
 |
🔮
Want to control the data access but don't know how?
| All-in-one SQL Editor Web-based IDE specifically for performing SQL specific tasks. Data Anonymization State-of-the-art column level anonymization engine to cover complex situations like subquery, CTE. Database Access Control Organization level policy to centralize the database access control. |
 |
👩💼
Want to enforce organization policy and monitor database activity but don't know how?
| Manage Database Resources A single place to manage environments, database instances, database users for application development, with optional Terraform integration. Policy Enforcement Enforce organization wide SQL Review policy, backup policy and data access policy. SQL Editor Admin mode CLI like experience without setting up bastion. |
 |
🔒
Want to avoid data leakage, change outage and detect malicious behavior but don't know how?
| Centralize Change, Query and Admin Tasks A single place to perform different tasks on different databases, thus enforce policy and monitor activity accordingly. RBAC Two-level RBAC model mapping to the organization wide privileges and application team privileges respectively. Anomaly Center and Audit Logging Capture all database anomalies, user actions and system events and present them in a holistic view. |
 |
Bytebase is a Database CI/CD solution for the Developers and DBAs. It's the only database CI/CD project included by the CNCF Landscape. The Bytebase family consists of these tools:
| Topic | |
|---|---|
| 🏗️ | Installation |
| 🎮 | Demo |
| 👩🏫 | Tutorials |
| 💎 | Design Principles |
| 🧩 | Data Model |
| 🎭 | Roles |
| 🕊 | Developing and Contributing |
| 🤺 | Bytebase vs Alternatives |
# One-liner installation script from latest release
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/bytebase/install/main/install.sh)"
Live demo at https://demo.bytebase.com
You can also book a 30min product walkthrough with one of our product experts.
| 🪶 | Dependency Free | Start with a single command ./bytebase without any external dependency. External PostgreSQL data store and others are optional. |
| 🔗 | Integration First | Solely focus on database management and leave the rest to others. We have native VCS integration with GitHub/GitLab, Terraform Provider, webhook, and etc. |
| 💂♀️ | Engineering Disciplined | Disciplined bi-weekly release and engineering practice. |
More details in Data Model Doc.
More details in Roles and Permissions Doc.
Bytebase employs RBAC (Role-Based-Access-Control) and provides two role sets at the workspace and project level:
Owner, DBA, Developer. The workspace role maps to the role in an engineering organization.Owner, Developer. The project level role maps to the role in a specific team or project.Every user is assigned a workspace role, and if a particular user is involved in a particular project, then she will also be assigned a project role accordingly.
Below diagram describes a typical mapping between an engineering org and the corresponding roles in the Bytebase workspace
Bytebase is built with a curated tech stack. It is optimized for developer experience and is very easy to start working on the code:
It has no external dependency.
1 command to start backend and 1 command to start frontend, both with live reload support.
Interactive code walkthrough
Follow Life of a Feature.
git clone https://github.com/bytebase/bytebaseair -c scripts/.air.tomlChange the open file limit if you encounter "error: too many open files".
ulimit -n 10240If you need additional runtime parameters such as --backup-bucket, please add them like this:
air -c scripts/.air.toml -- --backup-region us-east-1 --backup-bucket s3:\\/\\/example-bucket --backup-credential ~/.aws/credentialscd frontend && pnpm i && pnpm devBytebase should now be running at http://localhost:3000 and change either frontend or backend code would trigger live reload.
Either Flyway or Liquibase is a library and CLI focusing on schema change. While Bytebase is an one-stop solution covering the entire database development lifecycle for Developers and DBAs to collaborate.
Another key difference is Bytebase doesn't support Oracle and SQL Server. This is a conscious decision we make so that we can focus on supporting other databases without good tooliing support. In particular, many of our users tell us Bytebase is by far the best (and sometimes the only) database tool that can support their PostgreSQL and ClickHouse use cases.
Either Yearning or Archery provides a DBA operation portal. While Bytebase provides a collaboration
workspace for DBAs and Developers, and brings DevOps practice to the Database Change Management (DCM).
Bytebase has the similar Project concept seen in GitLab/GitHub and provides native GitOps integration
with GitLab/GitHub.
Another key difference is Yearning, Archery are open source projects maintained by the individuals part-time. While Bytebase is open-sourced, it adopts an open-core model and is a commercialized product, supported by a fully staffed team releasing new version every 2 weeks.
Check out our FAQ.
Please login to review this project.
No reviews for this project yet.
Self-hosted tool for staying up-to-date with web-site conte…
Identity document verification using Machine Learning and G…
A powerful data logger for Tesla vehicles.
Comments (0)
Please login to join the discussion on this project.