Connect a database
Point MetaGuard at your own Postgres or MySQL and every tool on the left — PII scanning, governance scoring, quality checks, lineage — runs against your real schema instead of the sample catalog.
The URL Supabase, Neon, Railway, PlanetScale and RDS all hand you. It is parsed in your browser and never stored.
What happens to your credentials
Never stored on the server
There is no user account and no database behind MetaGuard. Credentials arrive in one request, open one connection, and are gone when the request ends.
Held only in this browser tab
They live in sessionStorage, which the browser wipes when you close the tab. “Disconnect & forget” clears it immediately.
Read-only, always
Every session is opened with READ ONLY set at the transaction level, so MetaGuard cannot modify your data even by accident.
Your rows stay in your database
Profiling runs aggregate queries — counts of nulls, distinct values, and pattern matches. No cell value is ever selected, shown, or sent to the AI model. Only column names and types reach Gemini.
Before you connect
- Use a read-only role if you have one. MetaGuard only ever needs SELECT and catalog access.
- Managed databases usually block unknown IPs — you may need to allow public access or allowlist this deployment's egress IP.
- Prefer a staging or sample database for a first run so you can see what the scan does.
No database handy?
Every page falls back to a built-in sample catalog, so you can explore the whole product without connecting anything.