Platforms

The same native SQLly workbench on the desktops where real database work happens.

SQLly brings the same native workbench to macOS, Windows, and Linux. There is also a clearly labeled browser preview for a quick look before you download anything.

One app, three platforms

Not one app with three coats of paint, and not a webview pretending to be native. The interface is drawn on the GPU through each platform's own graphics path, Metal on macOS, Direct3D 11 with DirectWrite on Windows, Vulkan on Linux - from the same Rust source. Your system fonts, your window behavior, your file dialogs.

Which page to read

  • macOS, Windows & Linux - how SQLly draws, opens windows, and renders text on each system, and which processors each build targets. Read it if you want to know what is native on your machine, or why a Linux session uses Wayland or X11.
  • macOS & the Mac App Store - the two ways to run SQLly on a Mac, and the features Apple's sandbox changes in the App Store edition, with what to do instead. Read it before choosing between them.
  • Live preview, the in-tab demo. It runs against a bundled sample database and cannot reach your servers; native dialogs, the keychain, and local files stay in the desktop app.
macOS, Windows & Linux
One GPU-rendered workbench across macOS, Windows, and Linux, using the native graphics path on each rather than a webview in a trench coat.
macOS & the Mac App Store
Two ways to run SQLly on a Mac - the direct download and the Mac App Store edition - and exactly what the App Store edition does differently.

What changes from one platform to the next

The editor, explorer, result grid, tools, and safety features are the same everywhere. The differences are the ones you would expect from your operating system:

macOSWindowsLinux
Shortcut modifier⌘ - for example ⌘B to toggle the explorerCtrl - CtrlBCtrl - CtrlB
Saved passwordsKeychainCredential ManagerSecret Service
Settings and connections~/Library/Application Support/SQLLY/%APPDATA%\SQLLY\~/.config/SQLLY/

Most shortcuts follow the same rule: where these docs show ⌘, Windows and Linux use Ctrl. You can see and change every binding in the keymap. The settings folder holds the same files on every platform, so moving from a Mac to a Linux desktop is a copy, see Files & sync. Passwords never travel with it; each machine's own credential store keeps them.

Getting a build. The Download page lists every release for each platform. The macOS build is signed and notarized for Apple Silicon; the Windows and Linux builds for x64 and ARM64 are a supported beta and are not yet signed, so your system may warn you the first time you open one.

Why not a cloud IDE

Because the job involves credentials to production databases on private networks. A desktop app connects from your machine, using your keychain, your VPN, and your existing network rules - and nothing about your schema or your results has to pass through a third party to get onto your screen. That constraint shapes the rest of the product, so it is worth stating outright.

If you do need SQLly in a browser against your own databases, relay proxy mode runs the browser build through a relay you control, which holds the credentials so the page never sees a password.