Every live Drupal site runs on someone else's update schedule. A security release for Drupal core, or for one of the contributed modules you run, lands on the Drupal project's calendar (never yours) and someone has to read it, test it against the modules you actually run, and ship it before the hole is used against you. That job never ends, and a critical fix never waits for a convenient week.
Managed hands that job to us. Two things age on a running Drupal site, on two separate clocks: the stack underneath (the servers, database, PHP and cache) keeps itself patched and self-healing on every plan, no add-on needed; your Drupal code does not. Deciding which release is security-critical, building it, testing it against your modules, and shipping it to live is the hands-on work Managed takes over, driven by our tailored update automation, typically the same day a fix ships.
It is the same promise we make everywhere else, pointed at the layer that changes most often: we don't strand the people who trusted us. A security release should never cost you a weekend.
Three plans, three depths of delegation: one site, one site with fuller cover, or a whole platform. An Ægir platform (Ægir is the open-source control panel that manages whole fleets of Drupal sites) is one shared Drupal codebase that many of your sites run on, so the top plan is priced per platform, not per site. The Managed Basic plan covers security releases only; non-security updates fold into the Managed Extended and Enterprise plans. Prices are per month; onboarding is a one-time setup.
Legacy cores stay first-class. Pressflow 6, the high-performance Drupal 6 fork, and Drupal 7 run here on the newest PHP each core supports, and Managed keeps Drupal 7 through Drupal 11 current: core, contributed modules and the PHP-compatibility work. A Pressflow 6 site joins that cover the moment it takes the Drupal 6 to Drupal 7 hop. We never force a legacy site onto modern Drupal; the crossings we support are Drupal 7 to Backdrop, the community fork that carries the Drupal 7 way forward, and the Drupal 6 to Drupal 7 hop that opens the same road to a Pressflow 6 site, both now ordinary, supported upgrades on our stack. Both run on a copy of your site while the original keeps serving, so you click through the result and decide in your own time, and a single task hands the domain over when you are happy. Weighing a legacy core? Talk to us »
Same-day is how we run today. A critical security release is typically patched the same day it ships (current practice, not a binding turnaround). Anything we commit in writing lives in the Terms of Drupal Service. The response and support levels come with the hosted plan under your Managed subscription, handled through our private helpdesk.
Onboarding comes first. Before the monthly service begins we build your tailored update automation around your codebase and prove the first update end to end: a one-time setup fee, shown on each plan above. Your subscription starts once onboarding completes; using our Managed service means you agree to the Terms of Drupal Service.