On your premises, with the supplier mechanics a tender asks for.
A government department or public sector undertaking may need its identity and access systems inside its own buildings, bought through a tender. Pramaan runs on your servers, and Frontier Labs states its supplier status the way the procurement order asks. Sector rules are yours to map; here is the evidence the product produces.
The statutes this page names
The Digital Personal Data Protection Rules were published in the Gazette of India on 13 November 2025, and their phased compliance period ends on 13 May 2027. The Act's highest penalty, up to ₹250 crore, is for a Data Fiduciary's failure to maintain reasonable security safeguards. CERT-In's Directions No. 20(3)/2022 require all service providers, intermediaries, data centres, body corporate and Government organisations to keep the logs of all their ICT systems. The period is a rolling 180 days, within Indian jurisdiction. The sources, and which Pramaan evidence fits each safeguard.
Class-I local supplier: the tender mechanics
Frontier Labs is a Class-I local supplier (asserted per tender) under the Public Procurement (Preference to Make in India) Order, which draws the Class-I line at local content equal to or more than 50%. That is a status of the supplier, not a feature of the product, and not a certificate.
- At each tender the bidder states the percentage of local content and where the local value is added, and certifies both itself.
- For a procurement above ₹10 crore, self-certification is not enough: a certificate from the company's statutory auditor or cost auditor is required.
Access problems, and what Pramaan offers
| Access problem | What Pramaan offers | From tier |
|---|---|---|
| Identity has to run inside your own buildings, without calling out to the vendor. | On your servers, the broker has no licence-check server, no telemetry beacon and no phone-home. Our register lists six optional outbound connections, each with its own switch, on the sovereignty page. | Every tier |
| Some networks have no route to the internet at all. | Air-gapped install: identity plane only, rig-proven; offline app enrolment and the copilot model are not proven, and no update procedure exists today. | Pramaan Sovereign+ |
| Departments and field offices reuse the same private address ranges. | Multi-site routing: an app routed by its Site is reached only through a connector in that Site, so the same private address range in another Site never collides with it. | Pramaan Sovereign |
| A system integrator maintains an application for the length of a contract. | Publish the application through a connector: it dials out to the broker and opens no inbound port. A private application is denied unless an access rule allows it, so admit the integrator's group on this application and no other. | Pramaan Zero Trust |
| Administrators need SSH to servers without long-lived keys on their laptops. | Pramaan's own browser SSH terminal signs in with just-in-time SSH certificates, each valid for 60 seconds. | Pramaan Sovereign |
What the product produces as evidence
- Audit log. When the web edge refuses a request, because of the person's groups or your access rules, the refusal is written as an audit event. The broker keeps its audit events in its PostgreSQL database, on servers you run.
- Receipts. When an AI agent acts through the broker, the broker can hand back a signed action receipt, which an auditor can verify offline against the public key.
- Transparency log. Each audit event is added to a transparency log, whose signed summary you can check without asking us.
Not claimed
- Compliance with a department's or ministry's security rules. Mapping them to your controls stays with you.
- A certificate of local content. The Class-I status is asserted per tender.
- More of an air-gapped install than the identity plane. Offline app enrolment and the copilot model are not proven, and no update procedure exists today.
- Customers or references. This page names none.
- A certification or a third-party audit. Pramaan was internally audited on 13 June 2026; no third-party penetration test yet.
For your engineers
Technical detail: the evidence chain
On direct connections, the raw-TCP listener writes an audit event when its access checks refuse a connection after the person's token has been read. The transparency log follows RFC 6962; each audit event is a leaf. Run the broker with PostgreSQL: without DATABASE_URL, the broker keeps all its state in memory and loses it on restart.
Questions
Is Frontier Labs a Class-I local supplier?
Yes: a Class-I local supplier (asserted per tender) under the Public Procurement (Preference to Make in India) Order. It is a status of the supplier, not a certificate, and it holds for every tier.
What changes for a large procurement?
For a procurement above ₹10 crore, self-certification is not enough: a certificate from the company's statutory auditor or cost auditor is required.
Can Pramaan run with no internet connection?
The identity plane can. The scope is: identity plane only, rig-proven; offline app enrolment and the copilot model are not proven, and no update procedure exists today.
Does Pramaan keep our logs for CERT-In?
No. The broker keeps its own audit events in its PostgreSQL database, on your servers. Keeping the logs of all your ICT systems for 180 days stays with you.
Talk to us, or try it first
-
Book a walkthrough
Against your own apps, not slides.
-
Run the lab
It uses a demonstration account; none of your data is involved.
-
See pricing
Published floors, named-user bands and what every tier includes.