Where it runs, and what that means for you.
The four questions procurement asks, answered without marketing language: how accurate, where hosted, how secured, and what happens if we leave.
Accuracy
Accuracy is a property of the survey, not of the software that displays it. Every capture is tied to ground control — DGPS and, where the site needs it, Total Station — and the achievable accuracy depends on that control, the flight parameters and the ground itself.
Which is why you will not find a headline centimetre figure here. Ask us about your site and we will tell you what is achievable on it, and what it would take. A number quoted without the survey behind it is worth nothing to either of us.
Where your data lives
MINFRA runs in Amazon Web Services in the Mumbai region — ap-south-1. Your imagery, models, point clouds and documents are stored and processed in India, not moved offshore.
For most of our clients that is a procurement requirement rather than a preference, so it is stated plainly rather than buried in a compliance annexe.
Security
Traffic is served over TLS end to end, behind Cloudflare for DNS, CDN, web application firewalling and DDoS protection. Passwords are hashed with Argon2, and sessions are token-based.
Access is scoped per project: a person, whether a colleague or a contractor, sees the projects they have been granted and nothing else. The assistant follows the same rule — it cannot answer from a document you are not entitled to open.
Open formats
Imagery and elevation are stored as cloud-optimised GeoTIFF, point clouds as COPC alongside a Potree octree for streaming, and vectors as GeoJSON reprojected to EPSG:4326.
These are open standards, readable by QGIS, ArcGIS and anything else that speaks them. If you stop using MINFRA, your survey data does not stop being usable — which is the point. A platform that holds your data hostage never has to earn the renewal.
Something we have not answered
Procurement questionnaires ask things this page does not cover.
Send it to frontdesk@unitos.org and we will answer in writing. If the honest answer is “not yet”, that is what you will get — it is a great deal cheaper for both of us than finding out during implementation.
See it running on your own data.
The fastest way to evaluate any of this is against a capture of your own site.