Know whether this is worth a conversation.
These are the questions that change scope, ownership or commercial risk. If your question depends on a particular product, use the assessment route and bring the operating context.
Fit and first engagement
Is InfiIoT a fit for our product?
The strongest fit is an industrial OEM with a repeatable product, an installed or planned fleet, and a service team that needs remote visibility, faster diagnosis or a connected service offering.
What happens on the first call?
We focus on one product, one service goal and the decision that is blocking progress. The call is for fit and scope; it is not a free design workshop.
What is the Product Blueprint?
It is a paid, two-week engagement that produces a system map, bounded pilot plan, named risks and owners, and a clear pilot, rework or stop decision.
Do we need a complete specification before talking?
No. Bring the current product, known constraints and the decision the team cannot make confidently. Rough sketches and field notes are useful.
Architecture and deployment
Do we need to replace our firmware, SCADA or service systems?
Usually not. We keep working control systems in place and add only the device, data and service pieces the product needs.
Can InfiIoT run on premises?
Yes. Deployment can use shared cloud, dedicated infrastructure or an on-premises environment. Data residency, access and operating ownership are agreed before the pilot.
Do we need to replace existing sensors?
Rarely. Mixed fleets are expected. Edge gateways and protocol conversion can connect equipment that cannot speak directly to the platform.
Which protocols are supported?
Current work includes MQTT, HTTPS, LoRa, NB-IoT and cellular, BLE, RS485 and Ethernet-based industrial protocols. The correct choice depends on the product and operating environment.
Ownership and operations
Who owns the data?
The customer does. Export, API access, retention, data residency and exit rights should be written into the deployment agreement.
Can the product use our brand?
Yes. Branding, domains, user roles and the service experience can be defined around the OEM product.
How long does a first deployment take?
It depends on the asset, interfaces and what the first decision must prove. The Product Blueprint exists to establish a credible pilot scope before anyone promises a date.
What happens after the pilot?
The pilot ends with an explicit decision: proceed, rework a named risk, or stop. A rollout plan then covers fleet provisioning, updates, monitoring, support and ownership.
Still depends on your product?
Bring the equipment and the blocked decision. We will use the first call to test fit, not to run a generic demonstration.
Plan the assessment →