SQLFluff

SQLFluff is an open-source SQL linter for ELT teams working across database engines. It is best for developers who want repeatable style and syntax checks in local workflows and CI, with automatic correction for many violations. Its free, MIT-licensed distribution removes purchasing friction, while dbt users should plan for additional templater setup and possible compile-time database access.

Overview

SQLFluff analyzes SQL for style and syntax problems so code review can concentrate on query behavior instead of formatting disputes. Its parser works without database access, which suits development and continuous-integration jobs that cannot or should not connect to a live system. A command-line autofix can correct many findings in one pass, although issues outside that supported set still need manual attention.

The project is released under the MIT License and the sole SQLFluff plan costs nothing. It is a linter rather than a database-testing system: it checks source text, not whether a query returns the right data.

Key features

Dialect and rule coverage

Documentation covers more than 25 SQL dialects, including T-SQL, PostgreSQL, BigQuery, and Snowflake; the product lists support for 28 languages. That breadth is valuable for mixed-engine organizations and teams standardizing SQL across projects. More than 70 rules address style, structure, and best practices, and custom rules let an organization encode conventions that generic presets cannot capture.

Autofix and review workflows

Autofix reduces repetitive cleanup by applying many lint corrections automatically. Because it does not fix every violation, teams still need review for changes the tool leaves untouched. CI/CD support makes linting enforceable on every change, while GitHub Actions output can place findings directly on pull requests instead of requiring reviewers to consult a separate report.

Templating and safety

Jinja templating and dbt support allow checks against generated SQL rather than only raw templates. The Jinja templater uses Jinja2 SandboxedEnvironment to restrict unsafe code execution, and SQLFluff itself does not execute SQL. However, macros such as dbt's run_query can execute arbitrary SQL. The dbt templater also requires the relevant dbt adapter and sqlfluff-templater-dbt package; models that query a database during compilation need database access. That makes plain SQL projects simpler to adopt than dbt projects with compile-time dependencies.

Installation and support

The project directs users to install from PyPI with pip or another Python package manager. Documentation, GitHub, Slack, and Stack Overflow provide community support rather than a separate paid support tier.

Pricing

There is no free trial because the product is already free, and no paid tier, seat charge, usage quota, or renewal term is stated. Every user receives the same open-source distribution, so organizations needing commercial support or contractual service terms should assess whether community channels meet their requirements.

Platforms

SQLFluff is listed for API, Linux, macOS, self-hosted deployments, and Windows. Python-package installation makes it suitable for developer machines and build environments, while self-hosting keeps execution within an organization's infrastructure.

Who it's for

Choose SQLFluff for ELT teams maintaining SQL across several dialects, especially when consistent rules, custom checks, pull-request feedback, and CI enforcement matter. It is also a good fit when linting must run without database connectivity. Teams using dbt should budget for adapter and templater installation and verify access requirements for models that query during compilation. If your priority is result validation rather than source-code quality, a database-testing tool is a better companion or alternative.

Pros and cons

• Pros: Free MIT-licensed software removes per-seat cost; support for more than 25 dialects covers heterogeneous estates; more than 70 rules and custom rules support detailed standards; autofix handles many routine violations; CI/CD and GitHub Actions annotations put feedback in the review path; parsing does not require database access.
• Cons: Autofix is partial, so not every finding is resolved automatically; dbt use adds two installation dependencies and may require compile-time database access; templating macros such as run_query can execute arbitrary SQL despite the linter's own non-execution model; community channels are the stated support route.

Alternatives

For a broad comparison, see SQL Linters and Formatters, Database Testing Tools, and Linters.

• SQL Formatter is a free MIT-licensed formatting library with a browser demo, suitable when formatting is the main requirement.
• SQLCheck is a free open-source command-line tool for Linux, macOS, and Windows.
• Sqruff is a free option spanning extensions, desktop systems, self-hosting, and the web.
• JSQLFormatter is a free formatter for Linux, macOS, self-hosted, and Windows environments.
• Poor SQL is a free, AGPL-licensed formatter with online and offline use plus SSMS and Visual Studio plugins.
• Sleek is a free open-source formatter distributed for extensions and desktop platforms.
• sqlfmt offers a free browser formatter that runs through WebAssembly with no installation.
• TSQLLint is free MIT-licensed software installable with dotnet-tool, Homebrew, or NPM.

Verdict

SQLFluff is the right choice for teams that need one free linter across multiple SQL dialects, enforceable rules, custom checks, and CI feedback without database connections. Look elsewhere when you need only lightweight formatting, a specialized alternative, or a workflow that cannot accommodate dbt's extra packages and possible compile-time access.