Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mantrixflow.com/llms.txt

Use this file to discover all available pages before exploring further.

PostgreSQL is the primary database source in MantrixFlow. Use it to read from production, staging, or analytics databases and replicate data to any PostgreSQL-compatible destination.

​
Connection fields

FieldDefaultDescription
Connection Name—Friendly label shown in the builder
Host—Database hostname or IP address
Port5432PostgreSQL port
Database—Database name
Username—Database user
Password—Database password
SchemapublicSchema to discover tables from
SSL Moderequiredisable, require, verify-ca, verify-full

​
Network access

MantrixFlow connects to the source database from the ELT server. The database must accept inbound connections from MantrixFlow’s static IP on port 5432. Supported network configurations:
  • Public endpoint with provider firewall or IP allowlist
  • Public endpoint with no provider allowlist (credentials must be strong)
Not yet supported (planned for a later release):
  • Private subnet / VPC-only databases without a public IP
  • VPN-only access
  • Bastion host or jump server connections
See Private database access for MantrixFlow’s static outbound IP and provider firewall steps.

​
Provider setup

ProviderWhat to configure
NeonUse the direct connection string from the Neon Connect modal. If IP Allow is enabled, add MantrixFlow’s /32. See Neon IP Allow.
AWS RDS / Aurora PostgreSQLAdd an inbound security group rule for port 5432 from MantrixFlow’s /32. See AWS RDS security groups.
SupabaseUse the host from the Supabase dashboard. Add MantrixFlow’s /32 under Network Restrictions if enabled. See Supabase Network Restrictions.
GCP Cloud SQL for PostgreSQLEnable public IP and add MantrixFlow’s /32 under Authorized networks. See Google authorized networks.
Azure Database for PostgreSQLUse public access and create a firewall rule with start and end IP both equal to MantrixFlow’s IP. See Azure firewall rules.
Aiven for PostgreSQLAdd MantrixFlow’s /32 to the service IP filter. See Aiven access restrictions.
DigitalOcean Managed PostgreSQLAdd MantrixFlow’s IP as a trusted source on the database cluster. See DigitalOcean trusted sources.
Render PostgresUse the external connection details and restrict access to MantrixFlow’s IP if you have access restrictions enabled. See Render Postgres networking.
Self-hostedThe server must have a public IP or be port-forwarded so MantrixFlow can reach it on port 5432.

​
Permissions

Create a dedicated read-only user instead of using the database owner or an admin account. 
CREATE USER mxf_source WITH PASSWORD 'strong_password';
GRANT CONNECT ON DATABASE your_db TO mxf_source;
GRANT USAGE ON SCHEMA public TO mxf_source;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO mxf_source;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO mxf_source;
For incremental sync, add an index on the cursor column: 
CREATE INDEX ON orders (updated_at);

​
Step by step

1

Create the source user

Run the CREATE USER and GRANT statements above in your PostgreSQL provider.
2

Add MantrixFlow's IP to your firewall

Copy MantrixFlow’s static outbound IP from the connection form and add it as a /32 rule in your provider’s firewall or allowlist.
3

Add the source connection in MantrixFlow

Open Connections → + New Connection. Set the role to Source and choose PostgreSQL. Fill in all fields and click Test Connection. Save after the test passes.
4

Create a pipeline

Go to Data Pipelines → + New Pipeline, select this source connection, and follow the Postgres-to-Postgres guide.

​
SSL modes

ModeWhen to use
disableLocal dev only. Never use in production.
requireUse with most managed providers. Encrypts the connection.
verify-caVerifies the server certificate against a trusted CA.
verify-fullVerifies the server certificate and hostname. Strictest mode.

​
Supported data types

All official PostgreSQL types are supported. Complex types (geometric, range, text search, composite, enum) are landed as TEXT for cross-provider compatibility. See Data type compatibility for the full mapping table and cross-type widening rules.

​
Troubleshooting

SymptomCauseFix
Connection timeoutProvider firewall blocking MantrixFlowAdd MantrixFlow’s /32 to the provider allowlist
Authentication failedWrong credentials or database nameRe-check host, database, username, and password
No tables discoveredUser missing USAGE on schemaRun GRANT USAGE ON SCHEMA
Table missing from discoveryUser missing SELECT on that tableRun GRANT SELECT ON TABLE
TLS / SSL errorProvider requires stricter SSL modeChange SSL mode to require, verify-ca, or verify-full