Connector framework
Relational databases, object stores, files and APIs through one extensible connector registry.
Your data platform, in your infrastructure.
DataStack connects your databases, object stores, files and APIs, runs pipelines on DuckDB or Spark, and lands data as Parquet or Apache Iceberg tables in storage you control. Every run records lineage automatically, so you always know which source produced which table, through which pipeline.
How data moves
The Problem
Most teams choose between months of custom pipeline code or a SaaS tool that sends their data through someone else's cloud and bills by volume. Either way, lineage and governance get bolted on later—if at all.
What Works Today
Relational databases, object stores, files and APIs through one extensible connector registry.
DuckDB for lightweight workloads and Spark (local or standalone) for heavier batch jobs—behind one engine interface.
Parquet files or managed Apache Iceberg tables with partitioning, safe schema evolution, snapshots and time travel.
Source → pipeline → engine → format → storage is recorded on every run, including Iceberg snapshot and schema IDs.
Local disk, MinIO or S3. Metadata and data stay in your infrastructure—data residency by default.
A web UI with a data explorer, plus a full API, so pipelines can be built by hand or driven from your own tooling.
Early-access teams get a guided setup and a direct line to the people building it. Prefer us to run it for you? It's part of our data engineering engagements.