Are passwords sent anywhere?

No. Parsing runs locally; secrets never leave your Mac.

Which schemes are supported?

Common SQL and cache URI schemes including Postgres, MySQL, and Redis-style URLs.

Is there a browser demo?

Yes. Try the parser here, then use the desktop app for offline clipboard detection.

Connection String Parser

Break apart database connection strings for Postgres, MySQL, Redis, and other engines without pasting credentials into a public parser. DataEngUtils extracts host, port, database, user, and query parameters locally — critical when rotating secrets, debugging VPN issues, or documenting which environment a stale .env entry points to. Data platform teams use it daily because connection URIs show up in logs, Helm values, and incident threads where exfiltrating even redacted strings to a website is unacceptable. The parser keeps passwords masked in the UI while still showing the parameters you need to compare staging versus production endpoints.

Try it free

InputOutput

How it works

1. Paste a URI
Drop a postgres://, mysql://, or redis:// string into the parser.
2. Review components
See normalized fields and flags such as sslmode or application_name.
3. Copy safe snippets
Share host and database names without exposing passwords in screenshots.

Why not use an online tool?

Online inspectors tools require uploading your pipeline inputs to a third-party server. For production work, that is a security and compliance risk. DataEngUtils runs locally — same convenience, none of the exposure.