Database governance lives upstream, on the production database. Here is how to actually govern the source: reviewed changes, scoped access, codified policy, and audit where the data is born.

How to Govern Data at the Source: A Guide to Upstream Database Governance

Data governance and database governance are four letters apart and constantly conflated. They are different disciplines, owned by different teams, solved by different tools. Here is the dividing line.

Data Governance vs. Database Governance: The Difference Is the Base

PopSQL shuts down on September 1, 2026. Compare Bytebase and PopSQL across query collaboration, supported databases, access control, data masking, audit logging, and pricing before you migrate.

Bytebase vs. PopSQL: a side-by-side comparison for migrating teams

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

The best SQL editors built exclusively for PostgreSQL: what each one is good at, who it fits, and when a Postgres-only tool beats a multi-database client.

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

What LGPD means for database operations: how it actually differs from GDPR, what the ANPD sanctions in practice, and the database controls (classification, masking, retention, audit) that hold up.

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


> PopSQL is a collaborative SQL editor that shuts down on September 1, 2026. Bytebase is an open-source database governance platform whose SQL Editor covers the same shared-query workflow, plus the governance around it.

PopSQL and Bytebase both give a team one web editor and one query library instead of `.sql` files scattered across laptops. The overlap ends there. PopSQL was built for analytics collaboration: charts, dashboards, scheduled queries, real-time co-editing. Bytebase is built for governed database access: who can query what, which columns are masked, what an auditor sees afterward.

The comparison has a deadline. TigerData (formerly Timescale) acquired PopSQL in April 2024, [moved it to limited support in September 2025](https://popsql.com/blog/popsql-limited-support), and deletes all data when it shuts down on September 1, 2026. So the question is not which to adopt; it is whether Bytebase covers what your team used PopSQL for.

## What Bytebase and PopSQL have in common

- Web-based SQL editor with schema browsing and autocomplete.
- A shared, searchable query library scoped to the team, not the laptop.
- Centralized connections: members query through the platform instead of managing per-machine credentials.
- Coverage for the common engines: PostgreSQL, MySQL, SQL Server, Snowflake, BigQuery, ClickHouse, and more.

## Key differences between Bytebase and PopSQL

|                                                     | PopSQL                             | Bytebase                                                           |
| --------------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------ |
| Status                                              | Shuts down September 1, 2026       | Actively developed                                                 |
| [Product position](#product-position)               | Collaborative SQL editor           | Database governance platform                                       |
| [Deployment](#deployment)                           | Cloud service (web + desktop app)  | Self-hosted (Docker/K8s/binary) or cloud                           |
| [Supported databases](#supported-databases)         | 12, analytics-leaning              | 25, OLTP + NoSQL + warehouses                                      |
| [Shared query library](#query-and-collaboration)    | ✅ Folders, search                 | ✅ Project worksheets                                              |
| [Real-time co-editing](#query-and-collaboration)    | ✅                                 | ❌                                                                 |
| [Charts and dashboards](#charts-and-schedules)      | ✅ Dashboards                      | Result charts only                                                 |
| [Scheduled queries](#charts-and-schedules)          | ✅                                 | ❌                                                                 |
| [Access control](#access-control)                   | Shared connections with roles      | ✅ Database/table-level, Just-in-Time access                       |
| [Data masking](#data-masking)                       | ❌                                 | ✅ Dynamic, column-level (Enterprise plan)                         |
| [Audit log](#audit-log)                             | ❌                                 | ✅ Pro plan and above                                              |
| [Schema change workflow](#schema-change-workflow)   | ❌                                 | ✅ Review, approval, SQL lint (200+ rules)                         |
| Open source                                         | ❌                                 | ✅                                                                 |
| [Pricing](#pricing)                                 | N/A (winding down)                 | Free Community; paid Pro and Enterprise plans                      |

### Product position

- **PopSQL**: A collaborative SQL editor for analytics work: write a query together, chart the result, pin it to a dashboard, schedule it to Slack. Governance never went deeper than workspace roles and shared connections.

  ![popsql](/content/blog/bytebase-vs-popsql/popsql.webp)

- **Bytebase**: A database governance platform. The [SQL Editor](https://docs.bytebase.com/sql-editor/overview/) covers everyday querying, and the platform around it handles access requests, data masking, schema change review, and audit logging across every connected database.

  ![bb-sql-editor](/content/blog/bytebase-vs-popsql/bb-sql-editor.webp)

### Deployment

- **PopSQL**: Cloud-only. Queries route through PopSQL's servers; the desktop app is a client to the same service. That architecture is why the shutdown deletes everything: the query library lives on their side.

- **Bytebase**: Self-hosted by default: a single Go binary, a [Docker image](https://docs.bytebase.com/get-started/deploy-with-docker), or a [Helm chart](https://docs.bytebase.com/get-started/deploy-with-kubernetes). Queries and metadata stay inside your network; a hosted Cloud option exists. Open source, so the exit path is plain files and a binary you control.

### Supported databases

- **PopSQL**: 12 connectors, leaning analytics: PostgreSQL, MySQL, SQL Server, Snowflake, BigQuery, Redshift, ClickHouse, Athena, Azure Synapse, Presto, Trino, and TigerData.

- **Bytebase**: 25 engines: 9 RDBMS (MySQL, PostgreSQL, Oracle, SQL Server, MariaDB, TiDB, OceanBase, CockroachDB, Spanner), 6 NoSQL (MongoDB, Redis, Cassandra, DocumentDB, DynamoDB, Cosmos DB), 9 warehouses (Snowflake, BigQuery, Redshift, ClickHouse, Databricks, Hive, StarRocks, Doris, Trino), and Elasticsearch. Depth varies by engine: mainstream ones like MySQL and PostgreSQL get the deepest support (SQL review rules, schema sync, data masking), while the rest cover querying and change deployment.

### Query and collaboration

- **PopSQL**: The strongest collaboration on either side: real-time co-editing with visible cursors, query version history with diffs, inline comments.

- **Bytebase**: Worksheets are saved and shared within a project, so the team query library carries over. Sharing is at the worksheet level, not the keystroke level: no multiplayer cursors, and access follows project membership.

  ![bb-sheets](/content/blog/bytebase-vs-popsql/bb-sheets.webp)

### Charts and schedules

- **PopSQL**: Built-in charts, lightweight dashboards, query variables for self-serve reports, and scheduled runs pushed to Slack or email. For many teams, this BI layer was the main reason PopSQL stuck.

- **Bytebase**: Query results render as charts inside the SQL Editor, but there are no dashboards and no scheduled queries. If dashboards were your primary PopSQL use, pair Bytebase with a BI tool like Metabase, or start with the BI tool.

### Access control

- **PopSQL**: Shared connections with workspace roles. Sharing a connection shares the credential's full power: whatever that database user can read, every member on the connection can read.

- **Bytebase**: Users never see database credentials. [Database permissions](https://docs.bytebase.com/security/database-permission/overview) are granted per project, database, or table; developers can request [Just-in-Time access](https://docs.bytebase.com/security/database-permission/overview) that expires automatically; environments carry different policies, for example read-only on production.

  ![bb-access-control](/content/blog/bytebase-vs-popsql/bb-access-control.webp)

### Data masking

- **PopSQL**: None. Query results show whatever the shared connection can see, including PII.

- **Bytebase**: [Dynamic data masking](https://docs.bytebase.com/security/data-masking/overview) at the column level (Enterprise). Queries return masked values unless the user is explicitly authorized; semantic types (email, phone, SSN) apply the same rule consistently across schemas.

  ![bb-masking-graph](/content/blog/bytebase-vs-popsql/bb-masking-graph.webp)

### Audit log

- **PopSQL**: No audit trail of who ran what. When a SOC 2 or PCI auditor asks "who queried production last quarter?", the workspace has no answer.

- **Bytebase**: The [audit log](https://docs.bytebase.com/security/audit-log) (Pro and above) records every query, change, approval, and policy edit. Filter by user, action, or time range; export for SIEM ingestion.

  ![bb-audit-log](/content/blog/bytebase-vs-popsql/bb-audit-log-dropdown.webp)

### Schema change workflow

- **PopSQL**: Out of scope. DDL typed into the editor runs like any other query.

- **Bytebase**: Schema changes flow through an issue, like a pull request for the database: automated [SQL review](https://docs.bytebase.com/sql-review/review-rules) with 200+ rules, [custom approval flows](https://docs.bytebase.com/change-database/approval), full change history with rollback scripts. Ad-hoc DDL typed into the SQL Editor is redirected into that workflow.

  ![bb-issue-waiting](/content/blog/bytebase-vs-popsql/bb-issue-waiting.webp)

### Pricing

- **PopSQL**: Winding down; the practical price is the migration itself.

- **Bytebase**: [Community](/pricing/) is free and self-hosted, up to 20 users and 10 instances, and includes the SQL Editor, shared worksheets, SQL review, and the change workflow. Pro adds SSO, audit log, and user groups. Enterprise adds dynamic data masking, database/table-level access control, Just-in-Time access, and custom approval flows.

## When Bytebase is the right landing spot

- PopSQL was the shared home for your SQL, and you also need access control, masking, or an audit trail, whether for SOC 2, PCI, GDPR, or a DBA tired of handing out credentials.
- You want the replacement self-hosted and open source, so no vendor shutdown forces the next migration.
- Schema changes and ad-hoc queries travel the same ungoverned path today, and you want changes reviewed and approved.

## When it is not

- Dashboards and scheduled queries were the point. A BI tool such as Metabase is the honest replacement for that half of PopSQL, often paired with Bytebase for governed access.
- Real-time multiplayer editing is essential to how your analysts work. Bytebase shares worksheets, not live cursors.

## FAQ

### Can Bytebase import my PopSQL queries directly?

There is no one-click importer. Export via PopSQL's GitHub Sync to plain `.sql` files, then save the active ones as worksheets in the relevant Bytebase project.

### Does Bytebase have a desktop app like PopSQL?

No. Bytebase is web-based: deploy once, everyone uses the browser. No per-machine install or driver setup.

### Is the free Community plan enough to replace PopSQL?

For the core workflow, yes: SQL Editor, shared worksheets, and the schema change workflow are all in Community (up to 20 users, 10 instances). Audit log arrives with Pro; masking and fine-grained access control with Enterprise.

### We only used PopSQL for dashboards. Should we still look at Bytebase?

Not as the dashboard replacement. Pick a BI tool for that. Teams add Bytebase when the second problem shows up: too many people holding production credentials with no record of what they run.


The
Bytebase Blog

How to Govern Data at the Source: A Guide to Upstream Database Governance

Data Governance vs. Database Governance: The Difference Is the Base

Database Governance for Fintech: Guarding the Ledger

Explore the standard for database governance

Solutions & Platform

Resources

Change Management

Access & Security

AI & Agents

Comparisons

Company

Legal

The Bytebase Blog

How to Govern Data at the Source: A Guide to Upstream Database Governance

Data Governance vs. Database Governance: The Difference Is the Base

Database Governance for Fintech: Guarding the Ledger

Explore the standard for database governance

The
Bytebase Blog