Skip to main content

Flagship platform

Uchal Suraksha Portal

Real-Time Interstate Advance Protection Platform

Real-time contractor identity verification and advance allocation locking. One lookup tells a mill whether the contractor in front of them is already committed elsewhere — across state lines, without either mill exposing its records.

Interstate Sugar Industry Security Grid

Core architecture

Four things the platform does that nothing else does

The architecture exists to resolve one contradiction: mills are commercial competitors who nevertheless need to share a fraud signal.

Cross-Border Intelligence Grid

Real-time data synchronisation between Maharashtra and Karnataka sugar mills, so a duplicate contract raised across the state border is caught the moment the second mill queries it — not at the end of the season.

Zero-Data Storage Model

Cryptographic validation using SHA-256. A contractor's identity is matched on an irreversible hash, so factory financial data is never exposed to, nor permanently stored on, external servers.

4-Signal Risk Indicator

A simplified, CIBIL-style colour-coded assessment matrix — Safe, Verify, Alert and High Risk — computed automatically and read at a glance before any payout is validated.

Field Identity Mapping

Quick mobile and tablet verification for field officers and gate clerks, designed for one-handed use on a low-bandwidth connection in the middle of a cane field.

How it works

The 3-step security framework

From a mill's point of view the entire interaction is one lookup and one decision.

  1. Step 1

    Onboarding & identity check

    Contractor details are queried against the centralised network. The 12-digit Aadhaar is converted to a SHA-256 hash on the way in, and only that hash travels or is stored.

  2. Step 2

    Real-time audit

    The system instantly checks whether the contractor has an active contract or a locked advance at another participating mill, in either state, and folds their recorded history into the result.

  3. Step 3

    Informed payout

    Mill management receives a clear risk score and makes a secure advance disbursement decision. If the signal escalates, the money stays in the account.

4-signal risk indicator

A CIBIL-style score, for harvesting contracts

Every contractor carries a live, colour-coded trust signal, computed automatically from their active engagements and history. A mill manager sees it before authorising a single rupee.

SAFE

Safe

Meaning
Available · clean record
Trigger
0 active contracts, clean history
active = 0
VERIFY

Verify

Meaning
Single engagement — legitimate, worth confirming
Trigger
Exactly 1 active contract
active = 1
ALERT

Alert

Meaning
Multiple engagement — double-advance risk
Trigger
2 or more active contracts in the same season
active ≥ 2
HIGH RISK

High Risk

Meaning
Defaulted, blacklisted or flagged
Trigger
Any past defaulted record, or rating below 3.0
defaulted OR rating < 3.0

Signals are computed by the platform from active season contracts and recorded history. They update the moment another mill locks an advance, in either state.

Capabilities

What the platform actually does

Ten modules covering identity, contracts, labour, transport, reporting and oversight.

  1. Cryptographic Aadhaar Hasher

    SHA-256

    Converts a plain 12-digit Aadhaar into an anonymous 64-character SHA-256 token for privacy-safe identity matching. The raw number is never persisted.

  2. Contractor Registry & Signal Search

    Search by Aadhaar, hash, mobile or name and get the contractor's live 4-signal status, active agreements, associated cutters and full season history.

  3. Advance-Lock (Contract) Management

    When a mill pays an advance it “locks” the contractor, creating an active season contract. Locks across multiple mills automatically escalate the contractor to Alert.

  4. Labour Hub — cutter fleet & allocation

    Register cutters under a contractor or standalone, allocate and redistribute them across contractors and mills, and track advance amount, work status and assigned vehicle for each.

  5. Duplicate-Cutter Fraud Block

    Hard block

    A labourer's Aadhaar hash is unique across the network. The system hard-blocks any attempt to register the same cutter under a second contractor, in real time.

  6. RTO Vehicle & Fitness Verification

    Register and verify transport — tractor trolleys, 10-wheel trucks, harvesters, bullock carts — tracking RTO fitness validity, insurance state, carrying capacity and owner.

  7. Reports & Excel Generator

    Downloadable sheets for the contractors registry, cutter labour force, verified transport fleet and flagged multi-advance defaulters, plus a live searchable grid.

  8. Support & Dispute Resolution Desk

    Contractors file appeals against wrongful flags; mills and the Super Admin review evidence and resolve, clearing wrongful blocks. Priority, category and status tracked throughout.

  9. Activity & Identity Audit Logs

    Append-only

    An append-only security trail. Every authentication, duplicate block, status lock, onboarding request, RTO verification and password event is logged with timestamp and co-operative.

  10. AI Copilot & Role-Aware Analytics

    Gemini

    A server-side advisor answers fraud-prevention questions in conversational Marathi or English, framed with live statistics — alongside dashboards scoped to each role's permissions.

Zero-data storage

Your records never leave your factory.

The privacy architecture is not a feature bolted on afterwards — it is the reason competing mills can share risk signals at all.

Only the hash is stored, and a hash cannot be reversed.

The 12-digit Aadhaar number is converted into an irreversible 64-character SHA-256 hash. Only that hash is stored and searched. Mills detect the same person across the network without ever exposing or sharing the raw number.

Hash-based matching

Identity is matched on the hash alone, so cross-mill detection never requires anyone to transmit a raw Aadhaar number.

Duplicate-cutter blocking

Because a labourer's Aadhaar hash is unique, the system hard-blocks registering the same cutter under a second contractor.

Mill isolation (multi-tenant)

One mill cannot bulk-download or browse another mill's contractor directory. Cross-mill status is available only through a single, direct hashed-Aadhaar or mobile lookup.

bcrypt password security

Factory logins are hashed with bcrypt, and any legacy plaintext password is transparently upgraded on first login.

Server-side secrets

Government API keys for Aadhaar, RTO and SMS live in server environment variables and are never exposed to the browser.

Fair to honest contractors

A flagged contractor can file an appeal through the support desk, and mills or the Super Admin can clear a wrongful block.

Who it's for

Three roles, three very different views

Each role sees exactly what it is permitted to see — and nothing more.

Super Admin

Central regulator
  • Approve or reject new sugar-mill registrations
  • Audit the whole contractor registry and hash-ledger statistics live
  • Override wrongful blacklists and resolve high-priority disputes
  • Edit or delete contractor records and reset factory passwords
  • View full analytics across every mill

Sugar Factory / Mill

Co-operative member — the paying customer
  • Self-register pending Super Admin approval, with a mandatory first-login password change
  • Search any contractor by Aadhaar, hash or mobile and see their live signal
  • Lock a contractor as “Advance Paid”, creating an active season contract
  • Record season performance — cleared or defaulted — plus a rating
  • Register and verify transport vehicles and allocate cutters
  • See only their own engaged contractors — privacy-isolated

Contractor / Mukadam

The labour-gang leader
  • Self-onboard via Aadhaar OTP or mobile verification
  • Manage their own roster of cutters — add, edit and remove labourers
  • See their own live signal, identity status, assigned vehicles and history
  • File support tickets and appeals against wrongful flags

Season lifecycle

14 months of coverage, not 14 days of onboarding

A crushing season is not a software launch window. Support is scoped to the agricultural calendar, from first registration to the final audit.

  1. Pre-season

    Contractor registration

    Onboarding and identity verification of contractors and their cutter gangs before advances are negotiated, plus staff training at the factory and vehicle fitness checks on the transport fleet.

  2. Mid-season

    Field tracking

    Live signal monitoring as advances are locked across the network, cutter allocation and redistribution between contractors, and on-call technical assistance through the crushing peak.

  3. Post-season

    Final settlement

    Performance recording — cleared or defaulted — reconciliation of outstanding advances, and the closing audit run against the 31st March cut-off.

Dedicated account managers are assigned for the full 14-month cycle, not reassigned between seasons.

Integrations

Production roadmap

The current prototype simulates each of these gateways. Production plugs into the official ones.

These are planned integrations, not live partnerships. No accreditation or commercial agreement with any gateway is claimed.

  1. Aadhaar e-KYC (UIDAI)

    OTP generation for contractor self-onboarding, via an accredited AUA/KUA or Sub-AUA.

    UIDAI accredited AUA / KUA / Sub-AUA

    Simulated in prototype
  2. Mobile OTP SMS gateway

    Transactional OTP delivery for mobile verification, under TRAI-DLT sender registration.

    MSG91 · Twilio · Kaleyra

    Simulated in prototype
  3. RC & RTO Vahan (Parivahan)

    Vehicle fitness and registration checks pulled at agreement time rather than after the season starts.

    NIC Vahan · Signzy · Cashfree · Zoop

    Simulated in prototype

Illustrative scenarios

What the platform is designed to prevent

The scenarios below show the kind of outcome the product targets, written from the product brief.

Illustrative: These are illustrative examples, not real customer quotes. No named mill, person or organisation has endorsed this product. Real quotes will replace them once customers agree to be cited.

5 / 5
Illustrative
Three fraudulent roster registrations were flagged and avoided early in a season, before any advance changed hands.
Scenario · Mill operationsCo-operative sugar mill
5 / 5
Illustrative
Identity matching happened across mills without any raw Aadhaar number being stored, shared or exposed.
Scenario · CompliancePrivacy-safe matching
4 / 5
Illustrative
RTO fitness validity and carrying-load limits were checked at the agreement stage instead of mid-season.
Scenario · TransportFleet verification

Your quote could go here

Running a pilot with us? We'll publish your feedback here — named and attributed only with your written consent.

Tech & deployment

Enterprise-ready, and portable

A modular-monolith API with domain routers, a MySQL-backed data layer with an in-memory cache, and a bilingual React front end.

Enterprise-ready, and portable
FrontendReact 19 · TypeScript · Vite 6 · Tailwind CSS v4
BackendNode.js + Express modular monolith · TypeScript
DatabaseMySQL 8.0 — InnoDB, utf8mb4, migrations & seed included
SecuritySHA-256 identity hashing · bcrypt passwords · SSL/TLS in transit
AIGoogle Gemini (gemini-2.5-flash), server-side
DeploymentDocker-ready

Architecture

Domain routers for factories, contractors, labourers, vehicles, analytics and system, sitting over a MySQL data layer with an in-memory cache.

Deploy targets

  • Docker
  • Google Cloud Run
  • AWS ECS
  • Node + MySQL hosting

Secure your factory's capital ahead of the upcoming crushing season.

Walk through a live contractor lookup, the 4-signal logic and the zero-data-storage architecture with us. We'll use your own season's scenarios.

10-minute live demo · No commitment