Open-Source Databases · sqls-server

sqls

sqls is a Language Server Protocol (LSP) implementation for SQL that provides intelligent editing features like autocomplete, hover information, and code actions across multiple database systems (MySQL, PostgreSQL, SQLite, MSSQL, Vertica, H2). It integrates with editors via LSP plugins and requires database connection configuration to enable schema-aware functionality.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/sqls-server/sqls

1.3k

GitHub stars

Forks

Primary language

MIT

License (OSI-approved)

Key facts

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

Field	Value
Repository	sqls-server/sqls
Owner	sqls-server
Primary language	Go
License	MIT — OSI-approved
Stars	1.3k
Forks	87
Open issues	44
Latest release	v0.2.45 (2026-01-07)
Last updated	2026-05-14
Source	https://github.com/sqls-server/sqls

What sqls is

Written in Go, sqls implements LSP for SQL with support for DML autocomplete (SELECT, INSERT, UPDATE, DELETE), JOIN completion via foreign key detection, document formatting, and signature help. It connects to multiple RDBMS via standardized drivers and exposes SSH tunneling for remote database access.

Quickstart

Get the sqls source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/sqls-server/sqls.git2cd sqls3# follow the project's README for install & configuration

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

Best use cases

Multi-database SQL development in existing editors

Teams using Vim, Neovim, VS Code, or Emacs who need consistent SQL intelligence across MySQL, PostgreSQL, SQLite, and other databases without leaving their preferred editor environment.

Schema-aware SQL authoring with live database context

Development workflows where SQL is authored against live or staging databases; sqls can complete table names, columns, and JOIN clauses by inspecting actual schema via database connections.

Organizations standardizing on LSP-based development tooling

Companies building or extending LSP-based development platforms can embed sqls as a SQL editing component without vendor lock-in to proprietary SQL tools.

Implementation considerations

Database credentials must be stored in plaintext YAML config files or workspace configuration; implement file permission controls and consider secrets management integration if credentials are sensitive.
SSH tunneling support is available but requires private key management; test SSH key rotation and passphrase handling in your deployment process.
Editor plugin installation is required for each supported editor; vim, Neovim, VS Code, and Emacs plugins exist but are maintained separately—verify plugin compatibility with your editor version.
Connection priority follows a specific order (config flag > workspace config > default config file); document and test your configuration strategy to avoid unexpected connection switching.
Performance depends on database responsiveness; large schemas may impact autocomplete latency; test with production-scale databases in your environment.

When to avoid it — and what to weigh

Requiring stable, production-guaranteed API contracts — README explicitly states the project is under development with no stable release; destructive interface and configuration changes are expected, making it risky for critical workflows.
Need for DDL completion and advanced SQL analysis — CREATE TABLE and ALTER TABLE completion are marked incomplete; EXPLAIN SQL is not implemented. Use this if DML and basic schema awareness suffice.
Minimal operational overhead or vendor support required — This is community-maintained OSS with 44 open issues and no commercial support channel. Organizations needing SLAs should evaluate commercial alternatives.
Air-gapped or offline-only environments — sqls requires live database connections to provide most features; it cannot function without network access to target RDBMS systems.

License & commercial use

sqls is licensed under the MIT License, a permissive OSI-approved license permitting free use, modification, and distribution in both open-source and proprietary contexts.

MIT License permits commercial use without restriction. However, the project carries no warranty and is explicitly under development. Review your risk tolerance for production use and consider contractual liability implications if embedding sqls in a commercial product.

DEV.co evaluation signals

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

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	High

Security considerations

Database credentials are stored in plaintext YAML config files or passed via workspace settings; file permissions and host-level access controls are essential. SSH tunneling is supported but requires secure private key management. No mention of credential encryption, secrets rotation, or audit logging. LSP communication is unencrypted and local; ensure LSP socket/pipe permissions restrict access to intended users. Database queries executed by code actions are not logged or audited by sqls itself; implement database-level query logging separately if needed.

Alternatives to consider

DBeaver IDE

Full-featured SQL IDE with native autocomplete, visual schema exploration, and query execution; offers commercial support and stability guarantees but is heavier than an LSP-based editor extension.

pgFormatter (PostgreSQL) / Oracle SQL Developer

Database-specific SQL tools with strong formatting and validation; if targeting a single RDBMS, vendor-provided tools may offer deeper integrations and official support.

Copilot/ChatGPT SQL plugins in editors

AI-assisted SQL completion available in VS Code and other editors; trades schema awareness for broad SQL pattern knowledge and natural language querying.

Software development agency

Build on sqls with DEV.co software developers

sqls is free, open-source, and available now. Install via `go install` and configure your database connections to get started with schema-aware SQL editing in your favorite editor. Be aware: the project is under active development, so expect interface changes.

Talk to DEV.co

Related open-source tools

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

sqlc sqle sqlit

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Databases API Development Custom Software Development Talk to DEV.co

sqls FAQ

Does sqls execute or modify queries automatically?

No. sqls provides autocomplete, formatting, and signature help. Query execution is triggered explicitly via code actions and requires user confirmation. No destructive operations are automatic.

Can sqls work without a live database connection?

Partial. Basic SQL syntax highlighting and keyword completion work without a database. Schema-aware features (table/column autocomplete, JOIN completion) require a live connection.

Is there a web-based or cloud version of sqls?

Not mentioned in the repository. sqls is a local LSP server; you would need to host it yourself or integrate it into a custom cloud IDE.

What support or SLA is available if sqls breaks in production?

Community support only via GitHub issues. No commercial support, SLA, or guaranteed response times. Mitigate by pinning to a stable version and testing updates in non-critical environments first.

Software developers & web developers for hire

Adopting sqls is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source databases software in production.

Ready to add SQL intelligence to your editor workflow?

Talk to DEV.co Schedule a Consultation