Component Breakdown
1. Ingestion Service
Written in Go. It reads inventory, utilisation, billing and flow-log data from AWS (incl. Cost Explorer), Azure (incl. Cost Management), Google Cloud (incl. the BigQuery billing export) and Oracle Cloud (Usage API), and from datacenter platforms such as vSphere, Hyper-V and Redfish/IPMI/SNMP. Everything is normalised into one inventory.
2. Heuristic Engine
The core intelligence of AIPrunr. It correlates billing data and utilisation with network flow logs to find "zombie" resources: assets that are still billed but receive no business traffic. Every finding keeps the evidence behind it.
3. Encrypted Storage
A PostgreSQL database you control (on the appliance or your own server) stores inventory, findings and cost history. Cloud and datacenter credentials are encrypted with AES-256-GCM; use an encrypted disk for the rest.
4. Zero Egress Boundary
The entire appliance sits behind your corporate firewall. Only the dashboard port (3001) needs to be reachable, and only from your own network; the engine and a local database listen on the machine itself. Outbound, it connects only to the cloud APIs and datacenter platforms you configure, never to SANSIDERA.