Are We in Drupal's Renaissance?  🔗 **Source:** [Are We in Drupal's Renaissance?](https://youtube.com/watch?v=7ISddVI0SgE&is=xKBKfaCxv3CPMgyY) > [!note]+ Document Notes > --- > tags: [drupal, acquia, agentic-ai, content-governance, open-source-business-models, devrel] > author: Hayden (Headless) > source: Headless (YouTube) > reference: https://www.youtube.com/watch?v=7ISddVI0SgE > date created: 2026-09-28 08:17 > --- > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > > [!warning] Auto-caption artifacts and script ambiguities. The Drupal mascot's name (Druplicon) > > is captioned as "the Drupal con." The video names "Mautic" as the target of two different > > acquisitions serving two different purposes (marketing automation in 2019; "digital assets and > > product information" two years later) — this reads like a script or captioning error repeating > > one company name for what was likely a second, different deal; the source material does not > > resolve which. "Thomas Skola" and "Agile One" (the 2019 customer-data-platform deal) are > > unverified spellings. Verify company names, acquisition targets, and dates against Acquia's own > > record before citing any of this. > # 🏷️ Title: Are we in Drupal's Renaissance? > ## 🧭 Table of contents > - [📝 Summary](#-summary) > - [📖 Main content](#-main-content) > - [🗒️ Notes](#-notes) > - [📚 References](#-references) > - [🗣️ Paraphrase](#-paraphrase) > - [📰 Newsletter](#-newsletter) > - [✅ Action items](#-action-items) > - [🧪 Hypotheses](#-hypotheses) > - [📊 Methodology](#-methodology) > - [❓ Questions](#-questions) > - [🔮 Future research](#-future-research) > - [💡 Implications](#-implications) > - [🧠 Learning styles assessment](#-learning-styles-assessment) > - [📊 Accessibility assessment](#-accessibility-assessment) > - [🌍 DEIB assessment](#-deib-assessment) > - [✅ Logical validity](#-logical-validity) > - [🛡️ DARVO analysis](#-darvo-analysis) > - [🎯 Conclusion](#-conclusion) > ### 🔗 Quick reference > - Source: https://www.youtube.com/watch?v=7ISddVI0SgE (Headless, published 2026-09-27, last caption at 13:50) > - Dries Buytaert — Drupal's founder and Acquia's co-founder and CTO; his own blog posts and public announcements are the primary source for nearly every date and claim in this video > - Acquia — the commercial company built around Drupal, co-founded with Jay Batson in June 2007 > - Drupal Association — the nonprofit steward of drupal.org and Drupal's community infrastructure, named as the recipient of Acquia's Fair Trade contribution > ## 📝 Summary > - **What this is.** A 14-minute narrated video essay (Headless, published 2026-09-27, last caption at 00:13:50) tracing Drupal's 25-year history through the lens of one question: why Acquia's September 14, 2026 rebrand puts Drupal, not its own product names, back under the company logo. > - **The claim.** The narrator argues the rebrand is not new positioning bolted onto old software. It is Acquia catching its brand up to product work already shipped: Drupal CMS 1.0 (Jan 2025), Drupal Canvas 1.0 (Dec 2025), Acquia Source (Nov 2025), Source Workspace and Acquia AI (April 2026), all released before the rebrand made any of them visible under the Drupal name. > - **Why it matters.** The video names a real, specific failure mode: a platform can modernize for years while the people who last touched it years ago still ask "is that still around?" That gap between shipped capability and public perception is a DevRel-shaped problem, not just a marketing one. > - **Key stakeholders.** Dries Buytaert (founder, quoted only through his blog posts and public announcements, never on camera), Acquia (the commercial vendor), the Drupal Association (nonprofit steward, funding recipient), enterprise customers weighing managed versus self-managed tiers, and the volunteer contributors whose work (Views, Drupal CMS, Canvas) is credited as happening in parallel with Acquia's commercial moves. > - **Risks and tradeoffs.** The narrative leans entirely on Acquia's and Dries' own framing of its history, including its own regretted decision (killing Drupal Gardens). No competitor, analyst, or independent customer voice appears. The evidence for Drupal's continued enterprise relevance is entirely from 2009 (The Economist, the Grammy Awards, whitehouse.gov); no 2020s-era brand example is offered to counter the "still around?" skepticism the video itself raises. > - **Bottom line.** A vendor's rebrand read charitably as a genuine correction of a perception lag, built on real shipped features and a real funding commitment to the open-source foundation, but told entirely from that vendor's own historical record with no outside check. > ## 📖 Main content > - **The origin story is deliberately small-scale.** Dries Buytaert built a website in 2000 for himself and friends sharing an internet connection in Antwerp, released the underlying software in January 2001, and it became Drupal. A typo turned "Dorp" (Dutch for village) into drop.org. > - **The community formed around a saying that the video treats as load-bearing.** "Come for the code, stay for the community" appears twice, once early and again in the closing line, framing the whole 25-year arc as a community story with a commercial company grafted onto it later, not the reverse. > - **MTV is the origin of Acquia's business case (00:02:18).** Dries, still finishing his PhD, helped MTV with a Drupal support problem for free. That gap between "you can download this software" and "you need help running it for something that matters" is what became Acquia, incorporated with Jay Batson in June 2007. > - **The founding separation of concerns is stated explicitly and is the video's strongest artifact.** Dries' original 2007 announcement said Acquia would not close-source Drupal; the business would live in services around the open-source project, not inside it. > - **Acquia's first expansion (Jan 2009) already shows the managed-versus-custom tension that defines the whole video.** Acquia moved from supporting only its own curated Drupal package to supporting all of Drupal 6, including customers' own custom code, because customers' real websites were messier than any curated package. > - **Drupal Gardens is the video's one unambiguous regret, sourced to Dries himself.** A no-code, browser-only way to build a Drupal site, it reached over 100,000 sites before Acquia shut it down to focus resources on enterprise features (Cloud Site Factory). Dries later published a post titled, in his own words, about the product Acquia should not have killed. > - **The 2019-2021 acquisition run is where the video's own account gets confused (00:05:53).** It names Mautic for marketing automation in 2019, a majority investment from Vista, a deal for a customer data platform ("Agile One"), and then, two years later, another acquisition of "Mautic" for digital assets and product information. Two different deals attributed to one company name is very likely a script error, not two real Mautic acquisitions. > - **Community-built features earning a path into core is the throughline the video uses to argue Drupal never stopped moving.** Views started as a contributed module and merged into what became Drupal 8 in 2012. Drupal CMS 1.0 (Jan 2025) packaged core with search, media, and SEO so builders don't have to assemble it themselves. Drupal Canvas 1.0 (Dec 2025) added a visual, in-browser page builder. > - **The reputation-lag anecdote is the pivot of the whole essay (00:07:22).** At a Drupal AI event in New York, someone reportedly asked "Drupal? Is that still around?" The narrator's argument: the software modernized faster than its reputation, and this rebrand is Acquia trying to close that specific gap rather than open a new one. > - **Acquia Source reintroduces the market Gardens once served, this time deliberately split into two tiers.** Source CMS is the fully managed path (Acquia runs the Drupal back end; the team builds within it, cannot modify core, cannot install drupal.org contributed modules, can extend via custom components and APIs). Cloud Platform is the self-managed path for teams that need full control, including custom modules. The video's own example is a university that plausibly needs both: a heavily customized How does a company that spent the last 5 years making Drupal less visible in its brand suddenly bet its whole AI future on it? Acquia's newest rebrand puts it right there under the logo. Powered by Drupal. But to understand that decision you have to go back to a product Acquia shut down. A product its co-founder now says they never should have killed. Because the story behind this rebrand started long before anybody was selling AI agents. Y2K Napster AOL Instant Messenger Your music collection was becoming a folder full of MP3s. Your friends were screen names and getting online sounded like this. The year was 2000 and Dries Buytaert was a student in Antwerp. He and his friends shared an internet connection. They also needed somewhere to leave messages, updates about their network, interesting news, and where they're going for dinner. So he built a small website. After graduating, he put it online. He meant to register Dorp, the Dutch word for village. A typo helped turn it into drop.org. In January 2001, he released the software behind it. The project became Drupal. And that little blue face you might remember has a name. The Drupal con. It became a community mascot with local groups making their own versions. By 2005, people were meeting in Antwerp for the first ever Drupal con. Dries still has photos from those early gatherings. The people building this thing together were getting to know each other. Over the years, that became thousands of contributors writing code, fixing bugs, maintaining modules. Alongside them, people were translating the software, writing documentation, teaching newcomers, and organizing meetups and Drupal camps. You know, Drupal has a saying, "Come for the code, stay for the community." People found collaborators, careers, and friends through this thing that started as a way for a few students to leave each other messages. And early in that story, just 6 years after the software was released, MTV had a Drupal problem. The support department was a guy trying to finish his doctorate. Dries was still working on his PhD at the time, and Drupal was still something he worked on alongside it. When MTV contacted him, reached out, he helped them free, and there birthed the biggest opportunity. Organizations could download the software, but using it for an important website meant they also needed help, infrastructure, and someone they could turn to when things went wrong. Later, Dries met entrepreneur Jay Batson, and in June 2007, they incorporated Acquia. Drupal remained the open source project, and Acquia was the business built around helping organizations use it. The company wasn't supposed to replace the community. In his original announcement, Dries explicitly said Acquia would not close source Drupal. The business would be in the services around the software. For Acquia, the next challenge was deciding which parts of using Drupal it could make easier. Acquia initially offered support for its own selected package of Drupal software. Customers wanted something broader. Their websites used other modules, their own themes, their own code. They wanted help with the thing they actually had. In January 2009, Acquia expanded support to all of Drupal 6, including custom code. The neat package had to make room for the messy real website. And before Drupal was even 10 years old, it was powering websites for some of the most recognizable institutions in the world. The Economist, the Grammy Awards, even whitehouse.gov moved to Drupal in 2009. Remember where this started? A few students sharing an internet connection and figuring out where to get dinner. Now, the American presidency was publishing on software that grew out of that project in less than a decade. But Acquia was also pursuing almost the opposite idea. What if customers didn't have to manage all that software themselves? What if they could just open a browser and build a site? That product was Drupal Gardens. It let people build Drupal websites without touching code or looking after the infrastructure. At one point, more than 100,000 sites had used Drupal Gardens. And Acquia shut it down. Years later, Dries published a post called the product we should not have killed. That's a hell of a title to publish about your own company. And I respect it. But his explanation is what makes this story interesting. Enterprise customers needed more, custom integrations, stronger governance, tools for managing whole fleets of websites. Acquia developed that side of the business into Cloud Site Factory. Keeping both paths going stretched the resources of a young company, so it chose enterprise. Dries' regret was the customers they stopped serving, people who wanted Drupal without needing a development team. A website was only one piece of what Acquia wanted to provide, though. In 2019, it acquired Mautic for marketing automation, announced a majority investment from Vista, and signed a deal for customer data platform Agile One. Two years later came the agreement to acquire Mautic for digital assets and product information. Pages, campaigns, customer records, images, product details. Acquia was bringing more of a marketing team's work into its portfolio, digital experience platform DXP. And the Agile One announcement already had AI in its headline. That was in 2019. The new part of the story is where wants Drupal to sit inside all of it. But meanwhile, that community kept building. If you've built with Drupal, you know the name Views. It's the tool for turning your content into lists and displays through an interface. It began as a contributed module. In 2012, it was merged into code that would become Drupal 8. Something the community built became part of what Drupal shipped with. Making that shared work easier for more people to use has been a long-running effort. In January 2025, the project released Drupal CMS 1.0. It took Drupal core and packaged it with more of the things a site builder would otherwise have to assemble. Search, media handling, search engine optimization, and other common capabilities. The goal was to make getting started easier for people who needed to build a website without first becoming experts in the system underneath it. Then that December, Drupal Canvas 1.0 arrived, a visual page builder. Arrange components on the page, adjust the layout, work in the browser, give content teams more control over the pages they publish. These were changes to the open-source project available beyond Acquia. So, there are two stories moving in parallel now. Acquia had expanded its commercial product portfolio. The Drupal community had been working to make Drupal easier to use. Neither of these changes guaranteed that somebody who last tried Drupal years ago would ever notice. Drupal? Is that still around? Someone asked that at a Drupal AI event in New York. Thomas Skola recounted overhearing it in New York. Dries shared his post in May 2026. Dries' argument was that the software had been modernizing faster than its reputation. People remembered complexity. They remembered needing a developer. The people working on the project were looking at newer tools and seeing a different product. That gap matters to this rebrand. Putting Drupal back in the foreground means asking people to reconsider a name they may think they've already made up their mind about. And Acquia had already started rebuilding the kind of offering it once walked away from. In November 2025, Dries introduced the thinking behind Acquia Source, a new Drupal-based service revisiting the need Gardens had addressed. Today, Acquia offers two different paths. Source CMS provides the managed version. Acquia operates the Drupal back end. Your team builds and manages the site within that service. Cloud Platform is the path for teams that need control over their Drupal application, including custom modules and deeper development work. A university can need both. Its main website might have years of custom development behind it. A separate alumni campaign site may just need a few pages that are easy to publish and keep running. These are the same university and the same underlying CMS, but they're two very different jobs. But making Drupal easier to manage comes with a trade-off. By April 2026, Acquia was announcing a broader Source Workspace connecting content management, digital assets, web governance, and AI agents. The pieces of the portfolio were being brought into a shared working environment. And with Acquia AI, the company said users could create and manage agents in the browser with permissions and human review for higher risk actions. The pitch was expanding from where a team stores its content to how work gets done across it. And in June, Dries laid out the argument behind that bet. For one person making a small site, an AI builder might be enough. He acknowledged that. But generating a new page is different from managing years of existing content used by different people and systems. His own website was the example. More than 1,500 posts and 10,000 photos. He said he used an AI agent to work on it through Drupal. The agent could help make changes. Drupal still held the content and the controls around it. For an organization, those controls include who can edit something, which version has been approved, and what changed between revisions. His argument was that AI makes producing things easier while increasing the importance of managing what gets produced. And that's what makes this interesting. The capabilities the community spent years developing have another job to do as AI becomes part of the workflow. Then, on September 14, 2026, Acquia changed how it presented that story. Drupal returned to prominence in the brand. The homepage moved from digital experience platform to agentic content platform. Dries said the products had evolved faster than people's awareness of them. That was his explanation for the rebrand. Made the company easier to understand with content at the center and Drupal visibly underneath it. The product work preceded the new identity. So did a concrete commitment to the community behind it. Back in June, the Drupal Association described Acquia's fair trade initiative. 2% of eligible partner deals goes to the association. Funded by Acquia, it comes out of Acquia's margin without reducing the partner's revenue or adding a customer surcharge. That helps fund the organization supporting Drupal's infrastructure and community programs. I like that connection. More businesses built around Drupal can help support the shared project that makes that business possible. And giving more teams a practical way to use Drupal is part of that opportunity. The key is matching the service to the site. This is where those two paths make sense. In Source CMS, you cannot modify the underlying Drupal code or install contributed modules from drupal.org. You can extend it through things like custom components and APIs, but the managed service has boundaries. For that smaller alumni site, those boundaries might be perfectly fine. And if a university's central web team already approves every new module, individual site owners weren't choosing their own software in the first place. Keeping sites on a common setup can make updates and fixes easier to manage. A developer building a more customized application means a different level of access. If a particular module's essential to the project, that belongs in the decision from the start. That's why having both offerings matter. The campaign team can choose a managed service. The development team can take the route that gives them control over the application. Both can keep working with Drupal, and your needs can change after the site launches. Dries has also described a way for customers to leave that managed service, export a complete Drupal site, including its code, configuration, and content, and run it elsewhere. That was his public promise in December 2025. It's a useful thing to try and explore in a demo. What comes with your site when you're ready to run it somewhere else. Being able to take a working application with you would give the growing team more options than a content export alone, and that's an appealing direction. Start with the help you need, and have room for the project to grow. Now, there's one last detail in Acquia's history that makes this rebrand more interesting to me. If we go back to Dries' original startup announcement in 2007, he was already describing Drupal as a place to keep managed content that other tools and websites could access. He was already talking about APIs and detailed access controls. 19 years later, the other tool might be an AI agent. The tools connecting to Drupal have changed. The work the community put into organizing and managing content still has massive value. And that's my answer to the question we started with. Acquia sees a new use for capabilities Drupal has spent years developing. At the same time, it's returning to customers who want those capabilities without managing the whole application themselves. That's why I like this direction for Acquia. It gives Drupal a more visible place in the story and gives different teams more ways to work with it. And behind that name are the people who've kept building, teaching, and sharing what they know. Come for the code, stay for the community. I'd like to see more people get the chance to find out why that line has lasted 25 years. I'm Hayden. This is Headless., Are We in Drupal's Renaissance?, Hayden (Headless), 01m3ksq6mys3jr5b2jx1vnth84.