Case study · Platform record · Platform record · Foundation

Vinkura Core

We built Core — delivered through AEGIS — as the shared substrate under every module we have shipped: identity, connections, workflow, geospatial context, and audit.

AEGIS platform

Who
Institutions running Vinkura field and command systems
Where
On-premises, sovereign cloud, or controlled hybrid — the same foundation
Mission
Stop procuring another silo every time a new operational need appears
Vinkura Core operational records and workflow architecture
One operating layer across products that already run in the field.

01 / The situation

Institutions procure tools that share no data. An FIR printout is walked to the evidence locker for re-entry. Duty rosters live beside court calendars and never meet. Command reconstructs the day from windows that do not know each other.

Core is not a field yatra. It is the reason Pehchan, DDMS, Hawk-Eye, Trinetra, e-Maalkhana, Sentinel, Forge, Orbit, and Voice can share a person, a place, a case, and an audit trail. The Hindustan Wires profile of the sovereign platform is the public record of that intent.

02 / What we built

We built Core as the shared sovereign substrate: an API layer, identity and access, an entity graph connecting operational records, workflow orchestration, geospatial context, and an append-only audit ledger. Modules exchange state through controlled interfaces instead of copying data between isolated tools.

AEGIS is how that substrate is deployed — on-premises, in a sovereign cloud, or across a controlled hybrid. Offline and edge operation, reconciliation, environment policy, and multi-tenant separation are platform capabilities, which is why DDMS and Trinetra can keep working when the network does not.

  1. 01Connect

    Ingest approved records and operational feeds through secure APIs, files, and departmental integrations.

  2. 02Structure

    Resolve entities, permissions, location, provenance, and workflow state into a common operating model.

  3. 03Operate

    Deliver role-specific systems for command, field teams, analysts, supervisors, and administrators.

  4. 04Account

    Preserve source lineage, human decisions, policy checks, and a complete audit trail.

Unified data fabric

Connect structured records, documents, events, and approved external systems without replacing every source system.

Identity and access

Departmental roles, granular permissions, tenant boundaries, and attributable activity across every operational surface — the same controls behind Pehchan.

Workflow and intelligence runtime

Forge procedures and governed models with traceable inputs, outputs, and human review points.

Audit and compliance

An inspectable record of access, decisions, approvals, changes, and system actions across every module.

03 / How it ran

When an authorised user opens a case, Core can connect the assigned officers, evidence chain, next hearing, and pending forensic work without asking each department to re-enter the same record. When a control room opens Sentinel, the duty posture and the Hawk-Eye frame share identity and place because they sit on the same substrate.

That is already true of the systems with press: DDMS in Muzaffarnagar, Pehchan in Ganderbal, Hawk-Eye in Bareilly and Anantnag, e-Maalkhana at Mirganj. Core is the reason they are one operating family.

AEGIS command center and sovereign operational platform
AEGIS is the unified platform module: identity, data, intelligence, workflow, place, audit.
AEGIS platform operating system diagram
New modules inherit identity, audit, and entity context instead of inventing another vendor link.

04 / What changed

New modules join the same institutional operating picture instead of creating another silo. Command gains a connected view across operational systems.

The institution keeps authority over permissions, deployment, and the record of every action. Interoperability is governed infrastructure rather than a collection of one-off vendor links.

05 / Where we take this

We are taking Core from the modules already shipped into a thicker shared entity graph: one person, post, case, item, and camera identity across every surface.

Next on our side: more of Personnel, Traffic, and E-TA/DA inheriting the same foundation, and the same on-prem / sovereign / hybrid deployment path for every new operational product we put in the field.

06/ News & media

Platform coverage, plus the field systems that already run on this foundation.

AEGIS platformUnified operational platform moduleVinkura Core productFoundation product pageHindustan Wires newsroomPlatform press recordPehchan case studyIdentity on AEGISAll deploymentsField systems that run on this foundation

08 / Request a briefing

Talk to us about running this architecture in your district, unit, or command. We brief from the systems we have already deployed — not from a slide of hypotheticals.

Request a briefing