Exabytes Cloud Hosting vs Custom Servers for Farms

Latency Budget: On-Farm vs Cyberjaya RTT

Exabytes serves its cloud VMs from Peninsular data center facilities anchored in Cyberjaya. A farm office in Johor Bahru or Kedah sees roughly 10–25 ms round-trip time; an estate in Tawau or Miri jumps to 45–70 ms once traffic crosses the submarine backbone. That latency matters less for weekly MPOB yield reports and more for closed-loop control. A fertigation solenoid valve on Modbus RTU responds in under 2 ms when wired to a custom server on the estate LAN. Over a cloud MQTT path, you add TLS handshake, NAT traversal, and a cellular hop—realistically 80–150 ms with jitter. If your water pump logic depends on responding to a moisture sensor within half a second, cloud-only doesn’t qualify.

Three-Year Ringgit Cost Model

Exabytes’ Business Cloud tier with 4 vCPU and 8 GB RAM typically runs RM79–99/month on standard billing cycles. Three years of that is RM2,844–3,564 with zero capex and no cooling load. A custom Dell PowerEdge T350 (Xeon E-2300, 32 GB ECC, four 4 TB drives in RAID-5) costs roughly RM11,000 in Malaysia including warranty, plus about RM70/month electricity and RM300/year in fan and drive replacements. That works out to roughly RM15,200 over three years—northeast of five times the cloud bill. The breakeven flips only when you run eight or more VMs, host heavy local CCTV analytics, or carry 10+ sensor gateways that need dedicated sub-GHz radios. Otherwise, cloud wins purely on money.

Software Stack: FarmOS, MQTT, and Node-RED

Both platforms can run FarmOS (Drupal-based field records), but the surrounding stack differs. On Exabytes, you deploy via cPanel or Docker with typical LEMP setup—fine for planting calendars, harvest weights, and chemical logs. The custom server lets you attach a USB serial adapter to an RS-485 network on chicken coop environmental controllers or oil palm irrigation panels. Add Eclipse Mosquitto as a local broker, Node-RED for flow logic, Grafana for live dashboards, and a WireGuard tunnel pushing hourly aggregates to Exabytes for the KL head office. The cloud VM becomes the public reporting mirror, not the control brain.

Power, Internet, and Rural Uptime Realities

TNB brownouts in Perak padi areas and Sabah inland plantations are common enough to derail field automation. A cloud VM in Cyberjaya stays up through local outages but is useless when the estate’s CelcomDigi or Maxis LTE backhaul drops—which happens monthly in remote areas. A custom server on a UPS plus a small backup inverter keeps the local loop running indefinitely, but your Grafana dashboard disappears to remote viewers without connectivity. The practical resolution is hybrid: keep close-loop control and sensor buffering on the custom server, then batch-sync production and traceability data to Exabytes during stable connectivity windows, typically after midnight when cellular backhaul is uncontended.

Decision Rules for Smallholders vs Estate

A 2–10 hectare smallholder running durian or chili fertigation should take Exabytes directly: RM79/month VM, a cellular IoT temperature sensor, and FarmOS in the cloud. No on-site IT, no generator concerns, and MPOB traceability exports available from any phone. An estate over 100 hectares with multiple field controllers, diesel pumps, and permanent staff should buy the custom server for the estate office, pair it with a WireGuard VPN to Exabytes, and keep the cloud instance as the public-facing API for distributors and auditors. The split is simple: anything that actuates machinery stays local; anything that produces reports goes through the cloud.