A query library with governance
Worksheets are shared per project, access follows project membership, and nobody handles raw database credentials — the PopSQL workflow, with controls a SOC 2 or PCI auditor can verify.
Bytebase holds the credential. People sign in with SSO; every statement runs as them.
Queries routed through PopSQL's cloud over shared connections. Whoever had the connection had its credential.
Project roles down to the table. Just-in-time access that expires on its own.
Workspace roles on shared connections. Finer scope came from the database's own roles.
Browser SQL Editor: schema browser, autocompletion, saved sheets, history, AI assistant.
Real-time co-editing, version history, inline comments, charts, dashboards, scheduled runs.
Dynamic masking by semantic type on results and exports. Unmasking is an approved, expiring grant.
Export is its own permission: approved, time-boxed, masked, and logged.
Export from the grid, or a scheduled run to Slack or email. No record of its own.
Production is read-only in the editor. An UPDATE or ALTER becomes a reviewed change.
Direct edits committed on the shared connection. No review step in between.
One log of every query, export, grant, and approval, per person.
No audit trail of who ran what.
Schema changes get their own workflow: review, rollout, batch change, rollback. Same log.
Worksheets are shared per project, access follows project membership, and nobody handles raw database credentials — the PopSQL workflow, with controls a SOC 2 or PCI auditor can verify.
Self-hosted and open source: queries and metadata live inside your network as plain data you control — no vendor shutdown can delete your team's SQL again.
RBAC, risk-based approval flows, dynamic data masking, and complete audit logs — the controls security and compliance teams require.
Go deeper on how Bytebase covers the PopSQL workflow — shared queries, access control, masking, and audit — after the September 1, 2026 shutdown.