k6 Cloud to Neon Integration
AI-first ETL from k6 Cloud into Neon. Governed entities, incremental sync, typed landing tables.
How Datrise loads k6 Cloud into Neon
Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times into Neon as a typed table per source entity. 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 by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.
Ideal for serverless Postgres workloads that scale to zero between syncs.
Endpoints
k6 Cloud: Load testing runs and performance thresholds.
Neon: Serverless Postgres destination with branching and autoscaling.
How k6 Cloud entities map to Neon
| k6 Cloud entity | Neon object | Notes |
|---|---|---|
| test runs | k6_cloud_test_runs | id PK · custom fields → jsonb columns |
| thresholds | k6_cloud_thresholds | id PK · linked to k6_cloud_test_runs |
| checks | k6_cloud_checks | id PK · linked to k6_cloud_test_runs |
| metrics | k6_cloud_metrics | id PK · linked to k6_cloud_test_runs |
FAQ
How does Datrise handle k6 Cloud's custom fields in Neon?
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 Neon types.
How does the k6 Cloud to Neon sync stay up to date?
It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.
Related pipelines
More destinations for k6 Cloud
Early access
Connect k6 Cloud to Neon 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.