Putti builds the platform layer behind connected hardware in New Zealand: device and fleet management, scalable data ingestion, companion iOS and Android apps and dashboards. Our Auckland team has delivered 100+ projects since 2010 with zero failures, including EV charging platforms such as Hikotron and Invisible Urban.
What does the software for a connected product involve?
Connected products live or die on their software. The hardware collects data. The software turns it into something people can use, at scale and without downtime.
That starts with device and fleet management: provisioning, monitoring and controlling devices, from a pilot of ten to a fleet of thousands. It continues with data ingestion built so a platform that works for a pilot keeps working as the fleet grows. Then come native iOS and Android apps that pair with the hardware, and dashboards and alerting that turn raw readings into information an operations team can act on.
Underneath, the software has to speak the hardware's language. That means firmware interfaces and protocol support, including standards like OCPP for EV charging.
What connected products have we shipped?
Hikotron is a connected EV charging platform that links IoT chargers to native iOS and Android apps, so drivers can find stations, run sessions and pay. Invisible Urban is a three-part EV charging platform with a driver app, an admin portal and an installer app, with OCPP integration so chargers from different makers work together.
Both are part of 100+ projects delivered since 2010 with a zero-failure record.
Where do you start with a connected product?
With the question of what happens at ten thousand devices, not ten. If you're building a connected product or an IoT platform, see our IoT software service or tell us what you're building. A proof of concept in 2 to 4 weeks is a fast way to test the platform idea before committing to the full build.
Last updated: November 2, 2026
Frequently asked questions
-
Who builds IoT software in New Zealand?
Putti, an Auckland software team, builds the platform layer behind connected hardware for New Zealand businesses: device and fleet management, data ingestion, companion iOS and Android apps, and dashboards. Our connected-product work includes the Hikotron and Invisible Urban EV charging platforms, part of 100+ projects delivered since 2010.
-
What is the software side of an IoT product?
Everything that turns sensor readings into something people can use. That's the platform that provisions and monitors devices, the pipelines that ingest their data, the apps that pair with the hardware and the dashboards that alert an operations team. The hardware collects the data. The software decides whether it's useful.
-
Do you build companion apps for connected hardware?
Yes. We build native iOS and Android apps that pair with the hardware. Hikotron's app, for example, links IoT chargers to a native app for finding stations, running charging sessions and paying. A companion app is often the whole customer experience of the product, so it has to feel reliable even when the connection isn't.
-
Can you build an EV charging platform?
Yes. Hikotron is a connected EV charging platform linking IoT chargers to native apps. Invisible Urban is a three-part platform: a driver app, an admin portal and an installer app, with OCPP integration so chargers from different makers work together. OCPP is the standard that keeps a charging network from being locked to one vendor.
-
Will an IoT platform scale from a pilot to thousands of devices?
It can, if it's designed for that from the start. We build data ingestion so a platform that works for a pilot of ten devices keeps working reliably as the fleet grows to thousands. Retrofitting scale into a pilot is where most connected products stall, so we design the pipeline for the fleet you'll have, not the one you start with.
-
Do you work on the hardware or firmware?
We build the software layer, including the interfaces and protocol support that connect to your hardware, such as OCPP for EV charging. The hardware itself is usually built by your hardware team or manufacturer. We work with them on the interface, so the device and the platform agree on how they talk to each other.