Skip to content

Agentic security updates for Drupal

Patch your Drupal fleet
before attackers do.

Sentinel’s agents prepare Drupal security updates and open a pull request on your own GitHub or GitLab, where your CI runs your tests. Your team reviews and deploys. Autopilot can deploy for you when your required checks pass.

Start free. Monitor up to 20 sites per billing account at no charge.*

Card required. Free monitoring does not charge the card. Paid features require separate approval.****

Add agentic patching for US$19.99 per site a month, excluding applicable tax. The patching price includes a monthly AI allowance.***

For agencies and in-house teams running Drupal 10.3+ and 11

Sample monitoring list of fictional Drupal sites.
Monitoring
Sample security update waiting for a person to press Deploy.
Copilot
Sample Patching overview with fictional sites and jobs.
Patching
Sample Autopilot run log, from advisory to confirmed deploy.
Autopilot
Sample monthly security report with SLA results.
SLA reports

What’s new

Introductory pricing**

Monitoring is free. Patching is per site.

Monitoring is free on Pay as you go, for up to 20 sites per billing account.* Add agentic patching only on the sites you choose. The patching price includes a monthly AI allowance.***

See pricing
Autopilot

Deploys while your team sleeps

Sites whose required checks pass deploy on your schedule, under the consent you set for each site.

How Autopilot works
Agency

50 sites, patching included

One plan for agencies, on your own OpenAI or Anthropic key. Try it free for 14 days.****

Explore Agency
Security for the agentic era

Agents do the update work.
Your team keeps the final say.

Each job runs on an isolated server. An agent reads the advisory, updates the code and explains what changed in plain words. Your CI runs your tests.

  • Agentic security updates

    Move from a security release to a proposed update with automated patching.

    When we detect an eligible Drupal security release, enabled patching can prepare changes and open a pull request for your CI to test. Timing depends on the site, queue, available AI allowance or key, and applicable job limits. Review and deployment follow your accepted workflow.

    Sample security update waiting for a person to press Deploy.
  • Agentic maintenance

    Routine updates without the routine.

    Regular core and module updates on a schedule you set, grouped into one pull request per site for your team to review.

    Sample Patching overview with fictional sites and jobs.
  • Agentic upgradesComing

    Major upgrades, prepared for you.

    Drupal and CivicTheme major upgrades, worked through by agents on a private copy of your site.

    Sample Drupal 10 to 11 upgrade checklist. Agentic upgrades are coming.

Automation for every team

The routine work moves to agents. Your people keep the decisions.

Review a finished pull request, tested by your CI, instead of starting an update from scratch. Every step the agent took is in the transcript.

How Copilot works
Sample security update waiting for a person to press Deploy.

One place for
Drupal security upkeep

Security and maintenance updates, prepared on an isolated server and tested by your CI. Explore Patching

Sample Patching overview with fictional sites and jobs.
The threat

Exploits arrive in hours.
Your fix should not wait for the next sprint.

Once a fix is public, attackers can study it too. Drupal learned this in 2014, when automated attacks hit unpatched Drupal 7 sites within hours of a security release.1

A fix that waits for next sprint is a real risk to your customers and your reputation. Australia’s Essential Eight asks for fixes to online services within 48 hours of release when the vendor rates a flaw critical or a working exploit exists.4

  1. Drupal Security Team, PSA-2014-003
  2. VulnCheck, 2025 Q1 Trends in Vulnerability Exploitation
  3. Australian Signals Directorate, Patching applications and operating systems
  4. Australian Signals Directorate, Essential Eight maturity model
After a flaw goes public
  1. Hour 0A flaw goes publicUsually with its fix
  2. HoursDrupal 7 sites attacked, 2014Automated attacks within hours1
  3. Day 1Exploitation already seen28.3% of known exploited flaws, Q1 20252
  4. Day 2Malicious code expectedWithin 48 hours, sometimes 243
  5. Day 2Essential Eight deadlineCritical fixes to online services4

From advisory to production in five steps

Sentinel does the routine work. The decisions stay with your team.

  1. 01

    Advisory matched

    Drupal.org publishes a fix. Sentinel matches it to the versions your sites report.

    Sentinel
  2. 02

    Agent prepares

    An agent updates the code on an isolated server and opens a pull request on your Git host, with notes.

    Agent
  3. 03

    Tests run

    Your own CI runs your automated tests. Your required checks must pass.

    Your CI
  4. 04

    You decide

    A person reviews and presses Deploy, or merges and deploys the usual way. Or Autopilot deploys sites whose required checks pass, under the consent you set per site.

    Your team
  5. 05

    Deployed and confirmed

    Backup where your platform supports it, merge, deploy, and a check that the site reports the new version.

    Sentinel

Your code, your hosting, your call.

  • Pull requests in your repository

    Every change is a pull request on your own GitHub or GitLab.

  • Production stays separate

    An update job never touches production. Deployment is its own step.

  • No surprise upgrades

    Major upgrades only when you choose them. A stable module never moves to a development release.

  • No SSH access needed

    Deployment uses your hosting platform’s API or your own pipeline.

  • Every step logged

    A full transcript of what the agents did. Organisation administrators can export the activity log.

  • Instructions ignored

    The agent never follows instructions written in your repository’s files.


Connected in minutes.

  1. 01

    Register your site

    Add the site in the dashboard and copy its own API key.

  2. 02

    Install the connector

    Add drupal/sentinel_connector with Composer and paste the key. It reports by cron, Drush or on demand.

  3. 03

    Turn on Patching

    Connect your Git host and your hosting platform or pipeline, make sure your CI runs automated tests, then choose Copilot or Autopilot per site.

HOW IT WORKS01 / 03
Terminal — your Drupal project
$ composer require drupal/sentinel_connector
Installing the Sentinel Connector…
$ drush en sentinel_connector -y
✓ Connector enabled
Commit → your deployment pipeline → production✓ Deployed

Install. Enable. Deploy.

Add the connector with Composer, enable it with Drush, then deploy through your usual pipeline.

A small free Drupal module tells Sentinel what is installed. That report drives your monitoring and confirms each patch landed. It only reports: updates reach your site through your own Git host.

INTRODUCTORY PRICING

Start free. Add patching when you’re ready.

Introductory subscription prices. The rate card you accept stays with your billing account for its lifetime, while we continue the Service.**

Start free

Pay as you go

US$0 monitoring, up to 20 sites*

Add agentic patching for US$19.99 per site a month, excluding applicable tax. The patching price includes a monthly AI allowance.***

  • Free monitoring, alerts and SLA reports
  • Patching only on the sites you choose
  • Or use your own OpenAI or Anthropic key
Start free

14-day free trial

Agency

US$499 a month, excluding applicable tax

50 sites with monitoring and agentic patching included*

  • US$9.99 a month for each site after 50, with separate approval
  • Your own OpenAI or Anthropic key
  • Client reports and SLA tracking
Start 14-day free trial

By agreement

Enterprise

Let’s talk

Large fleets and custom terms

  • Everything in Agency
  • Agreed contract and invoicing
Contact us

USD list prices, excluding applicable tax. Card needed to start.**** Compare plans

A few useful details

Before you connect.

Can I monitor a fleet of Drupal sites?

Yes. Pay as you go monitoring is free for up to 20 sites per billing account, across its organisations. Agency covers 50 sites, and more with separate approval. Contact sales for Enterprise capacity. All three plans allow unlimited organisations and up to 50 distinct active customer users per billing account.

Can I generate SLA or monthly customer reports?

Yes. Set a security patching SLA for each site, from 6 hours to 28 days, then open the monthly report for an organisation or one client. It shows which sites met the SLA and which changes were confirmed, and it prints or downloads as a PDF. Every plan includes reports, PDF export, patching SLA tracking, refresh and full recorded history.

Can my customers sign in?

Yes. Create an organisation for each customer and invite their users, within your billing account’s shared 50-user limit. Each person sees only the organisations and sites they are authorised to access.

Can an organisation be an internal department?

Yes. Organisations can separate customers or departments within your business.

What does SLA mean here?

It means a security-patching SLA: the time allowed to fix a known security issue on a site. It is not an uptime guarantee, and Sentinel Connector does not install updates for you. A site with no data is never reported as met.

Does it check Drupal core as well as modules?

Yes. Core is assessed once, and packaged modules are matched to their Drupal.org project. Submodules retain their project identity.

What happens to custom modules?

Custom code and modules without reliable project or version metadata remain unassessed. They are visible in the inventory, without an unsupported healthy verdict.

Is syncing the same as an assessment?

No. A sync records the installed inventory. A separate assessment checks upstream release and advisory evidence, with its own status and timestamps.

How often is my site checked?

Each time your site reports a change, Sentinel checks it against Drupal.org straight away. Every site is also rechecked on weekday mornings, with extra checks during Drupal’s weekly security release window. The dashboard shows when Drupal.org data was last checked.

Where can I get the Drupal module?

Install it with Composer from Drupal.org: composer require 'drupal/sentinel_connector:^1.0'. Each site has a setup guide with its own connection values in the dashboard.

Pricing

What does "introductory price" mean?

Launch prices. The rate card you accept, including free Pay as you go monitoring for up to 20 sites, stays with your billing account for its lifetime, while we continue the Service. We may change prices for new billing accounts.

What happens when a site uses its Included AI?

Patching on that site pauses when the next AI call cannot fit in its Included AI for the month, until the 1st (UTC), unless you use prepaid AI credit or your own key.

Do I pay less if I use my own AI key?

No. The site price stays the same, and Included AI is not refunded or credited. Your provider bills you directly for the AI you use.

Which AI providers can I use?

OpenAI and Anthropic. Agency and membership patching always use your own key. You can ask us to support another provider.

Why do you need a card for free monitoring?

To confirm you are a real customer. A valid card and accepted billing terms are needed for every account. Free monitoring does not charge the card, and paid features need separate approval.

What if I need more than 20 sites?

Choose Agency. It covers 50 sites, and each additional site needs separate approval. Pay as you go covers up to 20 sites per billing account.

Agentic Drupal patching.
You stay in control.

Monitoring is free on Pay as you go, for up to 20 sites per billing account.* Card required. Free monitoring does not charge the card. Paid features require separate approval.****