OpenAI Berlin DevDay: Dots Rollout and Platform Strategy

What happened

OpenAI used its DevDay Exchange event in Berlin to say that its AI assistant, Dots, should roll out more widely in Europe "in a few weeks." According to The Decoder's coverage, most of the sessions repeated announcements OpenAI had already made, but a few new details emerged.

The other notable figure was usage growth. Weekly users of Codex, OpenAI's coding tool, in Germany have grown twentyfold since January. Speakers repeatedly pointed to ChatGPT's 1.2 billion weekly users, which The Decoder reads as the backdrop to the event's main message.

That underlying message was that OpenAI wants developers to build their businesses directly on its infrastructure. The Berlin event was therefore less about new products than about positioning OpenAI as a platform on which other companies build their own services.

Why it matters

The shift from selling a tool to offering a platform changes how organisations are likely to adopt AI. When the provider's infrastructure becomes the base layer, decisions about data, integration and model choice move from individual teams to the operating model as a whole. Leaders planning digital transformation will need to judge not only which AI features they want, but which dependencies they are willing to accept.

For service organisations, a platform strategy also means that AI assistants and developer tools can be embedded into existing workflows rather than bolted on. The European rollout timeline for Dots, and the rapid uptake of Codex in Germany, suggest that adoption is moving from pilots to routine use faster than many planning cycles assume.

By the numbers

• 1.2 billion weekly users of ChatGPT, as cited by OpenAI at the Berlin event.
• Twentyfold growth in weekly Codex users in Germany since January.
• "A few weeks" is the timeframe OpenAI gave for Dots' wider European rollout.

The Renascence take

Most coverage of events like this focuses on the headline product, but the more useful signal is what the company keeps repeating. When a provider rehearses the same usage figures and the same platform message across sessions, it is telling the market where its commercial priorities sit.

The real story in Berlin is not Dots; it is the dependency being designed around it. Customers rarely notice when a platform becomes their infrastructure, and that is precisely why it deserves attention now. The behavioural principle at work is default effect: once a tool sits inside a team's build process, switching becomes costly long before anyone has formally chosen a supplier. Customer-obsessed operators should therefore map where AI decisions are being made by default in their own organisations, and set explicit rules for data, fallbacks and vendor exit before the platform choice is made for them.