The crates

All fifteen crates with what each one does, what lives inside it, and how many tests stand behind it.

SQLly is one Rust workspace of fifteen crates, arranged so that anything the interface can do, the CLI engine and the language server can do too. Each crate below lists what it does, what lives inside it, and how many tests stand behind it - 7,413 tests in total as of this writing.

Language & intelligence

CrateWhat it doesTests
sqlly-langThe SQL language layer: the canonical statement model, the lexers and parsers behind it, the tokenizer IntelliSense leans on, and the formatter. Dialect-invariant by design, so one model serves every engine.253
sqlly-intelEverything that reasons about SQL and the objects it names: schema-aware IntelliSense, metadata and the model engine, query analysis, and a regression suite grown from user feedback reports.635
sqlly-aiThe AI side: a local, searchable catalog of database objects, schema search and natural-language Q&A, and natural-language-to-SQL - all through a provider you configure, with token-budgeted context instead of the whole schema.405

Databases & the service core

CrateWhat it doesTests
sqlly-enginesEvery database backend behind one set of traits: SQL Server over TDS, PostgreSQL, MySQL, SQLite, libSQL/Turso, DuckDB, ClickHouse, Oracle, and Redis, with SSH tunneling built in and conformance suites pinning each dialect's behavior.137
sqlly-coreShared product primitives: connection storage and management with OS-keyring secrets, the object model, sessions, bounded spill-to-disk row streams, redaction, and crash recovery.196
sqlly-servicesThe headless, UI-agnostic service layer: admin tools, row editing, dumps, plans, transfer, compare, and the catalog - the code every frontend calls, unchanged.1,094

The interfaces

CrateWhat it doesTests
sqlly-gpuiThe product: every view, pane, and dialog of the desktop app, the theme, and the bindings between interface and services. The largest crate, and the one you spend your day in.4,009
sqlly-browserThe same gpui app compiled to WebAssembly for the in-tab browser preview; browser-impossible subsystems are swapped for web equivalents or clearly disabled. It adds no tests of its own, correctness comes from the crates it wraps.0
sqlly-cliThe command-line surface: the engine subprocess the app spawns (with request/response correlated logging), standalone CLI commands, and the MCP server with its agent tool loop.393
sqlly-lspA Language Server Protocol server for T-SQL, backed by the same IntelliSense model the app uses, so editors like VS Code get the completions SQLly is tested on.36

Remote access & transport

CrateWhat it doesTests
sqlly-wireThe relay's outer-frame codec: chunking, reassembly, and capacity math for the binary protocol that flows between clients, the relay, and on-prem bridges.48
sqlly-remoteEverything between a SQLly client and an engine that is not in the same process: the transport that carries requests and streamed results over the relay path.94
sqlly-bridgeThe on-prem responder daemon: runs inside your network, dials out to the relay, and makes your database reachable from your own remote SQLly sessions without any inbound port.64
sqlly-relayThe public TLS forwarding relay: routes encrypted traffic between a traveling client and its on-prem bridge while remaining unable to read it.41

Test support

CrateWhat it doesTests
sqlly-testkitShared test infrastructure: golden-file comparison with cross-platform line-ending handling, live-database conformance harnesses, and container helpers used by the engine suites.8
Counts drift with the code. The numbers above are a snapshot and move with every release.