SQLlylibSQL and Turso GUI for Mac, Windows and Linux
Work with a Turso Cloud database or your own sqld server exactly like SQLite - same dialect, same IntelliSense, same compare tools - with an auth token instead of a user name and password.
- Connects over
- HTTP(S) to Turso Cloud or a self-hosted sqld
- Default port
- 8080 for sqld; Turso hosts always use HTTPS
- Sign-in
- Database auth token, or none for a local server
- Paste a URL
- libsql://…turso.io?authToken=…
What SQLly does for libSQL and Turso
libSQL is SQLite over the network - Turso Cloud, or sqld on your own
machine. SQLly gives it the SQLite dialect and tooling, and is upfront about the places
where a network server behaves differently from a local file.
Token sign-in, kept safe
Paste the database’s auth token - or a libsql:// URL with ?authToken= - and it goes straight to your operating system’s secure store, never to a file. A Turso host is always reached over HTTPS.
SQLite’s dialect, exactly
Queries run with SQLite’s own dialect, and every storage class comes through faithfully: 64-bit integers stay exact, blobs stay binary, and each column’s declared type is captured.
SQLite in SQLly →Scripts run as one unit
A multi-statement script runs as a single unit, so BEGIN … COMMIT and the auto-rollback safety setting work, and the first failing statement stops the script with the server’s own message.
Compare and track your schema
Schema Compare, Schema History snapshots and Data Compare all work on libSQL, as do the Test Data Generator and the structure editor - useful for keeping a Turso database in step with a local SQLite file.
Schema Compare →Plans, dashboard and integrity checks
Estimated plans use SQLite’s EXPLAIN QUERY PLAN, the Server Dashboard and Disk Usage read the database’s page counters, and Maintenance offers REINDEX and the integrity check (the server refuses VACUUM and ANALYZE).
Honest about cancel and paging
The libSQL server cannot interrupt a running statement, so Cancel abandons the request; and a whole result arrives before its first row appears. For very large reads, page with LIMIT and OFFSET.
Connect to Turso or a libSQL server
- Download SQLly for macOS, Windows or Linux from the download page and open it.
- Create a connection and pick libSQL / Turso. The port defaults to 8080, sqld’s own; a Turso host uses HTTPS.
- Enter the host - your
…turso.ioaddress, or the machine running sqld - or paste alibsql://URL, or a plainhttp://orhttps://endpoint. - Paste the auth token, or leave it blank for a local server without authentication. There is no user name or password.
- Test, save and connect. For a self-hosted server behind a bastion, SSH tunnels, proxies, Kubernetes port-forwards and the TLS modes all work.
Every SQLly tool on libSQL / Turso
This is the same engine matrix the app uses to enable or disable its menus, so what you read here is what you get. Where a tool doesn’t apply to libSQL / Turso, the app says why - and so do we.
| Tool | libSQL / Turso |
|---|---|
| Explorer, IntelliSense and hover cards | Yes |
| Estimated execution plans | Yes SQLite's EXPLAIN QUERY PLAN. |
| Server Dashboard | Yes The database's size, free list and contents. |
| Disk Usage and Object Browser | Yes |
| Maintenance menu | Yes REINDEX and the integrity check; the server refuses VACUUM and ANALYZE. |
| Schema Compare and Schema History | Yes |
| Data Compare | Yes |
| Test Data Generator | Yes |
| Table Structure Editor | Yes |
| SSH tunnels, proxies and Kubernetes port-forward | Yes For self-hosted servers. |
| Read-only connections | Yes |
| Auto-rollback safety wrap | Yes |
| Edit rows in the results grid | No Not available on libSQL / Turso yet. |
| Actual (executed) plans | No libSQL exposes SQLite's estimated plan only. |
| Activity Monitor | No libSQL serves each request on its own; there is no session list. |
| Query Insights | No libSQL keeps no query statistics store. |
| Data Transfer | No Cannot write to libSQL yet; export rows as SQL and run them in a query tab. |
| Index Analyzer | No libSQL keeps no index usage counters. |
| Security editor (users, roles, grants) | No Not available on libSQL / Turso. |
| Backup / Restore | No Use Turso's own backups, or copy sqld's data directory. |
| Create and drop database dialogs | No libSQL databases are created on the server. |
| Procedure Mode | No libSQL has no stored procedures. |
| SQL Agent, Extended Events and guided designers | No SQL Server and Azure SQL only. |
Questions about libSQL / Turso in SQLly
Does SQLly work with Turso Cloud?
Yes. Choose libSQL / Turso in the connection editor, enter your …turso.io host and paste the database's auth token, or paste a libsql:// URL with ?authToken= and SQLly fills everything in. The token is kept in your operating system's secure store, and a Turso host is always reached over HTTPS.
Can I connect to a local sqld server without a token?
Yes. Leave the auth token blank for a local server without authentication; sqld's default port 8080 is filled in for you. For a remote self-hosted server, SSH tunnels, proxies, Kubernetes port-forwards and the TLS modes all work.
Do transactions work over libSQL?
Yes. A script with several statements runs as one unit, so BEGIN … COMMIT and the auto-rollback safety setting work, and the first failing statement stops the script with the server's own message.
Why can't SQLly stop a long-running libSQL query?
The libSQL server has no way to interrupt a running statement, so Cancel abandons the request instead. A whole result also arrives before its first row appears, so page very large reads with LIMIT and OFFSET.
Read more
In the docs
Other databases
Bring your libSQL / Turso home to the pig
SQLly is free to start on macOS, Windows and Linux, with no account required.