ASocks VS Cloud Studio IoT

Cloud Studio IoT's answer:

• MQTT: a dedicated MQTT server per instance, with TLS
• HTTP API and TCP for devices and for integrations
• LoRaWAN through external network servers: The Things Stack, LORIOT, ThingPark X, Helium, ChirpStack, Orbiwise and IoT Creators
• Modbus and OPC UA through a software gateway installed at the edge, which forwards the data over MQTT
• A documented REST API, so other systems can read and write what the platform stores
• SQL Server for storage, on AWS or on the customer's own servers
• Native iOS and Android apps
• An AI Copilot over the customer's own telemetry, with dashboards from a prompt and device actions in beta

Cloud Studio IoT's answer:

Cloud Studio IoT is white label first. One instance serves all of a partner's customers, each seeing only its own data, with the partner's brand across the interface, the reports and the notifications.

It is also connectivity agnostic. Devices arrive over MQTT, with a dedicated MQTT server per instance and TLS, or over the HTTP API. LoRaWAN devices come through the network server the customer already uses, with integrations for The Things Stack, LORIOT, ThingPark X, Helium, ChirpStack, Orbiwise and IoT Creators. Industrial equipment speaking Modbus or OPC UA connects through a software gateway installed at the edge.

On top of that data: more than 30 vertical templates, dashboards, SCADA-style views, threshold alerts with notifications by email, SMS, WhatsApp, voice call and push, downloadable reports, native iOS and Android apps, and an AI Copilot that answers questions about the telemetry in plain language. It runs on AWS or on the customer's own servers, and there are more than 150,000 connected devices in production.

Cloud Studio IoT's answer:

Because the buyer is usually a partner, not the end user: system integrators, device manufacturers and service operators that need to deliver monitoring to their own customers under their own brand, without building a platform first.

Open-source platforms are cheaper to license and more expensive to run, because the integration, the scaling and the maintenance stay with you. Cloud Studio IoT arrives with those pieces assembled: multi-tenant white label, vertical templates, device decoders, mobile apps and support, so the cost sits in a subscription instead of in engineering time.

Deployment is measured in days. In a public air quality project for the Government of the Canary Islands, 240 solar-powered 4G sensors went live in 120 schools across seven islands in 18 working days, against the 79 planned. And when data cannot leave the site, the same platform installs on-premise.

Cloud Studio IoT's answer:

Cloud Studio IoT started in Madrid in 2020, from a team that had spent years building industrial and telemetry projects one at a time. The same plumbing came back on every project: connect the devices, store the data, draw the dashboards, wire up the alarms. The customer paid for it once and nobody paid for it twice.

So we built that layer once and made it white-label. System integrators, device manufacturers and service operators put their own brand on the platform, connect their devices and sell the result as their own product, instead of spending a year building a platform that is not their business.

The largest deployment today is the public lighting of Buenos Aires: with our partner Smartmation, the platform manages and monitors around 150,000 street lights. Other partners run early fire detection at industrial sites (MoviTHERM, in California), air quality across 120 schools in the Canary Islands for the regional government, and oil well monitoring with more than 20,000 variables in real time.

The platform handles more than 150,000 connected devices and the company works with 35+ partners. We sell to the people who build the solution, not to the end customer.

Cloud Studio IoT's answer:

We sell through partners, so most end customers belong to them. The deployments we can name:

• City of Buenos Aires public lighting, with our partner Smartmation: the platform manages and monitors around 150,000 street lights, our largest single deployment.
• MoviTHERM (Irvine, California): a thermography specialist that integrated its thermal cameras with Cloud Studio IoT and launched its early fire detection system for industrial sites — coal processing, biomass plants, recycling centres and wood processing — in under a month.
• Gesplan, for the Government of the Canary Islands: 240 solar-powered 4G air quality sensors across 120 schools on the seven islands, with a public dashboard per school. The fieldwork took 18 working days against the 79 planned.
• Oil well monitoring: real-time control with automatic alerts and more than 20,000 variables.
• Vesta, at the Tárraco Roman necropolis in Tarragona: heritage conservation monitoring.

In total the platform runs more than 150,000 connected devices across 35+ partners and 20+ use cases.

Cloud Studio IoT's answer:

We sell B2B2B, so our customer is whoever builds the IoT solution, not the company that finally uses it.

Three profiles:

• System integrators who win projects in smart cities, water, energy, agriculture or industry and do not want to build and maintain a platform for each one.
• Device manufacturers that need a branded cloud and a mobile app to sell with their hardware.
• Service operators who monitor assets for their own clients and bill for the service.

Inside those companies we talk to technical founders, CTOs and project managers. What they have in common: the platform is not their business, the project has a deadline, and the end customer must see their brand, not ours.