Platform Purple to Neon Integration

How Datrise loads Platform Purple into Neon

Datrise syncs Platform Purple's licenses, products, customers, activations, entitlements, and orders 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

Platform Purple: Software licensing, entitlements, and activations.

Neon: Serverless Postgres destination with branching and autoscaling.

How Platform Purple entities map to Neon

Platform Purple entity	Neon object	Notes
licenses	`platform_purple_licenses`	id PK · custom fields → jsonb columns
products	`platform_purple_products`	id PK · linked to platform_purple_licenses
customers	`platform_purple_customers`	id PK · linked to platform_purple_licenses
activations	`platform_purple_activations`	id PK · linked to platform_purple_licenses

FAQ

How does Datrise handle Platform Purple'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 Platform Purple 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

Early access

Connect Platform Purple 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.