A Drupal site rarely goes down after an update. It goes quietly wrong: a Webform stops sending, login loops back to itself, site search returns nothing. NorthDuty checks every Drupal site you support from the outside, with health checks every 5 minutes and real-browser journeys through the forms, logins and searches the site exists for. Those journeys re-run as soon as your deploy finishes.
Start your 7-day trial — no credit card, free plan after.
Webforms, logins and search checked in a real browser — re-run after every Drupal deploy.
Every site gets the same two layers, whatever its module stack or host.
Contact, enquiry, registration and application forms run as journeys: open the page, fill the fields, submit, and confirm the success message appears. A broken handler, a CAPTCHA change or a JavaScript error fails the journey at the step where it breaks.
Log in with a test account and land on the right page. Run a site search and check that results appear. These are the flows a Search API, cache or permissions change breaks without touching the homepage.
Call a signed NorthDuty webhook from your deploy step (Drush script, Pantheon Quicksilver, Acquia Cloud Hooks, Platform.sh hooks, or GitHub, GitLab or Bitbucket CI) and every journey and health check runs against the release you just shipped.
Every 5 minutes by default: uptime, SSL expiry, DNS, blank-page detection, broken resources and JavaScript errors. These are the failures a 200 response hides.
When a journey fails, you get the step, the screenshot and the run history, so triage starts with the answer.
Each run keeps a step-by-step screenshot timeline: open the page, fill the fields, submit, check the confirmation. A Webform that stopped confirming shows up as one red step, not a vague alert.
NorthDuty reads each site and proposes the journeys worth monitoring, such as the enquiry form, the member login or the course search. Turn them on in one click or describe your own in plain text.
Most Drupal incidents have a cause you can name: a core security release, a composer update that pulled in a new contrib version, update hooks that changed a schema, or a config import that dropped a setting on production. The site still returns 200 and the homepage still renders, so an uptime check stays green. The broken part is further in, on the Webform confirmation, the login redirect or the search results page.
Agencies on Drupal support retainers feel this most. Government, university and nonprofit sites carry forms and logins their users depend on, release windows are tight, and nobody can click through every flow on every site after every patch. NorthDuty does that clicking. It runs each site's key flows as journeys in a real browser and reports the step that failed, with a screenshot of what the visitor saw.
Built for support retainers: many sites, regular security releases, and clients who should never be the first to notice.
Ten client sites take an afternoon, not a sprint.
Health monitoring starts straight away: uptime, SSL, DNS, blank pages and JavaScript errors, every 5 minutes by default.
Accept the AI-suggested flows or write your own in plain text: the Webform on the contact page, the member login, the site search, the event registration.
Add one signed POST to the end of your deploy (after drush deploy or updb and cim), or point your CI or host's deploy hook at your NorthDuty webhook URL. Staging and preview deploys can be marked and are ignored.
Per-project alert rules go to your channels (and the client's, if you want). Scheduled reports and status pages keep the retainer visible.
Explore pricing, feature details, solution pages, and related tools connected to this website monitoring use case.
Pricing
NorthDuty plans are sized by how many checkout, signup and login journeys you monitor: Free, $29 Starter, $79 Pro, $199 Business. 7-day trial, no card.
Compare pricing plansHub
Explore NorthDuty features: coverage-aware AI journeys, a cross-site workspace overview, website health checks, and connected incident response.
Browse FeaturesHub
Explore NorthDuty solutions for ecommerce website monitoring, SaaS website monitoring, agency website monitoring, and startup website monitoring.
Browse SolutionsFeature
Checkout form monitoring that submits a real test entry on a schedule and alerts you when it fails. Free plan includes 1 daily form check; paid from $29/mo.
Explore Form MonitoringFeature
Monitor login flows with NorthDuty user journeys so authentication pages, forms, JavaScript, APIs, and account-access steps keep working.
Explore Login MonitoringFeature
NorthDuty runs your checkout, signup, login and form flows in a real browser on a schedule and reports the exact step that failed, with a screenshot.
Explore User Journey MonitoringFeature
Automatically run health checks and user journeys the moment your site is deployed or your CMS publishes a change.
Explore Deployment MonitoringFeature
WordPress monitoring for client rosters: real-browser journey checks and uptime that catch what plugin and theme updates break.
Explore WordPress MonitoringSolution
Monitor client sites for broken checkouts and forms, blank pages, post-launch issues, and client-ready reports.
View For AgenciesFeature
Generate PDF reports covering website health and user journeys. Download on demand or schedule recurring email delivery.
Explore ReportsFeature
See NorthDuty monitor a real WooCommerce store: a full checkout journey in a real browser, a free-shipping rule that silently broke, and a booking API that timed out — the step, screenshot and explanation NorthDuty recorded.
Explore Live DemoAnswers to common questions about this monitoring feature and when teams should use it.
Drupal monitoring checks that a Drupal site is not just online but working: pages render, Webforms submit, logins succeed and search returns results, including right after an update. NorthDuty does this from outside the site with real-browser journeys and health checks.
No. NorthDuty runs from outside in a real browser, so there is nothing to install, no extra code on the client's site, and monitoring keeps running even when the site itself is in trouble. The only optional step is a webhook call from your deploy so checks run the moment a release lands.
Yes. That is the main thing it is for. A journey fails at the broken step, with a screenshot of what the visitor would have seen. If your deploy calls the NorthDuty webhook, every journey and health check runs as soon as the update is live instead of at the next scheduled run.
Each project has a webhook URL. Post to it at the end of your deploy, signed with HMAC-SHA256 over the timestamp and request body (X-ND-Timestamp and X-ND-Signature headers). It works from a Drush or shell script, Pantheon Quicksilver, Acquia Cloud Hooks or Platform.sh deploy hooks. GitHub, GitLab and Bitbucket CI webhooks are recognised directly, and non-production environments are ignored.
Yes. NorthDuty checks the public site the way a visitor reaches it, so the host does not matter. The host only affects where you put the webhook call.
Plans are sized by journeys and sites, not per site: Starter ($29) covers 6 journeys across 2 sites, Pro ($79) covers 15 journeys across 5 sites, and Business ($199) covers 45 journeys across 15 sites.
Put every Drupal site you support in one workspace, and hear about the broken form before the client does.
7 days with Pro features and limits, no credit card — then keep one daily journey on the free plan.