# Letos: a Qt SQLite database manager, formerly SQLiteStudio

> Letos is a free, open source SQLite database manager written in C++ with Qt, renamed from SQLiteStudio. It ships prebuilt packages for most platforms, and it is the wrong tool for client-server databases.

**pawelsalawa/letos** — A free, open source, multi-platform SQLite database manager.

- Repository: https://github.com/pawelsalawa/letos
- Website: https://letos.org
- Stars: 6,763 · Forks: 662
- Language: C
- License: NOASSERTION
- Published: 2026-09-22 · Updated: 2026-09-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/pawelsalawa-letos

## The gap Letos fills for anyone holding a .sqlite file

SQLite has no server process. The database is a file, and everything that touches it is a library linked into some other program. That makes SQLite easy to embed and awkward to inspect: there is no connection string to paste into a general-purpose database client, because there is nothing listening on a port. Letos exists for that gap. It is a desktop application that opens SQLite files directly and gives you a GUI over them.

The audience is narrow and specific. Developers who embed SQLite in an application and need to look at what the application actually wrote. Analysts handed a .db file exported from somewhere else. Anyone maintaining a small local dataset who does not want to install a server just to run a few queries. The README describes the project as "a free, open source, multi-platform SQLite database manager written in C++, with use of Qt framework," and the repository topics list sqlite, sqlite3-database, sqlcipher and wxsqlite3 alongside qt and cpp. The presence of SQLCipher and wxSQLite3 in that list matters: these are the encrypted SQLite variants, which tells you the project targets more than plain unencrypted files.

The name change is the first thing to get straight. The project was previously called SQLiteStudio and was renamed to Letos. The README gives the reason plainly: to avoid confusion with the official SQLite project, since Letos is "an independent application not affiliated with the SQLite authors." If you search for SQLiteStudio today you will find this project under its old name, and older 3.x.x builds are still distributed through a Dropbox folder linked from the README. That history is useful when you find tutorials or forum posts written before the rename.

## How the Qt application and its plugins are laid out

The repository layout tells you most of what you need about the architecture. At the top level there is a Letos/ directory and a Plugins/ directory, plus scripts/, an InnoSetupScript.iss file for the Windows installer, and crowdin.yml for translation management. The split between Letos/ and Plugins/ is the structural fact worth noting: the core application and its extensions are separate trees, so database-specific behaviour can live in plugins rather than in the main binary.

C++ with Qt is the whole stack. Qt is a cross-platform application framework, which is how one codebase produces builds for several operating systems, and the topics list qt and qt5 rather than any newer major version. The README does not describe the internal module boundaries, the plugin interface, or the query execution path, so anything beyond the directory split would be guesswork. What can be said from the repository is that the compiled artifact is a native desktop application, not an Electron or browser-based tool, and that the encryption support implied by the sqlcipher and wxsqlite3 topics is part of what the application handles.

The repository also carries ChangeLog.md and release-checklist.md at the top level, which is a maintenance signal rather than a feature. A release checklist committed to the repository suggests releases follow a written procedure rather than being cut ad hoc. The last push to the repository was on 2026-09-18, and releases 4.0.1, 4.0.2 and 4.0.3 landed between 2026-07-06 and 2026-08-12. That is a project still receiving commits and tagged releases.

## Installing Letos and opening a database for the first time

The README does not walk through a first session, so the practical path is: get a build for your platform, then open a file. The preferred route according to the README is your operating system package manager, if it carries a package. The README links a Repology badge for packaging status, which is where you check whether your distribution has one. The second route is the Releases page, which the README calls the source of the most recent packages.

If your distribution packages Letos, installation is a single command. The package name varies by distribution, so check the Repology listing rather than assuming; on Debian-derived systems the pattern looks like this.

```bash
sudo apt install letos
```

After installation, launching the application gives you a window with no database attached. In a SQLite GUI the normal first step is to register or add a database file, which points the application at a path on disk rather than at a host and port.

```bash
letos
```

There is no connection dialog asking for credentials, because SQLite has none. You select the file, and the application reads it in place. The README does not document the exact menu labels or the dialog flow, so treat the on-screen wording as authoritative over anything written elsewhere.

If your platform has no package and you would rather build from source, the README points to a wiki page titled Compiling_application_from_sources rather than putting build instructions in the README itself. That page is the place to look for the Qt version and dependency list, and it is the only source the project offers for that step.

## Where Letos stops being the right tool

The limitation is in the name. Letos manages SQLite, and SQLite is an embedded, file-based engine. It is not a client for PostgreSQL, MySQL, MariaDB, SQL Server or anything else that runs as a server. If your work is mostly against a networked database, this application does not address it, and no amount of configuration changes that.

A second constraint follows from the packaging model. The README tells you to check whether your OS package manager has a package and otherwise to use the Releases page. That means currency varies by platform: a distribution package can lag well behind the tagged releases, and the README itself frames the Releases page as where the most recent packages live. If you need a specific recent version, the distribution route may not give it to you.

There is also a licensing wrinkle worth reading before you ship anything. The repository's licence is classified as NOASSERTION, meaning the standard tooling could not map it to a known identifier. Separately, the README states that official letos.org builds contain a proprietary icon set, Icons8, licensed to Letos by icons8.com, with more detail on a wiki page. The application is described as free to use including in commercial environments, and the badges claim no paid edition and no telemetry, but the icon set is a distinct component from the code. If you redistribute builds or bundle the application, that distinction is the thing to read up on. This is not legal advice; read the LICENSE file and the Icons8 wiki page yourself.

Finally, the README documents no command-line interface and no scripting mode. If your workflow is automated, headless or driven from a shell, a Qt desktop application is the wrong shape for it.

## How Letos differs from the sqlite3 shell and from DB Browser for SQLite

The obvious alternative for inspecting a SQLite file is the sqlite3 command-line shell that ships with SQLite itself. The difference is not capability so much as interface and workflow. The shell is text, scriptable, pipeable and available almost anywhere SQLite is installed; you type SQL and read tabular output in a terminal. Letos is a GUI application built on Qt, with a window, menus and dialogs, and its distribution model is a downloaded or packaged desktop binary rather than something already on the machine. If you want to run a query inside a CI job or a shell script, the shell wins outright. If you want to browse a schema, edit rows and see results without composing SQL for every step, the GUI is the point.

DB Browser for SQLite occupies the same category as Letos: a free, open source, cross-platform graphical SQLite manager. Both open SQLite files directly and both are desktop applications. The distinguishing details visible in this repository are the implementation and the extension surface. Letos is C++ with Qt, and the repository separates a Plugins/ tree from the core Letos/ tree, with sqlcipher and wxsqlite3 among the listed topics, which points at encrypted-database support and a plugin-based extension model. The README does not enumerate the plugins or compare features against any other tool, so a feature-by-feature comparison is not something the project's own documentation supports. Choose on the specifics you can verify: the encryption variants you need, the platform packages available to you, and whether the plugin layout matters for your workflow.

## Maintenance, releases and what upgrading costs you

The commit and release record is the strongest signal here. The last push was on 2026-09-18, and three releases were tagged in the preceding six weeks: 4.0.1 on 2026-07-06, 4.0.2 on 2026-08-07 and 4.0.3 on 2026-08-12. The repository is not archived. For a desktop tool, that cadence means you should expect to update, and the README's own guidance tells you where from: the Releases page for the most recent packages, or your OS package manager if it has one.

The upgrade cost depends on which route you took. If you installed through a distribution package, upgrades arrive on the distribution's schedule, which the README implicitly acknowledges by pointing to Releases for the newest builds. If you installed a release artifact, you check the Releases page yourself. Nothing in the README describes an in-application updater, a migration step for the application's own settings, or a rollback procedure, so plan on a manual reinstall when a new version matters to you. The ChangeLog.md file in the repository is where release-to-release changes are recorded; the README does not summarise them.

On licensing, the practical points are the NOASSERTION classification on the repository and the separate Icons8 icon set in official builds. The README's claim that Letos is free to use, including commercially, and that there is no paid edition, describes the project's intent. Whether that matches your organisation's requirements is a question for whoever reads licences where you work, starting from the LICENSE file.

## Conclusion

Adopt Letos if you work with SQLite files directly and want a desktop GUI that is free in commercial environments and collects no telemetry. Do not adopt it if your data lives in PostgreSQL, MySQL or another client-server engine, or if you need a scriptable command-line tool rather than a Qt application. Before committing, check the Releases page for your platform, confirm your package manager carries a current build, and read the wiki FAQ entry on the SQLiteStudio rename so the older name does not confuse your team.

## FAQ

### What is Letos?

It is a free, open source, multi-platform SQLite database manager written in C++ with the Qt framework. It was previously known as SQLiteStudio and was renamed to avoid confusion with the official SQLite project.

### How do I use Letos?

Install a build for your platform, either from your OS package manager if it has a package or from the Releases page, then launch the application and point it at a SQLite database file. The README does not document the menu flow, so follow the on-screen dialogs.

### Is Letos the same project as SQLiteStudio?

Yes. The README states the project was previously known as SQLiteStudio and that the name was changed to avoid confusion with the official SQLite project. Older 3.x.x versions are still distributed under the SQLiteStudio name from a Dropbox folder linked in the README.

### Does Letos work with databases other than SQLite?

No. The README describes it as a SQLite database manager, and SQLite is a file-based engine with no server process. There is no indication in the README that it connects to client-server engines such as PostgreSQL or MySQL.

### Can I use Letos in a commercial environment?

The README states Letos is free to use, including in commercial environments, and the project badges claim no paid edition. Note that official letos.org builds contain a proprietary Icons8 icon set licensed separately, and the repository licence is classified as NOASSERTION, so read the LICENSE file and the Icons8 wiki page before redistributing.

## Sources

- [Issues](https://github.com/pawelsalawa/letos/issues)
- [pawelsalawa/letos on GitHub](https://github.com/pawelsalawa/letos)
- [Project website](https://letos.org)
- [README](https://github.com/pawelsalawa/letos/blob/master/README.md)
- [Releases](https://github.com/pawelsalawa/letos/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/pawelsalawa-letos