Credentials in the Cloud
Cloud database tools store your credentials on their servers. One breach, and your production database is exposed.
Stop sending your database credentials to third-party clouds. QueryGlow runs 100% on YOUR servers. Zero telemetry. Zero tracking. Complete control.
Every cloud tool is another place your credentials live. Another potential breach point.
Cloud database tools store your credentials on their servers. One breach, and your production database is exposed.
Cloud tools can see your queries, your schema, your data. Even if they promise not to look, the access exists.
GDPR, HIPAA, SOC2—using cloud tools means adding another data processor to your compliance documentation.
Cloud tools can change pricing, terms, or shut down. Self-hosted means you control your tools forever.
| Aspect | Cloud Tools | QueryGlow (Self-Hosted) |
|---|---|---|
| Data Location | Their servers | Your servers only ✨ |
| Credential Storage | In their database | AES-256-GCM encrypted on your server ✨ |
| Telemetry | Usually yes | Zero—we never see anything ✨ |
| GDPR Compliance | Another data processor to document | No third-party data transfer ✨ |
| Vendor Shutdown Risk | Lose access if they close | You own the code forever ✨ |
| Network Access | Must expose DB to internet | Runs inside your VPC ✨ |
| Air-Gapped Support | Not possible | Full offline operation ✨ |
| Pricing | Monthly per user | $79 once, unlimited users ✨ |
Cloud
Their servers
QueryGlow
Your servers only ✨
Cloud
In their database
QueryGlow
AES-256-GCM encrypted on your server ✨
Cloud
Usually yes
QueryGlow
Zero—we never see anything ✨
Cloud
Another data processor to document
QueryGlow
No third-party data transfer ✨
Cloud
Lose access if they close
QueryGlow
You own the code forever ✨
Cloud
Must expose DB to internet
QueryGlow
Runs inside your VPC ✨
Cloud
Not possible
QueryGlow
Full offline operation ✨
Cloud
Monthly per user
QueryGlow
$79 once, unlimited users ✨
QueryGlow is packaged for Docker. Build from source and run on any VPS (DigitalOcean, Hetzner, AWS, your office server) or locally on your laptop.
# docker-compose.yml
services:
queryglow:
build: . # Build from source
ports:
- "3000:3000"
environment:
- SESSION_SECRET=${SESSION_SECRET}
- DATA_DIR=/app/data
volumes:
- queryglow-data:/app/data
volumes:
queryglow-data:5 minutes from git clone to running instance. No complicated setup.
Connect to databases inside your VPC without opening public ports. QueryGlow runs inside your firewall.
We don't track your queries. We don't see your schema. Everything stays on your machine.
Air-gapped environment? No problem. QueryGlow works fully offline (AI features need API access).
Self-hosted is just the start. QueryGlow has multiple layers of protection.
All database credentials are encrypted at rest with AES-256-GCM. Even with server access, passwords are unreadable without the key.
Blocks DROP DATABASE (always), prevents DELETE/UPDATE without WHERE, auto-limits SELECT to 1000 rows. On by default.
Connect to databases behind firewalls without exposing ports. Paste your private key directly—ephemeral ports for security.
When using AI SQL generation, only your schema (table/column names) is sent. Your actual row data never leaves your server.
No analytics, no tracking, no "phone home." QueryGlow doesn't know when you use it, what you query, or who your users are.
AI features use YOUR API keys (OpenAI, Claude, Gemini). No markup, no middleman, no key sharing.
Companies that can't or won't send database credentials to third-party clouds.
Healthcare, finance, government—anywhere compliance requires data control.
Networks with no internet access. QueryGlow works fully offline (AI features excepted).
Organizations that make data privacy a core value, not just a checkbox.
$79 once. Your servers. Your data. Forever.