Meghdoot is here. The service layer isn't.
We propose to build it. Eighty-four named services across the four domains the Expression of Interest specifies, all of them billing in rupees through the Unified Payments Interface, speaking in the twenty-two scheduled Indian languages through Bhashini, and signing their compliance evidence under the Controller of Certifying Authorities. The existing BOSS Linux, OpenStack, Ceph, KVM and Kubernetes substrate stays exactly as it is today.
Where the foreign clouds run out of road
Twelve places where Amazon, Microsoft, Google, Snowflake and Databricks leave Indian banks, hospitals, state governments and small businesses under-served. The architecture in the slides that follow closes forty-seven such gaps without inventing a single new one.
A note on the synthesis
We started with four hundred and twenty-eight unique selling propositions, harvested from twenty-four independent deep-research reports across the four domains. After de-duplication and clustering, the catalogue contains eighty-four canonical services. Every single one of them traces back to at least one source idea, and the audit on a later slide proves it.
Where the new work fits
Four new layers stack on top of the Meghdoot foundation. The BOSS Linux host, the OpenStack control plane, the Ceph storage layer, the KVM hypervisor and the Kubernetes orchestration all stay exactly as they are operating today at C-DAC. Click any layer below to see what it contains.
The four domains your EOI calls out
Compute, Artificial Intelligence, Data and Analytics, and Migration. Each domain is led by a named senior researcher with the PhD-plus-three-years background the EOI asks for. Crucially, all four domains share the same nine integration buses for consent, identity, billing, language and the rest. That shared bus layer is what makes this one architecture rather than four products glued together at the edges.
What the Compute domain ships
Serverless functions that restart in twenty-five milliseconds. WebAssembly running at gram-panchayat exchanges. Memory pooled across servers using Compute Express Link. An auto-scaler trained on the actual Indian Premier League finals, election counting days and Diwali sale spikes. Confidential virtual machines whose attestation chain ends at the Controller of Certifying Authorities, not at a foreign vendor's root.
Twenty-two AI services for India
A language model gateway that bills in rupees and serves Sarvam, Krutrim, BharatGPT, Param and Hanooman as first-class endpoints. Speech recognition, text-to-speech, translation and Aadhaar-and-PAN form reading across all twenty-two scheduled languages. A traffic-violation vision pipeline aligned with the AIS-140 standard. Crop disease diagnosis built in collaboration with state agricultural universities. Federated learning that lets AIIMS, Apollo and other hospital networks train a shared model without exporting a single patient record.
Seventeen services for storing and querying data
A sovereign data lake on Indian soil, where every Apache Iceberg table is partitioned by a residency key derived from the Data Protection Act. Real-time streaming through Apache Flink. Vector search for AI applications. Business intelligence that takes a question in Hindi or Tamil and returns a chart. Receipt-grade lineage signed under the same sovereign certificate chain as the rest of the platform. And a confidential clean room where two banks can compute joint fraud statistics without either bank ever exposing a single customer record.
Thirteen services for the migration question
A six-hour cutover orchestrator that satisfies the Reserve Bank's Master Direction on IT Outsourcing 2023. A COBOL-to-Java transpiler that uses the Z3 theorem prover to issue a mathematical equivalence certificate for every translated subroutine, the kind of evidence a Reserve Bank inspector will accept. Modernisation paths for SAP ECC to S/4HANA, Oracle Forms to React-and-Quarkus, the state Bhulekh land-records systems, the desktop accounting world of Tally and Busy and Marg, and the VMware estates that public-sector units will need to evacuate before vendor support ends.
The nine integration buses
Every service in the catalogue speaks to every other service through these nine buses, never directly. The bus list, in plain English: consent receipts under the Data Protection Act, certificates signed at the Controller of Certifying Authorities, per-second rupee billing through the National Payments Corporation, twenty-two-language translation via Bhashini, the Open Network for Digital Commerce protocol, Aadhaar and DigiLocker identity, Goods-and-Services Tax filings, the federated edge mesh across BharatNet and RailTel, and telemetry flowing into the C-DAC security operations centre.
The five user-facing surfaces
A tenant dashboard derived from OpenStack Skyline and internationalised into all twenty-two scheduled languages. A developer marketplace built on Backstage with a gallery of Heat templates and software development kits. A finance console with sub-paisa rupee precision and full Goods-and-Services Tax invoice generation. An attestation visualiser that surfaces the confidential-hardware chain in a form a Reserve Bank inspector can verify. A read-only regulator portal scoped per agency. Below these five, every request requires a Keystone identity token. There is no other way in.
Twenty-one cross-domain connections
Each row below is a directed flow of data or events between two named services, carried by a specific Meghdoot mechanism, with a measurable outcome that proves the connection is real rather than aspirational. Hover any row and the matching edge will light up in the diagram on the left.
The Indian Digital Public Infrastructure we wire into
Ten sovereign rails that the platform integrates with directly: the Unified Payments Interface for billing, the Open Network for Digital Commerce for retail events, Bhashini for languages, the Goods-and-Services Tax Network for filings, the Account Aggregator framework for financial-data consent, DigiLocker for documents, Aadhaar for identity, the Ayushman Bharat Digital Mission for health records, BharatNet and RailTel for edge presence, and the Controller of Certifying Authorities for digital certificates. None of these is a commercial API a foreign cloud can simply purchase. Most require sovereign accreditation that takes years.
Side-by-side with the global hyperscalers
A like-for-like comparison on the capabilities Indian regulators actually demand of cloud providers. A Native mark means the capability is scheduled, billed, signed and audited at the substrate level. A Partial mark means it is commercially available but as an add-on the customer is expected to integrate themselves.
Sixty-two compliance clauses across fifteen regulators
Every clause maps to the service that satisfies it and the mechanism that enforces it. The evidence artefact for each clause is signed under the same sovereign certificate chain that secures the rest of the platform, so an inspector can verify it without having to trust the vendor.
Where each of the four hundred and twenty-eight ideas ended up
Every one of the raw ideas was assigned to exactly one of four outcomes. Only 1.4 percent were retired, well below the 5 percent ceiling we set ourselves at the start of the synthesis. The Sankey diagram below traces the full flow and the table on the right gives the counts.
428 ideas, traced to 84 services
Sixty months of delivery
The horizon matches the three-plus-two-year empanelment window the EOI specifies. Phase one ships thirty-one services covering the whole of Compute, the Integration Layer and the User Experience Layer. The Artificial Intelligence catalogue follows in Phase two, Data and Analytics in Phase three, Migration in Phase four. Phase five is the national rollout with edge expansion, MeitY empanelment and STQC certification. The month boundaries shown are indicative; they become firm at the Letter of Engagement stage, once team capacity and C-DAC priorities are agreed in writing.
The five-step co-development model
We follow the engagement model C-DAC Chennai specifies in the Expression of Interest. Five sequential gates, each with named deliverables and explicit ownership across the academic consortium, the C-DAC counterpart team, and the named industry partners. The responsibility matrix below shows who owns what at the co-development stage.
People, hardware and the budget envelope
An indicative five-year envelope, subject to detailed sizing in the Statement of Work. The one hundred and eighty-six headcount is split across the academic consortium, the C-DAC counterpart team and the named industry partners. Hardware grows from a three-rack proof-of-concept laboratory at month three to a national-scale fleet by month sixty.
Why foreign clouds cannot copy us in eighteen months
The advantages below stack on top of each other. A Payment Aggregator licence from the Reserve Bank takes well over a year. Becoming a Goods-and-Services Tax application service provider takes months. The Aadhaar e-KYC sub-licence from UIDAI is a multi-year process. Add the Bhashini National Language Translation Mission memorandum, the federated-learning accreditation under the Ayushman Bharat Digital Mission, the integration with C-DAC's own Made-in-India BOSS Linux, and the access to anonymised public-sector-bank COBOL corpora that foreign vendors legally cannot hold. No single advantage rests on the slogan "we are Indian" alone.
Invite us to the technical presentation
This pitch and the accompanying written proposal lay out eighty-four services, twenty-one cross-domain connections, sixty-two compliance clauses and a five-year delivery plan. The next step the EOI specifies is a technical presentation in person. We are ready to come to C-DAC Chennai, walk the evaluation panel through the architecture in detail, field questions on any service in the catalogue, and discuss which workstreams the consortium and the C-DAC counterpart team should prioritise for the Letter of Engagement.