Joule Studio Classic vs the new Joule Studio: what changed
Boidra Expert3 min read
SAP's Joule Studio has moved fast - from a low-code skill builder to an intent-based development platform in barely eighteen months. If you are deciding when and how to build on it, the version you target matters. Here is the progression.
Joule Studio Classic - skill building (Q4 2024)
The first release landed in SAP Build in Q4 2024 as a low-code / no-code environment to create, deploy, monitor and manage custom Joule skills. Think of a "skill" as a discrete capability you teach Joule - a bounded action it can perform. Foundational, but skill-centric: you were assembling individual abilities, not autonomous workers.
The Agent Builder era (2025)
Through 2025, Studio grew from skills to agents:
- Skill Builder reached GA in July 2025.
- Agent Builder reached GA in December 2025.
The leap: Agent Builder lets you create context-aware agents that plan, reason and execute multi-step processes across systems, with adaptability and self-learning. You were no longer scripting one skill at a time - you were defining agents that figure out the steps themselves.
Joule Studio 2.0 - intent-based development (2026)
Announced at SAP Sapphire in May 2026 and rolling out from June 2026, Joule Studio 2.0 is a categorical change, built on one architectural decision: intent-based development.
Instead of assembling skills or configuring agents by hand, you describe a business outcome in plain language, and the platform generates a full artifact suite automatically:
- a PRD,
- technical specs,
- code scaffolding,
- an evaluation harness, and
- multi-agent orchestration.
It also ships as a fully managed, zero-infrastructure agent builder - with a period of free design-time access, a large partner fund, and support for developer tooling like Cursor and Claude Code.
Side by side
| Joule Studio Classic (2024) | Agent Builder (2025) | Joule Studio 2.0 (2026) | |
|---|---|---|---|
| Unit of work | Skills | Agents | Outcomes (intent) |
| How you build | Low-code assembly | Configure planning agents | Describe the result in plain language |
| Autonomy | You script each skill | Agents plan & execute steps | Platform generates the whole suite |
| Infra | On SAP Build | On SAP Build | Fully managed, zero-infra |
| Dev tooling | Studio UI | Studio UI | + Cursor / Claude Code |
What it means for you
- If you built on Classic's skills, your investment still runs - but the modern unit is the agent, and increasingly the outcome.
- Starting fresh in 2026? Target the agent / intent-based model, not skill-by-skill assembly.
- The move toward auto-generated multi-agent orchestration rewards teams who already think in terms of bounded, cooperating agents.
Classic asked "what can Joule do?" - one skill at a time. 2.0 asks "what outcome do you want?" - and assembles the agents to deliver it.
Where Boidra fits
We design bounded, well-scoped agents over open protocols (A2A, MCP) - exactly the shape Joule Studio 2.0's orchestration wants to consume. Whether you are modernizing Classic skills or starting intent-first, we help you build agents that slot into the new model instead of fighting it.
Keep reading
New SAP AI Core Calculator 2.0
What does an SAP AI agent really cost? Explore SAP AI Core Cost Calculator 2.0, understand Capacity Units, and compare model consumption. A worked example shows how orchestration and prompt optimization can outweigh foundation-model costs and why budgeting for the complete workflow matters.
Telemetry in AI: why it matters and how it improves testing
You cannot test what you cannot see. AI telemetry - a span for every agent step - turns non-deterministic systems into something you can measure, regression-test and trust.
How SAP Joule works: from copilot to a network of agents
Joule is SAP’s AI copilot - natively embedded in SAP apps and grounded in business data. In 2025–2026 it grew from a single assistant into an orchestrated network of specialized agents.