DatriseAI-first ETL

Ashby Apache Superset

AI-first ETL from Ashby into Apache Superset. Governed entities, incremental sync, typed landing tables.

How Datrise loads Ashby into Apache Superset

Datrise syncs Ashby's records, events, and configuration objects into Apache Superset as governed SQL tables Superset queries directly. Flexible or custom fields land in flattened columns for the explore UI, and timestamps such as created, updated, and status changes are typed as temporal columns for time-series charts.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned tables to keep dashboards responsive. Superset charts run live SQL, so Datrise lands query-friendly, indexed tables rather than wide raw payloads.

Ideal for open-source dashboards over your own database.

Endpoints

Ashby: SaaS or API data source for analytics and warehouse sync.

Apache Superset: Open-source BI for SQL exploration, charts, and dashboard publishing.

How Ashby entities map to Apache Superset

Ashby entityApache Superset objectNotes
recordsashby_recordsid PK · custom fields → flattened columns for the explore UI
eventsashby_eventstemporal columns for time-series charts events
configuration objectsashby_configuration_objectsid PK · linked to ashby_records

FAQ

How does Datrise handle Ashby's custom fields in Apache Superset?

Flexible values are stored as flattened columns for the explore UI, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Apache Superset types.

How does the Ashby to Apache Superset sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the queried tables.

Related pipelines

Early access

Connect Ashby to Apache Superset 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.