The free period ends on September 30
Joule for Developers stops being free on September 30, 2026. SAP published the date in a post on SAP Community on September 23, which states that the no-cost promotional period ends that day and that ABAP AI capabilities move to commercial licensing from October 1. If you let your ABAP developers onto the tool during the promotion, you have six days of free usage left and then an unbudgeted line arriving in a month whose forecast is already written.
Two caveats on the sourcing first. We could not read the post body directly, because automated retrieval of the page returned an access error, so everything here rests on the dates SAP published and nothing further. The post carries a community handle rather than a real name, so we are attributing it to SAP rather than to a person, and there are no quotes to pass along.
None of this is unfair on SAP's side. A promotional window that closes on the date it advertised is ordinary, and free evaluation periods are how developers find out whether a tool is any good before a procurement conversation starts. The SAP Community post is dated seven days ahead of the change. Whether SAP flagged the end date earlier somewhere else, we cannot tell from what we can read.
The cutoff dates split by tool
The detail to carry into your planning meeting is that the end date is not the same everywhere. SAP separates the tools. ABAP AI capabilities move to commercial licensing on October 1. SAP Build Process Automation generative AI features and Joule Studio classic edition generative AI keep full access through December 31, 2026. AI chat in SAP Build Code and Business Application Studio continues past December 31.
So your exposure depends on which surface your developers actually open. A team doing ABAP work feels this on October 1. A team building process automation flows has until the end of December, and a developer who mostly uses the chat in Business Application Studio may not feel it in the near term at all. Those are three different conversations with three different budget owners.
Which means the first job is a list of names against tools. Most platform owners can name the pilot team and would struggle to name everyone who has clicked through since. Sorting that list by the four surfaces above tells you who needs an answer this week and who can wait until November.
The first invoice will also be your first measurement
Nobody can calculate what this will cost yet, which makes cost the wrong thing to chase this week. The harder problem is visibility. A team that adopted a tool during a free period has no spending baseline for it, because there was never a number attached to the usage. The first bill therefore arrives as the first measurement anyone has taken, and you will be reading it and reacting to it in the same hour.
Usage is freely observable right now in a way it will not be after the month turns. Today you can ask people what they use and look at whatever telemetry your tenant already gives you, without anyone getting defensive about a figure that has money attached. From October 1, every question about usage is also a question about spend, and people answer those differently.
SAP has been open about this problem in its own house, having pulled AI token spend into its regular finance planning after internal usage grew faster than forecast. The same pattern turns up in every BTP pilot that becomes a running cost. Consumption nobody had to account for is consumption nobody wrote down.
Six days is a short window for terms you cannot read
The narrow criticism is worth making precisely. The pricing mechanism for the commercial phase is not clearly stated in the material available to us. The descriptions we found contradict each other about how the charge is constructed, so we will not repeat any of them, and we would ignore any secondhand version circulating this week until SAP's own terms are in front of you.
A team cannot plan for a cost whose shape it cannot determine. To produce a forecast you need to know what the meter counts and at what rate, and neither is legible from the public material today. Six days is tight for that work even with clear terms in hand, and it is tighter when the first task is chasing an account team for a readable answer.
The reasonable ask of SAP is small. Publish the commercial terms in the same place as the deadline, in language a platform owner can hand to finance without a follow-up call. Teams that have worked through a licensing change with a checklist know that the date is the easy half, and the unit of charge is the half that decides whether anyone can sign.
Get the usage number while it is still free to look at
The useful work between now and September 30 is counting. Find out who has Joule for Developers turned on, which of the four surfaces they use, and roughly how often. You will not get precision, and precision was never the goal here. A rough count taken before the meter starts is worth more than an exact figure taken after it.
Do it the direct way. A message in the developer channel asking who used it this month will get you further in an afternoon than a licensing ticket will in a fortnight. Ask team leads which of their people would notice if access stopped on October 1, and write the names down. That list is your renewal scope, and it is also your evidence if the first invoice looks wrong.
Then decide, before the thirtieth, who keeps access. Developers who tried it twice in July cost nothing to switch off, and the ones using it daily are the case you will be making to whoever signs. Send that message today, and put October 1 and December 31 in the same calendar entry so the second date does not surprise anyone in the middle of year-end.
