TRANSFORMATION LAYER

Describe it. The agent builds it.

Stop hand-writing SQL and Python. Tell Sprinkle's AI agent what you need — it drafts the transform, infers dependencies, generates tests and ships a tested, scheduled pipeline your team can review.

// how the agent works

From a sentence to
a shipped pipeline.

The agent reads your warehouse schema, drafts the transform in SQL or Python, wires it into the DAG and adds tests — you stay in the loop, reviewing diffs before anything runs in production.

01 · prompt

Describe what you want, in plain English.

"Monthly revenue by region from paid orders" is enough. The agent knows your schema, joins and grain — no boilerplate, no scaffolding.

02 · generate

SQL or Python, picked for the job.

The agent writes warehouse-native SQL for analytics work, and switches to Python when you need pandas, ML or anything SQL can't express.

03 · review

You approve, the agent ships.

Every generated transform lands as a PR with diff, inferred lineage and auto-generated tests. Hit approve and it's scheduled. Reject and iterate by prompting again.

// orchestration

The agent wires the DAG for you.

As the agent generates each transform, it reads upstream references and slots the new node into your dependency graph automatically — no manual wiring, no YAML, no broken refs.

  • Dependencies inferred from generated SQL and Python
  • Incremental materializations chosen by the agent
  • Backfills planned and executed from a single prompt
  • Visual lineage from raw source → final metric
// data quality

The agent writes the tests, too.

Every generated transform ships with assertions the agent inferred from the schema and the prompt — uniqueness, nullability, referential integrity. You review them in the PR; the pipeline pauses if they fail.

  • Row- and column-level assertions, generated automatically
  • Anomaly checks proposed on key metrics
  • PR-style review on every agent change
  • Slack & PagerDuty alerts when a check fails in production
10x
// faster than hand-writing pipelines
0
// boilerplate or YAML to write
100%
// warehouse-native output
SQL + Py
// the agent generates both