RexaDB
Modern database studio for teams who ship.
RexaDB is a modern desktop database studio for PostgreSQL, MySQL, SQLite, MongoDB, and more. Visualize schemas, write SQL, browse data, and let AI handle the heavy lifting — all from one fast, keyboard-friendly app.
Supports 100+ databases through JDBC — PostgreSQL, MySQL, SQLite, MongoDB, Redis, MariaDB, ClickHouse, SQL Server, Supabase, Neon, Turso, PlanetScale, Timescale, and more. Sign in with your provider and your databases appear instantly, no saved connections needed.
Key Features
- Fast data browsing — Virtualized grid that handles millions of rows, with filtering and record inspection
- Lightning queries — Multi-tab SQL editor (Monaco) with split-view results, autocomplete, formatting, EXPLAIN / profiling, and export to CSV, JSON, or Markdown
- Schema visualization — Interactive ER diagrams with real-time updates, relationship explorer, and schema documentation
- AI Agent — Generate complex queries, understand schemas, and get results without switching context (Anthropic, Google, OpenAI, and more)
- Workflow Automation — Scheduled jobs, chained actions, and one-click runtimes
- Safe by design — Read-only mode, transaction safeguards, and connection encryption. Your data never leaves your machine.
- Team-ready — Team workspaces, shared connections, role-based access, SSO, query version control, audit logging
- Cross-platform — Desktop builds for macOS (arm64 / Intel), Windows, and Linux
Supported Databases
PostgreSQL • MySQL • SQLite • MongoDB • Redis • MariaDB • ClickHouse • SQL Server • Supabase • Neon • Turso • PlanetScale • Timescale • +100 more via JDBC
Downloads
Download RexaDB free (no credit card required):
macOS • Windows • Linux
Getting Started (Development)
# install dependencies
npm install
# run web app
npm run dev
# run desktop app (Tauri)
npm run tauri:dev
Install with Nix (NixOS / nix)
RexaDB ships a Nix flake (flake.nix, nix/) with a reproducible dev
shell, per-component packages, the desktop app, and NixOS / Home Manager
modules (Linux-first; macOS gets nix develop + headless packages).
# full toolchain: bun, node, rust, cargo-tauri, JDK 21, WebKitGTK deps
nix develop
# build pieces
nix build .#frontend # Next.js static export
nix build .#rexadb-server # compiled sidecar server
nix build .#rexadb-oracle-bridge
nix build .#java-bridge # bridge.jar + minimal JRE
# desktop app (Linux) — run it, or install via the HM module
nix build .#rexadb
nix run . # launch RexaDB
nix run .#server # sidecar only (REXADB_SERVER_PORT=3867)
# optional: install into your profile
nix profile install .#rexadb
Tagged releases push prebuilt x86_64-linux binaries to the
rexadb Cachix cache (see nixConfig in
flake.nix), so nix run / nix profile install download instead of
compiling on that platform — no setup needed on your end. Other systems
(aarch64-linux, macOS) still build from source. If you see a trust warning
about the cache key, update your flake input to the latest release tag.
If Nix prints ignoring untrusted substituter 'https://rexadb.cachix.org', you are not a trusted user and starts compiling anyway, your daemon runs
multi-user (default on NixOS / Determinate / macOS installs): it discards
cache settings that come from flakes. Register the cache in the system
config instead — this trusts exactly this cache and grants nothing else:
# Linux (NixOS: set nix.settings.extra-substituters /
# nix.settings.extra-trusted-public-keys declaratively instead)
printf '%s\n' \
'extra-substituters = https://rexadb.cachix.org' \
'extra-trusted-public-keys = rexadb.cachix.org-1:pVrB+j93ten7xXFzxhAdQ2m/Eco2yiwfBT0Wk5QgYww=' \
| sudo tee -a /etc/nix/nix.conf
sudo systemctl restart nix-daemon
# macOS
printf '%s\n' \
'extra-substituters = https://rexadb.cachix.org' \
'extra-trusted-public-keys = rexadb.cachix.org-1:pVrB+j93ten7xXFzxhAdQ2m/Eco2yiwfBT0Wk5QgYww=' \
| sudo tee -a /etc/nix/nix.conf
sudo launchctl kickstart -k system/org.nixos.nix-daemon
Alternative: add yourself to trusted-users (root $USER in the same
file). That also fixes every other flake-provided cache at once, but it is
much broader — a trusted user may configure any substituter and use other
restricted settings — so prefer the scoped lines above unless you know you
want that. Single-user Nix installs are unaffected (every user is trusted).
NixOS module (flake input inputs.rexadb.url = "github:RexaDB/RexaDB"):
services.rexadb = {
enable = true;
package = inputs.rexadb.packages.${pkgs.system}.rexadb-server;
};
Home Manager:
programs.rexadb = {
enable = true;
package = inputs.rexadb.packages.${pkgs.system}.rexadb;
};
Notes:
flake.lock is committed for reproducible builds; run nix flake update
to bump inputs..envrc (use flake, for direnv users) is covered by the repo's
.env* gitignore rule — git add -f .envrc to commit it.packages.rexadb is Linux-only (webkitgtk_4_1 / Tauri bundling).
nix flake check --no-build validates evaluation on all systems.- Like the other release builds, the Nix frontend build does not bake in
.env secrets — provide runtime config the usual way.
Updating a Nix install
A Nix install cannot replace its own binary — it lives in the read-only
store — so RexaDB does not update itself there. Instead the app checks the
release feed and shows an Update via nix notice in the app header (and
on the connections screen) when a newer version is out. Dismissing it hides
it until the next release.
How you update depends on how you installed it:
| Install | Update |
|---|
| Configuration flake, unpinned input | nix flake update, then rebuild and switch your configuration |
| Configuration flake, pinned release tag | Change the RexaDB tag in your flake, then rebuild and switch your configuration |
Profile install (nix profile install .#rexadb) | nix profile upgrade — a configuration rebuild does not touch a profile |
# configuration flake
nix flake update
nh os switch ./configuration # your rebuild command
# profile install
nix profile upgrade
nix flake update without an argument updates every input, so it works
whatever you named the RexaDB input in your flake. Settings → App Updates
lists the steps for each way of installing, with a button that copies the
command, and links the release notes.
- Supabase config is baked at build time (
NEXT_PUBLIC_*): the Nix
packages build with placeholder values, so all local-first features
work but Supabase-backed features (sign-in, teams) are inert. Real
secrets must never enter the Nix store; to make a cloud-connected
build, substitute your own values for NEXT_PUBLIC_SUPABASE_URL /
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY in nix/frontend.nix (and
nix/rexadb.nix for the desktop app).
- The Nix desktop build ships with the Tauri auto-updater disabled (it
would otherwise require the release signing key, which never enters
PR/fork builds — signing stays tag-gated in
build.yml). Update via
nix flake update / nix profile upgrade instead.
- Portable
.deb / AppImage installers come from the normal release
workflows (build.yml, arch-appimage.yml). The Nix build’s internal
Tauri .deb is only used to lay out store paths; it is not a portable
Debian package and is not uploaded to GitHub releases.
Links
Sponsors
Thank you to our sponsors for supporting RexaDB:
License
RexaDB is licensed under the GNU General Public License v3.0 (GPL-3.0-or-later).
Copyright
© 2026 RexaDB. All rights reserved.
