Credentials Over Slack
DMing database passwords in Slack. Pinning .env files in channels. It's insecure and you know it.
For Digital Agencies
Manage 50+ Client Databases Without the Chaos
Stop sharing .env files over Slack. Give your team secure, centralized access to every client database — self-hosted on your own infrastructure, so client data never leaves your network. $79 once, unlimited devs.
Illustration: a per-seat tool at $20 per user per month costs $200+/month for a 10-person team. QueryGlow: $79 once. Unlimited devs. Unlimited clients.
- Unlimited Devs
- Unlimited Clients
- Web-Based
- AES-256 Encryption
The Agency Credential Nightmare
20 clients × 3 environments = 60 connection strings. Here's what goes wrong.
Per-Seat Pricing Explosion
Illustration: a per-seat tool at $20 per user per month. 10 devs × $20/seat = $200/month. Add 3 contractors for a sprint? Another $60. Costs scale with headcount.
Contractor Offboarding
Contract ends. Now you need to rotate passwords on 15 databases. Or you don't, and hope for the best.
Dev/Staging/Prod Confusion
60 connection strings across 20 clients. Someone eventually runs DELETE on the wrong database.
Zero Per-Seat Costs
Illustration: a per-seat tool at $20 per user per month vs QueryGlow
| Team Size | Per-Seat SaaS | QueryGlow |
|---|---|---|
| 5 developers | $1,200/year | $79 once |
| 10 developers | $2,400/year | $79 once |
| 15 developers | $3,600/year | $79 once |
| 20 developers | $4,800/year | $79 once |
| + 5 contractors | +$1,200/year | $0 extra |
Agencies fluctuate. Freelancers come and go. Don't pay $240/year for a seat used for 2 weeks.
Built for Agency Workflows
Multiple clients. Rotating contractors. Junior devs. We get it.
Centralized Credentials
All credentials encrypted with AES-256-GCM on your server. Devs access databases through the UI without seeing raw passwords.
Environment Color Coding
Production is red. Staging is yellow. Dev is green. Visual safety rails across all 60 of your client connections.
Multiple Instances
Deploy separate QueryGlow instances per client on your own servers. Clean isolation. Shut the instance down when the project ends; a client who wants to keep one buys their own license.
Web-Based Access
Give contractors a URL instead of installing software on their machines. When they leave, rotate the shared login. No app installs on their machines, no per-seat licenses to manage.
AI SQL Generation
New dev on a project? They describe what they need, get working SQL. OpenAI, Claude, or Gemini—your API keys.
SSH Tunnels Built-In
Connect to client servers securely. Paste your private key directly—no terminal setup for every new dev.
Clean Contractor Workflow
One login to rotate when contracts end, not fifteen.
1
Share URL
Give the contractor your QueryGlow URL
2
They Work
Full database access without raw credentials
3
Contract Ends
Rotate one shared login, not fifteen database passwords
The old way: Contractor leaves → rotate 15 database passwords → update 15 config files → redeploy 15 apps.
The QueryGlow way: Contractor leaves, rotate one shared login, done.
Client Isolation Options
Option 1: Single Instance
All clients in one QueryGlow instance. Use naming conventions (Client_Prod, Client_Staging) and color coding. Simpler to manage.
Best for: Smaller agencies, trusted teams
Option 2: Instance Per Client
Deploy separate QueryGlow instances per major client on your servers. Full isolation. Shut it down when the project ends.
Best for: Enterprise clients, strict compliance
Six Engines Your Clients Use
One tool for PostgreSQL, MySQL, MariaDB, SQLite, CockroachDB and TimescaleDB client databases. No more switching between pgAdmin, MySQL Workbench and SQLite Browser.
Agency FAQs
How much does QueryGlow cost for our agency?
QueryGlow is $79 once for unlimited users. Whether you have 5 developers or 50, full-time employees or contractors, the price is the same. No per-seat fees, no monthly subscriptions, no surprise bills when you scale up for a big project.
Can we isolate client databases from each other?
Yes. You have two options: (1) Keep all clients in one QueryGlow instance with clear naming and color coding, or (2) Deploy separate QueryGlow instances per client or client group on your own servers for full isolation. Each instance has its own encrypted credential store. When a project ends, shut that instance down. The license keeps the software on your infrastructure; a client who wants their own installation purchases their own license.
How do we handle contractor access?
Give contractors the QueryGlow URL. They access databases through the web UI without ever seeing raw connection strings or passwords. Safe Mode protects against accidents. When the contract ends, rotate the one shared QueryGlow login instead of passwords across 15 client databases.
Is QueryGlow safe for junior developers?
Yes. Safe Mode is designed for exactly this. It blocks DROP DATABASE (always, cannot be bypassed), prevents DELETE/UPDATE without WHERE clauses, and auto-limits SELECT queries to 1000 rows. Environment color coding adds another visual layer—red means production, proceed with caution.
What databases do our clients typically use?
QueryGlow supports PostgreSQL, MySQL, MariaDB, SQLite, CockroachDB, and TimescaleDB—6 databases in one tool. Most agency clients use Postgres or MySQL, but you're covered for the edge cases too.
How do we deploy QueryGlow for the agency?
Clone the repo, run docker compose up --build, done. You can run it on a single small VPS for the whole agency, or deploy separate instances per major client. Put it behind your company VPN or add Cloudflare Access for extra security.
Stop DMing Credentials
Try the live demo first. No signup, no credit card. If it clicks, grab a lifetime license for $79.