C-DAC and CDAC Routes for AI Partnerships

A Bengaluru founder printed a two-page 'strategic MoU with C-DAC' and asked a cousin in Electronics City to get it signed. The cousin knew someone who knew a scientist. The scientist was polite. The legal cell was not. There was no open call, no work package, no IP clause, and no reason for a scientific society of the Ministry of Electronics and IT to put its mark on a startup's Series A deck. The PDF died in a shared drive named Partnerships.

C-DAC — the Centre for Development of Advanced Computing — is real. It is MeitY's premier R&D organisation for high-performance computing, applied AI and language technology, cyber security, e-governance stacks, health informatics and more. It has multiple centres. It publishes tenders and expressions of interest. It transfers technology. It sits on government programmes as an implementing agency. None of that is a concierge desk for private agent vendors.

This guide is how to approach C-DAC without inventing a corridor. It is written for Indian AI firms that want a defensible public-sector route, and for department officers who are tired of vendors dropping C-DAC's name as if it were an empanelment. It is not an official C-DAC brochure. It is not a promise of a meeting.

If your only plan is a logo, stop. If your plan is a named problem, a named centre, and a path that already exists on cdac.in or eprocure.gov.in, continue.

What C-DAC is — and is not

C-DAC is a scientific society under MeitY. It is not NIC. It is not NICSI. It is not MeitY's empanelment desk. It is not a GeM category. Officers who say 'get C-DAC on the file and we can buy' are mixing an R&D body with a procurement channel. You can still end up on a file with C-DAC. You get there by a contract, a consortium, a sponsored project, or a technology-transfer licence — not by a handshake in the lobby.

Centres matter. Pune has long been associated with high-performance computing and PARAM-class work. Other centres carry language technology, cyber, health, e-governance and training strengths. The public site lists centres and contact paths. Write to the centre whose published work matches your problem. A speech-to-text firm that emails a supercomputing group about 'synergy in AI' is asking to be ignored.

C-DAC also buys. It issues GeM bids and CPPP tenders for goods, works, cloud, and services. It issues EoIs for transfer of technology. Those are the opposite of a partnership fantasy. They are competitive processes in which C-DAC is the buyer or the licensor. Treat them with the same bid hygiene you would bring to a ministry.

Honest doors, and the fake door next to each

Door that exists	Where you will see it	What you owe	Fake door
Published tender / GeM bid where C-DAC is buyer	cdac.in tenders, gem.gov.in, eprocure.gov.in	A complete bid, not a coffee	'Our man will get us empanelled at C-DAC'
EoI / ToT for a C-DAC technology	C-DAC tenders and ToT notices	Licence fees, capability to implement, honest localisation	A slide that says we use PARAM
Consortium on a MeitY or state R&D call	MeitY calls, state IT RFPs, mission tenders	A work-share, IP, and who is lead	A logo page with no work package
Sponsored research / consultancy with a centre	Centre business rules, after a scoped note	Money, a statement of work, publication and IP terms	An unpaid 'knowledge partnership' for LinkedIn
Implementing-agency overlay (C-DAC runs a programme)	MeitY or line-ministry scheme documents	Eligibility as a vendor or grantee under that scheme	Assuming every C-DAC programme is an open vendor list

How to approach a centre without wasting their week

Write a two-page note, not a pitch deck. Page one: the public problem in one Indian institution (a language pair, a document class, a constrained HPC job, an air-gapped evaluation). Page two: what you have already built, where it runs, whether you train on customer data (Prcept does not), and the single ask — a technical meeting, a response to their published EoI, or an invitation to join a consortium they are already forming. Attach a one-page architecture. Do not attach a valuation.

Name the group. C-DAC's public pages and papers will tell you who works on speech, on multilingual models, on cyber forensics, on health. Use their published email format if the site gives one. Copy the centre head only if the group page says to. A spray of 'Dear Sir' to every cdac.in address is a reputation event.

Accept the first no. Scientists are measured on programmes, not on startup courtesy. If they point you at a tender, bid the tender. If they point you at a ToT, read the ToT. If they say the work is internal, believe them. A second mail that says 'just a quick MoU' confirms you were never listening.

1. Map the centre and the published theme before you write.
2. Check tenders and EoIs on cdac.in, GeM and CPPP the same week. You may already be a bidder, not a partner.
3. Send the two-page note from a founder or CTO, not a business-development intern.
4. Offer a scoped technical demo on their terms, including on-prem if they ask.
5. If a formal engagement starts, insist on a contract with work, money, IP and exit — not a 'framework of cooperation' with empty schedules.

Consortiums: the only 'partnership' word that usually survives audit

When a MeitY mission, a state language project, or a national HPC programme needs both a research lab and a productiser, C-DAC may lead or join a consortium. Your value in that room is not 'AI'. It is a deployable runtime, a district operations model, an air-gap media protocol, or a language pair they do not want to productise. Write that noun into the consortium agreement.

Lead, share, and subcontract are different. If C-DAC is lead, you will live inside their procurement and their branding. If you are lead and you name C-DAC without a letter, you will be disqualified or embarrassed. If you are a subcontractor, read the prime's GCC on disclosure and percentage. Do not hide.

IP is the argument you should have early. Background IP stays with whoever brought it. Foreground IP follows the call document. Publication rights matter to scientists. Commercialisation rights matter to you. A sentence that says 'joint IP to be decided later' is how the product dies in year two.

What not to invent on your website

Do not write 'C-DAC empaneled AI partner' unless a published empanelment list contains your legal name and a validity date. C-DAC is not, in ordinary speech, an empanelment marketplace like a state IT vendor list. Using the name as if it were one is a representation risk.

Do not publish a draft MoU template with C-DAC's emblem. You do not have the emblem. A 'standard C-DAC MoU' circulating on WhatsApp is not a government form.

Do not claim that a meeting, a lab tour, or a joint webinar is a technical evaluation. Department buyers who later ask C-DAC 'did you certify this vendor' will get an honest no. That no will land on your bid.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Every serious AI firm has a C-DAC MoU.

Many serious firms have a contract, a ToT, or a consortium schedule. Many more have a PDF that legal never signed. Ask to see the work package. If there is none, there is no partnership.

We need their logo to clear a state empanelment.

State RFEs score OEM authorisations, ISO, turnover, and work orders. They rarely score a decorative MoU. If the RFE actually awards marks for a C-DAC collaboration, it will define acceptable evidence. Meet that definition.

Scientists will not talk to startups.

Scientists will not talk to spray. They will talk to a note that cites their paper and asks a narrow question. Be that note.

If we name C-DAC as a reference without asking, it is only business development.

It is a misrepresentation. Stop.

A 30-day C-DAC approach you can defend

Run this once per problem, not as a standing 'government relations' motion.

1. Week 1: read cdac.in — centres, themes, current tenders and ToT notices. Search GeM and CPPP for C-DAC as buyer. List the three live doors. Kill the MoU draft.
2. Week 2: pick one centre and one problem. Write the two-page note. Have technical and legal read it. Send it once.
3. Week 3: if a tender or EoI is open, bid it. If a meeting is offered, take a CTO and a one-page architecture, not a sales crew.
4. Week 4: if a consortium or consultancy is real, negotiate work, money, IP, publication, branding and exit. If nothing is real, write a one-line close and leave the centre alone.

How this shows up in the file

Internal file note for your own board: we will not claim C-DAC affiliation except where a signed instrument exists. External covering letter, if an instrument exists: name the instrument, the centre, the work package, and the end date. If an instrument does not exist, do not mention C-DAC except as a public body whose tenders you watch.

Department officers should ask one question of any vendor who says 'we work with C-DAC': show the contract or the published award. No document, no mark.

This article is informational field guidance for Indian public institutions and their vendors, not legal, tax, procurement or engineering advice. Confirm the live circular, RFE, GCC, GeM term, state G.O. and your counsel before you file anything. Incentives, ceilings and portal screens change.