DatriseAI-first ETL

k6 Cloud to Supabase Integration

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

How Datrise loads k6 Cloud into Supabase

Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times 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

k6 Cloud: Load testing runs and performance thresholds.

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

How k6 Cloud entities map to Supabase

k6 Cloud entitySupabase objectNotes
test runsk6_cloud_test_runsid PK · custom fields → jsonb columns
thresholdsk6_cloud_thresholdsid PK · linked to k6_cloud_test_runs
checksk6_cloud_checksid PK · linked to k6_cloud_test_runs
metricsk6_cloud_metricsid PK · linked to k6_cloud_test_runs

FAQ

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