Acquia supports everything Drupal 6

Last year, Acquia opened for business, offering commercial support for a defined software distribution called Acquia Drupal. One could purchase commercial support for all the modules in Acquia Drupal. As I mentioned last week in my 2009 predictions for Drupal, one of the things we learned relatively fast is that people wanted more than just Acquia Drupal. They wanted support for all modules, themes and custom code.

No surprise, but when we set out to build Acquia little more than a year ago, we weren't quite sure how we'd go about supporting everything with the limited resources we had available. We have since learned and grew a lot, and we decided that we're finally ready to start providing technical support for all of Drupal 6.x -- not just Acquia Drupal but all modules and themes available on, as well as custom code.

So last week we rolled out a big release of the Acquia Network, the new Acquia Network connector (available from, see Gabor's blog post for details), a 156 page "Getting Started Guide" on Drupal, and a ton of new content on our website. Starting today, we're ready to give many more customers what they want: support for everything Drupal 6.

We'll continue to tweak and experiment with our offering in 2009 so we didn't make a big deal out of this change (i.e. no press release, no analyst briefings). However, I wanted to bring this to your attention because I'm really excited about it. It means it will be easier for us to help take Drupal to the enterprise, and that Acquia will contribute to more and different parts of the Drupal project.

While Acquia Drupal no longer defines our support boundaries, it is still a great on-ramp for people getting started with Drupal. We are continuing to invest in Acquia Drupal so watch this space for more Acquia Drupal announcements.

Kudos to the entire Acquia team for making this milestone happen. Thanks!


Anonymous (not verified):

Will you guys be submitting patches to d.o contrib modules and themes via the projects' issue queues, as you come across bugs and etc?


All Acquia created patches are submitted back to the Drupal project. Acquia engineers work closely with core maintainers and contributed module maintainers to ensure that there is little or no divergence between Acquia Drupal source code and the source code of available on

Alex Rollin (not verified):


This is great news. I am excited about all the possibilities.

Acquia can help all of us in the Drupal support network to see just how far a company can go towards offering systematic support.


Chris Johnson (not verified):

That's an interesting challenge Acquia has taken on. The contrib repository is large and constantly growing, and the quality is highly variable. On top of that are the maintainers who do not apply corrective patches from their queues in a timely manner.

But I can see where customers would want that, and how it might be priced like a "shared risk" pool sort of like insurance.

Dries, as you know, we're* supporting about 120 modules for Drupal 6 for our largest customer. It's a tough job! ;-)

*(we = OpenBand/MCDean)

Gerhard Killesreiter (not verified):

Can't say that I am surprised about this change. From my experience I knew that the previous offer wouldn't be sufficient for most people.

dchakrab (not verified):

I'm curious, as I have been for a while now. Can you clarify this a little?

For example, how would one "support" a theme that is available in contrib, but fails to meet accessibility requirements? Or a module that has bugs?

Does support = end-user hand-holding, or more involved, we'll-fix-the-bugs support?



Nick Lewis (not verified):

I think this is one giant leap in Acquia's strategy, and Drupal as a whole. To be honest, the original Acquia Drupal -- while safe -- struck me as way too timid of an offering for a start-up of Acquia's potential.

Cheers to Acquia getting more ambitious about its cat herding abilities!

I'd imagine by "support" you mean developing an internal knowledge base to use to help, and warn customers in regards to 3rd party modules, letting them understand the benefits/costs/dangers if you don't have the incentive to fix a 3rd party module outright.