DrupalCon Europe comes to Rotterdam from September 28 to October 1, 2026, at the Postillion Hotel & Convention Centre WTC. As in every edition, the value isn't only in the sessions you manage to attend. It's in what the full program reveals when you read it as a map: which topics moved up a category, which ones split into their own tracks, and which ones went from novelty to daily work.
This year the map is fairly clear. A developer who reviews the agenda before traveling can anticipate three underlying moves in Drupal, and prepare for each one without waiting for the event to end. Here they are.
01 · AI Stopped Being One Talk and Became Two Separate Conversations
The strongest signal in the program is how artificial intelligence was organized. Instead of a generic AI track, Rotterdam opens two separate summits on Monday the 28th: the AI Dev Summit and the Enterprise Drupal AI Summit. That split says more than any keynote.
The AI Dev Summit speaks to the builder. Its focus is Drupal as an MCP server, agentic architecture, AI-assisted development, and working with AI frameworks and services on top of Drupal AI and Drupal CMS. It's concrete implementation: what you can build today, and with which pieces.
The Enterprise Drupal AI Summit speaks to the decision-maker. Its agenda centers on governance, strategy, business value, and the security and compliance considerations that show up when AI reaches production. It brings a keynote from Peter Hinssen, an interview with Dries Buytaert, and eight enterprise cases with projects already in production.
For a developer, that separation is useful for a practical reason. The technical question ("how do I expose my Drupal entities as tools for an agent through MCP") and the organizational question ("who approves what the agent can touch, and how do I audit it") move at different speeds and address different audiences. Seeing them on separate tracks helps you keep the demo apart from the governance decision. If you're going to Rotterdam to build, the AI Dev Summit is your day. If you also have to defend those decisions to the business, the enterprise summit's material is the argument you'll need afterward.
Underneath it all is Drupal's positioning as the open platform for the content layer in the AI era. In the main Development, AI & Agentic Architecture track, that positioning lands on verifiable mechanisms: the Model Context Protocol, orchestration with ECA, and building agents on top of the CMS itself. We work along that line in enterprise portals with a developer dedicated to the Drupal AI Initiative, and the pattern we see matches what the program signals. The mature AI conversation in Drupal no longer asks whether the CMS can talk to a model. It asks how that conversation is governed when the content is sensitive.
02 · Drupal Canvas and Drupal CMS Move from Novelty to Operational Tool
In the Rotterdam program, Drupal Canvas and Drupal CMS are now discussed as daily operational tools. They appear next to migration and real implementation sessions, among the maintenance topics. A year ago they were the announcement; today they're part of the present you have to operate.
Drupal Canvas is the visual page builder for Drupal CMS 2.x, the evolution of what used to be called Experience Builder. Its promise is concrete: the business team assembles and publishes pages without depending on the developer for every layout change. When that promise holds, the developer gets time back for the work that genuinely needs engineering judgment, such as integrations, performance, and data architecture.
The fact that Canvas and Drupal CMS appear alongside migration talks matters for anyone already operating a portal on earlier versions. The question shifts from "what does the new tool bring" to "how do I get what I have up to there without breaking what works." That's an architecture conversation, with an inventory of contributed modules, a technical-debt review, and a phased migration plan. If you administer an enterprise portal on Drupal, the sessions in this track are the ones that leave you actionable work for the Monday after the event. The decision to migrate to Drupal 11 has its own criteria, which we developed in Drupal 11 and Three Reasons to Migrate Your Enterprise Portal in 2026.
A note on naming, because it's easy to confuse in the ecosystem. Drupal 11 is the product, in its two pieces: Drupal CMS and Drupal Core. Acquia and Dropsolid are ecosystem providers that build on top of that base, not versions of Drupal. All three appear in Rotterdam as Diamond sponsors, a sign that commercial and technical interest are aligned this year. At esinergia we work as an Acquia Elite Partner in LATAM and as Dropsolid's exclusive LATAM allies, and that dual presence lets us see both DXP architecture routes without committing to just one.
03 · Contribution and Digital Sovereignty Are the Same Thread
In Drupal, contributing to the project and sustaining your platform's digital sovereignty are the same decision. Thursday, October 1, is Contribution Day, with mentoring for first-time contributors, and that day carries much of the work that keeps the project alive through the year. The code that supports enterprise portals across half the world comes from there, and the Drupal Association's partner ladder measures exactly that sustained contribution, with six levels where continuous contribution defines your position.
This year there's a data point that connects contribution to something larger. The program elevates digital sovereignty from a keynote topic to a track of its own: Digital Sovereignty & Open Web. It's a direct response to European concern about data control, vendor dependence, and platform portability. And it's an architecture conversation, because sovereignty is decided in where the data lives, who can process it, and how easy it is to leave a provider.
For a team operating portals in regulated sectors, the thread between contribution and sovereignty is direct. An open-source CMS with a community that contributes continuously is, in practice, a portability guarantee: no one can take away the base you built on. That argument carries weight in healthcare, higher education, and the public sector, where the data is sensitive and the platform's permanence is measured in decades, not quarters. Contributing to drupal.org becomes part of the technical case for why the platform is still yours.
Frequently Asked Questions About DrupalCon Rotterdam 2026
When and where is DrupalCon Rotterdam 2026?
DrupalCon Europe 2026 runs from September 28 to October 1, 2026, at the Postillion Hotel & Convention Centre WTC in Rotterdam, the Netherlands. Monday the 28th opens with the summits, Tuesday the 29th starts the main conference with the Driesnote, and Thursday, October 1, is the contribution day.
What is Drupal Canvas?
Drupal Canvas is the visual page builder for Drupal CMS 2.x, the evolution of the tool formerly called Experience Builder. It lets the business team assemble and publish pages without depending on the developer for every layout change, and leaves the engineering work for integrations, performance, and data architecture.
What's the difference between the AI Dev Summit and the Enterprise Drupal AI Summit?
The AI Dev Summit is for the builder: Drupal as an MCP server, agentic architecture, AI-assisted development, and frameworks on top of Drupal AI and Drupal CMS. The Enterprise Drupal AI Summit is for the decision-maker: governance, strategy, business value, and security, with a keynote from Peter Hinssen and eight enterprise cases. Both take place on Monday, September 28.
What is DrupalCon's Contribution Day?
Contribution Day is when the community contributes code, documentation, and translations to the Drupal project, with mentoring for first-time contributors. In Rotterdam it's Thursday, October 1. That sustained contribution is what the Drupal Association's partner ladder measures.
What to Pack, and What to Review When You're Back
If you're heading to Rotterdam to build, three concrete things to put the above into practice.
- Before the event: review how your Drupal entities are exposed today, because the AI Dev Summit will cover exposing them through MCP, and it helps to arrive with your inventory clear.
- During the event: cross what you see of Canvas against your own migration backlog, and land every demo against your real platform.
- When you're back: read the sovereignty track with your list of portals in regulated sectors beside you, to translate the European conversation into your context.
If you haven't confirmed attendance yet, the registration information has dates and fees, and much of a DrupalCon's value runs through the social and networking events, where the conversations that started in the sessions get closed.
DrupalCon Rotterdam 2026 works as a preview of how you'll be working with Drupal in 2027: AI governed by design from the start, the business publishing on its own through Canvas, and sovereignty treated as an architecture criterion from day one of the project. The program already says so, and Rotterdam puts it on stage.
Subscribe to Insights if you want the next analysis on enterprise platform architecture.