Skip to content

EARLY ACCESS · INVITATION ONLY

Automated security patching for Drupal

Copilot and Autopilot let an AI agent prepare, test and ship Drupal security updates across your fleet. Patching is in testing now. Anyone is welcome to apply for a place.

Apply by email What to include

Copilot

You start each update.

An AI agent prepares the security update in your repository, runs your tests and opens a pull request on your own Git host. Your team reviews it. Nothing is deployed until a person approves it.

Autopilot

Security updates on a schedule.

Everything in Copilot, plus security updates on the schedule you choose, deployed under the consent you give each site. Only for sites whose automated tests pass the gate. Pause any site at any time.

How applying works

  1. Send us an email

    Use the template on this page. You do not need a Sentinel Connector account to apply.

  2. We review your fleet

    We look at your hosting, Git host and tests, and check that we can support them in this stage of testing.

  3. We send instructions

    If we can take you on, we invite you and send set-up instructions. If not yet, we tell you and keep your place for a later round.

What to include in your email

Email getintouch@sentinelconnector.io with the subject “Patching early access application”. The button below opens your email app with the template filled in. Answer what you can and leave the rest blank.

  • Fleet size. How many Drupal sites you look after, and how many you would try first, so we can plan places in the test group.
  • Hosting platform. The agent deploys through your hosting platform or your own pipeline. We test with each platform before we invite its users.
  • Git host. Updates arrive as pull requests on your own Git host. Whether it is GitHub or GitLab, in the cloud or self-hosted, decides how we connect.
  • Automated tests. Autopilot only runs for sites whose tests pass the gate. Copilot works without tests, but tests make every update safer.
  • How you patch today. Your current process and how long a fix takes to reach production show us where the agent can save the most time.
  • Rules you work under. Government, compliance or data residency rules change what we can offer. Tell us early.

Please do not send passwords, tokens, keys or access to your repositories. If you are invited, we ask for what we need through the dashboard, where it is stored encrypted.

Patching early access application

ABOUT YOU
- Name:
- Role:
- Organisation and website:
- Country and time zone:
- Agency or in-house team:

YOUR FLEET
- Number of Drupal sites you look after:
- Number of sites you would try first:
- Drupal core versions (for example 10.4, 11.2):
- Managed with Composer (all, some, none):
- Distribution, if any (for example GovCMS):

HOSTING
- Hosting platforms, with the number of sites on each
  (for example Platform.sh 12, Acquia 5, Pantheon 3, own servers 2):
- How code reaches production (Git push to the platform, CI pipeline, manual):

GIT REPOSITORY
- Git host (GitHub, GitLab, Bitbucket, Azure DevOps, other):
- Cloud or self-hosted (for example github.com, gitlab.com,
  GitHub Enterprise Server, self-managed GitLab):
- Automated tests run on pull requests (all sites, some, none):
- Kinds of tests (PHPUnit, Behat, visual regression, other):

PATCHING TODAY
- How you apply security updates now:
- Usual time from a security advisory to production:
- Interested in (Copilot, Autopilot, both):
- AI provider you would use (Anthropic, OpenAI, not sure yet):

ANYTHING ELSE
- Already using Sentinel Connector (yes, no):
- Security, compliance or data residency rules we should know:
- Earliest date you could start:
- Anything else:

Please do not send passwords, tokens, keys or repository access.
Open in my email app