Enterprise Academic Platform for NSUT
A Drupal platform for Netaji Subhas University of Technology in Delhi, where each department publishes its own notices, calendars and faculty pages.
- Drupal
- PHP
- MySQL
After launch, for years
A Drupal site is not finished when it launches. Security releases arrive on a schedule, modules fall behind core, and the person who built it moves on. This is the work of keeping a Drupal platform patched, upgraded and understood, by a team that has built them.
Most Drupal sites that get into trouble do not fail at launch. They fail two or three years later, when a security release was skipped because nobody was sure what it would break, a contributed module stopped being maintained, and the only person who understood the custom code left. By then an upgrade that should have taken a week takes a quarter.
Drupal support is the routine work that prevents that. Security releases go on within days of coming out. Core and contributed modules are kept within supported versions, so the next major upgrade is a short project. On a neglected site it can turn into a rebuild. Custom code is documented as it is touched, so the platform does not depend on one person’s memory.
We built the Drupal platforms for a technical university and an insurance broker, both on our work page, and we look after both of them today. That is the background this support comes from: we know where large Drupal sites tend to break, because we have had to make them not break.
Support is one part of the Drupal work we do. We also build enterprise Drupal platforms, run migrations from older versions, and write custom modules and themes, so a problem in your site rarely has to be handed to someone else.
If your site is still on Drupal 7, which reached end of life in January 2025, support is not the first step. Start with Drupal migration, and come back here once you are on a supported version.
Drupal publishes security advisories on a fixed weekly window. We review each one against your site and apply the ones that affect you, tested on staging first.
Minor core releases and contributed modules kept current, so you never fall more than one step behind a supported version.
Drupal 10 to 11, planned as a project with an assessment of deprecated code and modules that have no forward path. You hear about it well before the old version runs out of support.
Uptime monitoring, daily backups kept off the server, and a restore that has actually been tested.
A monthly allowance of developer hours for bugs, new fields, a changed workflow, or a new content type. Three plans: 8, 20 or 50 hours a month, depending on how much the platform changes.
Every custom module we touch gets written down, so the platform stops depending on whoever built it.
Core version, contributed modules, custom code, hosting and the backlog of skipped updates. You get a written report before agreeing to anything monthly.
If the site is behind, we bring it current once, as a fixed piece of work, so the monthly plan starts from a clean baseline.
Security releases, updates, monitoring and the agreed developer hours, with a short report at the end of each month on what changed.
When the next major version approaches, we send an assessment and a plan while there is still comfortable time before the old version runs out of support.
The platform and the tools around it. Nothing here is chosen because it is new.
A Drupal platform for Netaji Subhas University of Technology in Delhi, where each department publishes its own notices, calendars and faculty pages.
A Drupal rebuild for Mahindra Insurance Brokers, bringing older, scattered systems onto one platform.
Yes, and most support work starts that way. The audit is how we learn the site before we are responsible for it.
Critical ones within days of release, after a test on staging. Lower-risk releases go out in the next scheduled update.
No. We work with whatever you have now, a managed Drupal platform or an ordinary cloud server. If the hosting itself is the problem, we will say so, but it is not a condition.
Now, if you have not started. Leave it until Drupal 10 is close to leaving security support and you are upgrading in a hurry, which is when things break. Drupal.org publishes the support dates for each version, and the audit tells you how much of your code is ready.
Plans come with 8, 20 or 50 developer hours a month. A stable site that mostly needs updates sits at 8. A platform with a team asking for regular changes usually needs 20. Fifty is for platforms under active development, close to a part-time developer.
It depends on the size of the site, how far behind it is, and which plan you choose. After the audit you get a fixed monthly figure in writing.
Send the address and what is worrying you about it. You get an audit plan and a monthly figure, written by a person who works on Drupal.
Vikalp Development
We usually reply within one business day