Exabytes Hosting vs Custom Cloud for Farm Analytics

Cost per Node: Cloud VM vs Raw Hardware

Start with what Exabytes lists publicly: entry-level Cloud VPS plans in Malaysia run 2 vCPU / 4 GB RAM / 80 GB NVMe at roughly RM150 per month. That includes a KL data-center hypervisor, DDoS scrubbing, and Bahasa-melayu support tickets. A farm-analytics stack — ThingsBoard CE, MQTT broker, Grafana, TimescaleDB — fits in 4 GB easily, provided you stop running PostgreSQL on the same node.

A custom cloud is not cheaper on month one. A realistic 3-node Proxmox VE 8.x cluster using secondhand Dell OptiPlex 7060 minis (i5-8500T, 16 GB DDR4, 256 GB NVMe) costs about RM1,100 per node, plus an APC Back-UPS at RM850 and a managed TP-Link switch at RM400. Total capital outlay: roughly RM4,150. At RM150/month saved, the break-even point lands between 24 and 30 months.

What the price tag hides is bandwidth. A 300-sensor LoRaWAN deployment sending a 50-byte payload every 5 minutes generates about 129 MB per month — trivial for either option. The problem is the burst: when a padi-field pump controller pushes 5,000 MQTT messages after a firmware update, a shared-hosting account with a hard process limit will drop the connection. Custom hardware absorbs that burst locally; an Exabytes VM forces you to size the instance for the spike, not the average.

IoT Ingress: MQTT, LoRaWAN, and Gateways

Malaysia’s MCMC allocates the 923–925 MHz band for LPWAN, which means your gateway runs on the AS923-1 frequency plan. A Dragino LG02 gateway (roughly RM950) works fine for estate trial blocks. For larger plots, a Multitech Conduit AP at RM2,200 handles 500+ end nodes with better receive sensitivity under rubber-canopy attenuation.

The real architectural decision is where the MQTT broker lives. With Exabytes, your Mosquitto broker sits at a KL IP address and the field gateway connects over Unifi or 4G. Expect 35–60 ms round-trip from Alor Setar or Kota Bharu, plus packet loss during the November monsoon. QoS 1 messages will retransmit, but you eat TCP backoff delays.

With a custom cloud, run Mosquitto on the gateway itself or on a local Proxmox node. The broker sees <1 ms latency, and the local TimescaleDB instance buffers 72 hours of sensor history even when the 4G router drops. Replication to a remote dashboard becomes a nightly rsync — not a real-time dependency. For a padi-block irrigation controller that closes a furrow gate based on soil-moisture thresholds, that offline-first behavior is the difference between one missed command and an entire flooded block.

Data Residency and Jabatan Pertanian Compliance

Jabatan Pertanian still collects block-level yield declarations, soil-test results, and input-subsidy records for schemes like the Skim Subsidi Padi. These files are not personal data under the PDPA, but district officers routinely ask where the data is hosted. An Exabytes VM pinned to the KL data center answers that question cleanly. Paying extra to pin data to a Malaysian datacenter, rather than letting it drift to Singapore, matters for field audits.

A custom cloud in your own estate office is even simpler to explain: the data never leaves the property boundary. This is relevant for FGV and Felda research plots, where trial data on yield response to fertilizer is considered operationally sensitive. No cloud provider’s data-processing agreement will ever be as airtight as a lockable server cabinet in the estate manager’s office.

One caveat: LoRaWAN gateways themselves need MCMC Type Approval under the Communications and Multimedia Act 1998. Buying through a local distributor who handles SIRIM certification is non-negotiable.

Operational Load: Patches, Reboots, Pipe Breaks

Exabytes’ value is not the CPU — it is that their engineers reboot the hypervisor, swap failed disks, and answer support tickets in a language your coop staff actually reads. Email support respond times vary, but the KL Pejabat is reachable during business hours.

A custom cloud transfers every ounce of that burden to you. The estate’s IT person — typically a farm manager who also handles fertilizer invoices — will need quarterly patching discipline. Update Proxmox with `apt update && apt dist-upgrade`, watch the `pveupdate` logs, and replace failed NVMe drives before they degrade your ZFS pool. This is manageable if you have an MSP retainer in Kulim or Ipoh at RM1,500–2,000 per quarter, but that retainer evaporates your hardware savings.

Power quality is the silent killer. TNB rural supply drops voltage during the afternoon thunderstorm season; a cheap USV will misbehave and cause HVDC lockups. Budget for a line-interactive UPS and accept that node #3 is your offline hot spare.

Verdict for Padi and Estate Telemetry

Choose Exabytes when the farm analytics stack is centralized: sensors push data to a dashboard in headquarters, and nobody on-site needs to log into a server console mid-crisis. A coop with 3–4 staff and no technical hire should not be running Proxmox.

Choose a custom cloud when you have an agro-tech research partner, a Politeknik Jasin intern, or a data-savvy estate manager — and when the control loop needs to close locally. Sub-1ms MQTT ingestion plus offline buffering is the only architecture that survives a Kedah monsoon without gaps in your 15-minute soil-moisture time series.