# SQL Editor

> Query production through one governed web SQL editor: shared connections, just-in-time access, dynamic data masking, and a full audit log. Open-source.

Source: https://www.bytebase.com/sql-editor/

---

## Query production through one governed SQL editor.

A desktop client puts a production credential on every laptop and bypasses the audit log. Bytebase runs a web SQL editor that every query flows through — shared connections, governance applied centrally, and one place an auditor can read.

## One editor in front of the database.

### Shared connection inventory

Connections live in Bytebase, not on laptops, so no one downloads a production credential just to run a query.

### A full query environment

Schema browser, autocomplete, result grid, query history, and AI-assisted SQL — in the browser, against the real schema.

### Every query logged

Each statement is recorded with author, database, and timestamp, so the audit log is a read, not a reconstruction.

## Access and protection on every query.

### Just-in-time access

Query rights are requested per task, time-boxed, and auto-expiring — no standing access. /just-in-time-database-access

### Dynamic data masking

Sensitive columns are masked at query time based on the requester's role. /dynamic-data-masking

### Least-privilege RBAC

Role-based access maps who can query what — the baseline auditors check for SOC 2, HIPAA, and GDPR.

## Read in order.

### Dynamic data masking best practices

Role-based policies, column-level granularity, unmask audit trail. /blog/dynamic-data-masking-best-practices

### Database access control best practices

Least privilege, RBAC, just-in-time access, and the controls auditors check. /blog/database-access-control-best-practices

### Just-in-time database access

Time-boxed query rights granted on request, expired automatically. /blog/just-in-time-database-access

## Get Started

- [Contact us](https://www.bytebase.com/contact-us/)
- [Start now (cloud)](https://console.bytebase.com)