Jam SQL Studio Jam SQL Studio for Linux
Quick Install Recommended
Works on Ubuntu, Debian, Fedora, RHEL, Arch, Manjaro, and derivatives. Reads /etc/os-release and uname -m, downloads the matching package for your distribution and CPU architecture (x64 or ARM64), and installs it with your package manager. Uses sudo unless you are already root, and asks first if Jam SQL Studio is already installed.
curl -fsSL https://jamsql.com/install.sh | bash Or download manually:
System requirements
| Distribution | Anything with glibc 2.30 or newer — the highest version Jam SQL Studio's binaries (Electron 34.3.0 and the bundled native modules) link against. The build fails if any binary needs a newer one, and each release is installed and started on Ubuntu 20.04, Debian 11, Rocky Linux 9 and the current Ubuntu LTS, Debian, Fedora and Arch before it ships. In practice: Ubuntu 20.04+, Debian 11+, Fedora 32+, RHEL / Rocky / AlmaLinux 9+, and current Arch. Debian 10 and RHEL 8 ship glibc 2.28 and are too old. |
|---|---|
| CPU architecture | x64 (amd64) and ARM64 (aarch64). Both architectures get all three package formats. |
| Package formats | .deb, .rpm and Arch (.pacman). There is no AppImage, Snap or Flatpak build. |
| Library dependencies | libgtk-3-0, libnotify4, libnss3, libxss1, libxtst6, xdg-utils, libatspi2.0-0, libuuid1, libsecret-1-0, libasound2 (libasound2t64 on newer releases) and libgbm1, plus libappindicator3-1 as a recommendation — the names as declared by the .deb; the .rpm and Arch packages declare the equivalents. Installing through apt, dnf or pacman pulls them in for you. |
| Disk space | The package declares an installed size of about 1 GB. Downloads range from roughly 200 MB for the ARM64 .deb to 350 MB for the x64 .rpm. |
| Runtimes | None to install. Chromium, Node.js and every database driver are bundled — including the Oracle Thin driver, so no Oracle Client is needed. |
| Account | Not required. Jam SQL Studio is free for personal, non-commercial use and works offline. |
Installing on Linux
The install script is the shortest path: it reads uname -m and /etc/os-release, picks the matching package for your architecture and distribution family, downloads it and hands it to your package manager. It uses sudo when you are not already root, and if it finds an existing installation it asks whether to upgrade before touching anything.
Prefer to do it by hand? Download a package above and run the command for your distribution.
Debian, Ubuntu and derivatives
Installing through apt resolves the dependencies in one step. The leading ./ matters — without it apt looks for a package of that name in your repositories.
sudo apt install ./JamSQLStudio-latest-linux-x64.deb Using dpkg instead works too, but it does not fetch dependencies, so follow it with sudo apt-get install -f — which is exactly what the install script does.
Fedora, RHEL, Rocky, AlmaLinux and openSUSE
sudo dnf install ./JamSQLStudio-latest-linux-x64.rpm On systems old enough to predate dnf, swap in yum.
Arch, Manjaro and derivatives
The Arch build is a standard zstd package that we publish with a .pacman extension. Rename it before installing, the same way the install script does:
mv JamSQLStudio-latest-linux-x64.pacman jam-sql-studio.pkg.tar.zst sudo pacman -U jam-sql-studio.pkg.tar.zst Where everything lands
- Application files:
/opt/JamSQLStudio - Command on your PATH:
/usr/bin/jam-sql-studio(registered through update-alternatives where available) - Desktop entry:
/usr/share/applications/jam-sql-studio.desktop, so it appears in your application menu - Package name for later:
jam-sql-studio
On Ubuntu 24.04 and other distributions with a modern AppArmor, the package also installs an AppArmor profile at /etc/apparmor.d/jam-sql-studio. Where the kernel supports unprivileged user namespaces the Chromium sandbox uses those; where it does not, the packaging falls back to the setuid sandbox helper.
Downloading a specific version
Every release keeps a permanent versioned URL next to the rolling latest one, so you can pin a build or roll back without hunting for a mirror:
Every latest alias uses the plain x64 / arm64 spelling, for example https://downloads.jamsql.com/downloads/JamSQLStudio-latest-linux-x64.deb. Versioned filenames keep whatever architecture name the packaging tool itself emits, which is not always the same string:
JamSQLStudio-1.4.20-linux-amd64.debandJamSQLStudio-1.4.20-linux-arm64.debJamSQLStudio-1.4.20-linux-x86_64.rpmandJamSQLStudio-1.4.20-linux-aarch64.rpmJamSQLStudio-1.4.20-linux-x64.pacmanandJamSQLStudio-1.4.20-linux-aarch64.pacman
They all live in the same https://downloads.jamsql.com/downloads/ folder as the latest aliases.
How updates work
Jam SQL Studio checks the release feed about a minute after launch and then once an hour, downloads a newer version in the background and offers to restart into it; a manual check lives in Settings → Updates. Releases are rolled out in stages, so a brand-new version does not always reach every machine on the first day. You can always update by hand instead: re-run the install script, or install the newer package over the current one and your package manager upgrades it in place.
What is in the download
- Six engines in one app: SQL Server and Azure SQL, PostgreSQL, MySQL and MariaDB, Oracle, SQLite, and Azure Data Explorer (Kusto).
- Query editor with IntelliSense, execution plans, SQL notebooks, table explorer, charts, schema compare and data compare.
- A local MCP server so AI agents can work against your databases under your rules.
- Free for personal, non-commercial use, with no account and no sign-in. Pro is $9.99/month or $99/year, adds a commercial-use licence and lifts the caps on a handful of bulk operations, and comes with a 14-day trial that you start by signing in inside the app (no card required).
Not sure which package or architecture applies to your distro? The Linux packaging notes list the tested formats, distro families and dependencies. New here? Start with the getting started guide, then set up your first server in connections.
Frequently asked questions
Which Linux package should I download?
Take the .deb on Ubuntu, Debian, Linux Mint, Pop!_OS, Elementary, Zorin and Kali; the .rpm on Fedora, RHEL, CentOS, Rocky, AlmaLinux and openSUSE; and the Arch package on Arch, Manjaro, EndeavourOS, Garuda and Artix. If you would rather not decide, the install script reads /etc/os-release and uname -m and picks the right package and architecture for you.
Does installing Jam SQL Studio on Linux need root?
Yes. All three packages install system-wide into /opt/JamSQLStudio, so apt, dnf and pacman need root. The install script uses sudo when you are not already root and stops with an explanation if neither is available. There is no per-user install option on Linux.
Is there an AppImage, Snap or Flatpak build?
No. We publish only .deb, .rpm and Arch packages. AppImage was dropped deliberately: it needs FUSE, which plenty of systems do not have installed; the Chromium sandbox fails on hosts without unprivileged user namespaces, which forced a no-sandbox workaround; and the bundled native modules were not resolved reliably from inside the image. Distribution packages get proper dependency resolution and desktop integration instead.
Where does Jam SQL Studio install, and how do I remove it?
The application files go to /opt/JamSQLStudio, a jam-sql-studio command is put on your PATH at /usr/bin/jam-sql-studio, and a desktop entry is installed so the app shows up in your launcher. To remove it, use sudo apt remove jam-sql-studio, sudo dnf remove jam-sql-studio or sudo pacman -R jam-sql-studio.
How do updates work on Linux?
Jam SQL Studio checks for updates about a minute after launch and then once an hour, downloads the new version in the background and offers to restart into it. You can force a check from Settings → Updates. You can also update by hand at any time: re-run the install script, or install the newer package over the current one and your package manager upgrades it in place.