Skip to content

For in-house teams

One Drupal fleet.
One patching policy.

Give each department its own organisation and keep one agreed approach to security updates.

Set the policy across your sites

Decide who approves changes, when updates run and which patching targets apply. Configure each site to follow that policy. Keep departments in separate organisations and give each team access to the sites it manages.

Sample Patching overview with fictional sites and jobs.

Test the change, then deploy

Agents prepare security updates as pull requests in your GitHub or GitLab repository. Your CI runs your automated tests. Those tests are required.

In Copilot, a person reviews the change and presses Deploy. Autopilot deploys on your schedule when your required checks pass, under the consent you set for each site. Your team handles exceptions.

Sample security update waiting for a person to press Deploy.

Give management clear evidence

Monthly reports show recorded fixes, targets met or missed, and outstanding work, including gaps or unknown periods. Bring that evidence to management and audit reviews.

Sample monthly security report with SLA results.

Start small. Grow when you need to.

Start free with Pay as you go

Pay as you go monitors up to 20 sites per billing account at no charge.* Add agentic patching for US$19.99 per site a month, excluding applicable tax. The patching price includes a monthly AI allowance.***

Use Agency for a larger estate

Agency includes monitoring and agentic patching for 50 sites at US$499 a month, excluding applicable tax.** Each site after 50 costs US$9.99 a month, with separate approval.* Your own OpenAI or Anthropic key is required.*** Try it free for 14 days.****

Agree the infrastructure and terms you need

Enterprise is for estates that need agreed terms.

  • Custom infrastructure on AWS, Google Cloud or Azure
  • Single sign-on and a named contact
  • Agreed contract and invoicing

Put your patching policy into daily work.