For years, Cherwell was the out-of-the-box answer for enterprise IT. You bought it and it came up running — service management, configurable to your business, ready to scale. That market never went away. Cherwell did.
Today, Drupal sits in that same market: a full-service, open-source platform that scales for any enterprise or industrial operation that wants to come out of the box running. Add Drup-AID and it does the job the way modern software should — AI-driven, not click-path-driven.
If you run on Cherwell Service Management, the clock is already ticking. Ivanti has set Cherwell’s end-of-life date for December 31, 2026 — and cloud customers can no longer renew. Your choices, as the vendor frames them, are to be migrated into Ivanti Neurons for ITSM or to re-platform onto something like ServiceNow. Both mean a costly migration, a new per-seat license, and a fresh round of vendor lock-in.
There’s a third option nobody in that conversation wants to mention: own your platform instead of renting it.
I say that as a former Cherwell employee. I worked inside that platform — built the mApps, wired up the workflows, lived in the designer. I know what made it good, and I know exactly what it cost you in licensing and lock-in. That’s why I built Drup-AID: an open-source, self-hosted, AI-driven one-stop platform that does the jobs Cherwell did, without the EOL clock or the renewal invoice.
What you actually liked about Cherwell
Strip away the branding and Cherwell was really four things in one place:
- A self-service portal for your users
- A knowledge base they could search
- Workflow automation behind the scenes
- A configurable data model (mApps) you could shape to your business
You didn’t love it because it was Cherwell. You loved it because it was one place that did all of that. That’s the bar any real alternative has to clear — and it’s exactly where most “Cherwell replacements” fall down: they hand you ITSM, then sell you three more tools for the portal, the content, and the automation.
What Drup-AID does differently
Drup-AID is built on Drupal 11 — the same open-source platform that runs governments, universities, and Fortune 500s — with an AI layer wired in natively. Drupal already gives you the portal, the searchable knowledge base, configurable content models, and granular permissions out of the box. Drup-AID adds the part that’s new: AI agents that do the work, driven by plain-English instructions instead of a designer full of click-paths.
The differences that matter when you’re choosing what to run for the next decade:
- Open source, not end-of-life. No vendor can sunset it out from under you. The code is yours; the roadmap is the community’s.
- Self-hosted — your data on your hardware. Run it on an ordinary hosting account or your own servers. Nothing has to touch a vendor’s cloud. For regulated and industrial operations with an in-house mandate, that isn’t a nice-to-have — it’s the whole ballgame.
- AI-driven from the ground up, not bolted on. You build and change the platform by chatting with it. “Add a catering-request field to the contact form.” “Draft a reply to this ticket using our knowledge base.” The AI is the interface, not a per-seat add-on.
- No per-seat licensing, no renewal trap. One platform you own, not a meter that runs while you sleep.
“AI-driven” should mean the AI does the work
Every legacy vendor is now stapling an “AI assistant” onto a 15-year-old product and calling it transformation. Drup-AID starts from the other end: the AI agents are the platform. A request comes in, the system reasons about it, drafts the response or edits the content or routes the ticket, and shows you its work — every change is a revision you can roll back. That’s what AI-driven should mean: not a chatbot in the corner, but agents that actually move the work forward.
Why trust this over another listicle
Most “best Cherwell alternatives” posts are written by people selling the next platform. I’m not migrating you from one lock-in to another. I built Drup-AID, I run my own company on it, and I’ll help you deploy it for yours. That’s the whole pitch: I built it · I run on it · I’ll deploy it for you.
Don’t wait for the deactivation notice
Cherwell’s cloud environments deactivate 30 days after your renewal date once you stop renewing. Migrations take longer than that. The teams who come out of this ahead are the ones who pick their next platform on their own terms — not under a vendor’s countdown.
If you’d rather own your next platform than rent it, here’s where to start:
- Watch the free course → the Drup-AID Developer Academy walks through building on the platform, chapter by chapter.
- See the code → Drup-AID is open source on GitHub.
- Talk to a former Cherwell developer → if you’re staring down a Cherwell migration and want an open, AI-driven path instead, get in touch with Peak AI Design.
The end of Cherwell doesn’t have to mean the start of another decade of lock-in. It can mean the moment you finally own your stack.
Comments