# Cloud or on-premise IPMS for government institutions

URL: https://zernyxhub.com/blog/cloud-vs-on-premise-ipms
Author: Dr. Deepak Chitkara, Founder, Zernyx Innovations
Published: 2026-11-05
Category: Technology transfer

> Cloud IP management software or an on-premise install? Costs, cybersecurity and a decision table for government institutions, with DPDP and CERT-In checks.

**Short answer:** Most government universities and institutes are better served by cloud IP management software hosted in India, because the vendor runs cybersecurity, backups and updates under its contract. On-premise suits institutions with a strong IT team or a rule that data stay on campus. Either way, the institution remains responsible for inventor data under section 8(1) of the DPDP Act, 2023.

When a government university or research institute decides to move its patent records off spreadsheets, the first technical question is usually where the software should run. Some IT committees assume a server on campus is the safe choice. Others assume the cloud is the modern one. Neither assumption answers the real question, which is who will operate the system well for the next ten years.

The honest answer depends more on your staff and your rules than on technology. This post sets out the options, the legal and policy points a government institution must check, a cost comparison and a decision table.

## What is the difference between cloud and on-premise IPMS?

An IP management system (IPMS) holds invention disclosures, patent filings, deadlines, agreements and inventor details. The software can run in two broad ways.

| Question | Cloud (vendor hosted) | On-premise (your server) |
|---|---|---|
| Where the data sits | Vendor's data centre, ideally in India | Your campus data centre or server room |
| Who installs updates and security patches | The vendor | Your IT team |
| Who runs backups and disaster recovery | The vendor, as contracted | Your IT team |
| Upfront cost | Low; usually a subscription | Server hardware, licences and set-up |
| Running cost | Annual subscription | Staff time, power, hardware renewal |
| Speed to start | Weeks | Months, after procurement and set-up |
| Who answers for the inventor data in law | The institution | The institution |

That last row is the one most committees miss. Moving to the cloud does not move responsibility.

**Cloud or on-premise: what you take on**
Cloud IPMS:
- Vendor runs updates and backups
- Subscription instead of hardware
- Contract must name safeguards
- Choose India hosting
On-premise IPMS:
- Your team runs updates and backups
- Hardware and set-up cost upfront
- Data stays on campus
- Needs staff for years
Pick the model your institution can operate well for ten years.

## What does the DPDP Act mean for this choice?

The [Digital Personal Data Protection Act, 2023](https://www.meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf) treats the institution that decides how inventor data is used as the Data Fiduciary. A software vendor processing that data on its behalf is a Data Processor. MeitY notified the Act's commencement on 13 November 2025, and most duties of a Data Fiduciary take effect eighteen months later, around 13 May 2027.

Four provisions shape the cloud decision:

- Section 8(1) keeps the fiduciary responsible for compliance, including processing by its processor.
- Section 8(2) allows a processor to be engaged only under a valid contract.
- Section 8(5) requires reasonable security safeguards, and the [DPDP Rules, 2025](https://www.meity.gov.in/static/uploads/2025/11/53450e6e5dc0bfa85ebd78686cadad39.pdf) list them in Rule 6, including encryption or masking, access control, logs and backups.
- Section 8(6) requires the fiduciary to inform the Data Protection Board and affected people of a breach.

The Schedule to the Act allows a penalty of up to ₹250 crore for failing to take reasonable security safeguards. With an on-premise system, your IT team must deliver those safeguards. With a cloud system, your contract must make the vendor deliver them, and you must be able to check. Our post on [the DPDP Act and IP management software](https://zernyxhub.com/blog/dpdp-ip-management-software) has the full checklist.

## What do CERT-In's directions require?

CERT-In's [directions of 28 April 2022](https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf), issued under section 70B(6) of the Information Technology Act, 2000, apply to "all service providers, intermediaries, data centres, body corporate and Government organisations". Three requirements matter here:

| Requirement | What the directions say | Who does it in each model |
|---|---|---|
| Incident reporting | Report listed cyber incidents to CERT-In within 6 hours of noticing them | Cloud: vendor and institution agree who reports; on-premise: your IT team |
| Log retention | Keep ICT system logs securely for a rolling 180 days, within Indian jurisdiction | Cloud: vendor, in India; on-premise: your servers |
| Clock synchronisation | Connect to the NTP server of NIC or NPL, or a source traceable to them | Cloud: vendor; on-premise: your IT team |

The log rule is one reason many institutions insist on India hosting for any cloud service. Ask the vendor in writing where logs are kept and for how long.

## What about MeitY empanelment and GeM?

MeitY empanels cloud service offerings for government use. Its [Cloud Services Bouquet guidelines](https://egovstandards.gov.in/sites/default/files/2026-03/Cloud%20Services%20Bouquet.pdf), prepared by its Cloud Management Office, say empanelled services must meet MeitY's empanelment controls and are listed on the Government eMarketplace (GeM) once empanelled. The same document describes itself as advisory.

For a government institution, two practical questions follow. Does the IPMS vendor host on a MeitY-empanelled cloud? And can you buy it through GeM, or through a route your finance office accepts? Ask your IT cell whether your ministry or state has issued instructions on cloud use, because some have.

## Why is cybersecurity the biggest cost of running IPMS on campus?

An IPMS holds unpublished inventions, draft patent specifications, licence terms and inventor details. Before a patent application is published, a leaked draft can harm the invention's novelty and hand a competitor the idea. That makes the system a target worth protecting properly, and protection is expensive when you do it yourself.

Running a server on campus safely means more than installing the software. Someone has to:

| Security task | What it involves | Who does it on cloud | Who does it on-premise |
|---|---|---|---|
| Patching | Applying operating system, database and application updates as soon as they are released | Vendor, under the contract | Your IT team |
| Network defence | Firewall, intrusion detection, secure remote access for reviewers and attorneys | Vendor | Your IT team, with paid tools |
| Monitoring and logs | Watching for unusual access, keeping logs for 180 days in India under CERT-In's directions | Vendor | Your IT team |
| Incident response | Containing an attack, reporting to CERT-In within 6 hours, informing the Data Protection Board and inventors | Vendor and institution together, as the contract sets out | Your IT team alone |
| Security testing | Regular vulnerability assessment and penetration testing by a qualified auditor | Vendor, with reports shared on request | Your institution pays an auditor |
| Backups and recovery | Encrypted backups, tested restores, a disaster recovery site | Vendor | Your IT team |

Each of these needs skilled people. A university IT department that runs email, Wi-Fi and admissions systems rarely has a security engineer free to watch one more server around the clock. Hiring one, or contracting a managed security service, costs lakhs of rupees a year before any software is bought. Automated scanning tools, increasingly helped by AI, also mean an unpatched server exposed to the internet does not stay unnoticed for long.

A cloud vendor spreads that cost across all its customers and is bound by its contract to run these controls. That is the strongest practical argument for cloud. One legal point stays the same: under section 8(1) of the DPDP Act the institution remains responsible for inventor data, so the vendor's duties must be written into the agreement, with audit reports and breach notice you can rely on.

**Where five years of on-premise money goes**
₹62 lakh over five years (illustration):
- Software (28%): Licence and support
- Security (48%): Engineer time, tools, audits
- Hardware and backup (18%): Servers, storage, recovery
- Patching and admin (6%): General IT staff time
Invented figures, from the cost table below.

## How do the costs compare?

**Illustration with invented figures** for a mid-sized institution over five years:

| Cost line | Cloud | On-premise |
|---|---|---|
| Software | Subscription ₹2,00,000 a year × 5 = ₹10,00,000 | Licence ₹10,00,000 plus ₹1,50,000 a year support × 5 = ₹17,50,000 |
| Server and storage hardware | Included | ₹6,00,000 |
| Backup and disaster recovery | Included | ₹1,00,000 a year × 5 = ₹5,00,000 |
| General IT staff time for patching and administration | Minimal | 10% of one engineer at ₹7,00,000 a year × 5 = ₹3,50,000 |
| Security engineer or managed security service | Included | Half of an ₹8,00,000 a year service, ₹4,00,000 × 5 = ₹20,00,000 |
| Firewall, endpoint and monitoring tools | Included | ₹1,00,000 a year × 5 = ₹5,00,000 |
| Vulnerability assessment and penetration testing | Included; ask for the reports | ₹1,00,000 a year × 5 = ₹5,00,000 |
| Five-year total | ₹10,00,000 | ₹62,00,000 |

Your quotes will differ, and some vendors offer only one model. The lesson from the illustration is to count security and staff time honestly. Leave them out and on-premise looks cheaper than it is; put them in and the security lines alone can exceed the whole cloud subscription.

## Which should you choose? A decision table

**Five questions before you decide**
1. Rules: Does any policy require data on campus?
2. Staff: Can IT patch, back up and monitor for years?
3. Hosting: Will the vendor host and log in India?
4. Contract: Rule 6 safeguards and breach notice in writing
5. Exit: Can you export all records if you leave?

| If your situation is | Lean towards |
|---|---|
| A written rule or ministry instruction requires data on campus | On-premise, or a private cloud your institution controls |
| A small IPR cell and a stretched IT team | Cloud hosted in India |
| A strong central IT team already running secure servers | Either; compare five-year costs |
| You need to start within a quarter | Cloud |
| Many campuses or remote reviewers need access | Cloud |

My own view is that most government institutions without a dedicated security team should choose cloud software hosted in India, with a tight contract. I am less sure about large institutions with mature data centres; for them, the five-year cost comparison should decide.

## What should a cloud contract include?

If you choose cloud software, the contract is where the institution's protection lives. At a minimum it should cover:

- Hosting location for data, backups and logs, named as India if that is your requirement.
- The Rule 6 security safeguards, described in terms you can check, and the right to audit or receive audit reports.
- A breach notice period short enough for the institution to meet its own duties under section 8(6) of the DPDP Act and CERT-In's 6-hour reporting rule.
- Who reports an incident to CERT-In, and how the two sides share information during one.
- A full export of records and documents, in a usable format, on exit, followed by deletion and a certificate.
- Uptime and support commitments, with what happens if they are missed.

Ask your legal office to review the processor terms against the DPDP Act before signing. These points matter more than the subscription price.

## Common mistakes

- Assuming the cloud vendor carries the legal risk. Under section 8(1), it does not.
- Buying on-premise and then not budgeting for security staff, testing, patching and backups.
- Signing without an exit clause that guarantees a full export of records and documents.
- Forgetting where the logs are kept.
- Choosing before asking the finance office how the purchase will be made.

[Zernyx IPMS](https://ipms.zernyxhub.com/) is an IP lifecycle management platform for universities and research institutions, to manage patents, filings and IP portfolios end to end. Ask about hosting, logs and exports in your first call with any vendor, including us.

## Common questions

### Can a government university use cloud IP management software?

Generally yes, subject to its own IT and procurement rules. Many government bodies prefer cloud services empanelled by MeitY, which MeitY's cloud guidelines say are listed on the Government eMarketplace once empanelled. Check your institution's IT policy and any ministry instructions before buying.

### Does the DPDP Act require inventor data to stay in India?

The Act does not impose a general rule that all personal data stay in India. Section 16 lets the government restrict transfers to countries it notifies. Separately, CERT-In's 2022 directions require covered entities, including government organisations, to keep ICT system logs within Indian jurisdiction for 180 days. Many institutions ask for India hosting anyway.

### Who is responsible for a data breach in a cloud IPMS?

The institution, as Data Fiduciary, remains responsible under section 8(1) of the DPDP Act, including for processing by its vendor. That is why the contract must name the security safeguards in Rule 6 of the DPDP Rules, 2025 and a breach notice period.

### Is on-premise IP management software more secure?

Only if the institution can run it well: patching, backups, access control, log retention, security testing and incident response. That usually needs a security engineer or a managed security service, which costs lakhs of rupees a year. An on-premise server that misses updates is less secure than a well-run cloud service.

---

Published by Zernyx Hub. More: https://zernyxhub.com/llms.txt
