TrackSyte Neo 2 — gateway for secure remote asset monitoring

What Neo 2 is (and is not)

Neo 2 is TrackSyte’s multi-protocol industrial IoT gateway for secure remote asset monitoring. It sits on remote plant, CCTV towers, power kits and industrial assets, brings supported machine and IO interfaces into one path, and forwards operational data into TrackSyte® Portal so UK teams act on exceptions, not routines.

Neo 2 supports everything the original Neo does, and ships fitted with Ethernet, RS485, CAN bus and a 12V supply — plus Bluetooth for nearby power and battery conversations. The product-of-record story for the gateway lives on this page; sector and capability pages reuse the same locked interfaces without inventing extras.

TrackSyte is built from Cornwall HQ with UK field language — towers, hire plant, temporary power and perimeter sites. See About for who we are and how we work with operators who live on exceptions, not dashboards.

GNSS is fitted as standard on Neo 2 — a full-constellation GPS/GNSS receiver that can support tracking and GPS-related functions, alongside the gateway and Portal monitoring stack. The primary product category remains a multi-protocol gateway for secure remote asset monitoring.

There is no Canvas product naming on this page, and we do not invent compliance badges. Neo 2 is also not a PID panel, a camera VMS or a replacement for manufacturer controllers — it connects and monitors the asset stack you already run.

Connectivity at a glance

In: CAN bus connectivity · Modbus connectivity · GPIO connectivity · RS485 connectivity.

Out: LTE-M cellular connectivity · NB-IoT cellular connectivity · Ethernet connectivity.

Fitted: 12V supply · Bluetooth · GNSS (fitted as standard — full-constellation).

Into Portal: MQTT · API.

That mix is the locked truth for Neo 2 after the 2026-09-25 product-truth override. Also fitted: 12V supply, Bluetooth, and GNSS as standard — a full-constellation GPS/GNSS receiver that can support tracking and GPS-related functions. Neo 2 works with Victron, smart/lithium BMS and Smart Shunt where that kit is on site. Family depth for Hub and related hardware still lives on Hardware & integrations — Hub remains part of the product family; it is not the exclusive RS485 story.

• ✓CAN bus connectivity
• ✓Modbus connectivity
• ✓GPIO connectivity
• ✓RS485 connectivity
• ✓LTE-M cellular connectivity
• ✓NB-IoT cellular connectivity
• ✓Ethernet connectivity
• ✓12V supply
• ✓Bluetooth
• ✓GNSS (fitted as standard — full-constellation)

Designed for

Neo 2 is built for the same remote fleets TrackSyte already serves — and for plant networks that need a proper field gateway.

• ✓CCTV tower monitoring
• ✓PID / perimeter monitoring
• ✓Construction equipment telematics
• ✓Temporary power, pumps & welfare

Protocols and interfaces

Honest interface table for Neo 2. Family and Hub depth remain on Hardware & integrations. Do not invent Hub-only interface limitations we have not confirmed.

• ✓CAN: Plant / vehicle networks (in) — see CAN bus capability
• ✓Modbus: Field devices that speak Modbus (in)
• ✓GPIO: Discrete status / IO (in)
• ✓RS485: Serial field bus fitted on Neo 2 — not exclusive to Hub
• ✓LTE-M: Cellular backhaul (out)
• ✓NB-IoT: Cellular backhaul (out)
• ✓Ethernet: Wired backhaul fitted on Neo 2 (out)
• ✓12V supply: Fitted power supply for the gateway
• ✓Bluetooth: Nearby device conversations (e.g. power / battery kit)
• ✓GNSS: Fitted as standard — full-constellation GPS/GNSS that can support tracking and GPS-related functions
• ✓MQTT / API: Data path into TrackSyte® Portal

CAN as a differentiator

CAN unlocks plant and vehicle networks — diggers, excavators and other machine buses — that Ethernet-only gateways never see. For qualified plant and hire buyers that is a Tier-1 differentiator and a useful long-tail search path. Sales and enablement can lean on CAN when the buyer already knows their machines speak it.

It is not TrackSyte’s primary UK head-volume SEO bet versus CCTV towers, PID or “secure remote asset monitoring.” Treat CAN as depth for the right buyer; the deep dive lives on the CAN bus capability page, with construction proof on construction equipment telematics. Do not promise UK search-volume leadership on CAN from this hardware page.

Works with TrackSyte Portal

Neo 2 is the field gateway; TrackSyte® Portal is the secure remote asset monitoring software. Status, alerts and operational data arrive over MQTT / API so ops, hire desks and security managers share one view. The commercial outcome is familiar to TrackSyte buyers: despatch on exceptions, not routines.

For visit-cost proof, see commercial impact and the site visit calculator. Those pages carry the ROI narrative; this page stays focused on what Neo 2 is and how it connects.

Integrations

Neo 2 and Portal work with TrackSyte’s real integration paths — only where true today. We do not invent OEM partnerships, certification seals or vapour SKUs on this page.

Neo 2 works with Victron power systems; smart and lithium batteries with BMS; and can talk to Smart Shunt for battery monitoring where that kit is on site. Power-adjacent buyers often start with Victron or EFOY; security stacks may add Ajax; plant and custom estates lean on the API path. Each integration page remains the source of truth for that relationship.

Security

Physical asset context. Neo 2 is designed for towers, PID sites, plant and temporary power — remote assets where someone still has to decide whether to drive out. Physical security language on sector pages (CCTV, PID) stays about the site job; this hardware page states that Neo 2 supports those assets without replacing detection or response products.

Cyber basics. Authentication, TLS, certificates and MQTT protect the path into Portal. That is the honest security language for this gateway. No invented ISO, SOC or compliance badges. If a future certification is approved, it will be added deliberately — not implied here.

Neo 2 vs Hub / family

Neo 2 is the multi-protocol field gateway: CAN, Modbus, GPIO and RS485 in, plus cellular and Ethernet out into the Portal, with a fitted 12V supply and Bluetooth.

Hub remains an Ethernet-connected device gateway and the place for broader hardware-integrations depth. Do not invent exclusive-Hub interface claims we have not confirmed — RS485 is fitted on Neo 2 as well as available on Hub.

Canonical Neo 2 detail is this page. Route buyers by site constraint and asset type — choose hardware from what the asset actually needs, not from invented exclusive-Hub limitations.