It’s spring cleaning season and we delivered - with a bunch of quality-of-life upgrades including protected tags, smoother Workflows, and bringing back some fan-favourite features, April’s updates will be sure to spark joy ✨
🆕 Key New Features
Protected Release Tags
Last month, we introduced Deployment Release Reviews to help you provide reviews on Prompts and Workflows after hitting deploy. This month, we’re adding to it with Protected Release Tags — a feature which will enforce Releases marked as “protected” to have at least one approval from a Reviewer and have zero outstanding change requests - beforeit can be assigned to a Prompt / Deployment. Useful for anyone working in critical/sensitive deployments that need more rigorous approvals before going live.
Just mark a tag as protected in the UI or API.
Dynamic Model Selection for Inline Prompts
You asked and we listened - inline prompts now accept expression inputs to represent the Model invoked in the Prompt. Previously, you were only able to statically select a model for a given Prompt Node - but now, you can use expression inputs to dynamically reference a model from an upstream Node or Workflow Input.
Inline Prompt Nodes just got a major power-up.
So if you’re looking to A/B testing models, route between cost tiers, or looking to make changes to adapt to user preference, this is a great feature for you.
Ports on Workflow Nodes
All Workflow Nodes now support Ports! Ports act as a connector to Nodes that use branching logic and conditional execution to determine which Nodes to execute next in the workflow. Before, you had to use a separate Conditional Node to set up branching logic in your workflow. Now, every node has a “Ports” attribute that controls which path to take next, so you can simplify the number of nodes in your workflow to deliver the functionality you want.
This makes it easier to parse how data flows through your Workflow, making it easier to visually see what happens next and what logic was applied.
Grouping a Selection into a New Subworkflow Node
You can now select multiple Nodes and instantly group them into a new Subworkflow - and all existing connections will be maintained. You can even drag Nodes into existing Subworkflows, to keep things modular and tidy.
Useful as you build increasingly more complex systems to keep everything neat and tidy.
Add Node on Edge
Previously, the only way to add a Node was to drag and drop a new Node from the Nodes Panel. Now - you can now click any edge between nodes to insert a new node right into the middle of your flow. A Node selection menu will appear, allowing you to choose the type of Node and the new Node will be connected to the edge.
Building and refactoring Workflows is now much faster — especially during prototyping.
Non-Streaming Prompt Nodes
Prompt Nodes now let you choose between streaming and non-streaming execution. Non-streaming mode is ideal when parallelism matters — like with workflows that host Map Nodes.
Streaming and non-streaming options.
Test Suite Run Progress
Track live progress as your evaluation runs — just hover over the indicator to see how many test cases are done and how many are still moving along so you can keep tabs on progress.
See the progress of an evaluation report run while it’s actively running.
Run From Node Re-enabled for SDK-Enabled Workflows
We brought back the fan-favorite Run From Node feature for SDK-enabled Workflows! Pick up execution right from any Node using a previous execution (just like before) and hit the play button which will use the “State” saved from the previous execution to run the Workflow from that point going forward. Use this feature to directly see the difference in any change that you’ve made from a specific Node onwards.
To invoke a Workflow starting from a Node, click the mini play button on the Node when a previous execution is loaded.
Sandbox Cost Tracking for Workflows
You can now see how much your Subworkflows are costing — right inside the Workflow Sandbox. After a run, we’ll show you the total cost of everything triggered by your Subworkflow and Deployment Subworkflow Nodes.
This is an aggregate sum of total costs for your workflow invoked by your Subworkflow Nodes.
It’s spring cleaning season and we delivered - with a bunch of quality-of-life upgrades including protected tags, smoother Workflows, and bringing back some fan-favourite features, April’s updates will be sure to spark joy ✨
🆕 Key New Features
Protected Release Tags
Last month, we introduced Deployment Release Reviews to help you provide reviews on Prompts and Workflows after hitting deploy. This month, we’re adding to it with Protected Release Tags — a feature which will enforce Releases marked as “protected” to have at least one approval from a Reviewer and have zero outstanding change requests - beforeit can be assigned to a Prompt / Deployment. Useful for anyone working in critical/sensitive deployments that need more rigorous approvals before going live.
Just mark a tag as protected in the UI or API.
Dynamic Model Selection for Inline Prompts
You asked and we listened - inline prompts now accept expression inputs to represent the Model invoked in the Prompt. Previously, you were only able to statically select a model for a given Prompt Node - but now, you can use expression inputs to dynamically reference a model from an upstream Node or Workflow Input.
Inline Prompt Nodes just got a major power-up.
So if you’re looking to A/B testing models, route between cost tiers, or looking to make changes to adapt to user preference, this is a great feature for you.
Ports on Workflow Nodes
All Workflow Nodes now support Ports! Ports act as a connector to Nodes that use branching logic and conditional execution to determine which Nodes to execute next in the workflow. Before, you had to use a separate Conditional Node to set up branching logic in your workflow. Now, every node has a “Ports” attribute that controls which path to take next, so you can simplify the number of nodes in your workflow to deliver the functionality you want.
This makes it easier to parse how data flows through your Workflow, making it easier to visually see what happens next and what logic was applied.
Grouping a Selection into a New Subworkflow Node
You can now select multiple Nodes and instantly group them into a new Subworkflow - and all existing connections will be maintained. You can even drag Nodes into existing Subworkflows, to keep things modular and tidy.
Useful as you build increasingly more complex systems to keep everything neat and tidy.
Add Node on Edge
Previously, the only way to add a Node was to drag and drop a new Node from the Nodes Panel. Now - you can now click any edge between nodes to insert a new node right into the middle of your flow. A Node selection menu will appear, allowing you to choose the type of Node and the new Node will be connected to the edge.
Building and refactoring Workflows is now much faster — especially during prototyping.
Non-Streaming Prompt Nodes
Prompt Nodes now let you choose between streaming and non-streaming execution. Non-streaming mode is ideal when parallelism matters — like with workflows that host Map Nodes.
Streaming and non-streaming options.
Test Suite Run Progress
Track live progress as your evaluation runs — just hover over the indicator to see how many test cases are done and how many are still moving along so you can keep tabs on progress.
See the progress of an evaluation report run while it’s actively running.
Run From Node Re-enabled for SDK-Enabled Workflows
We brought back the fan-favorite Run From Node feature for SDK-enabled Workflows! Pick up execution right from any Node using a previous execution (just like before) and hit the play button which will use the “State” saved from the previous execution to run the Workflow from that point going forward. Use this feature to directly see the difference in any change that you’ve made from a specific Node onwards.
To invoke a Workflow starting from a Node, click the mini play button on the Node when a previous execution is loaded.
Sandbox Cost Tracking for Workflows
You can now see how much your Subworkflows are costing — right inside the Workflow Sandbox. After a run, we’ll show you the total cost of everything triggered by your Subworkflow and Deployment Subworkflow Nodes.
This is an aggregate sum of total costs for your workflow invoked by your Subworkflow Nodes.
Sharon brings a background in product marketing and a proven ability to help SaaS companies achieve remarkable growth. With a well-established history of crafting strategies that resonate with audiences, she’s passionate about bridging the gap between cutting-edge AI solutions and the people who need them most. As part of Vellum's GTM team, Sharon focuses on connecting businesses and people with the right solutions that deliver impact, making advanced technology accessible and effective.
Flagship Model Report: Gpt-5.1 vs Gemini 3 Pro vs Claude Opus 4.5
LLM basics
November 27, 2025
•
14 min
Gumloop Alternatives (Reviewed & Explained)
The Best AI Tips — Direct To Your Inbox
Latest AI news, tips, and techniques
Specific tips for Your AI use cases
No spam
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Each issue is packed with valuable resources, tools, and insights that help us stay ahead in AI development. We've discovered strategies and frameworks that boosted our efficiency by 30%, making it a must-read for anyone in the field.
Marina Trajkovska
Head of Engineering
This is just a great newsletter. The content is so helpful, even when I’m busy I read them.
Jeremy Hicks
Solutions Architect
Experiment, Evaluate, Deploy, Repeat.
AI development doesn’t end once you've defined your system. Learn how Vellum helps you manage the entire AI development lifecycle.
Case study CTA component (cutting eng overhead) = {{coursemojo-cta}}
6+ months on engineering time saved
Learn how CourseMojo uses Vellum to enable their domain experts to collaborate on AI initiatives, reaching 10x of business growth without expanding the engineering team.
.png)
.svg)
.svg)
