DataGrip runs on current Linux desktops through JetBrains Toolbox, a standalone tarball, or Snap. Toolbox is the recommended route when you want JetBrains to manage updates and multiple IDE versions. A standalone install gives you an explicit location, while Snap updates itself and needs classic confinement.
Check whether your Linux desktop is supported
JetBrains lists Ubuntu 24.04 and 26.04 LTS, Fedora 43 and 44, Debian 13, and Amazon Linux 2023 among supported distributions. DataGrip needs an x86_64 or arm64 CPU, 8 GB of RAM, 10 GB of disk space, and glibc 2.28 or later. You do not need a separate Java installation because DataGrip includes JetBrains Runtime.
Before choosing an installer, keep a Linux package management guide nearby if your distribution uses a package workflow you have not used before. The choice affects updates, permissions, and where DataGrip stores its files.
Choose an installation route
| Route | Choose it when | What manages updates |
|---|---|---|
| JetBrains Toolbox | You use more than one JetBrains IDE or need to switch versions. | Toolbox |
| Standalone tarball | You need DataGrip in a specific directory or want a manual install. | You |
| Snap | Your distribution runs snapd and automatic updates suit your desktop. | Snap |
JetBrains recommends Toolbox for managing its products and versions. The standalone route is useful when an organization requires a specific install path. JetBrains also documents performance and file-management limitations with the DataGrip Snap, so use Toolbox when those symptoms affect your work.
Install DataGrip with JetBrains Toolbox
Download the Linux Toolbox tarball from the JetBrains Toolbox page. On Debian and Ubuntu, JetBrains lists libxi6, libxrender1, libxtst6, mesa-utils, libfontconfig, libgtk-3-bin, tar, dbus-user-session, and libxcb-keysyms1 as required packages.
Extract the downloaded archive into a directory you own, then start Toolbox from its bin directory. Replace the placeholder with the archive name your browser downloaded.
tar -xvf jetbrains-toolbox-*.tar.gz -C ~/.local/share
cd ~/.local/share/jetbrains-toolbox-*/bin
./jetbrains-toolbox
Select DataGrip in Toolbox and choose Install. Toolbox creates a desktop entry on first launch, and it can install a specific available version when you need one. If you also use another JetBrains database or editor tool, compare its setup with this IntelliJ IDEA installation guide.
Install the standalone DataGrip tarball
Download the Linux tarball from the official DataGrip download page. Pick the ARM64 archive only for an arm64 machine. Extract every upgrade into a clean directory rather than over an existing installation.
sudo tar xzf datagrip-*.tar.gz -C /opt
cd /opt/DataGrip-*/bin
./datagrip.sh
The launcher starts DataGrip from the extracted installation. After the first launch, use Tools > Create Desktop Entry if you want it in your application menu. A Linux command line guide can help when you need to inspect permissions or launch a program from an install directory.
Install DataGrip with Snap
DataGrip is available from Snapcraft. Ubuntu includes snapd by default. On another supported distribution, install and start snapd before installing DataGrip.
sudo snap install datagrip --classic
datagrip
The classic flag is required because the DataGrip Snap needs broad system access. Snap installs the stable channel by default and refreshes it automatically. Use the DataGrip Snap page for current channel details rather than copying a version number into an install command.
Create your first database connection
Open or create a project, then add a data source for your database engine. DataGrip needs the host, port, database name, and authentication details. It loads cached metadata at startup and does not automatically establish each database connection.
Use a local development database first. If you are preparing MySQL data for the connection, make a recoverable copy with this MySQL backup guide before running schema changes or data edits.
Use SSH or TLS for remote databases
A successful login does not decide whether a remote database connection is appropriate. Set the database host and port explicitly, then configure an SSH tunnel or TLS in the data source settings when your database requires it. Keep credentials out of shared project files and avoid exposing a database port just to make a desktop client connect.
If the database runs beside a web application, this LAMP installation guide explains the local service components you may be connecting to. Containerized databases need separate network and volume choices, covered in this Docker and Podman tutorial.
Verify the installation
- Start DataGrip from Toolbox, your desktop menu, the standalone launcher, or the datagrip command.
- Create a project and add a local development data source.
- Use Test Connection before browsing or changing database objects.
- For a remote server, confirm its SSH or TLS requirement before saving credentials.
Start with one disposable connection, verify the driver and network settings, then add production access with the database team’s authentication and transport requirements. DataGrip installs the IDE. Your database access policy still controls what that IDE can reach.