Soil probes in the field, climate controllers in the greenhouse, tank sensors in the yard and drones over the crop all report from places with weak coverage. ConnectMQ brings them onto one managed MQTT broker, so your farm dashboard, irrigation controller and phone app act on live data.
No card required
Fields, orchards and pivots sit at the edge of cellular coverage or behind a LoRaWAN gateway. Devices drop off, readings go missing and failed HTTP uploads go unnoticed.
The greenhouse climate computer, irrigation controller, weather station, tank monitor and drone platform each have their own portal and login. Nobody sees the whole farm in one place.
A stuck valve, an empty fertigation tank, a vent that did not open or a cold room warming up overnight costs crop and produce — and is usually found hours later.
Growers and agri-tech teams use ConnectMQ as the shared MQTT layer between devices in the field and the software that decides what happens next.
A private broker instance in the cloud, reachable over TLS from any gateway or cellular modem. No server in the farm office to keep running and no broker for your team to patch.
Every gateway, drone and controller has its own username and password, and per-topic ACLs keep growers, agronomists and service contractors to their own farms and fields.
Small MQTT packets suit LTE-M, NB-IoT and LoRaWAN backhaul. Persistent sessions and QoS 1 deliver valve commands after a reconnect, and retained messages hold the last state of every valve, pump and tank.
Threshold rules on soil moisture, greenhouse temperature, tank level or cold room temperature trigger alerts and notifications, and Last Will warns when a field gateway goes silent.
Most farms and agri-tech teams start with one connected job — irrigation, a greenhouse or tank levels — then add drones and cold rooms on the same topic tree.
Spraying and scouting drone fleets connected to your farm management platform
Explore the use caseTemperature, humidity, CO₂, PAR light and substrate data for the climate computer and grower
Explore the use caseSoil probes, valves and pumps over LTE-M, NB-IoT or LoRaWAN, with reliable valve commands
Explore the use caseRemote level readings from fuel, chemical, LPG and bulk tanks for vendor-managed inventory and timely refills
Explore the use caseagri/farm-12/field-7/soil-03
agri/farm-12/field-7/valve-2/set
agri/farm-12/field-7/valve-2/state (retained)
agri/farm-12/gh-2/climate
agri/farm-12/drone/dr-04/telemetryYour LoRaWAN network server, such as ChirpStack or The Things Stack, exposes decoded uplinks over MQTT or webhooks. A small bridge forwards them to ConnectMQ under topics like agri/{farm}/{field}/{sensor}, and your dashboard, irrigation controller and app subscribe there.
Yes. MQTT has a tiny header, keeps one long-lived connection and works well over LTE-M and NB-IoT modems. Persistent sessions and QoS 1 make sure commands and readings arrive after a dropout, and retained messages give an app the last known value straight away.
Many greenhouse controllers and gateways publish over MQTT or can be bridged from Modbus. Use MQTT to share climate data and setpoints with dashboards, apps and alerting, and keep closed-loop control of vents, screens and heating in the local climate computer, so the greenhouse keeps running if the internet goes down.
The drone or its ground station publishes position, battery and mission progress as small MQTT messages over LTE or the base station’s link, and receives mission commands on its own topic. Large files such as multispectral imagery are uploaded separately; MQTT carries the status and the “upload complete” event.
Start on the Free plan — no card required. Connect one field, greenhouse or tank yard, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
