Company
We have built these networks ourselves.
We spent our first years building networks and the software on top of them, for a province, for product companies, for operators. HOLOIN is what we built once we had seen the same gap at every one of them: the data existed and nobody was reading it as one record.
| Legal entity | Chirp Technologies LLC |
| Registered | Pennsylvania, United States, April 2019 · Philadelphia |
| Engineering | United States and Pakistan |
| Founder | Asif Hussain |
| Product | HOLOIN, release 1.5.2 · holoin.ai |
| Partners | Partner programmes with a LoRaWAN network-server vendor and a LoRaWAN sensor maker; partner accounts with two cloud providers. Named on request. |
| Client reviews | 4.9 of 5 from four verified reviews · Clutch |
Networks first, then the software on top of them.
Chirp began as an engineering company for connected systems: a LoRaWAN system demonstrated for a province's smart-city programme, commissioning tools for a sensor maker, the firmware and cloud pieces between a device and a dashboard. Before Chirp, its founder spent two years at MachineQ, a Comcast company, testing LoRaWAN devices for specification compliance and configuring the network servers behind a national IoT network, and was the IoT architect of an end-to-end LoRaWAN water-metering system for a town's water utility — meters in the pits, the gateways, the network server and its device provisioning, the sensor decoders, the head-end, the utility's own dashboards.
The work taught us where connectivity projects fail: not at the radio, but afterwards, when the data lands in one vendor's dashboard and the operator still runs the site from memory and a phone call. In time we stopped taking custom software and turned to two things only: advising operators on what their assets can already tell them, and building HOLOIN to hold that as one live record.
Today the company is seven people across two countries, one founder who answers his own email, and partners who install and support in their regions. We are small on purpose: the work is to make what you already run intelligible, not to sell you people.
Read before write.
Every engagement and every installation starts read-only. Control stays with the people who have it; a write, where one is ever wanted, is switched on for that site with a written reason and proven by the device’s own evidence.
Your servers, your data, your record.
HOLOIN installs on hardware you own, in a PostgreSQL database you can open, with backups in a standard format, or on a dedicated server we run for you. On a server we run for you, our access to your data is off by default: your administrator grants it, for a set time, and every action is logged against both identities.
Statistics a person can read.
An asset's normal is a median and a spread by hour of the week; a trend is a line with its fit; a proposed rule comes with the past failures it would have caught. Nothing on a page says "trust the model".
Claims with sources.
Every capability we name is shown on a live installation; every number on holoin.ai carries the test run it came from. A project is named on this site only with the customer’s written permission or the customer’s own public announcement. What we cannot yet show, we say is not yet shown.
Contact