Custom
Published entry path
Shown only where the public pricing source supports it.
For public-service pilots and procurement review
Consent-first verification architecture for public-service pilots
PRAMAAN is designed for public-service verification pilots where consent, auditability, data minimization, and clear fiduciary boundaries matter.
R9 waitlistPurpose and consentAudit trail by scopePublic-service workflowResidency by agreementNo live government approval claim
Sample preview — no real PII
Public-service pilot architecture card
Pilot status
R9 waitlist
Future public-sector engagementCitizen notice
Purpose: contractor onboarding
Shown before consentData boundary
Region pinning
Target / agreement dependentGrievance path
/legal/grievance
Visible routeNo government approval, UIDAI endorsement, police database, or live deployment is implied.
R9 waitlist
Rollout stage
Pilot, waitlist, and target capabilities stay labelled.
Consent
Processing posture
Public-sector features remain pilot, target, or by agreement unless shipped.
Audience stakes
Public-service verification needs transparency, consent proof, role boundaries, grievance routes, and careful deployment claims.
The redesign makes every page explain the buyer's operational world before asking for a conversion.
Public workflows need accountability
Municipal services, worker registration, contractor onboarding, and access checks need traceable purpose and consent.
Sovereignty language must be contractual
Region pinning, escrow, source review, on-prem, and sub-processors require agreement and implementation review.
Citizens need routes to challenge or correct
Grievance, DSR, and support routes must be obvious, not hidden behind an operator dashboard.
Specialized module
Public-sector pilot matrix
A careful public-sector pilot page for consent, auditability, data minimization, and grievance-ready verification workflows.
Municipal service pilots
Worker registration pilots
Contractor onboarding pilots
Public-service access checks
Who this is for
Role-based trust, not one generic buyer.
Each stakeholder gets the decision surface they need while the person being verified keeps consent and rights visible.
State or municipal officer
Service access workflows and auditability
PRAMAAN view: Pilot architecture, consent trail, and aggregate status.
Public procurement
Eligibility, commercial scope, and agreement terms
PRAMAAN view: Readiness matrix and contract-scoped capabilities.
IT department
Hosting, security, sub-processors, integration boundaries
PRAMAAN view: Architecture review material and target-state notes.
Citizen or worker
Purpose, consent, visibility, and grievance
PRAMAAN view: Notice, consent, limited result, DSR and grievance path.
Workflow
Request, consent, signal, review, and audit stay connected.
The person being verified sees the purpose before checks run; the operator receives a decision-support signal and escalation path.
- Request1
Public body defines the purpose
The pilot specifies service context, requester role, and data minimization rule.
- Notice2
Citizen or worker sees the notice
The person sees who is asking, why, and what routes exist for support or grievance.
- Consent3
Consent is captured before checks
No secret verification; refusal routes to the applicable manual public-service process.
- Audit4
Signal and audit trail are retained by scope
Operators receive permitted signals; audit logs support accountable review.
Capabilities
Built around the segment's daily operating model.
Capabilities are useful only when the live/planned/target boundary is visible.
Public-sector suitability
Designed for municipal services, worker registration, contractor onboarding, and service access pilots.
Readiness matrix
Every capability is labelled live, planned, target, or requires agreement.
Public accountability
Minimization, role-based access, audit logs, support, DSR, and grievance route stay visible.
Sovereignty review
Region pinning, escrow, source review, on-prem, and sub-processors are agreement-dependent and not claimed as live by default.
Citizen consent trail
Request, notice, consent, signal, audit trail, and grievance route are designed as one chain.
Not a surveillance layer
PRAMAAN is not positioned as a police database, UIDAI endorsement, or passive monitoring system.
Consent and DPDP
Citizen consent workflow
The public-service model is request, notice, consent, verification signal, audit trail, and grievance/DSR route.
No live government approval claim
No UIDAI endorsement claim
Consent and purpose before processing
Manual fallback may be required when consent is refused
Sample preview
Public-service pilot architecture card
Every preview uses dummy, masked data and is labelled so it cannot be confused with a real report.
Sample preview — no real PII
Public-service pilot architecture card
Pilot status
R9 waitlist
Future public-sector engagementCitizen notice
Purpose: contractor onboarding
Shown before consentData boundary
Region pinning
Target / agreement dependentGrievance path
/legal/grievance
Visible routeNo government approval, UIDAI endorsement, police database, or live deployment is implied.
Use cases
Specific workflows a buyer can recognize.
Municipal service access pilot
Verify eligibility or role signals with consent and a grievance route.
A reviewable decision-support trail.
Public contractor onboarding
Contractor workers complete purpose-specific verification before work assignment.
Cleaner contractor audit pack.
Worker registration pilot
Worker-owned profile supports status review without exposing raw PII by default.
Portable trust with public accountability.
Responsible use
What this is not
PRAMAAN is not claiming government endorsement, UIDAI endorsement, live public deployment, surveillance authority, or replacement of statutory police processes.
No UIDAI endorsement is claimed
Not a police database
Not a surveillance layer
Not a live public-sector approval claim
Not a substitute for statutory verification unless an authority accepts it
Public-sector rollout
Custom review
Pricing, procurement, citizen-cost treatment, residency, support, integrations, exports, continuity, and deployment terms require public-sector agreement and implementation review.
- No fixed public annual range
- No citizen-cost claim unless terms support it
- Sovereign, state-region, escrow, and on-prem features require agreement and implementation review
Public-sector waitlist
R9 waitlist
PRAMAAN does not claim live government approval. State, district, and municipal workflows require authority, procurement, privacy, security, residency, support, and implementation review before any rollout is claimed.
Integration and operations
Government readiness matrix
Capabilities are deliberately labelled to avoid converting roadmap into production claims.
Hosted pilot workflow
Planned
State-region deployment
Target
Source review / escrow
By agreement
On-prem
Target
Public-sector integration
By agreement
Proof and pilot clarity
Pilot posture
Public-sector content remains pilot/waitlist. Names, agencies, deployments, integrations, or outcomes are not published without approved source-of-truth.
FAQ
Government verification FAQ
Short, specific answers with consent, visibility, pricing, rollout, and limitation boundaries.
Related journeys
Move to the nearest workflow without losing context.
Explore a public-service verification pilot
Discuss a pilot only with clear status labels, governance, grievance routes, and procurement review.