Skip to main content
Connect your PostgreSQL database so Myrmex can audit its hardening and compliance, check its operational health, explore its schema, and — with approval — run SQL for you. Myrmex reaches the database over the native protocol through a Collector on your network. Operations run live and on demand through the Integration Specialist agent — Myrmex reads only what you ask for and keeps none of your data on the Myrmex side.

​
What Myrmex Can Do

Compliance audit

Run a Security Posture audit and map findings to CIS, ISO 27001, NIST CSF, and BACEN frameworks.

Health checks

Review connections, cache hit ratios, replication lag, and table bloat.

Explore tables

List schemas and tables so you can see what the database holds.

Describe structure

Inspect columns, types, indexes, and constraints for any table.

Sensitive-data scan

Scan tables and columns for personal or sensitive data that needs protection.

Run SQL

Execute read queries any time; write statements (DDL/DML) require your confirmation.

​
Before You Start

  • A Collector on a network that can reach the PostgreSQL host on its TCP port (default 5432). See Collector mode.
  • A dedicated database login for Myrmex (create it in Step 1).
  • TLS is recommended. Set SSL Mode to require to encrypt the connection; servers without TLS use disable (the audit flags the missing encryption).

​
Step 1 — Create the Credential in PostgreSQL

Create a dedicated, least-privilege role for auditing. pg_monitor grants read access to the statistics and configuration views the audit relies on.
Keep the account read-only for auditing. Grant a write-capable role only if you want the agents to run write statements (DDL/DML) through Run SQL.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → PostgreSQL, then fill in:

​
Connect

Click Connect to validate the login and TLS settings. The database then appears under Environment → Integrations alongside your other integrations, and you can start asking the AI about it in the Workspace.

​
Notes

  • Read-only by default. Auditing, health, schema exploration, and sensitive-data scans only need the read-only pg_monitor role. Provide a write-capable user only if you want confirmation-gated Run SQL writes.
  • Nothing is stored. Every operation runs in real time through the Collector; results return to your Workspace and no database data is retained on the Myrmex side.
  • TLS. require encrypts the session; verify-ca / verify-full also validate the server certificate. Prefer a verifying mode where you manage the server’s certificate.