PopSQL shuts down on September 1, 2026. Compare the top PopSQL alternatives for team SQL editing, dashboards, and governed database access before you migrate.

Top PopSQL Alternatives 2026: Where to Migrate Before the Shutdown

The best multi-database MCP servers in 2026. Compare DBHub, Google's MCP Toolbox for Databases, and Bytebase on engine breadth, host neutrality, and governance for connecting AI agents to more than one database. Single-engine Postgres servers are covered in a companion post.

Top 3 Open Source Multi-Database MCP Servers in 2026

The best open source Postgres MCP servers in 2026. Compare Postgres MCP Pro, Supabase MCP, and pgconsole on host neutrality, access model, and governance for connecting AI agents to PostgreSQL. Multi-database MCP servers are covered in a companion post.

Bytebase vs. SchemaHero: a side-by-side comparison for database schema migration

Money software is judged not on whether the feature works, but on what the database can prove eighteen months later. Fintech database governance through three principles: no invented data, no lost data, no trust.

Database Governance for Fintech: Guarding the Ledger

PostgreSQL has no ADD COLUMN ... AFTER. The reason one little number in a system catalog turned a "simple" feature into a decade-long engineering saga, and what you can do about it today.

Why It's So Hard to Add a Column in the Middle of a PostgreSQL Table

What a database MCP server actually hands an AI agent, how a query runs through one, and why a raw connection-string server is fine on your laptop but risky against production.

What is a Database MCP Server?

Most database MCP servers hand an agent a connection string and call it a day. The MCP server is the one place agent database access is governed or wide open.

Governed MCP vs. Raw MCP: How Agents Reach Your Database

AI agents are no longer just reading your database, they are authoring the migrations. The write path is a different risk class, and it needs its own gate.

When the Agent Writes the Migration, Who Approves It?

Generic PAM controls the database connection. Database PAM controls the SQL statement: per-query authorization and approval, SQL review, data masking, and statement-level audit. What the category means and why it exists.

What is Database PAM (Privileged Access Management)?

How to run SQL Server schema migrations safely in production, covering state-based vs migration-based workflows, online index operations, batched backfills, the expand-and-contract pattern, and CI/CD.

SQL Server Schema Migration and Change Management

CyberArk is a broad privileged access management (PAM) platform. Bytebase is a database-specific PAM for access control, masking, and SQL review. If you already run CyberArk, here is why you still need it for the database.

Bytebase vs. CyberArk: the database vertical in your PAM stack

How to store, rotate, and scope database credentials: secrets managers, dynamic credentials, the application path vs the human path, and the mistakes that leak passwords.

Managing Database Passwords and Secrets: Best Practices

The practical ways to audit MySQL activity, from the general query log to audit plugins, binlog CDC, and Bytebase, and where each one falls short.

MySQL Audit Logging Guide

Every critical asset has its system of record, except the database. Bytebase is the one. The standard for database development.

The Standard for Database Development

Dynamic data masking is chosen by access path, not product. Five approaches (engine-native, in-database, application, BI layer, and Bytebase) and which caller each one masks.

How to Implement Dynamic Data Masking: Five Approaches by Access Path

Static vs dynamic data masking, when each applies, how they differ on backups, performance, and reversibility, and when to run both.

Static vs Dynamic Data Masking: When to Use Which

The static data masking tools that produce safe non-production data, Delphix, Tonic.ai, and greenmask compared, plus how to roll your own when no tool fits.

Static Data Masking Tools (and How to Roll Your Own)

Compare BigQuery data masking options: native column-level dynamic data masking (built-in masking rules via policy tags and data policies, Dataplex catalog) and Bytebase fleet-wide masking.

BigQuery Dynamic Data Masking

Compare SQL Server data masking options, native Dynamic Data Masking (five mask types, SQL Server 2022 granular UNMASK) and Bytebase fleet-wide masking.

SQL Server Dynamic Data Masking

Compare Oracle data masking options. Native Data Redaction (five function types via DBMS_REDACT, EXEMPT REDACTION POLICY) and Bytebase fleet-wide masking.

Oracle Dynamic Data Masking

You write a one-line UPDATE against production. Here's the lane that keeps it safe: the four phases, the controls, and what each one prevents.

How to Handle Ad-hoc Database Data Changes?

Notes on the MySQL 9.7 LTS release: Hypergraph Optimizer in Community, JSON Duality View DML, Group Replication observability, and Dynamic Data Masking for Enterprise.

Notes on the MySQL 9.7 LTS release

Most DAC implementations stop at the connection. Real DAC operates at the statement and covers three vectors: machine, human, and AI agent.

What is Database Access Control (DAC)?

How to run dynamic data masking so it survives an audit: mask by role, go column-level, log unmask events, review policy changes in code, and keep environments in sync. Plus a vendor comparison and an end-to-end walkthrough.

Dynamic Data Masking Best Practices

How Bytebase audits the workflow layer: every SQL, schema change, approval, and export tied to a real user identity, with structured exports for any SIEM.

How Bytebase Handles Audit Logging

PostgreSQL 19 features I'm excited about: planner advisor framework, DDL extraction, online REPACK, pg_stat_recovery, parallel autovacuum, sequence sync, and 64-bit MultiXact.

PostgreSQL 19 features I'm excited about

Bytebase is HIPAA-compliant — independent verification that our administrative, physical, and technical safeguards meet the HIPAA Security Rule for handling Protected Health Information.

HIPAA Compliance

PAM tools gate the database connection. Databases also need SQL review, a schema change workflow, and per-statement approval. Here is where PAM stops and why most teams run it alongside Bytebase.

Bytebase vs. PAM: Why Database Teams Need More Than Privileged Access Management

What SOC 2 compliance audits actually want from your database audit log: not 'logging enabled' but evidence your auditor will accept. Lessons from going through our own audit.

SOC 2 Audit Log Requirements: Lessons From Our Own Audit

A side-by-side look at Bytebase and Atlas for database schema migration: how each one approaches migrations, their CI/CD and access control, supported databases, and what they cost. Updated for Atlas v1.1 and Bytebase 3.16.

Bytebase vs. Atlas: a side-by-side comparison for database schema migration

Database access control practices that hold up in a SOC 2 audit: least privilege, separation of duties, just-in-time access, statement-level enforcement, and the common mistakes that get flagged.

Database Access Control (DAC) Best Practices

A practical look at what SOX Section 404 expects from database changes: the four ITGC domains, the six questions auditors actually ask, and how to make compliance evidence a byproduct of your workflow.

Database Change Management for SOX Compliance

TRUNCATE and DELETE both remove rows, but they differ in speed, rollback behavior, and locking. Here is how each one behaves in PostgreSQL, MySQL, and SQL Server, and when to reach for which.

TRUNCATE vs DELETE in SQL: Differences Across PostgreSQL, MySQL, and SQL Server

A practical walk through six database design patterns you will actually meet in production: normalization, star schema, EAV, polymorphic associations, multi-tenancy, and the anti-patterns worth avoiding.

Database Design Patterns Every Developer Should Know

A practical walkthrough of pgvector: installing the extension, storing embeddings, writing similarity queries, building HNSW indexes, and knowing when plain PostgreSQL is enough.

pgvector: How to Add Vector Search to PostgreSQL

How upsert works across MySQL, PostgreSQL, and SQL Server, with the syntax for each, the edge cases worth knowing before you ship, and how upserts interact with migrations.

Upsert in SQL: INSERT ON DUPLICATE KEY vs ON CONFLICT Explained

AI agents need more than DDL. The full database lifecycle codified (schema, dependencies, ownership, history) gives LLMs the context to query correctly.

From Schema as Code to Schema as Context

How to find and fix slow MySQL queries: reading the slow query log, using EXPLAIN, tuning indexes, and rewriting queries, with a worked example for each.

How to Fix Slow MySQL Queries: A Practical Guide

Convex and Supabase are both backend-in-a-box platforms, but built on different foundations. This post compares their architecture, real-time model, data model, schema management, and pricing to help you decide.

Convex vs Supabase: Which Backend Platform Should You Choose?

Blue-green deployment is easy when your servers are stateless. The trouble starts at the database. This guide walks through why database blue-green is hard and how to do it without corrupting your data.

Database Blue-Green Deployment: A Practical Guide

A look at 10 data management tools developers and data engineers actually use in 2026: GUI clients, schema migration, pipelines, and analytics, with pricing for each.

Top 10 Data Management Tools in 2026

How to give AI agents governed access to your databases. Identity, authorization, query control, audit, and masking, applied to a new principal type.

How to Govern AI Agent Database Access

A look at three SQL editors built only for Postgres, with what each one is good at and who it fits, to help you pick the right one in 2026.

Enterprise Text-to-SQL: Context, Evaluation, and Governance

A practical look at the database deployment tools DevOps teams actually use in 2026, sorted by how each one defines, applies, and coordinates schema changes.

Database Deployment Tools for DevOps Teams in 2026

A walk-through of how renaming a single column can quietly break an analytics pipeline, why it happens, and how schema change detection and notification help you catch it early.

Schema Change Detection and Notification: Why a Simple Column Rename Can Break Your Data Pipeline

How to read a Postgres query plan, spot the common performance problems, and fix them without breaking other queries.

Postgres Query Plan: How to Read and Fix Performance Issues

A walk through every layer of the Postgres permission system that can raise ERROR 42501, why each one fires, and how the behavior differs from MySQL.

The Anatomy of Postgres Permission ERROR 42501

A practical look at Postgres logs: what they record, how the logging collector works, which parameters actually matter in production, and the mistakes that turn logs into expensive noise.

Postgres Logs Explained: A Practical Guide for Production

Postgres 19 widens MultiXactOffset to 64 bits, eliminating the hidden 4 billion member limit that caused catastrophic outages for high-concurrency workloads.

Postgres 19 Feature Preview: 64-bit MultiXactOffset

How to run MySQL schema migrations without blocking queries or causing downtime, covering the MySQL-specific behaviors that bite in production and the tools that work around them.

MySQL Schema Migration Best Practice

Postgres 19 introduces automatic sequence synchronization for logical replication, eliminating manual tracking and making major version upgrades and failover significantly easier.

Postgres 19 Feature Preview: Sequence Synchronization for Logical Replication

What multi-environment database deployment actually involves, the problems teams keep hitting, and the patterns (manual scripts vs GitOps) for handling them.

Database Multi-Environment Deployments - The Challenges and Patterns

A guide to open source sensitive data discovery tools, from NLP libraries like spaCy and Microsoft Presidio to multi-source scanners like Hawk-Eye and full metadata platforms like OpenMetadata.

Top Open Source Sensitive Data Discovery Tools in 2026

Database audit logging really has two layers: the infrastructure layer your cloud provider ships, and the workflow layer you have to build yourself. Here is what each one captures, and why an audit needs both.

Database Audit Logging: Two Layers, One Trail

A practical guide to HITRUST database compliance covering access control, audit logging, change management, and data protection.

Database Compliance for HITRUST: Controls, Risks, and Best Practices

What the "Require Primary Key" SQL review rule checks, the production problems a missing primary key tends to cause, and the SQL to fix tables that don't have one.

Require Primary Key: A SQL Review Rule Explained

What the "Enforce NOT VALID in CHECK" SQL Review rule does, why adding a CHECK constraint can lock your table, and how the two-step NOT VALID approach avoids it.

Enforce NOT VALID in CHECK: A SQL Review Rule Explained

The practical ways to audit a PostgreSQL database, from native logging to triggers, logical replication, pgAudit, and Bytebase, with the trade-offs of each.

Postgres Audit Logging Guide

Learn why CASCADE operations in SQL can lead to catastrophic data loss and how the "Prohibit CASCADE" review rule protects your production database.

Prohibit CASCADE: A SQL Review Rule Explained

A walkthrough of moving each Supabase piece (database, auth, storage, functions, realtime, networking) to its AWS counterpart, with a services-first order that keeps the final database cutover simple.

How to Migrate from Supabase to AWS

Six open-source PostgreSQL backup tools compared for 2026, with the language, license, interface, and best-fit use case for each, plus a note on which ones are still maintained.

What is Enterprise Database Management (EDM)?

A plain explanation of Postgres Transaction ID (XID) wraparound: what causes it, how to check how close you are, and what keeps it from taking your database offline.

Postgres Transaction ID (XID) Wraparound

How a CI/CD pipeline for database schema migration works end-to-end. What it gates, what it leaves outside, and the tools that fit.

How to Build a CI/CD Pipeline for Database Schema Migration

A practical guide to shipping features with PostgreSQL, covering my day-to-day development workflow, the tools I actually use, and real-world examples

How I Ship Features with Postgres

A practical look at what LGPD (Brazil's General Personal Data Protection Act) means for database operations, how it differs from GDPR, and the controls teams need to actually comply.

Database Compliance for LGPD: Implications and Best Practices

What a Postgres LATERAL JOIN does, when to reach for one, and the patterns and gotchas you'll run into using it.

What is Postgres LATERAL JOIN?

What MySQL Online DDL actually does, how its three algorithms (INSTANT, INPLACE, and COPY) differ, and the limitations to plan around before you run a schema change in production.

MySQL Online DDL: A Practical Guide

The best open-source Postgres connection poolers in 2026. Compare PgBouncer, Odyssey, PgDoorman, and PgDog — with our pick: PgBouncer if you want free, PgDog if you want a commercial vendor.

SQL Table Naming Dilemma: Singular vs. Plural

PostgreSQL 18 features that change how application developers write and ship code.

What's New in PostgreSQL 18: A Developer's Perspective

Compare Snowflake Dynamic Data Masking with database views and Bytebase fleet-wide masking on edition gate, policy management, and audit trail.

Snowflake Dynamic Data Masking (DDM) and Alternatives

A look at the open-source ways to add authentication and authorization to a Postgres app in 2025, from all-in-one platforms to libraries, identity servers, and the minimalist JWT-to-RLS pattern, with a "best for" note on each.

Postgres Case Sensitivity Explained

What pg_database_owner does in Postgres, why it was added, and how to use it without hitting the "cannot have explicit members" error.

What is pg_database_owner in Postgres

A reference for which Postgres DDL operations rewrite the whole table (and take heavy locks) versus which ones are metadata-only, plus how to test it yourself before you run it in production.

Which Postgres Operation causes a table rewrite

A practical rundown of the Postgres Row-Level Security traps that quietly break performance or leak data, with the fix for each.

Postgres Row-Level Security Footguns

A walk through the three ways to roll back changes in Postgres: transactions and SAVEPOINT, Point-in-Time Recovery, and compensating DML, and when each one fits.

Postgres Rollback Explained

Learn how Postgres locks affect schema migrations and which DDL operations conflict with DML to achieve zero-downtime deployments.

Postgres Schema Migration without Downtime

The limitations and gotchas of gh-ost for online MySQL schema changes, and when to reach for something else instead.

gh-ost Limitations You Need to Know Before Production

PostgreSQL best practices for application developers: connection naming, timeouts, online migrations, role separation, and UPSERT for reliable production apps.

Postgres best practices I wish every app developer knew

Learn how to use CREATE INDEX CONCURRENTLY in Postgres to build indexes without blocking writes. Pitfalls, safety checks, and performance tips.

How to Use Postgres CREATE INDEX CONCURRENTLY

Supabase and MongoDB take different paths to storing application data. This article compares them on data model, architecture, performance, pricing, and licensing to help you decide which one fits.

Supabase vs. MongoDB: a Complete Comparison in 2026

DataGrip is a SQL IDE built for individual developers; Bytebase is a web platform built for teams that need review and governance. This post compares their database support, features, and pricing to help you decide which fits.

Bytebase vs. DataGrip: a side-by-side comparison for database management

Supabase pricing starts free. We break down real costs for Pro ($25/mo) and Team ($599/mo) plans, explain overages, and compare each service head-to-head with AWS.

Supabase vs AWS: Feature and Pricing Comparison (2026)

Is Supabase free? Compare Supabase pricing vs AWS RDS and Aurora across free tier, Pro, and production plans. Includes Supabase free tier limits, storage costs, and compute pricing for 2026.

Supabase Pricing vs AWS RDS: Is Supabase Free? Full Cost Comparison (2026)

Learn how Bytebase enables organizations to implement comprehensive Database Security Lifecycle Management, unifying security and operations from development to production.

Database Security Lifecycle Management

Areas where MySQL shines and Postgres falls short.

Features I Wish Postgres Had but MySQL Already Has

Areas where PostgreSQL shines and MySQL falls short.

Features I Wish MySQL Had but Postgres Already Has

This guide focuses on HIPAA compliance at the database layer, providing healthcare organizations and database teams with practical guidance for implementing HIPAA Security Rule requirements.

HIPAA Data Security and Retention Requirements

Compare the online index creation difference between Postgres and MySQL

Postgres vs. MySQL: Online Index Creation

SOC 2 Data Security and Retention Requirements for Database Systems and How Bytebase Helps

SOC 2 Data Security and Retention Requirements

Compare the different indexing options between Postgres and MySQL

Postgres vs. MySQL: Indexing Options

Compare the JSON support difference between Postgres and MySQL

Postgres vs. MySQL: JSON Support

While PostgreSQL RLS is a powerful feature, it has inherent design limitations that hinder broader adoption. In this post, we’ll examine these limitations and explore alternatives.

Postgres Row-Level Security (RLS) Limitations and Alternatives

Evaluate several database schema diagram tools, and help you to choose the right one for 2025

Top 4 Free, Open Source Database Schema Diagram Tools to Visualize Database Easier in 2025

An overview of the most popular text-to-SQL AI tools in 2026, including DataGrip, TablePlus, SQL Chat, Vanna.ai, SQLAI.ai, Postgres.new, and DBHub MCP server. Compare features and capabilities to find the best SQL AI assistant for your workflow.

Top 5 Text-to-SQL Query Tools in 2026

Compare the DDL transaction difference between Postgres and MySQL

Postgres vs. MySQL: DDL Transaction Difference


After 6 months of intense development and over 2,000 commits, Bytebase version 0.1.0 finally arrives. The code is open sourced at [https://github.com/bytebase/bytebase](https://github.com/bytebase/bytebase) using Apache 2.0.

## **What is Bytebase**

Bytebase is a tool for database schema change and version control, its main audience are Developers and DBAs.

Database schema migrations (aka database migrations), like code changes, are one of the routine tasks for developing applications. Although schema changes are not as frequent as code changes, they are much more dangerous. Since the data is stateful, unlike the fast code rollback, the database rollback is much more complicated. Besides database changes, network changes are also dangerous and can cause large-scale service failures. While network configurations are usually stateless, so rollback and recovery are also faster.

> _Thus, database changes are usually the most likely ones causing long-lasting large-scale service outages. And in the extreme case, can even bankrupt the entire business._

Since this operation is so critical and impactful, there must be many tools to solve this problem? Yes, but the reality is although the database industry has more than 40 years history. DevOps, Database CI and even Database-as-Code have been hovering around for many years. There is still no industry benchmark solution handling this task, like GitLab to code hosting, Prometheus to service monitoring.

## **Why we build Bytebase**

Put simply, it's to answer the previous question

> _We want to make Bytebase the industry benchmark solution for managing database schema change._

Let's first evaluate the existing solutions first, roughly divided into 3 categories:

1. Tools been around for a long time

Many teams have already adopted tools like Flyway, Liquibase in their development workflow. These tools have already built a large customer base and a thriving community. They also have a solid schema change core and stood the test of time. But, these products are all more than 10 years old, and the tech stacks used are sort of dated. For example, Flyway and Liquibase are both based in Java. Nowadays, database changes are usually used as a step in CI, and the step is often executed in a separate container. To run a Flyway/Liquibase command, one must first download a JVM or use an image containing JVM. Also, they are thin on the frontend with no or basic functionalities. Another concern is they support everything from commercial to open source databases, regardless of XML or SQL migration format. This does carry weight over the years.

2. Homegrown tools

Usually when the dev group reaches ~50 people, a dedicated DBA must be summoned. And for a typical middle-sized to large company, the ratio of DBAs to Developers is between 1:150 to 1:400. To improve serving bandwidth, DBAs have to rely on tools. Starting from the most basic SQL review ticket, DBAs often would roll their own by using Python + Django. These tools are often stacked up bit by bit, starting with SQL review ticket, then cron inspector, and then monitoring, backup/restore, approval workflow etc, and finally we get a classic internal company system, like this:

![_](/content/blog/announce-bytebase/life-of-a-swe.webp)By Manu Cornet, [https://goomics.net/106/](https://goomics.net/106/)

3. Homegrown to open source tools

Some mindful engineers have open sourced their homegrown tools. A few have gained thousands of GitHub Stars, and been deployed in middle to large companies. These tools did provide great value. At least DBAs on longer need to reinvent wheels, especially those are not the wheels they are good at/enjoy building. But frankly speaking, from the underlying data model design all the way up to UI/UX, these open source tools are still quite far from the industry benchmark standard.

And we ask ourselves:

- What's the GitLab for database instead of for code?
- What's the Figma for DBAs instead of for designers?
- What's the Terraform for Database-as-Code instead of for Infrastructure-as-Code?

The current industry does not have a good answer yet. Before starting Bytebase, we used to be application developer, database kernel developer, DBA ourselves and have also managed the DevTools, DBA and even collaboration tool group in world's leading technology companies (Google and Ant Group). Thus we happen to have all the required skills to build such a tool.

## **How we build Bytebase**

Since this is a launch post, we will cover some design aspects, more to be covered in separate posts.

### Data modeling

Data modeling is always the center piece of the software, it's the one determining the celling of the software and is very hard to change after launch. Even being veterans in the database domain, we have spent tremendous time to make the data modeling right. Below is Bytebase's essence, its v1 data model:

![_](/content/blog/announce-bytebase/data-model.webp)

This is actually the 3rd iteration, and every iteration causes a significant refactoring. As an example, the upper right is to model the execution pipeline, Bytebase has studied all mainstream pipeline design and came up with a solution:

![_](/content/blog/announce-bytebase/data-model-pipeline.webp)

For those interested, please check our design notes: [https://github.com/bytebase/bytebase/tree/main/frontend/src/types/pipeline#readme](https://github.com/bytebase/bytebase/tree/main/frontend/src/types/pipeline#readme)

### UI and UX

To be honest, we lack the design skills to craft Bytebase to the level of the tools we aspire to like Figma, Notion, Linear. So our bottom line is to make it easy to use with a decent looking frontend. Looking at Bytebase's architecture graph:

![_](/content/blog/announce-bytebase/architecture.webp)

We deliberately put a large browser here to suggest the Bytebase console is a very critical piece of the product. Indeed, the frontend work takes 2/3 ~ 3/4 of the development time so far. And among those work, we spend most effort to polish the most frequently accessed UI - issue detail view.

### Issue detail view

![_](/content/blog/announce-bytebase/issue-detail-annotated.webp)

The number shows each sub-component of the issue detail view, let's take another look

![_](/content/blog/announce-bytebase/issue-detail-link.webp)

Each square shows an interactive area. Issue is the rendezvous, and we try to add link to every related object if possible.

### Slug design

Next let's talk about link, and in particular the slug part.

![_](/content/blog/announce-bytebase/slug-design.webp)

The URL is reached by first clicking the stage progress bar, followed by clicking the 2nd activity. This slug consists of 4 parts:

1. **add-createdat-column-to-userpostcomment-table-for-dev-environment**, the issue name.
2. **13008**, the issue ID and the key identifying the issue.
3. **?stage=dev-1**, query parameter, used to locate the stage, an issue can contain many stages and different stage can show different content.
4. **#activity14029**, anchor used to locate the exact comment position.

With this, user can learn the name, stage by skimming the URL usually seen in the doc, chat conversation. Also, by clicking the URL, user will navigate to the exact same place as the URL producer. All Bytebase pages have adopted this practice. BTW, you may notice we use auto increment integer as the issue ID instead of UUID, there are some tradeoffs involved. We will leave the discussion to a separate post.

## **Developer Experience**

Since Bytebase chooses open source, we do want to make it more accessible to the developers. So in the very beginning, we set a design goal for Bytebase:

> _Zero config, start with a single command within 10 seconds._

Bytebase achieves these by:

1. Use Golang as the backend, Golang is statically linked and requires no external dependency.
2. Use the embedding feature introduced in Go 1.16 to package the frontend files.
3. Use SQLite instead of the typical MySQL/PostgreSQL to store the data (this will be further discussed in a separate post).

The end result is the developer can just execute ./bytebase to start the entire Bytebase app. In fact, it usually takes **less than 1 second** from start to function.

### ASCII Banner

When startup process completes, the console will print out the Bytebase ASCII banner:

![_](/content/blog/announce-bytebase/banner-hello.webp)

First, this is for branding purpose. But more importantly, this is to allow user to easily identify the application status. Similarly, if Bytebase stops normally, it will print out the Bye ASCII banner:

![_](/content/blog/announce-bytebase/banner-bye.webp)

Both helps user to locate the Bytebase start/stop point among the abundant log entries.

### Let the product speak

Bytebase has built-in demo and read-only mode enabled by the respective --demo, --readonly flag. At the time of launch, we ran a public demo deployment with both flags on. Bytebase is a tool built for database professionals with its own design philosophy. Even for those veterans, there is a learning curve. The demo mode helps the new user to skip the cold start phase, and can jump directly to play with the core feature set. The read-only mode was originally developed for that public demo: we wanted clean data to show each visitor the desired demo state, and to achieve this, we needed to ensure the state was immutable and wouldn't be messed up by the previous visitor. Moreover, because the state was immutable, we could reference specific demo pages from our doc site as supplemental live examples. Later on, Bytebase can also leverage the read-only mode to develop enterprise-grade features like maintenance window and deployment freeze.

## **Tool not Platform (yet)**

Right before the launch, we made a minor change during the last thorough code review

> _Tool not Platform (yet)_

![_](/content/blog/announce-bytebase/tool-not-platform.webp)

It has taken a lot of effort to bring Bytebase to the public. Yet, there is a lot of work ahead. We don't have any previous experience to run an open source community, neither do we have any marketing experience. The chosen tech stack and the data model still needs to stand the test of time. All in all, we still need to be pragmatic and focused on building a solid tool first.

## **Conclude**

It's already a quite long post and thanks for following us thus far. You can visit [https://github.com/bytebase/bytebase](https://github.com/bytebase/bytebase) to check out our project. If you happen to be a DBA or a developer looking for a database schema change management tool, give Bytebase a try and let us know what you think. Feedback appreciated.

Go back to build 🚀🚀🚀


Bytebase is a tool for database schema change and version control, its main audience are Developers and DBAs. We want to make Bytebase the industry benchmark solution for managing database schema change.

Bytebase ブログ

データベースガバナンスのスタンダードを体験する

ソリューションとプラットフォーム

リソース

変更管理

アクセスとセキュリティ

AI とエージェント

比較

会社

法的事項