Speakers at the Enterprise AI Summit present production Drupal cases that prioritize source grounding, organisational context, controls and human oversight over simple model integration.
Real production cases—like EPSO’s retrieval-augmented answer engine—integrate AI into existing Drupal platforms with sourcing, multilingual support and auditability.
Speakers argue governance should be implemented inside systems (content models, access controls, workflows) so agents receive the right organisational context.
Deployed systems emphasize human review, cited sources, and legal or procedural constraints rather than relying on model capability alone.
Drupal-driven organisations. Sessions emphasize how putting AI into production is more than connecting a model to a website: it requires handling existing content, permissions, legal requirements, workflows and human decision-making.
Speakers describe governance as embedded controls rather than a separate compliance exercise. Examples include:
Scott Falconer of Acquia frames the problem as contextual. Organisational usefulness depends on giving AI the distinguishing information for a specific organisation—customers, products, workflows and institutional knowledge. Drupal's content structures and governance features are positioned as primary ways to control what contextual data agents receive and under what conditions.
User experience and operational outcomes
Glenn Hilton's session uses an AI-powered admissions experience at the University of Waterloo as an example of reshaping web UX with AI. Paulina Ryters-Menapace and Antonella Picarella present the EPSO candidate support case as a production service under legal and procedural scrutiny. Speakers emphasize measurable operational outcomes—reduced repeat questions and faster human-assisted responses—while noting those figures are project-reported rather than independently audited.
Sovereignty, auditability and enterprise constraints
Presenters discuss sovereignty and auditability as practical conditions that enable adoption in regulated contexts. That includes knowing where data lives, which models are approved, how spending is controlled, and ensuring outputs can be audited against institutional sources. Several sessions show that adding AI can be done without replacing the underlying Drupal systems, using a governed knowledge layer to serve both public users and internal onboarding needs.
The Summit, held aboard the SS Rotterdam, targets senior digital and business decision-makers. The programme places strategy and architecture ahead of hands-on coding, focusing on sovereignty, organisational context, AI-assisted user experiences, moderation and reported operational outcomes. Sessions are built around systems already serving users, not speculative roadmaps.
Takeaway for teams planning Drupal AI
What changes when Drupal becomes something an enterprise AI agent can act on, rather than the place where every user must work? Pantheon plans to show that model running end to end in Rotterdam.
The Enterprise AI Summit takes place in one week, on 28 September aboard the SS Rotterdam, and the countdown is a good moment to properly introduce a session that's been on the agenda for a while: sovereign AI with Julien Blanchez. Digital sovereignty has moved from a policy discussion into a boardroom question. Regula
AI becomes a different infrastructure problem once organisations need to know where data goes, which models are approved, and how spending is controlled. amazee.ai and Tag1 will bring those questions to DrupalCon Rotterdam through a private gateway and Scolta implementation.
For several DrupalCon Rotterdam sessions, the useful question is not simply whether Drupal teams can automate more. It is where automation should stop, where review should begin, and what people still have to judge for themselves.
Some Drupal problems begin with too much rather than too little: too much legacy HTML, hundreds of career choices and brand sites, or code generated faster than teams can understand it. These Rotterdam sessions examine the structures that need to exist before speed becomes useful.
Useful Drupal work does not reach wider audiences automatically. The September Townhall explores where community participation can help.
Loading more related stories...
Open the app view to save this story, compare related coverage, and continue from the same source.