datapipelines.co
Menu

What ships, and what is planned

Roadmap

Three bands, and the words mean what they say. Shipped is in the current release and specified in the packaged docs. Planned describes features being designed or developed. Later describes longer-term direction. Planned features have no announced release date.

Last updated 2026-09-16

Shipped

In the current release

The MCP server

An agent authors, runs, inspects and iterates pipelines through 41 tools over Streamable HTTP, with a scoped key and an audit row per call. The tool list.

Eight engines, one pipeline

Postgres, Oracle, SQL Server, MySQL, H2, DuckDB, SQLite and dp-lake — Parquet and Iceberg on S3, read in place. Each node runs where its data lives.

Joins without a warehouse

Every run gets a scratch database that exists for exactly that run; sources are staged into it and joined there. How federated query works.

Draft → release, by a person

Agents leave drafts. A human releases; a release is immutable; a discarded release can be restored. Every verb is audited with the surface it came through.

Published endpoints

A released pipeline served as a versioned GET under /api/x, parameters bound from the query string, keys scoped to a path prefix. SQL to API.

Agent probes

Catalogue statistics and indexes per table, and a bounded sql_probe that returns rows, wall time and the plan — so an agent fixes a slow shape from evidence.

Public beta

Known limitations

At production standard today: the pipeline lifecycle (draft, human release, immutable versions), API keys and the role-based scope matrix, purge, discard and restore, and promotion between deployments. What follows is scope, not warning — each line is a roadmap row, linked, with where it lands on this page.

  • No in-browser pipeline or template authoring without an agent — the editors preview, execute, release and discard; authoring is MCP-first today. docs/ROADMAP.md §2.2
  • No scheduler, and no scheduler UI — the design is ratified and implementation is planned (below). docs/ROADMAP.md §2.2
  • No JSONata or JavaScript transform nodes yet — designed and planned. docs/ROADMAP.md §2.2
  • No dashboards or report generation yet — the API a report or a dashboard would read ships today; the surfaces do not. docs/ROADMAP.md §2.2
  • No email delivery yet — alerts, report delivery and email output targets all wait on it. docs/ROADMAP.md §2.2
  • No audit-log screen yet — the audit log is written on every call and read by SQL today; the filter screen is on the backlog. docs/ROADMAP.md §2.2
  • The v2 band is design-stage — nested types, conditional execution, per-node retries, SAML, MFA and the rest of docs/ROADMAP.md §3 are decided direction, not shipped product.

Found something that is not on this list? Report what breaks — the bug form asks for the version and the correlation id, so a fix starts from evidence.

Planned

Designed, in progress

Scheduler

  • Schedules live in folders beside the pipelines they run, versioned like everything else.
  • Fired exactly once across every instance of the server — no duplicate runs when you scale out.
  • Every run is a first-class execution: same history, same result, same cancel, same audit.
  • The design is ratified; the implementation round is written.

Dashboards

  • Created by your agent, the way it creates a pipeline today.
  • Embedded in your own product — not a portal you send people to.
  • Fed by released pipelines and APIs, so the numbers are the ones a person released.
  • Filtered per viewer: the same dashboard shows each user their own rows.

JSONata and JavaScript nodes

  • Two new template types, not new entities — they inherit versioning, pins and the release rule.
  • One TRANSFORM node type with row, table and value modes: shape a nested API response, derive parameters, pivot what SQL cannot.
  • Sandboxed and bounded: pure functions over staged data, no network, no filesystem, a wall-clock deadline.

Later · decided, not scheduled

The next layer

Scheduled extracts to your lake

  • A scheduled pipeline materialises to Parquet on your own bucket; DuckDB — and Tableau — read it back at interactive speed.
  • The lake you already own becomes the extract store, with no second copy of the data anywhere else.

Email alerts

  • A scheduled pipeline, a condition, an email. Nothing else is promised until it exists.

Metrics

  • Measures defined once over a pipeline's output and read by dashboards and endpoints alike.

What is deliberately not on this page: a hosted plan, native mobile apps, a story-points feature, and Slack. The first two are decisions for after the planned band ships; the last two are not planned.

If you came here from Tableau

What this means beside Tableau

Today datapipelines gets a governed dataset into Tableau — as an API or into a database it reads. Planned: dashboards you embed in your own product. Later, extracts on your own bucket. The Tableau page keeps the two columns — ships today, roadmap — side by side.

Using datapipelines with Tableau Read the FAQ