One codebase, five products
A single installation becomes any of the five by changing one setting. Every page declares the module it belongs to; if the edition does not include it, the menu item never appears — so an officer never sees a menu full of features the force did not buy.
Runs on your own server
PHP and MySQL on ordinary departmental hosting. No appliance, no dongle, nothing to install on any desk. The database creates and upgrades itself on first load.
Nothing leaves the building
By default no case data is transmitted anywhere. The three exceptions — map tiles, the public IP-lookup service, and an optional language-model endpoint — are each a deliberate choice at install, and each can be left off.
Scanned documents stay local
An uploaded scan is read in the browser; only the extracted text reaches the server. On a locked-down deployment this is the difference between a tool that can be used and one that cannot.
Access and audit
Case-level visibility on every page and every file download. Every sign-in, failed sign-in, upload, export, deletion and case opened is logged with the officer, the object, the time and the address — filterable and exportable.
Chain of custody
A forensic hash on every exhibit, recorded at the moment it arrives and cited in the report. Which, alongside the access log, is what answers the defence question about who could have altered the record.
Section 63 certificate
The report carries the certificate for electronic records under the Bharatiya Sakshya Adhiniyam 2023 — which since 1 July 2024 requires two signatures, the person in charge of the system and an expert.
Deployment
Deployment packages exclude the configuration file, the edition setting, the storage directory and the logos, so an update can never overwrite live credentials or evidence. A pilot on a live case can be running within a day.