Engagements

How we work with
the Indian defence enterprise.

From a published problem statement to a fielded capability — through the iDEX pathway, with a clear pilot-to-production route and an honest stance on intellectual property.

The pathways

  • iDEX / DIO — we respond to Defence India Start-up Challenge (DISC), ADITI deep-tech and DRISHTI DPSU problem statements, and deliver against milestone-based SPARK / ADITI grants.
  • DcPP (Development-cum-Production Partner) — for capabilities ready to scale, we engage as a development-cum-production partner with the nodal Service or DPSU.
  • DPSU collaboration — direct engagement with shipyards and labs (e.g. MDL under DRISHTI) on decision-support tooling that integrates with in-service systems.
  • MSME & SC procurement preference — as an SC-led Micro Enterprise, our engagements are eligible under the Government of India's MSME and SC/ST public-procurement frameworks and DAP-2020 indigenous-content provisions.

Pilot → production

  • 1 · Prototype — a working, inspectable demonstrator built on transparent logic and synthetic data, so evaluation can begin without exposing classified data.
  • 2 · Pilot — live integration on a bounded scope (one block, one drawing class, one sensor network) with the customer's real systems and data, behind their firewall.
  • 3 · Production — air-gapped, RBAC-controlled, audited deployment at scale, with model cards, acceptance KPIs and a sustainment plan.

Deployment models

  • Air-gapped — fully offline on trusted hardware inside the classified network.
  • On-premise — on customer infrastructure, integrated with PLM/ERP/PDM and sensor grids.
  • MeghRaj / sovereign cloud — GI-Cloud for non-classified collaboration workloads.

Our IP stance

We retain background IP in our core engines and frameworks, and we are transparent about foreground IP created during a funded engagement — assigned or licensed per the programme's terms (iDEX/DcPP). Customer data, models trained on customer data, and mission-specific configurations remain the customer's. We do not reuse one customer's data to serve another.

Assurance

Every system is decision-support, not an autonomous authority. Outputs are explainable and traceable; write-back to systems of record is human-approved, with a two-person rule on critical actions. AES-256 at rest, RBAC, tamper-evident audit logs, and OWASP-hardened interfaces are standard.

Start an engagement