How to List an On-Prem Platform on GeM

GovTech founders treat GeM listing as a marketing milestone: a URL to paste in a deck. Buyers treat the listing as a contract-shaped promise: what will be delivered, in what mode, with what SLA, against which specification template. If you list a hosted login because that template was easier, you will win the wrong carts and lose the files you actually want.

This is a practical sequence for listing an on-prem, isolatable agent platform. GeM's seller console, category templates and document checks change. Read the live seller FAQs and console help on gem.gov.in the week you do this. Where this article says typically, confirm. Do not invent fee numbers from a blog. If you are not yet a seller, the companion troubleshooting piece on registration rejections is the prior chapter. Do not start a catalogue while your GST and cancelled cheque still disagree.

Pick the object you can fulfil from a government rack

Write a one-page fulfilment note before you touch the console. What does the buyer receive on day one — media, a key, a jump-host install, a version pin? What do they receive for three years — patches on media, a named Indian support desk, an isolation drill? If you cannot fulfil a line without a standing tunnel to your cloud, do not put that line in the listing.

Decide whether you are listing a software licence (goods-shaped), a subscription to support and updates (service-shaped), an implementation SKU, or more than one. Multiple listings are allowed and often cleaner than one SKU that lies about all three. If you also sell a hosted tier, give it a different listing and a different title. Do not make the buyer decode standard versus sovereign in a footnote. Public buyers will buy the cheaper title and ask for the isolation later.

The listing is a promise to a store officer, not a landing page.

Listing ingredient	On-prem posture	How founders accidentally SaaS-ify it
Title	On-premises / air-gappable agent platform, versioned	AI chatbot that matches a hosted template
Specification parameters	Deployment mode, licence type, isolation, language	Leaving deployment as cloud because it was the default
Offered service / SLA	Response clocks that work via ticket and media	99.9% SaaS uptime copied from a US page
Photo / brochure	A rack and a media docket, not a neon city	A stock cloud illustration
Price basis	Licence bands, environments, support years — stated	Per-seat/month that assumes your tenant
OEM / brand auth	You are the OEM, or you have the letter	Listing a model runtime you do not have rights to resell

Category and specification without self-harm

Search as a buyer would. Open the specification template. If mandatory parameters force hosting location: vendor cloud and you cannot change them, you are in the wrong category or you need a service listing / waiting for a better template. Do not tick a false hosting location to pass validation. That tick will be read against you in a dispute. Where optional parameters let you declare on-prem, no-outbound capable, Indian support, and customer content not used for training other tenants, declare them. Keep brand and model names consistent with your incorporation papers and your OEM letters.

Documents and claims you should not invent

DPIIT recognition, Udyam, STQC, ISO, SOC — attach what you have, current, in the name of the legal entity that is the seller. Do not attach a founder's personal certificate. Do not attach an expired DPIIT letter and hope. Relaxations for EMD or prior experience are often available if claimed with current documents; they are not automatic and they are not a substitute for a true specification.

Do not claim Make in India local-content percentages you have not calculated under the current DPIIT order. A later buyer will ask for the calculation. Software local content is not we have an office in Bengaluru. Do not paste a price you cannot honour for a government invoice cycle. GeM disputes are public in the way that matters: the buyer's file.

1. Finish seller KYC so names match GST, PAN, bank and certificates.
2. Write the fulfilment note (media, version, support without a tunnel).
3. Choose family (goods licence vs service vs split listings).
4. Fill only true specification parameters; abandon a template that forces a lie.
5. Attach current entity documents; claim startup/MSE only with live letters.
6. Mystery-shop your own listing as a buyer and fix the title.

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.

We will list SaaS now and explain on-prem in the ATC later.

Many buys will never reach an ATC. They will direct-purchase the title. List the object you want to be bought.

Our category does not have an isolation parameter.

Use the description fields you are allowed, publish a public data sheet that matches, and be ready for custom bids. Do not invent a Yes on a hosting parameter that is actually Cloud.

Consultants say pay for a listing agency.

Agencies can type. They cannot fulfil. If you use one, you still own every tick. Read the preview yourself.

A listing fortnight after KYC is green

1. Days 1–2: fulfilment note and split of SKUs.
2. Days 3–5: category hunt and honest parameter pass.
3. Days 6–8: documents in the seller entity's name.
4. Days 9–11: prices, SLA clocks, support story.
5. Days 12–14: buyer-side preview, fix title, ask one friendly procurement officer to try to misunderstand you.

How this shows up in the file

Keep a seller-side file: fulfilment note, screenshots of parameters, letters, and the date of each change. When a buyer disputes what standard support meant, you will want your own history. Update the listing when the product's isolation story changes. A stale Yes is a false statement.

Fulfilment note headings you can steal

Write: artefact delivered (version, media format, hash method); environments included; what go-live means (drill signed or URL live — pick one); how patches arrive; how a ticket is filed when the WAN is down; what the buyer must provide (VLAN, identity, time, DNS); what you will never require (standing tunnel, customer content for shared training). This note is internal first. Then it becomes the listing's truth serum.

Pricing that a store officer can compare

Publish bands: one production environment, optional extra sites, optional extra year of media support. Avoid contact us as the only price if the category requires a number. Avoid a per-token cloud price on an on-prem SKU. The officer will compare you to a hosted listing and the cheaper fiction will win.

When to wait and not list

Do not list if isolation is on the roadmap and not in the build. Do not list if KYC is red. Do not list if you cannot staff a media patch for twelve months. An empty quarter of listing work is better than a live SKU that teaches the market you over-claim. Buyers talk to each other in the same three WhatsApp groups. If a buyer needs you in a custom bid before the listing is live, you can still bid as a registered seller without a perfect catalogue card — confirm live. Do not invent a listing overnight by ticking cloud.

This article is informational field guidance, not legal or procurement advice. Confirm against the current Gazette, GFR, live GeM terms on gem.gov.in, DPIIT orders and your counsel before you file it.

How a buyer or seller should act on this

Treat “How to List an On-Prem Platform on GeM” as an operating problem, not a thought piece. A P5 GovTech Founder who searches “list software on GeM” is usually one bid, one CRAC, or one rejection away from a cash event. The file that wins is the one with dates, document names and a named officer — not a paragraph that restates GeM’s homepage.

GeM will let you list the wrong object quickly. An on-prem platform listing is a specification, a fulfilment promise and a support story that still works when the WAN is dead. That is why this guide ends in artefacts: screenshots of the live portal term, the clause you invoked, and the date you last checked it. GeM, GFR notes and state portals move. A citation without a date is folklore.

Confirm the live GeM FAQ, the current revenue policy and the bid text before you copy any number from a blog — including this one. If the portal and this article disagree, the portal wins. Put the printout in the file.

• Write the purpose of the buy in one sentence a DDO will sign.
• Name the route: catalogue, custom bid, bid, RA, CPPP, or state portal.
• Attach the exemption or preference documents you will actually upload (Udyam, DPIIT, MII, OEM).
• Record who can accept the consignee receipt and who raises the bill.
• Do not invent a category, a PAC, or a price-reasonableness story after L1 is public.

Close this loop before the next CAB

Put “How to List an On-Prem Platform on GeM” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P5 GovTech Founder, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “list software on GeM” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.