Skip to main content

Documentation Index

Fetch the complete documentation index at: https://heyhumm.ai/docs/llms.txt

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

Humm syncs tables from your PostgreSQL database into your warehouse via Airbyte, then queries the synced copy through your warehouse integration. Use this when you want PostgreSQL data available alongside CRM, billing, support, or product data without relying on live database queries for every question.

​
Source Type

Sync

Humm copies tables from the schemas you choose on a schedule. Humm then queries the synced tables rather than your PostgreSQL database directly.
See Choosing a Source Type for help deciding.

​
What Gets Synced

PostgreSQL data sync supports:
  • Tables from one or more schemas
  • Standard periodic sync using PostgreSQL xmin
  • Read-only analysis against the synced copy after each refresh
PostgreSQL data sync does not support CDC in the current version.

​
Credentials

Database Credentials

To connect PostgreSQL data sync, provide:
  • Host
  • Port such as 5432
  • Database
  • Schemas as a comma-separated, case-sensitive list such as public, sales
  • Username
  • Password
  • SSL Mode
  • Replication Method set to Standard (xmin)

​
SSH Tunnel Options

If your database is only reachable through a bastion host, choose an SSH tunnel method during setup.

​
SSH Key Authentication

Provide:
  • SSH Tunnel Jump Server Host
  • SSH Connection Port
  • SSH Login Username
  • SSH Private Key
Paste the full private key, including line breaks.

​
Password Authentication

Provide:
  • SSH Tunnel Jump Server Host
  • SSH Connection Port
  • SSH Login Username
  • SSH Password

​
No Tunnel

Choose No Tunnel if Humm can reach the PostgreSQL host directly.

​
Sync Behavior

  • Data is refreshed on a schedule after setup
  • Humm syncs tables from the schemas you configure
  • Humm reads the synced warehouse tables after the sync completes
  • xmin is the only supported replication method in the current version

​
Best For

  • Reporting on operational PostgreSQL data alongside CRM, billing, and support systems
  • Keeping analytics workloads off your live application database
  • Working with databases that require SSL or bastion-based SSH access