DatriseAI-first ETL

Intruder to PlanetScale Integration

AI-first ETL from Intruder into PlanetScale. Governed entities, incremental sync, typed landing tables.

How Datrise loads Intruder into PlanetScale

Datrise syncs Intruder's scans, issues, targets, severities, occurrences, and remediation statuses 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

Intruder: Continuous vulnerability scanning for internet assets.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Intruder entities map to PlanetScale

Intruder entityPlanetScale objectNotes
scansintruder_scansid PK · custom fields → JSON columns
issuesintruder_issuesid PK · linked to intruder_scans
targetsintruder_targetsid PK · linked to intruder_scans
severitiesintruder_severitiesid PK · linked to intruder_scans

FAQ

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