The Battle for the Dotcom How Drupalorg Grappled With the Commercial Shadow of Drupalcom

In the open-source world, where community trust and decentralized stewardship are central to success, domain identity carries enormous weight. For Drupal, one of the most influential content management systems of the past two decades, that identity has always been rooted in Drupal.org—the hub for community development, documentation, support forums, and the software itself. But looming in the background, often misunderstood by new users and occasionally manipulated for commercial leverage, was a parallel domain that Drupal’s core maintainers did not control: Drupal.com. The resulting tension between these two domains—a nonprofit community platform and a .com run by a commercial entity—sparked years of friction, confusion, and branding dilemmas for one of the web’s most trusted open-source ecosystems.

The origin of the conflict dates back to Drupal’s early 2000s rise from a Belgian university dorm room project to a major force in enterprise web development. As Drupal gained momentum among developers and government agencies, the community coalesced around Drupal.org, maintained by the nonprofit Drupal Association. This site was not only the download portal but also the heart of governance for code contributions, project modules, and community policies. From the start, the ethos was non-commercial, transparent, and deeply collaborative.

Meanwhile, Drupal.com was quietly owned and operated by Acquia, the commercial company co-founded in 2007 by Dries Buytaert, Drupal’s original creator. Acquia positioned itself as a cloud hosting and services company for enterprise-grade Drupal deployments. While Buytaert’s leadership in both worlds was foundational to the ecosystem’s growth, the simultaneous existence of Drupal.org and Drupal.com—with the latter pointing to a for-profit company—created inherent ambiguity that proved difficult to resolve.

For newcomers and corporate decision-makers, Drupal.com looked like it might be the official Drupal website. The name suggested authority, and the site itself was sleek, professionally branded, and geared toward enterprise buyers with high-value service contracts. This perception problem was amplified by search engines. For years, Drupal.com often outranked Drupal.org in results for generic Drupal queries, especially in sponsored ad placements. Users looking to learn about Drupal the open-source CMS were funneled toward enterprise marketing pitches, sometimes without realizing the difference.

The Drupal Association, tasked with stewarding the software and supporting the volunteer community, found itself in a difficult position. It could not forcibly reclaim Drupal.com—the domain was legally registered and operated by a company with direct ties to the project’s founder. Yet the optics of a commercial company implicitly speaking for the entire project via a coveted dotcom domain undermined the messaging that Drupal was a community-owned, collaborative effort. Concerns deepened as Acquia’s growth accelerated. By the early 2010s, the company had raised over $100 million in venture capital and positioned itself as the enterprise face of Drupal. The more it succeeded, the more Drupal.com became synonymous with Drupal in the minds of outsiders.

The community response ranged from concern to activism. Prominent developers and contributors raised questions in forums and at DrupalCons about governance, branding, and whether the dotcom presence diluted the open-source ethos. Some feared a future in which Acquia’s marketing would distort or overtake the narrative shaped by contributors worldwide. Others pointed out that while Buytaert had never misrepresented Acquia as the whole of Drupal, the confusion was structural and persistent.

In response, the Drupal Association explored options for regaining control or at least reframing the message. Discussions were held with Acquia about redirecting Drupal.com to Drupal.org, or at minimum providing a prominent disclaimer that Drupal.com was a commercial site and not the official home of the software. Acquia offered partial compromises. At one point, Drupal.com included a subtle footer note linking to Drupal.org, and later iterations featured more direct explanations of Acquia’s role. However, no formal transfer or redirection occurred, and the domain remained an asset under Acquia’s control.

By the mid-2010s, the Drupal Association shifted its strategy from confrontation to differentiation. Rather than trying to fold Drupal.com into the nonprofit domain structure, it doubled down on promoting Drupal.org as the center of community engagement, contribution, and governance. The association modernized the site’s design, improved its onboarding materials, and invested in branding that emphasized openness and inclusivity. The hope was that over time, the clarity of purpose would cut through the confusion.

Yet even into the 2020s, the duality persisted. New users often landed on Drupal.com first, especially when searching for enterprise resources or tutorials. Some companies mistakenly assumed Acquia was the maker of Drupal, not just a vendor in the ecosystem. Others were surprised to learn that the software they had adopted freely and modified internally came from a community-driven platform maintained elsewhere. This gap between perception and reality never fully closed.

The Drupal.org vs. Drupal.com issue illustrates a unique dilemma in the world of open-source branding. Unlike commercial software, which can tightly control its messaging, open-source projects must navigate decentralized governance, overlapping identities, and the ambiguity of ecosystem partners operating with their own agendas. In the case of Drupal, the problem was made trickier by the personal overlap—Buytaert was not only Acquia’s CTO but also the public face of Drupal itself, placing him in the awkward role of representing both the product and one of its most dominant commercial actors.

In hindsight, many in the community wished Drupal.com had been reserved early on by the Association or redirected permanently to the official site. The failure to do so introduced years of confusion and risked undermining the very community principles that had made the platform successful. At the same time, the incident forced the project to more clearly define its boundaries and recommit to the principle that no single company owns Drupal, no matter how prominent.

As of today, Drupal.com still exists as an Acquia-controlled domain, and Drupal.org continues to serve as the authoritative source for the software. The uneasy balance remains. But the episode left a permanent lesson in the history of web governance: in a distributed ecosystem, domain names are more than addresses—they are signposts of power, perception, and ownership. And if claimed too narrowly or too late, they can reshape the narrative of an entire project.

In the open-source world, where community trust and decentralized stewardship are central to success, domain identity carries enormous weight. For Drupal, one of the most influential content management systems of the past two decades, that identity has always been rooted in Drupal.org—the hub for community development, documentation, support forums, and the software itself. But looming…