When an advisory matches your site.
When a Drupal security advisory affects a site, the agent starts straight away or waits for the weekly Drupal security release window. You can set quiet hours. Highly critical advisories can skip the wait.
Everything else, on your schedule.
Regular updates to Drupal core, modules and other Composer packages that are not security fixes. Choose weekly, fortnightly, monthly, every two months or quarterly, and whether to take patch releases only or patch and minor releases.
Sentinel sees which of your sites need it.
Packages are updated. An AI agent follows the release notes in your code and configuration.
Your pipeline checks the pull request on your own Git host.
Review and deploy. Autopilot, rolling out separately, can do it under the consent you set.
The connector reports the new version, so done means done.
Automated up to the pull request.
Updates run on your schedules without anyone starting them. The agent stops at the pull request: your team reviews it, merges it and deploys.
Merges and deploys when tests pass.
Rolling out separately, on the same plan: you choose Copilot or Autopilot for each website once Autopilot is available to you. Everything in Copilot, plus the agent merges the pull request and deploys it once your tests pass, under the consent you give each site. Only for sites whose automated tests pass the gate. Pause any site at any time.
DATA REGIONS Coming soon
Patching runs each update in its own isolated workspace, so one site and five hundred sites get the same treatment. Today your data is processed in our Australian data centre.
Soon you will be able to choose the country where your data is processed, for teams with data residency or government rules. Tell us your needs in your application.
Use the template on this page. You do not need a Sentinel Connector account to apply.
We look at your hosting, Git host and tests, and check that we can support them in this stage of testing.
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.
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.
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.
