Cloud Services Procurement

Cloud services procurement in government refers to the acquisition of infrastructure, platform, and software-as-a-service (IaaS, PaaS, SaaS) by central ministries, PSUs, and state departments through MeitY-empanelled cloud service providers operating under the GI Cloud (MeghRaj) policy framework.

What is Cloud Services Procurement?

The central government's GI Cloud initiative, branded as MeghRaj, established a framework for procuring cloud services from empanelled providers. MeitY maintains an empanelled list of cloud service providers (CSPs) categorised by service tier and data sensitivity classification. Government bodies must procure cloud from this empanelled list rather than directly from unempanelled vendors.

Cloud procurement routes include:

• Direct procurement from MeghRaj (Government Cloud) for NIC-operated cloud
• Procurement from MeitY-empanelled private CSPs (AWS, Azure, GCP India regions, and domestic providers like NIC Cloud, BSNL Cloud) via open NIT or rate contract
• SaaS procurement through GeM for listed cloud applications
• Multi-year managed cloud contracts through System Integrator Contract where SI takes cloud responsibility

Data classification drives cloud choice: sensitive and restricted data must use government-owned or government-approved private cloud in India. Public-facing, non-sensitive applications may use commercial cloud from empanelled providers.

Evaluation for cloud tenders typically considers cost per compute unit (vCPU-hour, GB-month), SLA guarantees, security certifications (ISO 27001, SOC 2), and CERT-In compliance. Large multi-year cloud contracts use QCBS where security posture and performance track record factor alongside price.

Why Cloud Services Procurement matters for Indian government suppliers

Government cloud procurement is growing at 30-40% annually as departments modernise legacy applications. The MeitY empanelment acts as a quality gate, only empanelled providers can bid, creating a protected market for compliant vendors. Domestic cloud providers benefit from data residency mandates that restrict foreign-hosted government data.

Example

A central ministry issues an NIT on CPPP for managed cloud hosting of its citizen grievance portal, requiring IaaS on an empanelled CSP, guaranteed 99.9% uptime, ISO 27001 certification, and CERT-In compliance audit. The contract is for three years at estimated Rs 4 crore. The L1 empanelled provider at Rs 3.6 crore wins and provisions virtual machines within the Indian data region.

Frequently Asked Questions

Which cloud providers are empanelled by MeitY?

MeitY's empanelled CSP list includes NIC Cloud (government-owned), BSNL Cloud, and private providers including AWS India, Microsoft Azure (India regions), Google Cloud (India regions), and several domestic providers. The list is updated periodically and published on MeitY's website.

Can a non-empanelled cloud provider bid for government cloud tenders?

No. MeitY's GI Cloud policy requires all government cloud procurement to use empanelled CSPs. Non-empanelled providers must apply for MeitY empanelment before bidding on government cloud tenders.

What data residency requirements apply to government cloud?

All government data classified as "Restricted" or above must reside on servers physically located in India. Even for "Open" data, most government cloud tenders specify India-region hosting. This effectively bars offshore-only cloud providers from most government cloud contracts.

How is cloud pricing structured in government tenders?

Cloud tenders typically use a rate contract model with pricing per unit (vCPU-hour, GB storage/month, bandwidth GB). Buyers draw down against the rate contract as needed. Total estimated consumption over the contract period is stated in the NIT for bid comparison purposes.