Sharing sensitive defense and geospatial imagery with external AI providers was not an option
Satellite imagery of border regions, critical infrastructure, and asset or troop movements is highly classified. Routing this data to external or cloud-based AI platforms for processing would require it to leave our secured environment, creating serious national-security, data-sovereignty, and confidentiality concerns.
Globally trained AI models have limited context for Indian terrain and border operations
Most vision and OCR models are trained on general, worldwide datasets. While strong at generic object and text recognition, they do not fully understand Indian border terrain, locally relevant vehicle and asset types, regional number-plate and container-marking formats, or the multi-script text (Devanagari and other regional scripts) found on assets in our area of operations. A model may understand imagery in general but still lack the context in which it is actually being used.
Deploying a single AI model alone did not give us mission-grade intelligence
We learned that a powerful detection model on its own was not enough. Turning a raw satellite scene into an actionable threat assessment requires several layers working together — image validation, tiling, object detection, text extraction, geo-referencing, classification, and entity linking. The model is only one part of a much larger intelligence system.
Running AI within our own infrastructure introduced stability challenges
Hosting detection, OCR, and classification models on our own GPU servers introduced challenges around server connectivity, model availability, and service interruptions — unacceptable for a platform expected to monitor continuously. We needed additional monitoring and infrastructure hardening to make the services stable and reliable.
Intelligence data arrives in complex, unstructured formats
Imagery comes in specialised geospatial formats (GeoTIFF, NITF, HDF5, GeoPackage) with varying band counts, resolutions, and coordinate systems, and the useful text on assets is embedded inside the pixels. This information cannot be analysed directly by a generic model and must first be validated, tiled, cleaned, and structured.
Objects split across image tiles were missed, and validating detections was difficult
Large scenes must be broken into tiles for processing, which causes objects and text near tile edges to be cut in half and missed by naive detection. Beyond that, a detection can look confident yet still be a false positive or a misclassified threat. Technical metrics alone were not sufficient — analyst and operator feedback was essential to confirm whether detections were operationally relevant and useful.
Processing time on large satellite imagery was high
Source imagery can be extremely large (up to 10 GB per scene) and very high-resolution. Analysing it end to end is compute-intensive and, without careful optimisation, too slow to support real-time, round-the-clock threat monitoring.