Vantage to PlanetScale Integration

How Datrise loads Vantage into PlanetScale

Datrise syncs Vantage's costs, resources, providers, cost reports, tags, and budget alerts into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Vantage: Cloud cost visibility and spend allocation.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Vantage entities map to PlanetScale

Vantage entity	PlanetScale object	Notes
costs	`vantage_costs`	id PK · custom fields → JSON columns
resources	`vantage_resources`	id PK · linked to vantage_costs
providers	`vantage_providers`	id PK · linked to vantage_costs
cost reports	`vantage_cost_reports`	id PK · linked to vantage_costs

FAQ

How does Datrise handle Vantage's custom fields in PlanetScale?

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

How does the Vantage to PlanetScale sync stay up to date?

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

Related pipelines

Early access

Connect Vantage to PlanetScale 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.