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.

VeeaONE Platform™

One platform.
Every kind of site.

A hospital, a remote community and a construction site have very different requirements. VeeaONE gives each one the same foundation: a common runtime, consistent security model and centralized management across VeeaHubs and qualified edge systems. The applications and services deployed at each site determine what the platform does there.

A team reviewing dashboards and a VR headset together at a workshop table
The VeeaHub family of edge servers against a dark blue backdrop
  • Hospital
  • Manufacturing floor
  • Corporate campus
  • Branch office
  • Rural community
  • Government agency
  • Disaster recovery site
  • Construction site
  • School
  • Warehouse
  • Smart building
  • Multi-site enterprise
  • VeeaHub
  • VeeaONE Runtime
  • VeeaCloud
  • vMesh
  • vBus
  • Secure containers
  • Control Center
  • VeeaHub Manager
  • One console
  • One update path
  • One support team
  • Chain of trust
At a glance

Four capabilities. One platform.

  • Connect

    Bring wired, wireless and IoT connectivity into one platform, including Wi-Fi, Ethernet, Bluetooth, Zigbee, Matter, Thread, LoRaWAN and 4G/5G cellular.

  • Compute

    Run containerized applications wherever workloads need to operate—on VeeaHubs or qualified edge systems.

  • Secure

    Apply a consistent security model across devices, applications, sites and cloud management.

  • Manage

    Configure, update and monitor distributed sites through a common management plane, with local management available when needed.

The platform advantage

One platform across sites that have little in common

Organizations often accumulate separate networking, compute, security and IoT stacks for different types of sites. VeeaONE provides a common software foundation across them while allowing each location to use the hardware, connectivity and applications its workloads require.

A point solution per site type Bought for the site One networking vendor Bought for the network VeeaONE Platform™ One platform, any site
The same install serves a second use case No Partial
Add software capabilities when the deployed hardware has sufficient capacity No Partial
One console across unlike sites No Yes
Applications deploy through a common workflow across qualified targets No Partial
One platform management and support relationship across the estate No Yes
A remote site and a campus run the same software No Partial
Runs on hardware beyond the vendor's own No No
The same install

Three very different sites. One platform across them all.

Choose a site. Its users, applications, connectivity and hardware requirements may change. What remains consistent is the VeeaONE Runtime, security model and management experience.

Choose a site
Click a site

A hospital

  • SecureConnect™

Connect clinical, operational and building systems while applying consistent security policies and management across the organization.

What you get

  • Segmented network access
  • Protected device connectivity
  • Local application processing
  • Centralized policy and management

A remote town

  • AirLynx™

Combine available backhaul with wireless distribution to extend broadband and digital services across a community.

What you get

  • Flexible backhaul options
  • Wireless middle-mile distribution
  • Local content and digital services
  • Centralized network management

A construction site

  • MetaLynx™

Connect workers, cameras, sensors and equipment at a changing site, with local processing and centralized management.

What you get

  • Rapid site connectivity
  • Multi-protocol IoT integration
  • Local analytics and automation
  • Centralized deployment management

Across all three

  • SecureConnect™
  • AirLynx™
  • MetaLynx™

Each site runs the applications and connectivity appropriate to its needs while sharing a common software, security and management foundation.

What you get

  • Segmented network access
  • Protected device connectivity
  • Flexible backhaul options
  • Wireless middle-mile distribution
  • Local content and digital services
  • Multi-protocol IoT integration
  • Local analytics and automation
  • Local application processing
  • Centralized policy and management

The platform layer remains consistent.

On site Deployment hardware A VeeaHub or qualified edge system selected for the connectivity, compute, storage and environmental requirements of the site.
  • Wi-Fi
  • Ethernet
  • Bluetooth
  • Zigbee
  • Matter & Thread
  • LoRaWAN
  • 4G/5G WWAN
On each edge system VeeaONE Runtime A common execution environment for secure containerized applications, local services and communication between systems.
  • Secure containers
  • vMesh
  • vBus
  • Local resilience
Above all of them VeeaCloud Centralized configuration, deployment, updates and monitoring across the full estate, with local operation available when connectivity is interrupted.
  • Control Center
  • VeeaHub Manager
  • Software and application updates
  • Analytics

VeeaONE provides a consistent platform across sites, from local runtime and security to centralized deployment and management. When the existing system has sufficient compute, storage and connectivity, additional capabilities can be deployed as software without installing another dedicated appliance.

One runtime

One runtime. Multiple edge targets.

Edge applications often require separate packaging and validation for different hardware. VeeaONE Runtime provides a common execution and management layer across VeeaHubs and qualified edge systems.

Applications are containerized, validated for the capabilities of each target and deployed through the VeeaONE developer toolchain. This allows workloads to run where their compute, storage, connectivity and acceleration requirements are best met.

A containerized application The application or service being deployed, such as video analytics, AI inference or an automation workflow.
VeeaONE developer toolchain Package, validate and deploy applications across qualified targets.
VeeaONE Runtime The common execution and management layer across each supported target.
Native Veea hardware VeeaHubs Purpose-built Veea edge systems for connectivity, compute and local applications.
Qualified target Qualified x86 systems Supported Linux environments running on physical hardware or virtual machines.
Qualified target NVIDIA Jetson Qualified accelerator-backed systems for local AI inference and video analytics.
Qualified target Other qualified edge systems Systems approved for specialized compute, storage, connectivity or acceleration requirements.
Operated through VeeaONE
  • Target enrollment
  • Application deployment
  • Capability validation
  • Fleet visibility

Runtime capabilities and management features vary by qualified target and deployment configuration. See the VeeaONE developer documentation for supported targets and capabilities.

Getting there

From site requirements to a running deployment

  1. Define the site

    Identify the devices and systems already present, the workloads that will run locally, the connectivity available and what must continue during an uplink interruption. These requirements determine the hardware, applications and services needed.

  2. Deploy the edge systems

    Select and enroll VeeaHubs or qualified edge systems based on the requirements of the site. Where VeeaHubs are used, vMesh can connect them over wired or wireless links.

  3. Deploy the applications

    Install and manage containerized applications and services remotely through VeeaONE. When an existing system has sufficient resources, additional capabilities can be deployed without another hardware installation.

  4. Operate across sites

    Use VeeaCloud to configure, monitor and update distributed deployments. Applications designed for local operation can continue during a temporary loss of cloud connectivity.

A common runtime, hardware qualification process and management model reduce repeated integration work as sites and capabilities are added.

Build on it

Designed for developers and delivery partners

Extend VeeaONE with your own applications, integrate existing systems or use the platform to build and manage customer solutions.

DevelopersBring your own application

Build containerized applications, integrate with third-party systems and deploy across VeeaHubs and qualified edge targets.

Explore the developer platform

PartnersBuild and deliver customer solutions

Use VeeaONE to design, deploy and manage solutions for customers operating distributed sites.

  • Combine hardware, connectivity and applications for each site
  • Enroll targets and manage application deployments across fleets
  • Provide centralized and local management
  • Access partner enablement, environments and permissions through Veea

Become a partner

Before you ask

Questions to answer before deployment

How do I choose the right deployment hardware?

Start with the requirements of the site and its workloads: connectivity, compute, storage, acceleration, environmental conditions and what must continue during an uplink interruption. VeeaHubs are the native VeeaONE target, while qualified edge systems can support workloads with different hardware requirements.

Can I start with one solution and add another later?

Yes. Additional applications and services can be deployed as requirements evolve. If the existing edge systems have sufficient capacity and the required interfaces, the change may be completed remotely. New or upgraded hardware may be needed when requirements exceed the resources already available.

What keeps running when the internet goes down?

Applications designed to operate locally can continue during a temporary uplink interruption. On VeeaHubs, deployed containers and local mesh connectivity can continue operating, while remote management and cloud-dependent services may be unavailable. The site can synchronize with VeeaCloud after connectivity returns.

Does the platform only run on Veea hardware?

No. VeeaHubs are the native VeeaONE target, and VeeaONE Runtime also supports qualified x86 Linux systems, NVIDIA Jetson systems and other approved edge hardware. Runtime and management capabilities vary by target and deployment configuration.

How do I build my own application on it?

Use the VeeaONE developer tools to package, validate and deploy containerized applications across supported targets. Workloads can include application services, video analytics, local AI inference and operational automation. Documentation is available at docs.veeaone.com, while production access and third-party target enablement may require an approved Veea account and applicable agreement.

Where can I see the platform working today?

Explore Veea case studies covering deployed connectivity, edge computing and building-management applications. Two examples are Enhancing Building Asset Management and Enabling Common Area Wi-Fi as a Commercial Building Amenity.

What could your sites share?

Tell us where your sites are, what each one needs to run and what must stay local. We'll help you map a VeeaONE deployment using the hardware, connectivity and services appropriate to each location.