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 Construction

The alert arrives
before the machine does.

Cameras, AI models and the policy engine all run on the hubs that give your site its network — so a hard-hat breach or a person in a plant path becomes an alarm on site, in under 50 milliseconds, whether or not the site has working internet.

Book a smart-site demo See how it decides
A jobsite viewed through the system: workers and plant on an active site, with live detection overlays drawn around them.
The Veea Vision console showing detections on a live site view.
  • PPE compliance
  • Hazard zones
  • Plant proximity
  • After-hours motion
  • Fire, smoke and gas
  • Restricted entry
  • Dwell times
  • Geofences
  • Collision avoidance
  • RTSP / ONVIF cameras
  • RTLS tags
  • LoRaWAN
  • ChirpStack
  • BLE and UWB
  • Zero-touch onboarding
  • vMesh
  • PoE installs
  • Air-gapped operation
At a glance

Everything that decides, decides on site

  • Under 50 ms, detection to alert

    The camera, the model and the policy engine are on the same node, so nothing waits on a round-trip to decide whether that was a person or a pallet.

  • Runs air-gapped

    Video, telemetry and RTLS streams are processed and stored inside the mesh. Optional cloud backhaul is for cross-site reporting, not for the decision.

  • One install covers people, plant and perimeter

    Computer vision, RTLS and IoT sensors land in one timeline instead of three consoles that each know part of the story.

  • Live in under an hour

    The pilot kit arrives with hubs and the Smart Construction applications already provisioned for safety, compliance and asset use cases.

Local versus cloud

A round-trip is a decision you did not make in time

Connectivity on a jobsite is intermittent by nature: the uplink competes with plant, weather and a site that changes shape every week. A cloud-first stack answers a safety event at the speed of that uplink. An edge-native one answers at the speed of the node the camera is already plugged into.

On site, with MetaLynx™ Veea Cloud-based Round-trip per event
Alert latency Sub-50 ms (strongest) Seconds to minutes (weakest)
Keeps working when the uplink drops Yes (strongest) No (weakest)
Video and telemetry stay on site Yes (strongest) No (weakest)
Backhaul cost Minimal (strongest) High — video and telemetry (weakest)
Model updates Mesh OTA, no downtime (strongest) Central, adds delay (weakest)
Time to live Under an hour (strongest) Days to weeks (weakest)

Optional cloud backhaul is still there for cross-site reporting, orchestration and long-term retention. What changes is that nothing on the site waits for it.

How it decides

The loop closes inside the hoarding

One camera, one node, one zone. The frame is analyzed on the hub it is plugged into, the policy for that zone and that shift is applied there, and the alarm reaches the people in it — three hops that all sit inside the fence.

  • Camera sees a person in the plant path
  • The model and the zone policy run on this hub
  • The zone is alerted — siren, radio, dashboard, operator
  • Cloud is optional, and never in the loop

Under 50 ms

Cameras, RTLS readers and sensors join the same mesh. The dashed line leaving the site is the only path to the cloud, and no alert travels it.
Sensing

The site reports itself

Temperature, humidity, smoke, 3D scanning, ultrasonic and pressure all arrive over whichever radio the device was built for, and land in the same local system as the video. Analysis, storage and the rules that act on them stay on site.

What reports

  • Temperature
  • Humidity
  • Smoke
  • 3D scanning
  • Ultrasonic
  • Pressure
  • RTLS tags
  • Cameras

How it arrives

  • Bluetooth
  • Wi-Fi
  • LoRa
  • ZigBee
  • Z-Wave
  • Ethernet / PoE
Over the program

Three phases, one install

A site is rebuilt around you every few weeks — the excavation becomes a frame, the frame becomes rooms, and the hazards move with them. The hubs move too, and the policies and models follow them over the mesh.

Phase one

Substructure

Open ground, deep excavation, plant everywhere and almost no structure to mount to. Coverage follows the dig.

Phase two

Structure

A frame goes up and the site becomes vertical. Floors, edges and lifting zones are the hazards now.

Phase three

Fit-out

Enclosed, crowded with subcontractors, and full of tools and materials worth tracking. The same hubs, indoors.

The same hubs, moved — not re-bought. Policies and AI models replicate over the mesh, so a hub that moves floors arrives already knowing the rules.

Getting started

Powered on to alerting, inside an hour

  1. The kit arrives provisioned

    VeeaHub edge nodes with the MetaLynx Smart Construction applications already configured for safety, compliance and asset use cases.

  2. Hubs find each other

    The mesh is self-forming, so the second hub joins the first without a survey, a controller or a cable run between them.

  3. Cameras and tags onboard themselves

    Zero-touch onboarding for RTSP/ONVIF cameras, IoT sensors and RTLS tags — each one lands in the policy that governs its zone.

  4. Dashboards and alerts go live

    Live views, event-driven alerts and the unified policy engine, running on the site rather than on a subscription to somewhere else.

A pilot kit is a controlled, repeatable way to prove the platform on one site before it scales across a portfolio.

Advantages

What changes when the site watches itself

  • What you get Supervisors step in while it still matters, not after the shift report.
    Cloud-first An event is uploaded, queued, analyzed somewhere else and answered when the link allows.
    On site The frame is analyzed on the node it arrived at, and the zone is alerted from there.
  • What you get Less exposure, and a far shorter conversation about privacy and data sovereignty.
    Cloud-first Workforce video and telemetry leave the site to be useful.
    On site Analytics, video and telemetry stay inside the mesh, encrypted between hubs.
  • What you get Who was on site, what was running and where the risk built up — in one place.
    Cloud-first Safety, access and asset tracking each have their own console and their own version of the day.
    On site Computer vision, RTLS and sensor events land in one timeline with the zone and shift attached.
  • What you get Coverage follows the program instead of lagging a phase behind it.
    Cloud-first Extending coverage means a new survey, new cabling and a change request.
    On site Another hub joins the mesh and inherits the policies and models already running.
Security

Built into the platform, not bolted to the cloud

Stays putData does not leave to be useful

Video, telemetry and RTLS streams are processed and stored within the VeeaHub mesh, so sensitive workforce and operational data never has to cross the site boundary.

ContainedOne compromised camera stays one camera

Each hub enforces micro-segmented policies that isolate connected devices and applications, so a compromised endpoint cannot reach the rest of the site.

WatchedEncrypted mesh, secure onboarding

Hub-to-hub communication is encrypted end to end, cameras, IoT devices and tags onboard securely, and AI-driven intrusion detection runs at the edge.

See it running

The console the site actually watches

The Veea Vision console: a live site view with detections listed alongside it.
Detections, zones and the people and plant they involve — on one timeline, served from the site.
Specifications

What is in the deployment

Platform and nodes
Platform VeeaONE Platform™ with the MetaLynx™ Smart Construction application suite
Nodes VeeaHub™ models supporting CPU plus GPU/TPU edge inference
Mesh Powered by vMesh: self-forming, self-healing, with zero-touch device onboarding
Sensing and AI
Video RTSP/ONVIF camera support; local AI analytics; multiple concurrent streams
AI models PPE compliance, restricted zones, collision avoidance, fire and gas detection, anomalies. OTA updates without downtime
RTLS BLE/UWB options; real-time geofencing, utilization metrics, asset intelligence
IoT / IIoT Built-in LoRaWAN concentrator with ChirpStack; multi-protocol IoT device support
Security
Security Local-first processing; full encryption for data at rest and in motion; AI-driven cybersecurity and micro-segmentation
Operations
Management Local management interface; optional VeeaCloud™ for orchestration and reporting
Connectivity Ethernet, Wi-Fi, LTE/5G (optional) or satellite (optional); PoE-ready deployment
Latency target Sub-50 ms for event detection to actionable alert under typical conditions; sub-250 ms over satellite

Specifications subject to change without notice. Country-specific regulatory information is available on request.

Questions

What site teams ask first

What happens when the site loses its uplink?

Nothing that matters to safety. Detection, the policy engine and alerting all run on the hubs, so events are still analyzed and the zone is still alerted. Cloud backhaul, where you use it, catches up afterwards.

Does the video have to leave the site?

No. Video, telemetry and RTLS streams are processed and stored inside the mesh, and the system can run air-gapped. Optional cloud is for cross-site reporting and long-term retention, and it is your choice what is sent.

Can it run the site's other systems too?

Yes — Honeywell Niagara runs as a containerized app on the same hub, so HVAC, lighting, pumps, power and access sit beside safety and asset intelligence on one local platform. Portable Niagara covers that in full.

How does it grow as the project does?

Start with one hub and add hubs and cameras as the site expands. Policies and AI models replicate across the mesh, so a new node arrives already knowing the rules rather than needing to be configured into them.

What does it plug into?

Dashboards, SMS, email and webhooks reach the systems you already run, and events and trends export to BI tools over REST and webhooks. The platform underneath is MetaLynx™.

Which alerts can it raise?

PPE compliance including hard hats, vests and eyewear; entry into hazard or restricted zones; person and vehicle proximity; fire, smoke and gas; after-hours motion and perimeter anomalies; and dwell time or geofence rules per zone, per shift and per role.

Explore more

Other solutions on the same platform

Put it on one site first

The pilot kit is a full deployment in under an hour — hubs, cameras and the policy engine already provisioned. Prove it on the site giving you the most trouble, then let it follow the program.

Book a smart-site demo See the platform