🚀 Pipeline Editor is live

A safer, faster way to build and ship transforms just landed.

We’re releasing the new Pipeline Editor – a fully sandboxed environment where you can create, edit, test and version-control transforms without touching anything in production.

Let’s dive in 👇

🧪 Build in a sandbox, ship when ready

Every change you make lives in an isolated workspace until you commit to live. Preview outputs, test logic, rebase with the latest version, and iterate without worrying about breaking downstream pipelines.

What’s new:

• Rebase – sync your sandbox with the latest live version
• Sandbox Changes Summary – reset, stash, or publish changes
• Load Version – retrieve or delete previously stashed versions
• Safe commit flow – only admins + users with edit permissions can publish
• Full version control – track changes, stash drafts, manage iterations

This workflow is built for safe experimentation and predictable releases.

🛠️ How it works

Create a new transformOpen the Pipeline Editor → create a transform → edit SQL → save. Everything is stored in your sandbox until you commit.

Experiment safelyPreview SQL outputs before publishing. Rebase to pull the latest live updates. Use versioning to stash or reset your work.

Publish with confidenceOnce tested and validated, commit your changes to live. Pipelines update instantly, with full version transparency.

🔐 Permissions

Admins and users with edit rights can commit. View-only roles see everything but cannot publish changes. Permissions are managed in Settings → Roles.

📌 Known limitations (for now)

We keep it transparent – here’s what we’re improving next:

• Transforms can still be edited from the Transforms page → rebasing required
• Queries referencing warehouse tables outside Kleene’s ecosystem need refactoring
• Creating a transform from a siloed table may show SQL Preview errors in edge cases
• Bug: stashing/resetting a brand-new transform before first commit may behave inconsistently
• Pipeline Viewer currently shows executions for live transforms only
• First-time sandbox load may take a moment

🧭 Example workflows

1. Safely test changes

1. Open Pipeline Editor
2. Modify a transform
3. Save → preview SQL
4. Rebase if needed
5. Stash or commit

Result: Live pipelines stay untouched until you ship.

2. Publish a validated update

1. Edit SQL
2. Save to sandbox
3. Preview output
4. Review in Version Summary
5. Commit to live

Result: A clean, verified update goes live with full version control.

🎯 Why this matters

Teams ship faster when they can experiment without fear. The new Pipeline Editor gives you a safer development loop and tighter control over how changes move from idea → draft → production.

More updates coming soon. If you want a walkthrough, your CSM can set it up anytime.