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 centralized access to every client database, self-hosted on your own infrastructure, so client rows stay on your server. $79 once for your whole team.
Illustration: a per-seat tool at $20 per user per month costs $200+/month for a 10-person team. QueryGlow: $79 once. Your whole team. Every client database.
One license, the same for every team size.
- Whole Team, One Price
- Every Client Database
- Web-Based
- AES-256 Encryption
“Beautiful interface and very intuitive.”
Jean-Francois, Mildor Violon, verified customer
https://db.your-company.com
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.
See it before you pay
Open the live demo (read-only sample database, AI switched off), no signup. One license covers the whole agency, whatever its size.
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.
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 amber, development green, across all 60 of your client connections. The header shows environment, connection, database and table, and on production the Query Editor asks before any write.
A Sidebar Built for Many Clients
Search connections by name, engine, database, host or port. Sort by recently used, group by host, and resize the sidebar for long names. Every row shows the database and host:port.
Paste a URL, Find Databases
A client hands over a DATABASE_URL? Paste it and the form fills itself. Find databases on this server lists every database a login can open and adds them in one go.
Web-Based Access
Give contractors a URL instead of installing software on their machines. When they leave, rotate the shared login and revoke any Agent Access tokens they created. No per-seat licenses to manage.
Separate Instances per Client Group
Run a separate QueryGlow instance per client group, each on its own small server, separate per client. Shut it down when the project ends; a client who wants to keep one buys their own license.
AI SQL Generation
New dev on a project? They describe what they need and review the SQL before it runs. Your own OpenAI, Anthropic or Google key, entered in the app and stored encrypted.
SSH Tunnels Built-In
Reach client servers with your private key, no terminal setup for every new dev. Host keys are pinned on first use, so a client server that suddenly presents a different key is refused.
Backups You Own
./queryglow backup, restore and rollback cover the instance that holds your client credentials, and every ./queryglow update backs up first.
Letting coding agents at a client's staging database? The database MCP server gives each agent a read-only token for the connections you pick, and you can pause any agent with one click.
Contractor Workflow
When a contract ends, rotate the shared login and revoke any Agent Access tokens they created, not fifteen database passwords.
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 and revoke their agent tokens
The old way: Contractor leaves → rotate 15 database passwords → update 15 config files → redeploy 15 apps.
The QueryGlow way: Contractor leaves, rotate the shared login and revoke any Agent Access tokens they created.
Client Isolation Options
Option 1: Single Instance
All clients in one QueryGlow instance. Search the sidebar, sort by recent use, group by host; every row shows the database and host:port, and the header breadcrumb shows environment, connection, database and table. Simpler to manage.
Best for: Smaller agencies, trusted teams
Option 2: Instance Per Client Group
One small server (or VPS) per client group, each with its own QueryGlow instance. Full isolation. Shut it down when the project ends. Two instances on the same server need manual changes.
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 your whole team. Whether you have 5 developers or 50, full-time employees or contractors, the price is the same. Run it on every server you run under the same license, one install on each server. 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: search the sidebar, sort by recent use, group by host, and every row shows the database and host:port. (2) Run a separate QueryGlow instance per client or client group, each on its own small server or VPS, for full isolation; two instances on the same server need manual changes. 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 and the shared login. They access databases through the web UI without ever seeing the stored passwords or SSH keys. Safe Mode blocks destructive queries by default. When the contract ends, rotate the shared QueryGlow login and revoke any Agent Access tokens they created, instead of changing passwords across 15 client databases.
Is QueryGlow safe for junior developers?
Safe Mode is designed for exactly this. It blocks DROP DATABASE always. It blocks DROP TABLE, TRUNCATE and DELETE or UPDATE without WHERE by default. It adds LIMIT 1000 to a read that has none. On a connection marked production, the Query Editor shows the statement and asks before any write runs, and the red badge in the sidebar and header says where you are.
Does client data leave our network?
Rows and query results stay on your server, and QueryGlow has no telemetry. The optional Ask AI call sends table and column names, types and the prompt, never rows, to the AI provider whose key you entered, and your team's browsers load the SQL editor from cdn.jsdelivr.net.
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 and run ./queryglow install; ./queryglow update keeps it current with a backup first and an automatic rollback. Run one instance on a small VPS for the whole agency, or one instance per major client group, each on its own server. Put it behind your company VPN or add Cloudflare Access for extra security.
Stop DMing Credentials
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.
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.