Skip to main content
PawSQL can review SQL before a change is merged or released and return a pass, warning, or block decision to the engineering platform. Start by distinguishing a prebuilt connector from a custom API integration.

Support matrix

“No prebuilt connector” does not mean the platform cannot integrate with PawSQL. It means your pipeline or integration service must orchestrate the OpenAPI workflow.

Choose a path

Repository connectors

Connect CODING, GitHub, or GitLab and review SQL on repository events.

BlueKing pipeline connector

Add PawSQL review and a quality gate to a BlueKing pipeline.

OpenAPI pipeline integration

Build a review stage for a CI/CD system without a prebuilt connector.

Custom platform integration

Choose OpenAPI, webhooks, or an integration service for Jenkins, Gitee, CodeArts, and internal platforms.

Standard flow

Before you begin

Prepare the PawSQL endpoint, an integration identity, the target project, a review workspace, and an approved policy. The workspace must match the database engine and version used by the SQL. Add DDL or a database connection when schema context is required.
Automated review does not execute SQL or replace business validation, database authorization, change approval, backup, and rollback controls. Complete acceptance testing with sanitized SQL and a non-production environment first.

Next step

Read the integration model and core concepts and prerequisites and security, then choose a connector.