Get started with Veea

Tell us about your sites and what you want to run on them, and a Veea team member will follow up.

Prefer the full page? Go to Contact.

Smart IoT Connectivity

IoT without
the chaos.

Zigbee, LoRaWAN, Wi-Fi, Bluetooth, Modbus, BACnet — one VeeaHub speaks all of them, acts on the data where it is made, and gives you a single interface instead of a shelf of vendor gateways.

Talk to an engineer See why it gets messy
A night-time highway interchange overlaid with connected-vehicle data readouts
The VeeaHub family — two compact units, a flat indoor unit and an antenna-equipped outdoor unit — against a dark teal backdrop of app icons and light streaks above a city skyline
  • Zigbee
  • LoRaWAN
  • Wi-Fi
  • Bluetooth LE
  • Z-Wave
  • Thread
  • Modbus
  • BACnet
  • Ethernet
  • 5G
  • vMesh
  • Matter
  • Microsoft Azure
  • AWS IoT
  • Google Cloud
  • Siemens MindSphere
  • Niagara
  • Savant
  • MQTT
  • HTTPS
  • Veea APIs
  • Rules engine
  • Data brokers
  • AI & ML analytics
At a glance

One hub where a rack of gateways used to be

  • Every protocol that matters

    Zigbee, LoRaWAN, Wi-Fi, Bluetooth LE, Z-Wave, Modbus, BACnet and Ethernet — one device, one software stack.

  • Decisions made on site

    Rules, containers and AI models run on the hub, so a sensor reading becomes an action without a cloud round-trip.

  • Isolated by Trust Domains

    vTBA keeps devices, apps and users separated. Nothing leaves the network unless you say it can.

  • Whatever cloud you already run

    Azure, AWS, Google Cloud, MindSphere, Niagara or Savant — one control layer across all of them.

The problem

Nothing here is broken. It just does not fit together.

Your thermostats speak Zigbee, your locks speak Bluetooth, your meters speak Modbus. Each one arrives with its own gateway, its own firmware cycle, its own cloud and its own console — so before anyone sees a single useful reading, someone has to make eleven things agree.

BeforeSix protocols, four gateways, three clouds
  • Lighting
  • HVAC
  • Access
  • Occupancy
  • Cameras
  • Meters
  • Gateway
  • Gateway
  • Gateway
  • Gateway
  • Vendor cloud
  • Vendor cloud
  • Vendor cloud
AfterThe same six devices, one stack
  • Lighting
  • HVAC
  • Access
  • Occupancy
  • Cameras
  • Meters
  • VeeaHub
  • Your apps & your cloud
Why it gets messy

No radio wins. That is the whole problem.

Range, speed and battery life trade against each other, and physics does not negotiate. LoRaWAN reaches a hundred kilometers because it barely sends anything; Wi-Fi moves a gigabit because it barely leaves the room. Plot Veea's own published figures and the radios tile the space almost without overlapping — which means a real building needs several of them, and that is not a procurement mistake.

Throughput
10 kbps 100 kbps 1 Mbps 10 Mbps 100 Mbps 1 Gbps 10 m 100 m 1 km 10 km 100 km Wi-Fi · 15 – 100 m · 54 Mbps – 1.3 Gbps Bluetooth LE · 10 – 100 m · 125 kbps – 2 Mbps Zigbee / Thread · 30 – 100 m · 20 – 250 kbps Z-Wave · 30 – 50 m · 10 – 100 kbps LoRaWAN · 2 – 100 km · 10 – 50 kbps Wi-Fi Bluetooth LE Zigbee / Thread Z-Wave LoRaWAN
Range
Both axes logarithmic. Figures are Veea's published protocol data, plotted as the span each one covers rather than a single point — the gap between 100 m and 2 km is real, and LoRaWAN is the only thing that crosses it.
Bluetooth LE Rooms & wearables Wi-Fi Bandwidth indoors Z-Wave Home automation Zigbee / Thread Building control LoRaWAN Site-wide sensing
Range 10 – 100 m 15 – 100 m 30 – 50 m (weakest) 30 – 100 m 2 – 100 km (strongest)
Throughput 125 kbps – 2 Mbps 54 Mbps – 1.3 Gbps (strongest) 10 – 100 kbps 20 – 250 kbps 10 – 50 kbps (weakest)
Power usage Low Medium (weakest) Low Low Low
Ongoing cost One-time One-time One-time One-time One-time
Module cost Under $5 (strongest) Under $10 Under $10 $8 – 15 (weakest) $3 – 15
Topology P2P, star, mesh, broadcast (strongest) Star, mesh Mesh Mesh Star

Every one of these is the right answer somewhere. VeeaHub carries them all so the choice stays a design decision rather than a procurement commitment.

The gateway

What the one box is actually doing

SpeaksDown to the devices

The VeeaHub IoT Gateway application is the radio layer and the translation layer at once, so a new device type is a configuration rather than a purchase.

  • LoRa, Wi-Fi, Bluetooth LE, Zigbee, Z-Wave, Modbus, BACnet and Ethernet
  • Two-way: asynchronous telemetry in, commands and control back out
  • A hardware abstraction layer that discovers and manages devices for you
  • vMesh between hubs, so coverage extends by adding a hub, not a trench

ServesUp to your applications

Everything above the radios is yours: run it locally as microservices on the hub, hand it to your cloud, or both.

  • MQTT and HTTPS out — the two protocols your platform already expects
  • Veea APIs, data brokers, a rules engine and AI/ML analytics on the hub
  • Azure, AWS, Google Cloud, Siemens MindSphere, Niagara and Savant
  • vTBA and Trust Domains isolating devices, apps and users from each other
Deployment

What adding a device actually involves

  1. The device announces itself

    On whichever radio it was built for. No vendor gateway is added, because the hub already speaks it.

  2. The hub adopts it

    The hardware abstraction layer identifies it and places it in a Trust Domain with the things it is allowed to talk to.

  3. Rules run locally

    Thresholds, schedules, containers and models execute on the hub — the reading becomes an action on site.

  4. Your platform gets what it needs

    Over MQTT or HTTPS, into the cloud you already run — as much or as little as you choose to send.

Adding the hundredth device is the same four steps as the first, on the same console, whoever made it.

Advantages

What changes when one box speaks everything

  • What you get Hardware clutter and vendor lock-in both stop being design constraints.
    The old way A proprietary gateway per protocol, each with its own firmware cycle.
    With VeeaHub One device and one software stack covering every common radio and bus.
  • What you get Reaction in real time, and a backhaul bill that stops tracking sensor count.
    The old way Every reading travels to a cloud before anything decides what it means.
    With VeeaHub Rules, containers and models execute on the hub, beside the device.
  • What you get One security model to reason about instead of one per supplier.
    The old way Security is whatever each vendor happened to implement.
    With VeeaHub vTBA and Trust Domains isolate devices, applications and users centrally.
  • What you get Troubleshooting becomes a search rather than an investigation.
    The old way Separate consoles per vendor, per cloud and per site.
    With VeeaHub One interface across vendors, clouds and physical locations.
  • What you get The hundredth endpoint costs what the tenth did.
    The old way Scaling up means another integration project and another team.
    With VeeaHub Modular hubs join by vMesh; legacy and new devices coexist.
In deployment

Where a single stack pays for itself

  • Zigbee · BACnet · BLE Lighting, HVAC and access on one console Three subsystems that historically arrived as three vendors, three gateways and three dashboards, running against one hub per floor.
  • Modbus · Ethernet · Wi-Fi Machine data without a rip-and-replace Legacy controllers keep their wiring and their protocol; the hub reads them and puts the result on the same bus as everything modern.
  • LoRaWAN · 5G · vMesh Sensing past where the cabling stops Car parks, water, tanks and remote plant, on the one radio built to cross kilometers — gathered by the same hubs running the building.
  • BLE · Wi-Fi · Modbus Shop floor, stockroom and cold chain Refrigeration, footfall and stock sensing on one stack per store, reporting to the same platform across every site in the estate.
  • BLE · LoRaWAN · 5G Yards and docks that report themselves Asset tags, dock status and environmental sensing across a site far bigger than any one indoor radio can cover.
  • BLE · Zigbee · Wi-Fi Equipment and environment, continuously Roaming equipment, room conditions and access control — where the readings should be acted on locally and stay inside the building.
  • LoRaWAN · Modbus Sites nobody visits twice a week Pumping stations, substations and tunnels: long-range sensing where the alternative is sending someone to look.
  • Z-Wave · Thread · Wi-Fi Shared services across many units Metering, access and common-area plant, on the protocols residential devices already ship with.
  • LoRaWAN · 5G · vMesh Street furniture that answers back Parks, transit stops and civic infrastructure, instrumented without a cabling program for each one.
Before you ask

The questions that decide it

Do I have to replace the devices I already have?

No — that is most of the point. Alongside the wireless protocols the hub speaks Modbus, BACnet and Ethernet, so existing controllers keep their wiring, their protocol and their commissioning. The hub reads them and puts the result on the same bus as everything modern, which means a building can be instrumented without a capital project to rip anything out first.

What happens to the gateways I already run?

The VeeaHub is the gateway. Where you currently run one vendor box per protocol — each with its own firmware cycle, its own console and its own cloud account — those collapse into one device and one software stack. The saving is not mainly the hardware; it is the integration work and the number of systems somebody has to keep current.

Where does my data actually go?

To the hub first. Rules, containers and models execute there, so a reading becomes an action on site without a cloud round-trip. What leaves after that is your decision — over MQTT or HTTPS, to the platform you already run. Isolation between devices, applications and users is enforced by vTBA and Trust Domains, so nothing crosses a boundary you have not opened.

Which clouds and platforms does it work with?

Microsoft Azure, AWS IoT, Google Cloud, Siemens MindSphere, Niagara and Savant, plus anything that accepts MQTT or HTTPS. The hub is designed for the situation most estates are actually in — several vendors and more than one cloud — rather than assuming a single platform decision was made once and held.

How does coverage extend beyond one hub?

Hubs link to each other with vMesh, sharing load and routing traffic between themselves, so coverage grows by adding a hub rather than by trenching a cable back to a comms room. vMesh and vBus are the two core technologies underneath that.

Which VeeaHub do I need?

That depends on where it is going and what it has to reach — indoor, outdoor and rack-mounted models differ in radios, environmental rating and compute. The VeeaHub family covers the range; sizing a deployment is a conversation about the site rather than a number we can put on this page.

Keep looking

Explore more solutions

How many gateways are in your building?

Tell us what is already installed and what it speaks. We will tell you what one hub replaces.

Contact us See more solutions