DatriseAI-first ETL

Instatus to Supabase Integration

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

How Datrise loads Instatus into Supabase

Datrise syncs Instatus's incidents, components, incident updates, subscribers, status page views, and uptime history 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

Instatus: Fast status pages with incident timelines and subscribers.

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

How Instatus entities map to Supabase

Instatus entitySupabase objectNotes
incidentsinstatus_incidentsid PK · custom fields → jsonb columns
componentsinstatus_componentsid PK · linked to instatus_incidents
incident updatesinstatus_incident_updatesid PK · linked to instatus_incidents
subscribersinstatus_subscribersid PK · linked to instatus_incidents

FAQ

How does Datrise handle Instatus'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 Instatus 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 Instatus 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.