Your Database Credentials Stay on Your Server

Stop sending your database credentials to someone else's cloud. QueryGlow runs on your server, and your rows never leave it. No telemetry. No tracking.

Hosted tools often charge per user per month and keep your credentials. QueryGlow: $79 once. Your server. Your whole team.

Try the live demo
  • Zero Telemetry
  • AES-256 Encryption
  • GDPR-Friendly
  • Safe Mode by Default
https://db.your-company.com
QueryGlow Data Browser showing a customers table on a production PostgreSQL connection

QueryGlow 1.3.0 on your own server, opened in the browser.

The Problem with Cloud Database Tools

Every cloud tool is another place your credentials live. Another potential breach point. It's the same instinct that has teams self-hosting Supabase: your data on your servers, end to end.

Credentials in the Cloud

Cloud database tools store your credentials on their servers. One breach, and your production database is exposed.

Someone Else in the Path

A hosted tool sits between you and your database, so your queries and results pass through infrastructure you do not run.

Another Data Processor

GDPR, HIPAA, SOC 2: every hosted tool is one more data processor in your compliance documentation.

Vendor Lock-in

Cloud tools can change pricing, terms, or shut down. Self-hosted means you control your tools forever.

Cloud Tools vs Self-Hosted

Data Location

Cloud

Their servers

QueryGlow

Your servers only

Credential Storage

Cloud

In their database

QueryGlow

AES-256-GCM encrypted on your server

Telemetry

Cloud

Varies by vendor

QueryGlow

None. The app never phones home, not even for updates

GDPR Compliance

Cloud

Another data processor to document

QueryGlow

Rows stay on your server; outside parties are the optional AI call (schema only) and cdn.jsdelivr.net, which serves the SQL editor to browsers

Vendor Shutdown Risk

Cloud

Lose access if they close

QueryGlow

Source code included, perpetual 1.x license

Network Access

Cloud

Needs a route from their cloud to your database

QueryGlow

Runs inside your VPC

Updates

Cloud

On the vendor's schedule

QueryGlow

One command when you choose: backup first, automatic rollback

Pricing

Cloud

Often per user per month

QueryGlow

$79 once, your whole team on one install

See it before you pay

Open the live demo (read-only sample database, AI switched off), no signup. If it fits, buy once and run it on your own server for your whole team.

Try the live demo

Stripe checkout. You'll need a GitHub account for the repo invite. No refunds, so try the read-only demo first.

Deploy on Your Infrastructure

QueryGlow runs in Docker on a Linux server you control: any VPS (DigitalOcean, Hetzner, AWS) or your office server. You need Docker (512 MB RAM minimum, 1 GB recommended), a domain pointing at the server for HTTPS, and a non-root user with sudo.

git clone [email protected]:mxfschr/queryglow.git
cd queryglow
./queryglow install

# later, whenever you choose
./queryglow update

Clone the repository and run ./queryglow install. It sets up nginx, the HTTPS certificate, the login and the app on a Linux server that already has Docker with the compose plugin, or plugs into the nginx you already run.

./queryglow update backs up first, checks that the new version is serving and rolls back on its own if not. backup, restore and rollback keep your QueryGlow settings and data in backups you own. How updating works and what shipped in each release.

  • Private Network Access

    Connect to databases inside your VPC without opening public ports. QueryGlow runs inside your firewall.

  • Zero "Phone Home"

    We don't track your queries. We never see your schema. Your rows stay on your server; only the optional AI call sends the schema and your prompt to the provider you chose. Even the update check is a git fetch against your own remote, and only when you run it.

  • Behind Your Firewall

    Restrict port 443 to your VPN or office IPs; the installer needs a public DNS name and port 80 open for the certificate. No telemetry, no phone home. The browser fetches the SQL editor from cdn.jsdelivr.net, so keep that host reachable.

Security Built In

Self-hosted is just the start. QueryGlow has multiple layers of protection.

AES-256-GCM Encryption

Database passwords, SSH keys and AI keys entered in the app are encrypted at rest with AES-256-GCM, using a key only your server holds.

Web-Based Access

Self-hosted and web-based. Open your databases from any device with a browser, behind nginx Basic Auth over HTTPS. Your rows stay on your server.

SSH Tunnels with Host Key Pinning

Reach databases behind a bastion without opening ports. Host keys are pinned on first use; a server that presents a different key is refused, with both fingerprints shown.

Verify Server Certificate

SSL/TLS to your database, with an optional check of the server certificate against the public certificate authorities, per connection.

AI Sees Schema, Never Rows

Ask AI sends your database type, table and column names with their types, and your prompt. Never rows.

Your Own AI Keys

Your own OpenAI, Anthropic or Google key, entered in the app and stored encrypted on your server, with a Test button. A key in .env still wins.

Production Write Check

On a connection marked production, the Query Editor shows the statement and asks before any INSERT, UPDATE, DELETE or DDL runs. On by default.

Agents You Can See and Pause

AI agents get scoped tokens, read-only by default. Every call shows up in the Activity tab, and you can pause one token or all of them.

Zero Telemetry

No analytics, no tracking, no phoning home. QueryGlow does not know when you use it, what you query, or who your users are.

Built For Privacy-First Teams

Security-Conscious Teams

Companies that can't or won't send database credentials to third-party clouds.

Regulated Industries

Healthcare, finance, government: anywhere compliance requires data control.

Locked-Down Networks

Restrict access to your VPN or office IPs. The installer needs a public DNS name and port 80 reachable so Let's Encrypt can issue and renew the certificate. No telemetry, no phone home. Your rows never leave your server. What does go out: the optional Ask AI call (schema and prompt), the browser loading the SQL editor from cdn.jsdelivr.net, certificate renewal with Let's Encrypt, and the git fetch when you run ./queryglow update.

Privacy-First Companies

Organizations that make data privacy a core value, not just a checkbox.

6 Databases, Your Rows Stay on Your Server

One license covers PostgreSQL, MySQL, MariaDB, SQLite and TimescaleDB, and distributed setups are covered too, with a CockroachDB GUI running on the same self-hosted deployment.

PostgreSQLMySQLMariaDBSQLiteCockroachDBTimescaleDB

Frequently Asked Questions

What does "self-hosted" actually mean?
Self-hosted means you run QueryGlow on your own server: your VPS (DigitalOcean, Hetzner, AWS) or your office server. Your rows never touch our servers or any third-party cloud. You get the source code, run ./queryglow install on your server, and it runs there.
Does QueryGlow send any data to your servers?
No. QueryGlow has no telemetry, no tracking and no phoning home. We don't know when you use it, what databases you connect to, what queries you run, or how many people use it. Your rows never leave your server. What does go out: the optional Ask AI call to the provider you pick (schema and prompt, never rows), your browser loading the SQL editor from cdn.jsdelivr.net, certificate renewal with Let's Encrypt, and a git fetch against your own remote when you run ./queryglow update (or status, if you turned that check on).
Is QueryGlow GDPR compliant?
QueryGlow's self-hosted architecture is GDPR-friendly by design. You host it yourself and your rows stay on your server, so you keep control over data processing. There is no third-party processor for your data unless you enable the optional AI assistant, which sends table and column names, types and your prompt (never rows) to the AI provider you chose. Your browser also fetches the SQL editor from cdn.jsdelivr.net. Consult your legal team for your specific compliance requirements.
How are database credentials stored?
Database passwords, SSH keys and AI keys entered in the app are encrypted at rest with AES-256-GCM. The encryption key is derived from your SESSION_SECRET environment variable. Even if someone gains access to your QueryGlow server's data directory, they cannot read your database passwords without the encryption key.
How do updates reach a self-hosted install?
Only when you run them. ./queryglow update backs up your settings and app data first, checks the new nginx config before anything restarts, verifies the new version is serving, and rolls back to the previous release on its own if it is not. ./queryglow backup, restore and rollback are there when you need them. The app itself never checks for updates.
Can I run QueryGlow on a locked-down network?
Yes, with one condition at install time: the installer needs a public DNS name pointing at the server and port 80 reachable from the internet, so Let's Encrypt can issue and renew the certificate. Beyond that, restrict port 443 to your VPN or office IPs, or put Cloudflare Access in front as an extra layer. Outbound traffic is limited to the optional Ask AI call, certificate renewal with Let's Encrypt, and the git fetch when you run ./queryglow update. Your browser loads the Monaco SQL editor from cdn.jsdelivr.net, so on a network with no internet access the Query Editor will not load unless that host is reachable; the Data Browser does not depend on it.
What's the difference between this and cloud database tools?
Hosted database tools keep your credentials on their servers, route your queries and results through their infrastructure, and add another vendor to your compliance documentation. QueryGlow runs on your infrastructure. We never see your data, your credentials, or your queries.
Which web-based database client can I self-host with Docker?
QueryGlow is a web-based database client built for self-hosting with Docker: ./queryglow install on a Linux server sets up the app, HTTPS through Let's Encrypt and the login, and your team opens it from one URL. It works with PostgreSQL, MySQL, MariaDB, SQLite, CockroachDB and TimescaleDB, encrypts saved database passwords with AES-256-GCM and costs $79 once for the whole team, source code included.
Does QueryGlow have per-user accounts and roles?
No. QueryGlow has no per-user accounts or roles: sign-in happens at the web server with HTTP Basic Auth over HTTPS, and everyone who signs in has the same access. What limits the risk instead: by default, Safe Mode blocks destructive statements such as DROP TABLE, TRUNCATE and DELETE or UPDATE without WHERE, and the Query Editor asks before any write on a connection marked production. Each connection can use a database user that has only the grants it needs. AI agents get their own tokens, scoped to the connections you choose and read-only by default, and you can pause or revoke them. When someone leaves the team, you change the password on your server with htpasswd.
  • “fast and responsive”
    Jean-Francois, Mildor Violon, verified customer
  • “Beautiful interface and very intuitive.”
    Jean-Francois, Mildor Violon, verified customer

Watch his video story (2:45)

Take Control of Your Data

Try the live demo first: the real app on a sample database, read-only, AI switched off, no signup. If it clicks, grab a lifetime license for $79.

Try the live demo

After you pay: a GitHub invite to the private repository, then ./queryglow install on your server. Every 1.x update is one ./queryglow update away.

Related Solutions