Skip to content

Sentinel in two minutes

Drupal updates, handled.
You keep the final say.

Why Sentinel exists, who it is for, and how Copilot and Autopilot take the routine update work off your plate.

The problem

Keeping Drupal patched is a race run at awkward hours.

Security fixes arrive on their schedule, not yours.

Drupal sets aside a window each Wednesday for security releases. Depending on where you are, that lands in your evening, overnight, or in the middle of a busy day. Highly critical fixes can come out at other times too.

Pick a city to see the window in its local time.

UTC
Wed 4 pm to 10 pm UTC

Attackers read the fix too.

Once a fix is public, attackers can study it. In 2014, automated attacks hit unpatched Drupal 7 sites within hours of a security release.

Sentinel can start as soon as it sees a fix, so your update can be ready before attackers catch up. A fix that waits for the next sprint is a real risk.

Illustration: with Sentinel the update can be ready before attacks begin; the usual fix in the next sprint comes days or weeks later. Source: Drupal.org public service announcement PSA-2014-003. Bars are illustrative.

Then the routine updates pile up.

Core and module updates are small, dull and never-ending. They wait for a quiet week that never comes, and the backlog keeps growing.

Illustration: fourteen updates wait in a column while this sprint's column holds feature work.

Is it for you?

Two ways in, depending on where you start.

You have a pipeline. You’re ready.

Sentinel fits people who already ship Drupal code through Git: freelancers, agencies and in-house developers.

  • Your site’s code is in GitHub or GitLab
  • Your CI checks every pull request
  • Automated tests run in that CI
  • Drupal 10.3 or newer

Illustration: for freelancers, agencies and in-house teams, four checks marked ready: code in Git, CI on pull requests, automated tests, and Drupal 10.3 or 11.

No pipeline yet? Our team can set it up.

If you own a Drupal site but nobody runs a pipeline for it, we can build one for you: Git hosting, CI and deploys, plus the automated tests that updates need.

A separate, paid service. Setup is not part of any plan. Every site is different, so we look at yours first and send you a quote.

Illustration: five steps. Tell us about your site, we send a quote for this separate service, we set up Git, CI and deploys on your accounts, we add automated tests if you have none, then you turn on Copilot or Autopilot.

How it works

From a new release to a ready change.

A small module tells us what’s on your site.

Install the free Sentinel Connector module. It reports your Drupal core and module versions to Sentinel.

It only reports. It never updates your site.

Illustration: your Drupal site sends a site report to Sentinel, which finds one module that needs a security fix.

We spot the fix your site needs.

Sentinel checks every site against Drupal.org security advisories and releases. You see which sites need which fix, and how long each has waited.

Illustration: a sample Webform security advisory matched against eight sites; three run the affected version and need the fix.

An agent prepares the update.

An AI agent updates the packages with Composer, follows the release notes, and opens a pull request in your own repository on GitHub or GitLab. Your CI runs your tests on it.

A pull request (a merge request in GitLab) is a proposed code change that waits for your review.

Illustration: a sample pull request in your repository updates drupal/webform from 6.2.9 to 6.2.10, opened by Sentinel, with Composer install, PHPUnit and Behat checks passing.

Copilot

The agent prepares. You approve the deploy.

A security fix comes out while you sleep.

It might be 3 am for you, or a Wednesday evening. Either way, nobody has to get up.

Illustration: at 03:12 a sample Webform security release arrives and Sentinel starts preparing the update while your team is asleep.

Sentinel prepares it. Your tests run.

By the time anyone looks, the update is a pull request and your own tests have already run on it.

Illustration: at 03:41 a sample pull request opened by Sentinel has passed Composer install, PHPUnit and Behat, and waits for your review.

Wake up to a pull request, not a pager.

Look over the change and the test results with your morning coffee. Happy with it? Press Deploy.

Sentinel takes a backup where your hosting supports it, merges exactly what you reviewed, and deploys.

Illustration: at 08:05 the sample site shows one security update with tests passed, a link to what the agent did, and a Deploy button.

The site confirms it. Done means done.

After the deploy, the connector module reports the new version. You see the fix land, rather than hoping it did.

Illustration: before, webform 6.2.9 needs a security fix; after the deploy the site reports webform 6.2.10, up to date, confirmed by the site at 08:14.

Autopilot

Set your rules, then let it run.

Set your rules once.

Choose your schedule and quiet hours for security deploys, and give consent for each site. Pause a site, or switch it back to Copilot, at any time.

Quiet hours hold security deploys. Highly critical fixes skip them, unless you turn that off.

Illustration: sample site rules. Autopilot on, security deploys held between 9 am and 5 pm unless highly critical, required checks PHPUnit and Behat, and an email if a deploy fails.

A fix comes out. Sentinel prepares it. Your tests pass.

Same careful start as Copilot: a pull request in your repository, checked by your own tests.

Illustration: at 03:41 a sample pull request opened by Sentinel has passed its checks; Autopilot will deploy it when your rules allow.

It deploys while you sleep.

When your required checks pass, Autopilot takes a backup where your hosting supports it, merges and deploys when your rules allow. Then it checks the site reports the new version.

Illustration: overnight on a sample site, required checks pass, a backup is taken, the tested change is merged and deployed, and the site reports the new version.

Read the summary over breakfast.

You check the result instead of doing the work. If anything fails, Autopilot stops, comments on the pull request and tells your team.

Like Copilot, Autopilot needs automated tests. No tests yet? Our team can write them as part of a setup quote.

Illustration: an overnight summary. Two sample sites deployed and confirmed; on a third a test failed, nothing was deployed and the team was told.

Hand off the routine.
Keep the final say.

The AI behind each update costs cents. Less than your morning coffee.See pricing

Monitoring is free for up to 20 sites. Setup help is a separate service, quoted per site.