Heroku to ClickHouse Integration

How Datrise loads Heroku into ClickHouse

Datrise syncs Heroku's apps, dynos, releases, add-ons, config vars, and build logs into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

Heroku: Application platform with dynos and add-ons.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Heroku entities map to ClickHouse

Heroku entity	ClickHouse object	Notes
apps	`heroku_apps`	id PK · custom fields → JSON or Map columns
dynos	`heroku_dynos`	id PK · linked to heroku_apps
releases	`heroku_releases`	id PK · linked to heroku_apps
add-ons	`heroku_add_ons`	id PK · linked to heroku_apps

FAQ

How does Datrise handle Heroku's custom fields in ClickHouse?

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

How does the Heroku to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect Heroku to ClickHouse 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.