I've been working on Drupal Scan for a while now, and I think it's time to share what's coming and when. Building in public isn't always comfortable, but it keeps me accountable. And maybe it helps someone else planning a similar journey.
What is Drupal Scan?
Drupal Scan is a service that audits your Drupal sites for security issues, performance bottlenecks, pending module updates, code quality, and more. The goal is to give agencies and site owners a centralized dashboard where they can see the health of all their Drupal projects at a glance.
If you're managing multiple Drupal sites, or even one large one, you know how easy it is to miss things. A security update here, a deprecated function there. Drupal Scan aims to make that maintenance work visible and manageable.
The Roadmap
December 2025: Website Launch
Before the year ends, I'm publishing the website with the landing page and blog. English only for now. I want to validate the concept first before investing time in translations. If there's real traction, other languages will come later.
Early January 2026: Module Release
The Drupal module is the core piece that connects your sites to the service. I'm currently waiting to hear back about a namespace because there's an old, abandoned module using the name I want, and I've requested it. If I don't get an answer by early January, I'll just pick a different name and move forward. It won't be as catchy, but waiting forever isn't an option.
January 2026: Beta Access for Agencies
Once the module is out, I'll start giving free beta access to a small group of agencies. This won't be a public signup. I'll be inviting people manually and keeping it limited on purpose.
The goal here isn't growth, it's feedback. I need real users telling me what's useful, what's missing, and what doesn't work. That kind of input is worth more than any feature I could build in isolation.
February 2026: Paid Plans and Public Launch
By February, I plan to implement the paid tier features, end the closed beta, open public registration with a free tier available, and start accepting payments.
This is the real validation phase. The question I need to answer is simple: are people willing to pay for this? I believe there's value here, especially for agencies juggling dozens of Drupal projects. But belief isn't data. February is when I find out.
Why Build This?
Drupal maintenance is often invisible work. Sites run, updates get applied (hopefully), and nobody notices unless something breaks. I think there's an opportunity to make that work visible, both for agencies managing client sites and for clients who want to understand what they're paying for.
We'll see if I'm right.