One of the biggest challenges in building an IoT product is not the hardware — it is the software infrastructure around it. A typical IoT startup must build a device management backend, a messaging broker, a user authentication system, a mobile or web application, a data storage layer, and a way to monetize or share data. That is months of engineering work before a single customer can use the product.
FidesInnova eliminates all of that. This guide walks through exactly how to go from hardware to market in under a week — with cryptographic data integrity built in from day one.
The traditional IoT stack requires teams to build and maintain:
Each of these components takes weeks to months to build correctly. FidesInnova provides all of them out of the box — and adds zero-knowledge proof verification that no competing platform offers.
FidesInnova works with any MQTT-compatible IoT hardware. If you are starting from scratch, the FidesInnova reference devices (E-card V2, zk-MultiSensor, MiniSensor) come pre-configured. For existing hardware, you connect it to the integrated MQTT broker in the FidesInnova Node using standard MQTT over TCP or MQTTS (TLS-encrypted).
Deploy the FidesInnova Node on any Linux server (VPS, bare metal, or cloud VM). The node ships as a Docker container and is running in under 30 minutes. Register your devices through the web dashboard — each device receives a cryptographic identity tied to its firmware hash.
Service Contracts are JavaScript mini-programs that run inside the FidesInnova Node. They define what your device does with its data — forward readings to a database, trigger alerts, share data with other users, or submit ZKP proofs to the blockchain.
Alternatively, use the built-in Blockly visual editor — drag-and-drop programming with no code at all. Ideal for rapid prototyping or for non-developer team members.
Your customers do not need to wait for you to build a mobile app. The FidesInnova Mobile App (iOS and Android) connects to your node and gives end users a full device management dashboard immediately. Users can:
This is where FidesInnova separates from every other IoT platform. The ZKP SDK (C++ or Rust) is integrated into your device firmware. Once active, every sensor reading generates a zk-SNARK proof that:
These proofs are stored on the FidesInnova blockchain and browsable via the ZKP Explorer. Any third party — customer, regulator, insurer — can independently verify the integrity of your device data without trusting you.
Publish your Service Contract to the FidesInnova Service Market. Other users and platform operators can discover, install, and use your contract — and you earn a revenue share each time they do. This creates a recurring income stream from your IoT product without building a separate SaaS business.
Your IoT product is live. Devices are connected, data is flowing, proofs are on-chain, customers have a mobile app, and you have a monetization path through the Service Market. What would typically take 3–6 months of backend engineering took one week.
Environmental sensors, parking, waste management, street lighting — all deployed in days with ZKP-verified data for municipal reporting.
Sub-metering, solar generation monitoring, demand response devices — ZKP proofs enable provably accurate energy trading and regulatory compliance.
Remote patient monitoring devices — ZKP-verified vitals that clinicians and insurers can trust without accessing raw patient data.
Soil, weather, and irrigation sensors deployed rapidly — with verified data suitable for crop insurance and precision agriculture analytics.
Fleet telematics and EV charging monitors — ZKP-verified mileage and usage data for insurance, warranty, and carbon credit programs.
Condition monitoring for machinery — ZKP-backed anomaly detection alerts that hold up to regulatory scrutiny and insurance claims.
The FidesInnova platform is not just a shortcut — it is a better architecture. By using standardized IoT protocols (MQTT), a programmable Service Contract layer, a community marketplace, and zero-knowledge proof verification built in from day one, you ship faster and deliver a more trustworthy product than teams that build their own infrastructure from scratch.
The week-to-market timeline is not theoretical. It reflects the real reduction in engineering work when you stop building commodity infrastructure and start focusing on what makes your IoT product unique.