DEV.co
Open-Source Databases · actiontech

sqle

SQLE is an open-source SQL quality management platform supporting multiple database types (MySQL, PostgreSQL, Oracle, and Chinese national databases). It provides pre-deployment SQL auditing, post-deployment monitoring, and CI/CD integration to enforce SQL standards across the entire lifecycle.

Source: GitHub — github.com/actiontech/sqle
1.5k
GitHub stars
214
Forks
Go
Primary language
MPL-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryactiontech/sqle
Owneractiontech
Primary languageGo
LicenseMPL-2.0 — OSI-approved
Stars1.5k
Forks214
Open issues195
Latest releasev4.2606.0 (2026-07-03)
Last updated2026-07-03
Sourcehttps://github.com/actiontech/sqle

What sqle is

Go-based platform offering SQL parsing, rule-based auditing (1000+ built-in rules), execution plan analysis, slow query detection, change versioning, and rollback capabilities. Integrates with Jenkins, IDEs (JetBrains), and messaging platforms (Feishu, DingTalk) for workflow automation.

Quickstart

Get the sqle source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/actiontech/sqle.gitcd sqle# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Enterprise SQL governance and standardization

Organizations needing centralized SQL quality rules, audit trails, and enforcement across development, testing, and production—particularly those without dedicated database experts on staff.

DevOps pipeline SQL validation

Teams integrating SQL review into CI/CD workflows (Jenkins, etc.) to catch risky queries before deployment and automate approval workflows with team notifications.

Multi-database environments with change safety

Companies running MySQL, PostgreSQL, Oracle, or Chinese databases (OceanBase, Dameng, TDSQL) who need version-tracked changes, auto-generated rollback scripts, and recovery from accidental modifications.

Implementation considerations

  • Requires Go runtime and database connectivity; Docker Compose deployment recommended for initial setup but source/RPM options available for production hardening.
  • Rule library (1000+ rules) covers multiple scenarios (performance, security, compliance) but customization and tuning to organizational standards will be necessary.
  • Integration with CI/CD (Jenkins) and messaging (Feishu, DingTalk) requires network access and credential management; plan for approvals workflow design.
  • Change versioning and auto-generated rollback scripts depend on accurate schema detection; test thoroughly on target databases (especially less common versions of PostgreSQL, Oracle, Chinese DBs).
  • Monitoring and slow-query collection require database-level access and potentially agent/probe deployment; coordinate with database and infrastructure teams.

When to avoid it — and what to weigh

  • Lightweight single-database projects — Small teams with simple SQL workloads and no formal governance requirements; deployment and maintenance overhead likely exceeds value.
  • Real-time query execution optimization only — If your primary need is live query performance tuning without audit/governance, specialized query optimizers or database profilers may be more efficient.
  • Minimal English documentation tolerance — Primary documentation and UI are in Chinese; teams requiring full English documentation should evaluate translation burden and support availability.
  • Air-gapped or highly restricted security environments — Requires careful vetting of dependencies and integration points; deployment model (community vs. enterprise) and network architecture must align with security policies.

License & commercial use

MPL-2.0 (Mozilla Public License 2.0)—a weak copyleft open-source license. Allows commercial use, modification, and private deployment. Requires preservation of copyright/license notices and disclosure of source modifications under MPL-2.0. Does not require downstream proprietary software to be open-sourced, but MPL-covered files must remain under MPL-2.0.

MPL-2.0 permits commercial use without explicit permission. However, the project distinguishes between Community Edition (implied OSS), Professional Edition (commercial evaluation via form), and Enterprise Edition. Commercial support and advanced features require engagement with ActionTech (vendor). Review the Community/Professional/Enterprise comparison and obtain proper license agreement before production deployment of non-community versions.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

SQLE requires database credentials and direct access to parse/audit SQL and collect telemetry. No explicit security audit, vulnerability disclosure policy, or SOC2/ISO certification mentioned. Evaluate: credential storage (encryption, rotation), network isolation (especially for production databases), audit logging of SQLE admin actions, and compliance with organizational data residency/retention policies. Review dependency tree (Go modules) for supply-chain risk. Commercial support advisable for security-sensitive deployments.

Alternatives to consider

Aqua Data Studio / DBmarlin

Commercial tools with similar SQL auditing, execution plan analysis, and change management; vendor-backed support; may offer tighter IDE integration but higher license costs.

SonarQube (with SQL plugins) + custom scripting

Lightweight open-source approach using existing CI/CD ecosystems; less SQL-specific governance but flexible rule authoring; lower operational overhead for small teams.

Cloud database native auditing (AWS RDS Audit, Google Cloud Audit, Azure SQL Auditing)

If adopting cloud databases, built-in audit and compliance features reduce need for external platform; tighter integration but lock-in to cloud provider.

Software development agency

Build on sqle with DEV.co software developers

Start with the online demo (Community or Enterprise edition) to validate SQLE's audit rules and workflow against your database types and team processes. If multi-database governance and audit-trail compliance are priorities, engage ActionTech for Professional/Enterprise licensing and support consultation.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

sqle FAQ

Does SQLE replace manual code review or DBA approval?
No. SQLE automates early detection of SQL issues and standardization; approval workflows are customizable but human reviewers remain in the loop. It reduces DBA bottlenecks by pre-filtering problematic queries.
Can SQLE scan existing production databases for non-compliant SQL?
Yes, via slow-query log ingestion and execution plan capture. The platform can also ingest SQL from application code. However, retroactive remediation of legacy queries is a separate effort.
What is the difference between Community, Professional, and Enterprise editions?
README indicates three tiers but detailed feature matrix is in the comparison doc (actiontech.github.io/sqle-docs/docs/support/compare). Community is OSS; Professional and Enterprise require license negotiation with ActionTech.
Does SQLE support databases outside the listed ones (MySQL, PostgreSQL, Oracle, Chinese DBs)?
Not clearly stated. README lists 'more than 10' mainstream databases; expansion is noted as 'ongoing.' Verify specific DB version/dialect compatibility with vendor before adoption.

Custom software development services

DEV.co helps companies turn open-source tools like sqle into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source databases stack.

Evaluate SQLE for Your SQL Governance Needs

Start with the online demo (Community or Enterprise edition) to validate SQLE's audit rules and workflow against your database types and team processes. If multi-database governance and audit-trail compliance are priorities, engage ActionTech for Professional/Enterprise licensing and support consultation.