The questions evaluators ask first.

Three integrated layers: autonomous aerial platforms, self-sustaining solar ground stations that keep them charged and launch-ready, and the command software that authorises deployments, streams live video and produces an auditable evidence record.

The autonomous platform is one component of that system, not the product on its own. The capability comes from the three layers working together — which is why we describe ourselves as an autonomous systems company rather than a drone manufacturer.

Deliberately. Our primary customers are defence, paramilitary, government and critical-infrastructure operators, and publishing configuration detail — airframe, payload options, sensor and processing stack, endurance, range, datalink architecture, deployment topology — serves no legitimate customer interest and several illegitimate ones.

Technical disclosure happens with qualified counterparties, under NDA, through the appropriate procurement or evaluation channel.

Deployment is autonomous. On an authorised trigger, the best-placed station launches, the platform navigates to the coordinate, holds station, streams what it sees and returns to dock — with no pilot and no human dispatcher in that loop.

Action is not autonomous. Anything the platform does that affects a person requires an authorised officer, with the authorisation recorded against their identity.

The deploying authority does, under rules configured for that site before the system goes live. The platform gives an officer a live picture and AI-flagged detections; the officer decides. For sensitive actions, the system can require two officers to authorise independently.

The full authorisation chain — who requested, who approved, what was done, when — is sealed into the incident record.

Data from Indian deployments is held in India. Each customer's data sits in segregated tenancy — nothing is pooled across customers — and the deploying authority owns its operational records.

Sensitive sites can be deployed on-premise or air-gapped. Retention periods are configured to the customer's own policy rather than ours, and every viewing session is logged and auditable.

Yes, within the applicable regulatory framework. Operations are conducted under DGCA rules, and registration, airspace permissions and operator compliance obligations are handled as part of deployment rather than left with the customer.

Defence and government deployments additionally follow the authorisation regime of the deploying organisation, which can differ substantially from civil rules.

Pilot prototype stage. The system architecture is complete, the software layer — command dashboard and citizen application — is operational, and the full response cycle has been validated in simulation, including failsafe and abort paths.

Pilot hardware is in build, with controlled field demonstration as the next milestone, followed by operational pilots with government and enterprise counterparties. We state this precisely rather than implying deployed maturity we do not yet have.

Most systems sold today are piloted aircraft with a camera: they need an operator, a crew and a launch decision, which puts them back inside the response delay they were meant to remove.

Our unit of delivery is a standing response network — solar stations holding continuous readiness, autonomous dispatch without an operator, and a command layer that produces an admissible record. The comparison is not to a better drone; it is to the patrol that currently takes eight to fifteen minutes.

Yes — that is the intended deployment model. Existing cameras, fence-line sensors, alarm panels and access control can raise a verified trigger, and control-room operators can dispatch directly from the command dashboard or from an integrated command-and-control system.

A documented API also allows partner wearables and third-party safety devices to raise an authenticated trigger in civic deployments.

We quote against a scoped requirement rather than publishing a price list. Cost is driven by coverage area, station count, authority and integration model, data-residency requirements and service level — which vary by an order of magnitude between a single campus and a multi-district government programme.

Commercial structures typically combine infrastructure, a recurring service subscription and a maintenance contract.

A scoped briefing first, then a site survey and coverage model, then a controlled pilot measured against benchmarks agreed in advance — ideally your own reported response times, not ours.

Defence programmes can also engage through innovation challenges, formal trials, tenders and framework agreements, or co-development with a PSU or prime integrator.

Yes. Design, engineering and assembly are done in India, with domestic component sourcing and local supply-chain partners, and positioning that is NavIC-aware alongside global constellations.

For our defence and government customers this is a procurement requirement rather than a preference, and it constrains how the platform is designed from the outset.