DatriseAI-first ETL

Snowflake to Supabase Integration

AI-first ETL from Snowflake into Supabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Snowflake into Supabase

Datrise syncs Snowflake's databases, schemas, tables, views, query history, and warehouses into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Snowflake: Cloud data platform with separated storage and compute.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Snowflake entities map to Supabase

Snowflake entitySupabase objectNotes
databasessnowflake_databasesid PK · custom fields → jsonb columns
schemassnowflake_schemasid PK · linked to snowflake_databases
tablessnowflake_tablesid PK · linked to snowflake_databases
viewssnowflake_viewsid PK · linked to snowflake_databases

FAQ

How does Datrise handle Snowflake's custom fields in Supabase?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Supabase types.

How does the Snowflake to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Snowflake to Supabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.